|
Post by bpcollier on Oct 20, 2023 16:49:44 GMT -5
Hello! I have been using Chad's tools for several years, but it has been well over a year since I have started from scratch. I am having an issue where the lidar imports at the wrong scale and it comes in very small. After pulling my hair out for a while trying different lidar files, EPSG's, and even forcing the lidar unit, I could not get anything to work. Then I decided to try and go back to something I imported years ago and I know worked, and ran into the same issue. I have tried it using the latest release 3.3 and other releases as well, and still the same issue. Any help would be appreciated.
As an aside, I would settle for the Make Flat Course from OSM File to work, but I get some errors. I have never used this feature before, so I'm not sure if I am doing it right. Here are the errors:
Exception in Tkinter callback
Traceback (most recent call last):
File "tkinter\__init__.py", line 1705, in __call__
File "tgc_gui.py", line 624, in importOSMFile
File "tgc_image_terrain.py", line 344, in generate_flat_course
File "OSMTGC.py", line 535, in addOSMFromXML
UnboundLocalError: local variable 'latmin' referenced before assignment
Thanks!!
|
|
|
Post by BaconJunkie1 on Oct 23, 2023 17:04:46 GMT -5
I'm stumped as to what it could for sure ... I believe that I read that if you change the "Map Scale" setting from 2.0 on the Process LiDAR page in Chad's it will adjust the size. Make sure it is still set to 2.0 and holler back. If we need to we can get on TGC's Discord, you share your screen and let me watch what you are doing.
|
|
|
Post by bpcollier on Oct 24, 2023 21:44:26 GMT -5
Thanks for the suggestion. I double-checked Map Scale and it is still set to 2.0. That said, I think I found the problem, but someone with a bigger brain than mine can find the programming solution. The easy solution is below.
When processing the lidar and you get to the point where you draw the red box around the import area, I found that if I don't draw the box because I need the whole area, it imports at the wrong scale. If I draw a box as the instructions tell you to, it imports properly. It seems silly, but I just did it twice to make sure. In the meantime, I will process more lidar just so I can draw the box around what I need and it imports at the proper scale.
|
|
|
Post by BaconJunkie1 on Oct 25, 2023 19:39:51 GMT -5
Thanks for the suggestion. I double-checked Map Scale and it is still set to 2.0. That said, I think I found the problem, but someone with a bigger brain than mine can find the programming solution. The easy solution is below. When processing the lidar and you get to the point where you draw the red box around the import area, I found that if I don't draw the box because I need the whole area, it imports at the wrong scale. If I draw a box as the instructions tell you to, it imports properly. It seems silly, but I just did it twice to make sure. In the meantime, I will process more lidar just so I can draw the box around what I need and it imports at the proper scale. I'll buy that, thank you for helping the community by coming back to post what you found. [high five]
|
|