New error for Lidar work

[sandsaver01]

I was just playing around trying to make a course file for a Scottish course near Edinburgh. Somebody had already don some of the OSM work, so I located the appropriate Lidar and ran the tool. I had to force the EPSG because it said "prj2epsg.org may be down" (it wasn't as you will see). After I put in the EPSG the tool appeared to run just fine, generated the Lidar intensity image, but then choked on the OSM. I show the output of the tool below:

Processing: NT18SE_2PPM_LAS_PHASE2.laz
Problem looking up epsg with prj2epsg.org, try running the tool later.
prj2epsg.org may be down, using backup for force_epsg
Overwriting projection with EPSG:4277
Unit in use is 0.9999999999999999
Proj4 : pyproj.Proj('+units=m +init=epsg:4277 ', preserve_units=True)
Generating lidar intensity image
19.55% visualizing lidar
39.98% visualizing lidar
60.4% visualizing lidar
80.94% visualizing lidar
Adding golf features to lidar data
OpenStreetMap Overpass query: (node(inf,inf,inf,inf);way(inf,inf,inf,inf););out;
OpenStreetMap servers are too busy right now. Try running this tool later.

The error message generated was:

Exception in Tkinter callback
Traceback (most recent call last):
File "tkinter\__init__.py", line 1705, in __call__
File "tgc_gui.py", line 521, in runLidar
File "lidar_map_api.py", line 284, in generate_lidar_previews
AttributeError: 'NoneType' object has no attribute 'ways'

I assumed the OSM was busy so I tried it again the next day and got the same thing. So I then re-rean a course I know had worked correctly recently, and this was the output:

Processing: USGS_LPC_NV_LasVegas_QL1_2016_18801_LAS_2018_1.laz
Using metadata: USGS_LPC_NV_LasVegas_QL1_2016_18801_LAS_2018_meta.xml
Found Projection Parameters from metadata file
Unit in use is 0.3048006096012192
Proj4 : pyproj.Proj('+proj=tmerc +datum=NAD83 +ellps=GRS80 +a=6378137.0 +f=298.2572221009999 +k=0.9999 +x_0=199999.9999999998 +y_0=8000000.00000001 +lon_0=-115.583333333333 +lat_0=34.75 +units=m +axis=enu ', preserve_units=True)
Processing: USGS_LPC_NV_LasVegas_QL1_2016_18812_LAS_2018_1.laz
Using metadata: USGS_LPC_NV_LasVegas_QL1_2016_18812_LAS_2018_meta.xml
Found Projection Parameters from metadata file
Unit in use is 0.3048006096012192
Proj4 : pyproj.Proj('+proj=tmerc +datum=NAD83 +ellps=GRS80 +a=6378137.0 +f=298.2572221009999 +k=0.9999 +x_0=199999.9999999998 +y_0=8000000.00000001 +lon_0=-115.583333333333 +lat_0=34.75 +units=m +axis=enu ', preserve_units=True)
Processing: USGS_LPC_NV_LasVegas_QL1_2016_18901_LAS_2018_1.laz
Using metadata: USGS_LPC_NV_LasVegas_QL1_2016_18901_LAS_2018_meta.xml
Found Projection Parameters from metadata file
Unit in use is 0.3048006096012192
Generating lidar intensity image
Adding golf features to lidar data
OpenStreetMap Overpass query: (node(35.968235538654305,-114.88746336224321,35.98582983405214,-114.87689623228906);way(35.968235538654305,-114.88746336224321,35.98582983405214,-114.87689623228906););out;

You can see that both prj2epsg.py and OSM worked just fine. Has anyone seen this issue before? Is it just this particular Lidar file or Scotland in general?

Anybodies thoughts appreciated.

[champ39]

May 11, 2020 7:31:48 GMT -5 sandsaver01 said:

I was just playing around trying to make a course file for a Scottish course near Edinburgh. Somebody had already don some of the OSM work, so I located the appropriate Lidar and ran the tool. I had to force the EPSG because it said "prj2epsg.org may be down" (it wasn't as you will see). After I put in the EPSG the tool appeared to run just fine, generated the Lidar intensity image, but then choked on the OSM. I show the output of the tool below:

Processing: NT18SE_2PPM_LAS_PHASE2.laz
Problem looking up epsg with prj2epsg.org, try running the tool later.
prj2epsg.org may be down, using backup for force_epsg
Overwriting projection with EPSG:4277
Unit in use is 0.9999999999999999
Proj4 : pyproj.Proj('+units=m +init=epsg:4277 ', preserve_units=True)
Generating lidar intensity image
19.55% visualizing lidar
39.98% visualizing lidar
60.4% visualizing lidar
80.94% visualizing lidar
Adding golf features to lidar data
OpenStreetMap Overpass query: (node(inf,inf,inf,inf);way(inf,inf,inf,inf);out;
OpenStreetMap servers are too busy right now. Try running this tool later.

The error message generated was:

Exception in Tkinter callback
Traceback (most recent call last):
File "tkinter\__init__.py", line 1705, in __call__
File "tgc_gui.py", line 521, in runLidar
File "lidar_map_api.py", line 284, in generate_lidar_previews
AttributeError: 'NoneType' object has no attribute 'ways'


Anybodies thoughts appreciated.

Mike, I used the same Lidar tile as you (NT18SE_2PPM_LAS_PHASE2.laz), and using your EPSG of 4277, I got the same error that you did.

So, I then ran it again with EPSG:  27700, which I believe covers most of the UK...the thing is I could see only one golf course in the Lidar tile area (and part of that course was cut-off)...Aberdour Golf Club (a par 67, with just the bunkers and wooded areas mapped in OSM), so I'm unsure if this was the course you were refering to?

Anyhoo, I added a par 3 green and fairway to OSM...but to get it to work, I had to add the NT18NE_2PPM_LAS_PHASE2.laz, to cover the whole course:

I had a quick look at the bunkers in-game, all looks good...I just hope I've guessed at the correct course haha.

[sandsaver01]

champ39

May 12, 2020 7:04:56 GMT -5 champ39 said:

Mike, I used the same Lidar tile as you (NT18SE_2PPM_LAS_PHASE2.laz), and using your EPSG of 4277, I got the same error that you did.

So, I then ran it again with EPSG:  27700, which I believe covers most of the UK...the thing is I could see only one golf course in the Lidar tile area (and part of that course was cut-off)...Aberdour Golf Club (a par 67, with just the bunkers and wooded areas mapped in OSM), so I'm unsure if this was the course you were refering to?

Anyhoo, I added a par 3 green and fairway to OSM...but to get it to work, I had to add the NT18NE_2PPM_LAS_PHASE2.laz, to cover the whole course:

I had a quick look at the bunkers in-game, all looks good...I just hope I've guessed at the correct course haha. ;) 

Roger, you are my Hero! I appreciate you going to all that effort, and do not be peeved with me, but i was just doing that work because I was interested in doing an overseas course and picked that area to try out - I was not going to really do Aberdour.

I only posted the original question because I had never gotten those messages from Chad's Tool before, and I have done plenty using the incorrect EPSG. Usually then the tool runs and the right-hand side is a black square or some land nowhere near the course, rather than the error messages I got.

Thank you for finding the correct EPSG, and when I really do try a Scottish or UK course I will use that.