Been a While - Having Some Trouble

[metatropic]

May 14, 2024 12:22:43 GMT -5 BaconJunkie1 said:

Alister we are going to have to agree to disagree. You do a good job doing it your way but we have different methods, opinions and standards. 

And that’s fine. The way I see it it’s like doing a portrait. You can guarantee a good likeness by tracing a photo; but you can do just as well or better freehand with the right references and techniques. For me OSM is a starting point, like a lay in or preliminary sketch, laying out rough proportions and relationships. 

[metatropic]

May 14, 2024 11:43:40 GMT -5 Violinguy69 said:

May 14, 2024 11:39:47 GMT -5 Violinguy69 said:

Yes, National Map.

I really was hoping to do Lookout Mountain (GA) or Ohoopee Match Club (GA).  I just used the tool for Ohoopee and everything worked fine.  I need to do the OSM editing for it.  

Scratch that.  OSM is edited, but is not being generated in Chad's tool.  

I can only see 2018 LidAR data for Ohoopee, and course opened in 2019. Or maybe I have that wrong?

[Violinguy69]

May 14, 2024 15:30:32 GMT -5 metatropic said:

May 14, 2024 11:43:40 GMT -5 Violinguy69 said:

Scratch that.  OSM is edited, but is not being generated in Chad's tool.  

I can only see 2018 LidAR data for Ohoopee, and course opened in 2019. Or maybe I have that wrong?

Yeah, I saw "published in 2021" and got excited.  I'm going to keep trying until I get a course that works.  I have a few other ideas.  After dinner at least.  Thanks for your help so far!

[BaconJunkie1]

There not much that you would need to do to do The Minikahda Club, just spline and or update a few bunkers, the greens and fairways appear to ready to go.

EDIT: A few fairways near a few bunkers and the cartpaths need a little work. 

[Violinguy69]

May 14, 2024 16:38:36 GMT -5 BaconJunkie1 said:

There not much that you would need to do to do The Minikahda Club, just spline and or update a few bunkers, the greens and fairways appear to ready to go.

EDIT: A few fairways near a few bunkers and the cartpaths need a little work. 

If I can get the lidar to work, I'm still thinking about this one.  I also got another course to work, The Country Club of Tennessee.  It's a doozy in the mountains.

[metatropic]

May 16, 2024 11:46:04 GMT -5 Violinguy69 said:

May 14, 2024 16:38:36 GMT -5 BaconJunkie1 said:

There not much that you would need to do to do The Minikahda Club, just spline and or update a few bunkers, the greens and fairways appear to ready to go.

EDIT: A few fairways near a few bunkers and the cartpaths need a little work. 

If I can get the lidar to work, I'm still thinking about this one.  I also got another course to work, The Country Club of Tennessee.  It's a doozy in the mountains.


mmallahan may have some local knowledge of that place.

[BaconJunkie1]

You had mentioned "If you could get it to work and that things weren't showing up" so I tested it for you. Using the EPSG that Ali and I gave you the course imports into TGC 2019 perfectly. What I suspect is .... The 2019 step gets forgotten really easily, you have to open the course file in 2019 first, save it and then you can copy and paste the course file from 2019 to 2k23. 

[Violinguy69]

BaconJunkie1

Thanks. I got it to work as well. I'm going to try a few others tonight and then decide which one to finish. Any idea what the correct EPSG is for Muscle Shoals, AL is? I'm looking at that 8000 yard beast Fighting Joe.

[BaconJunkie1]

I use LASTools to get EPSGs, the latest .laz file for thecourse there didn't give me the .txt file I was looking for but an older version did .... try 6345.

The method that works for me is covered in this "How To" that I wrote, it looks like a lot but once setup, it takes seconds to get the EPSG provided the .laz/.las file gives the right type of .txt file. If not, just leave the EPSG box empty, it that doesn't work, this is your best route .... spatialreference.org/ref/epsg/

How To Use LASTools to get a EPSG from a LAS/LAZ file

First off, a LAZ file is just a compressed file with many LAS files inside of it.

- Go to your C drive in Window’s Explorer.

- Right click in a blank area and make a new folder named LASTools.

- In Windows Explorer go to “View” up above the files section>Show/Hide check the “File name extensions” box, now the .exe, .txt, … etc parts of the filenames should show.

- Go to this site and download LASTools to that folder that you made

rapidlasso.com/lastools/ or move the LASTools.zip file to that folder after it downloads to wherever you downloaded it to … It usually goes to the “Downloads” folder.

