|
Post by eerbaugh on Dec 13, 2020 23:32:22 GMT -5
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Dec 14, 2020 10:16:42 GMT -5
Your google drive is not set to share. If you are using NOAA wildfire lidar data, it tells you what the EPSG code is in the metadata link. www.fisheries.noaa.gov/inport/item/58709Scroll down to the Reference System 1 section
|
|
|
Post by eerbaugh on Dec 14, 2020 10:44:03 GMT -5
Your google drive is not set to share. If you are using NOAA wildfire lidar data, it tells you what the EPSG code is in the metadata link. www.fisheries.noaa.gov/inport/item/58709Scroll down to the Reference System 1 section Oops. Forgot to click share link when I copied the link. Lol I found the EPSG code in your link, but now when I try it I get the error: "Could not load USGS_LPC_CA_SoCal_Wildfires_B2_2018_w1972n1545_LAS_2019.laz Please report this issue." For all my files. And this: "No valid lidar files found, no action taken"
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Dec 14, 2020 11:57:47 GMT -5
Yeah... it looks like the EPSG code posted in their metadata file is not correct for pulling Openstreetmap nodes. Kern county is zone 5 so maybe try some of those. The lidar data is in meters.
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Dec 14, 2020 12:34:47 GMT -5
Oddly enough the EPSG code is 6350, which also works for the recent lidar data in Wisconsin. This info is available in the header of the las file.
p.s. I looked at your OSM and there were a few problems. You had holes with the same hole number and elements tagged improperly. I have fixed these, but there are still some alignment issues on import. Since I am already this far into messing with this course data, I figure I may as well adjust all the OSM splines. I'd be happy to build and publish the course, but it will be for pga2k21 only.
|
|
|
Post by eerbaugh on Dec 14, 2020 15:25:22 GMT -5
Oddly enough the EPSG code is 6350, which also works for the recent lidar data in Wisconsin. This info is available in the header of the las file. p.s. I looked at your OSM and there were a few problems. You had holes with the same hole number and elements tagged improperly. I have fixed these, but there are still some alignment issues on import. Since I am already this far into messing with this course data, I figure I may as well adjust all the OSM splines. I'd be happy to build and publish the course, but it will be for pga2k21 only. Oh good to know. This is my first attempt at a build. This is the course I play 2x3 times a week, so I plan on making it as true to the actual course as necessary. I'm guessing the hole number issue is why some holes weren't showing up. Thanks for the help. I'll take a look at the edits and try to learn from them. Course building is addictive. lol.
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Dec 14, 2020 15:54:48 GMT -5
Most of the OSM work needs to be redone. I am matching everything to how it looks in Google Maps and how it aligns to the lidar data in the game. I am on hole 4 or 5 right now with complete re-splining of the greens, bunkers, tee boxes (need to tag these as fairways) and adjustments to the rough, fairways and cartpaths (tag these as walking paths). I can go into detail as to why the splines need to be done the way I am doing them.
You to get splines.json and the 0.3.5 version of chadtools as well.
|
|
|
Post by eerbaugh on Dec 14, 2020 15:57:54 GMT -5
Most of the OSM work needs to be redone. I am matching everything to how it looks in Google Maps and how it aligns to the lidar data in the game. I am on hole 4 or 5 right now with complete re-splining of the greens, bunkers, tee boxes (need to tag these as fairways) and adjustments to the rough, fairways and cartpaths (tag these as walking paths). I can go into detail as to why the splines need to be done the way I am doing them. Ya, I found another course I was looking at, that was done by someone else in OSM had most of the fairways as closed lines, That explains why the fairways I traced were showing up, but the ones someone else did, were not. Good notes on Tee boxes and walking paths.
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Dec 14, 2020 16:04:05 GMT -5
Most of the OSM work needs to be redone. I am matching everything to how it looks in Google Maps and how it aligns to the lidar data in the game. I am on hole 4 or 5 right now with complete re-splining of the greens, bunkers, tee boxes (need to tag these as fairways) and adjustments to the rough, fairways and cartpaths (tag these as walking paths). I can go into detail as to why the splines need to be done the way I am doing them. Ya, I found another course I was looking at, that was done by someone else in OSM had most of the fairways as closed lines, That explains why the fairways I traced were showing up, but the ones someone else did, were not. Good notes on Tee boxes and walking paths. My first couple builds were a learning experience... You need to be familiar with how wide each type of spline renders in the game. This is why things need to be tagged a certain way and why alignment is important. On fairways, you need to draw then inside of where they are since they are 3 meters wider than the outside edge by default and then they attempt to put rough outside of that. Also, fairways need to have more nodes than you are placing. Look at the fairways I have adjusted to get an idea. Oh, and don't place nodes from different types of tags on top of each other and join them unless it is a green to fairway transition. It makes it difficult to work with in OSM and in the editor.
|
|
|
Post by eerbaugh on Dec 14, 2020 16:32:36 GMT -5
Ya, I found another course I was looking at, that was done by someone else in OSM had most of the fairways as closed lines, That explains why the fairways I traced were showing up, but the ones someone else did, were not. Good notes on Tee boxes and walking paths. My first couple builds were a learning experience... You need to be familiar with how wide each type of spline renders in the game. This is why things need to be tagged a certain way and why alignment is important. On fairways, you need to draw then inside of where they are since they are 3 meters wider than the outside edge by default and then they attempt to put rough outside of that. Also, fairways need to have more nodes than you are placing. Look at the fairways I have adjusted to get an idea. Oh, and don't place nodes from different types of tags on top of each other and join them unless it is a green to fairway transition. It makes it difficult to work with in OSM and in the editor. Ya, I tried to draw inside the fringe of the Fairway, when I could tell where the fringe was. Problem is at Edwards, depending on the time of the year, it can be impossible to tell the fairway from the fringe, from the rough. lol Like right now the course is in terrible shape because they don't overseed in the fall, and once the bermuda goes dormant, the fairways are basically like hitting off a parking lot.
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Dec 14, 2020 16:40:37 GMT -5
Yeah, it looks like most of the fairways are drawn about 5 meters too wide. The thing is, due to how this course is constructed in the desert, you will not be able to properly render fairway fringe or true light rough. I use multiple sat imagery sources to determine what is what, plus after you have done a few courses you start to innately just "know" what makes sense when you can't completely see it.
And in the background settings of OSM you can adjust contrast, brightness and such... can make a huge difference.
|
|
|
Post by eerbaugh on Dec 14, 2020 20:39:46 GMT -5
Yeah, it looks like most of the fairways are drawn about 5 meters too wide. The thing is, due to how this course is constructed in the desert, you will not be able to properly render fairway fringe or true light rough. I use multiple sat imagery sources to determine what is what, plus after you have done a few courses you start to innately just "know" what makes sense when you can't completely see it. And in the background settings of OSM you can adjust contrast, brightness and such... can make a huge difference. I just imported it with the EPSG and and those edits and with exception of the lack of scrub brush and wrong trees it looks exactly like the course. What is your reasoning for using fairways for tee boxes? Is it a person preference for appearance or does it have implications for play? Just curious
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Dec 15, 2020 7:44:43 GMT -5
Yeah, it looks like most of the fairways are drawn about 5 meters too wide. The thing is, due to how this course is constructed in the desert, you will not be able to properly render fairway fringe or true light rough. I use multiple sat imagery sources to determine what is what, plus after you have done a few courses you start to innately just "know" what makes sense when you can't completely see it. And in the background settings of OSM you can adjust contrast, brightness and such... can make a huge difference. I just imported it with the EPSG and and those edits and with exception of the lack of scrub brush and wrong trees it looks exactly like the course. What is your reasoning for using fairways for tee boxes? Is it a person preference for appearance or does it have implications for play? Just curious Tee Boxes in OSM come in as putting greens and this course doesn't use the putting green surface for the tee boxes. There are some technical reasons as well due to how the splines work. In a previous post I suggest that you use the 0.3.5 version of chadtools, this is so you can finetune the lidar populated trees. In my version of this course I chose to omit all palm trees so I can place them manually in the correct positions. There is still a huge amount of design work that needs to be done on this course before it is playable and ready for publish. Regarding the scrub brush, just use the autogenerated plants and grass set to maximum and then clear out what you don't want. Some interesting notes about this course. There isn't any way to do the concrete irrigation ditches due to how the game handles water surface interaction. Looking back over at the first tee...
|
|
|
Post by eerbaugh on Dec 15, 2020 13:50:24 GMT -5
HOLY sh%$! That looks incredible!
Oh ya. I need to update I'm using 0.3.2. And I found it annoying that there were plam trees where regular trees should be and a pain in the ass to manually change them
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Dec 15, 2020 15:18:00 GMT -5
HOLY sh%$! That looks incredible! Oh ya. I need to update I'm using 0.3.2. And I found it annoying that there were plam trees where regular trees should be and a pain in the ass to manually change them Update Edit: My version of the course is published as: Muroc Lake AFB CA (L) and I'd be curious what your thoughts are. Obviously I have never played this course in real life, nor knew anything about it until a couple days ago. I am also looking forward to playing your finished version and seeing how similar and different they are. This was a fun course to build and please let me know if I can help you out in any way. Actually, you need to use both 0.3.2 and 0.3.5 versions of chadtools. I made a post elsewhere about my workflow explaining why. The whole lidar course designer process is one pain in the ass after the other. Copy and Pasted from other thread about bypassing tgc2019 to convert course file to pga2k21... I only use 2k21 for the actual course editing since the designer now works so much better with mouse/keyboard than the tgc2019 version ever did. Anyway, the issue isn't your script. It is the fact that chadtools doesn't play nice with the 2k21 format. And after spending a few hundred hours of building dozens of courses I feel I have finally landed on a workflow that doesn't waste much time or effort. 1. Decide on course 2. Grab lidar data and process 1 tile to determine EPSG if not already known 3. OSM everything 4. Set splines.json to match course details (I use matching widths on my fairways and greens and a little OSM/designer trick to get perfect transitions on every green if the course calls for it) 5. Run chadtools 0.3.2 to build complete heightmap and do initial OSM build 6. Check course in tgc2019 7. Make any changes necessary in OSM and begin to finetune coordinate adjustments 8. Rinse and Repeat OSM alignment and re-running chadtools 0.3.2 until everything is 100% accurate 9. Run chadtools 0.3.5 to determine lidar tree mixture (btw, using OSM trees is not time effective since tree height is not properly accounted for during import) 10. Rinse and repeat running 0.3.5 until tree mixture and height matches as close as possible (keep OSM import turned off since this version causes issues with repeated OSM queries) 11. Finally save course file in tgc2019 and open in 2k21 to begin the actual course design work At this point steps 1 through 11 take about 30 minutes to 2 hours (not including the OSM spline tracing work as this usually takes anywhere from 2 to 8 hours or more based on course details) depending on how many x/y coordinate iterations are needed. 12. Smooth all cart paths and fairways. The design work in 2k21 varies wildly based on the availability and quality of source reference material, but you need to determine the point of diminishing returns pretty early on in the design process. Find a few "landmark" spots on the course and detail those out, do NOT use the multi-placement tool until in the final steps so you can keep your items levels low and hopefully the design tool response times stay reasonable. 13. Set your time of day so you can see deep shadows and adjust spline points in bunkers, fairways and greens that are not adhering to obvious topography slopes and other elevation changes. 14. Set green speed to 7-8 (about 162) and set 4 legal and useable pins. You may not always be able to get 4 pins per green to be in a legal position on your first pass. Personally, I try to never mess with the green contours, but sometimes it is necessary to massage a pesky green to behave properly, plus some lidar data can produce more aggressive than in reality slopes when the surface is near drastic elevation transitions. 15. Place at least 3 tee sets and match them (game yardage is not accurate to real life yardage and even more so on par 5 holes) to the course scorecard. 16. Use an oval soft edge blue shape to flatten all tee boxes 17. Playtest each tee set and pin position fixing any issues you come across 18. If you used any auto-generated grass/plants, remove these elements from where they shouldn't be. 19. Playtest from back tee set with highest wind setting 20. Finetune weather and time of day 21. Take photos 22. Final playtest and adjustments to all surface firmness and speeds 23. Submit course to TGCTours 24. Go to step 1
|
|