I'm seeing some discrepancies in a LiDAR dataset regarding the datum/geokeys displaying correctly in Global Mapper Version 14.0.3. The LAS file was created in GeoCue using the NA2011 datum, but GM sees the datum as WGS84. Also, the False Easting is not displaying correctly.
I've used LP360 and LASTools (LASinfo) to confirm that header information in the file is correct, but GM is not reading the file the same. I've included a txt from LASTools showing the correct header information (lines 42-54).
Is this a bug, or a known bug? Thanks in advance for your help.
Can you provide a file with this header so I can take a look? I would have expected the projection to come in as State Plane Michigan South NAD83 Feet, although the GeoTIFF header in the file looks to just store user-defined for the datum and PCS projection code, so the only way to know the datum would be to parse the text of the PCSCitationGeoKey.
Later versions of Global Mapper do this for some projections to handle these cases where the writing application doesn't store a full definition, but I'm not sure if that old version of GM does or not.
Thanks for the response, Mike. I have uploaded the LAS file I've been testing, as well as the correct .prj file (just in case). It wouldn't let me upload with the extension .las, so I changed it to .txt- be sure to change it back.
Let me know what you find. Thanks again!
I've updated the GeoTIFF projection interpreter used for Lidar LAS/LAZ files to check the citation text tags for the datum since the numeric tags themselves don't specify the datum (they are all the user-defined value of 32767). With that I can get out NAD83, but not NAD83 (2011) as that datum isn't built in to Global Mapper.
Thanks Mike. I had a feeling that's all it was. Great Tech Support. Thanks much!