MAJORHIGH
Weekend Golfer
PC: MAJORHIGH
Posts: 146
TGCT Name: Chris Lane
Tour: Challenge Circuit
|
Post by MAJORHIGH on Aug 26, 2019 15:56:21 GMT -5
Chad, couple of questions:
1. Is there a way to move masking into the process phase directly after LAZ files are opened. If we're already "box-selecting" the course area to narrow down the data needed to be processed, couldn't we also be able to mask the course at this phase as well.
2. Can an option be added to turn off the object and tree height detection? When processing the open LAZ data with the corresponding OSM waypoints, I usually only want fairways, greens, water, bunkers, and tee boxes. However, 90% of this final step is searching for data points that i'm not needing.
Thanks, Chris
|
|
|
Post by chadgolf on Aug 31, 2019 16:40:33 GMT -5
1.) I didn't do this because implementing Paint into my own program is too much work, so we do the quick and easy box. 2.) I forced this because it's the "Apple" like approach where everyone gets the same experience. It's complicated enough to run so the fewer options on that page the fewer mistakes someone could make. The other main motivation that they both share is that there is no way to make the lidar import process be the part of the program that takes the most time. Even for basic courses, this part could run 3 minutes. There's not much difference between 3 minutes and 6 minutes - people will go get a cup of coffee, hit a few putts, watch a TV show. Some courses take even longer. To save everyone's lives, the program does things in a quick -> slow -> quick order. It's quick(er) to open lidar, check the EPSG, and draw the box. This makes sure the data is what you want and you get a fast visual preview of it. Then it's slow to process every lidar point. Since it's so slow, we might as well only do it once. We also do the trees and some other bookkeeping that adds maybe 30% to the total processing time. The reward for this is that you should never have to touch the raw lidar files or use this tab again for the course. ------ Now is the fast part. Since we did all of the heavy lidar processing and stored it in a way that you can change your mind on almost anything, you can rerun the Import Heightmap and OSM step as much as you want. Want to keep changing the mask? Just edit it in paint and run Import Heightmap. I even make copies of the original mask, but you can paint in red, white, or blue. Are you in the process of editing OSM and you want to see it in game? No problem, just import, export and check in TGC. Need to fine tune the OSM alignment? Same thing, just change the numbers on Import Heightmap and rerun. Want to change your mind on the trees? Add them, try different settings, or don't import them at all now. If they were optional in step 1, then you'd have to rerun the full program and you'd have to redo the mask, etc. -------- If you're able to edit the program, you could comment out the tree detection section for your own use: github.com/chadrockey/TGC-Designer-Tools/blob/master/lidar_map_api.py#L426
|
|