- Now that the .zip file is downloaded and in the LASTools folder, go inside the LASTools folder that you made, right click on the LASTools.zip file and use the extract here option.

- Once it extracts the files and inside of that same folder, right click in a blank area and make another new folder named My LAZ Files to put the LAZ/LAS files into that that you want to read. Put your downloaded LAS/LAZ file into that folder, you just need 1 of them.

- Go to the “bin” folder inside of the LASTools folder and find “lasinfo.exe”. (the .exe part may not show if you don’t have that option turned on in Windows Explorer like I showed you up above)

- Double left click the “lasinfo.exe” to open the program

- Left click the “Browse” button

- Double left click the “\..” button

- Drag down or down arrow to the My LAZ Files folder that you made and double left click it

- Double left click the LAS/LAZ file that you want to read (later on empty this folder after you have found the correct EPSG file) and you should see a big turquoise box.

- Over on the right side, left click on “Output Options”, tick the “*_info.txt” box and click the “Output Options” to close it.

- Look below there and near the bottom and click the “Run32” button and another window will open

- Click “START” and it will read the LAZ/LAS file and add a .txt file inside the “My LAZ Files” folder

- Go to the “My LAZ Files” folder and double left click the .txt file to read it and the correct EPSG code should be the one after the “AXIS X East AXIS Y North” parts. Example: AXIS["X",EAST],AXIS["Y",NORTH],AUTHORITY["EPSG","6434" …. 6434 should be it.

- AFTER YOU HAVE YOUR COURSE IN THE GAME …. Empty the My LAZ Files folder after you have found the correct EPSG file to make finding the LAS/LAZ file that you want to read easier to find the next time.

[BaconJunkie1]

If your .txt file looks like this, you'll have to try the other methods I posted

lasinfo (210720) report for 'C:\LAStools\A LAZ Files\USGS_LPC_Alabama_Counties_LiDAR_001237.laz.laz'

reporting all LAS header entries:

file signature: 'LASF'

file source ID: 0

global_encoding: 0

project ID GUID data 1-4: 4DAE5607-585E-4637-E2AB-904D342ABAB8

version major.minor: 1.2

system identifier: 'ALTM 3100'

generating software: 'GeoCue LAS Updater'

file creation day/year: 129/2011

header size: 227

offset to point data: 751

number var. length records: 3

point data format: 1

point data record length: 28

number of point records: 5472158

number of points by return: 3804141 1074657 510164 83196 0

scale factor x y z: 0.01 0.01 0.01

offset x y z: 0 0 0

min x y z: 450000.00 3852000.00 153.65

max x y z: 451499.99 3853499.99 409.76

variable length header record 1 of 3:

reserved 43707

user ID 'LASF_Projection'

record ID 34735

length after header 192

description 'GeoTiff Projection Keys'

GeoKeyDirectoryTag version 1.1.0 number of keys 23

key 1024 tiff_tag_location 0 count 1 value_offset 1 - GTModelTypeGeoKey: ModelTypeProjected

key 2048 tiff_tag_location 0 count 1 value_offset 4269 - GeographicTypeGeoKey: GCS_NAD83

key 2049 tiff_tag_location 34737 count 6 value_offset 79 - GeogCitationGeoKey: NAD83

key 2050 tiff_tag_location 0 count 1 value_offset 6269 - GeogGeodeticDatumGeoKey: Datum_North_American_Datum_1983

key 2051 tiff_tag_location 0 count 1 value_offset 8901 - GeogPrimeMeridianGeoKey: PM_Greenwich

key 2054 tiff_tag_location 0 count 1 value_offset 9102 - GeogAngularUnitsGeoKey: Angular_Degree

key 2055 tiff_tag_location 34736 count 1 value_offset 9 - GeogAngularUnitSizeGeoKey: 0.01745329252

key 2056 tiff_tag_location 0 count 1 value_offset 7019 - GeogEllipsoidGeoKey: Ellipse_GRS_1980

key 2057 tiff_tag_location 34736 count 1 value_offset 6 - GeogSemiMajorAxisGeoKey: 6378137

key 2059 tiff_tag_location 34736 count 1 value_offset 7 - GeogInvFlatteningGeoKey: 298.2572221

key 2061 tiff_tag_location 34736 count 1 value_offset 8 - GeogPrimeMeridianLongGeoKey: 0

key 3072 tiff_tag_location 0 count 1 value_offset 26916 - ProjectedCSTypeGeoKey: NAD83 / UTM 16N

key 3073 tiff_tag_location 34737 count 53 value_offset 0 - PCSCitationGeoKey: NAD83 / UTM zone 16N|projection: Transverse Mercator

key 3075 tiff_tag_location 0 count 1 value_offset 1 - ProjCoordTransGeoKey: CT_TransverseMercator

key 3076 tiff_tag_location 0 count 1 value_offset 9001 - ProjLinearUnitsGeoKey: Linear_Meter

key 3077 tiff_tag_location 34736 count 1 value_offset 5 - ProjLinearUnitSizeGeoKey: 1

key 3081 tiff_tag_location 34736 count 1 value_offset 0 - ProjNatOriginLatGeoKey: 0

key 3082 tiff_tag_location 34736 count 1 value_offset 1 - ProjFalseEastingGeoKey: 500000

key 3083 tiff_tag_location 34736 count 1 value_offset 2 - ProjFalseNorthingGeoKey: 0

key 3088 tiff_tag_location 34736 count 1 value_offset 3 - ProjCenterLongGeoKey: -87

key 3092 tiff_tag_location 34736 count 1 value_offset 4 - ProjScaleAtNatOriginGeoKey: 0.9996

key 4097 tiff_tag_location 34737 count 26 value_offset 53 - VerticalCitationGeoKey: NAVD88 - Geoid09 (Meters)

key 4099 tiff_tag_location 0 count 1 value_offset 9001 - VerticalUnitsGeoKey: Linear_Meter

variable length header record 2 of 3:

reserved 43707

user ID 'LASF_Projection'

record ID 34736

length after header 80

description 'GeoTiff double parameters'

GeoDoubleParamsTag (number of doubles 10)

0 500000 0 -87 0.9996 1 6.37814e+006 298.257 0 0.0174533

variable length header record 3 of 3:

reserved 43707

user ID 'LASF_Projection'

record ID 34737

length after header 86

description 'GeoTiff ASCII parameters'

GeoAsciiParamsTag (number of characters 86)

NAD83 / UTM zone 16N|projection: Transverse Mercator|NAVD88 - Geoid09 (Meters)|NAD83|

the header is followed by 4 user-defined bytes

LASzip compression (version 2.1r0 c2 50000): POINT10 2 GPSTIME11 2

reporting minimum and maximum for all LAS point record entries ...

X 45000000 45149999

Y 385200000 385349999

Z 15365 40976

intensity 1 4978

return_number 1 4

number_of_returns 1 4

edge_of_flight_line 0 1

scan_direction_flag 0 1

classification 1 11

scan_angle_rank -18 21

user_data 32 32

point_source_ID 1050 1951

gps_time 61855.921305 65583.702062

number of first returns: 3804141

number of intermediate returns: 593985

number of last returns: 3802620

number of single returns: 2728588

overview over number of returns of given pulse: 2728588 1128496 1281852 333222 0 0 0

histogram of classification of points:

1515750 unclassified (1)

1958062 ground (2)

949 noise (7)

200954 water (9)

10959 rail (10)

1785484 road surface (11)

[sandgroper]

That's why I use Stealth to faithfully recreate the "exact" tee boxes, fairway splines, greens and bunkering from google maps as close as I can anyway.
It's what I did at Ballyhack. The OSM data was OK, but still needs cleaning up in the designer.

[Violinguy69]

BaconJunkie1

Thanks again for all your help. I got Fighting Joe to work, but whoever did the OSM editing didn't do a complete job. Next question - when I did this course in Chad's tool, the mask didn't really mask anything. There's another course there that I tried to get rid of and it's still there. Does the mask just limit the elevation data area? I suppose I don't mind having the other course in view, but it pushes the course I want all the way to the edge of the plot and that looks bad.

[metatropic]

May 17, 2024 8:52:36 GMT -5 Violinguy69 said:

BaconJunkie1

Thanks again for all your help. I got Fighting Joe to work, but whoever did the OSM editing didn't do a complete job. Next question - when I did this course in Chad's tool, the mask didn't really mask anything. There's another course there that I tried to get rid of and it's still there. Does the mask just limit the elevation data area? I suppose I don't mind having the other course in view, but it pushes the course I want all the way to the edge of the plot and that looks bad.

The mask just reduces the resolution of the elevation data under the red to the point that it doesn’t hurt the meters. Look carefully and you can see the join. To maximise meters mask everything that isn’t a playing surface. Particularly important in lumpy terrain which can kill your meters. You can fix the joins later. 

Hats off to Chad for the mask feature. It works really well.