|
|
Post by sandsaver01 on Jan 31, 2020 17:11:37 GMT -5
I am trying to do Alotian GC. I know Doyley has successfully generated a course file which looks fine, but the plant meter is already above 60% with no planting, and Alotian is covered in trees. I finally got a EPSG to work on the Lidar files, but when it chugs through and comes to where you are supposed to put a rectangle around the course and accept, the OSM data is not there. I know it is showing the right Lidar data because you can see the outlines of the holes through the trees, and Scott did trace out the course in OSM, but as you can see from the print-out below the tool is sending OSM off into the wilderness, using completely bogus coordinates: Adding golf features to lidar data
OpenStreetMap Overpass query: (node(44.84766623043966,-94.94979297492277,44.85553719590786,-94.93804568715512);way(44.84766623043966,-94.94979297492277,44.85553719590786,-94.93804568715512););out;
Mapquest Image URL Request: open.mapquestapi.com/staticmap/v5/map?key=MAPQUEST_API_KEY&scalebar=true&format=png¢er=44.85160186259672,-94.9439190010076&type=hyb&zoom=17&size=1500,1500The real coordinates are about 34.852796°, -92.592411° I do not know what is going on here. Any help? |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 31, 2020 20:33:02 GMT -5
I would think if the OSM does not appear when you draw the box, it's not the right EPSG code?
|
|
|
|
Post by champ39 on Feb 1, 2020 7:27:28 GMT -5
I had no joy with the lidar from 2016, but managed to get the lidar from 2010 to work, with "Force Lidar EPSG Projection"...3433
I didn't bother masking any of the course, I just wanted to pop it into the game to have a quick look
Looks like I should have...haha, sent the meter crashing over the top, I couldn't even change the lighting without getting a "course full" error
My PC hated running the tool on this one, so much elevation on the course, it was a real chug-fest (it took 45 minutes to do the 4 lidar tiles, to get to the "draw the rectangle" stage).
The course looks good though, I hope it can be masked enough to fit in the game lol.
|
|
|
|
Post by sandsaver01 on Feb 1, 2020 7:45:13 GMT -5
I had no joy with the lidar from 2016, but managed to get the lidar from 2010 to work, with "Force Lidar EPSG Projection"...3433 I think the Lidar from 2010 must be what Scott Doyley used when he built the course file; it just uses up too much plant meter to continue with. I also used EPSG 3433 for the 2016 lidar data and that is when I got the weird OSM results. You would think the EPSG would be the same for both sets of data on the same terrain, but I guess not. |
|
|
|
Post by champ39 on Feb 1, 2020 7:57:42 GMT -5
I had no joy with the lidar from 2016, but managed to get the lidar from 2010 to work, with "Force Lidar EPSG Projection"...3433 I think the Lidar from 2010 must be what Scott Doyley used when he built the course file; it just uses up too much plant meter to continue with. I also used EPSG 3433 for the 2016 lidar data and that is when I got the weird OSM results. You would think the EPSG would be the same for both sets of data on the same terrain, but I guess not. There wasn't any "image thumbnail previews" for the 2016 lidar in The National Map, and it's metadata co-ordinates matched none of the EPSG numbers for Arkansas, on Spatial Reference. If you don't have matching co-ordinates, you're going to end up in the wilderness...that's about the limit of my know-how I'm afraid.🙁 |
|
|
|
Post by sandsaver01 on Feb 1, 2020 8:38:22 GMT -5
I wonder why that is Roger. I suppose I could try downloading the terrain from 2016 and putting Scott's 2010 OSM on it; I might be able to move it around and get it to match up. I will have think about whether that is worth the trouble.
|
|
|
|
Post by champ39 on Feb 1, 2020 9:02:35 GMT -5
I wonder why that is Roger. I suppose I could try downloading the terrain from 2016 and putting Scott's 2010 OSM on it; I might be able to move it around and get it to match up. I will have think about whether that is worth the trouble. I've no idea how you would get that to work Mike, I'm also thinking from memory, that the 2016 lidar is a better quality level of data, so the heightmap may be even a larger file size than the 2010 one?. |
|
|
|
Post by sandsaver01 on Feb 1, 2020 10:21:21 GMT -5
Yes it is a larger file, but I plan to mask the cr@p out of it and see if I can get it down to size. If I try this, I plan on saving "save OSM as flat" and then importing the new terrain. I have low expectations and am not going to spend much time on it but what the heck  |
|
|
|
Post by champ39 on Feb 1, 2020 11:07:17 GMT -5
Go for it👍
|
|
|
|
Post by sandsaver01 on Feb 1, 2020 12:42:29 GMT -5
I tried it but no joy :'( I guess I will move on to something else when I publish Sand Hills. |
|
