ORD LAS file to State Plane Coordinates (Oklahoma)

Folks:

I am having a serious issue with importing USGS Lidar (*.LAS) data. By changing the units of type to Meter in the import dialog (the file is in meters) I get what seems to be relatively accurate elevation data (in US Survey Feet in an Oklahoma North Zone Seed File). However, the file is projected slightly smaller than the rectangle provided through ESRI software (by roughly 4%) and the file shows up in entirely the wrong XY location. As well, if I change the units of type to "unknown", the elevations show up in meters and the file still shows up in the wrong XY location. Without getting into too many additional details, does anyone know why these tiles are showing up in the entirely wrong location? Any of you folks run into this... solutions??

Thanks!

Mark

Parents Reply
  • Holly:

    We were able to access a site from which we were able to track down the EPSG code for the geographical coordinate system source. For those interested, the site is https://epsg.io/. One has only to click on the map to the location of their project to retrieve the code (in our case it was 6344).So, the workflow is thus:

    OpenRoads Modeling>Terrain>Terrain from File. Set the filter to *.las, open the LAS, turn on or off the file attributes (we only desired to keep "ground on), and change the Geographical Coordinate System source to the one which agree with the EPSG code number (I used the search tab to search "6344" and it retrieved key name "UTM83/2011-15). Click "OK" and then "Import" to project the LAS data into your file. Make sure- of course- that the current geographical coordinate system of your file is correct to begin with! 

    Thanks again, and hopefully this thread will be of help to others!

    Mark

    Mark Anthony Plum
    Chief Technology Officer

    1601 N.W. Expressway, Suite 400
    Oklahoma City, OK  73118
      
Children
No Data