| UNAVCO
 


Knowledge Base

Converting XYZ to LAT,LON,HGT

Converting RiScan output (XYZ)  to  WGS84 LAT,LON,HGT   

Will also convert to lat,lon,alt,R,G,B,A

  • Download nlastools.zip
  • Unzip the file to get a nlastools directory.
  • In there is a lidar2csv.sh script.
   Note: This needs to have Java 1.6 in your path.

  • You run it with: sh ~/nlastools/lidar2csv.sh -header lowres_Polydata001.txt

Also attached is a lidar.properties file. Place this in the directory where your data files are. This defines the coordinate reference system (I assume wgs84) and the fields.

Note - the above conversion outputs:
#longitude[unit="degrees"],latitude[unit="degrees"],altitude[unit="m"],red[],green[],blue[],amplitude[]

This nlastools package is new and hasn’t been used very much so any feedback would be appreciated.
Attached Files
There are no attachments for this article.
Comments (4)
Comment by Vinton Valentine on Fri, Mar 29th, 2013 at 2:43 PM
Thanks for looking into the issues I found and for fixing/enhancing the formatting. I will check out the new version. As for the duplicate line issue, I will send the info and example data file via your email address.
Comment by Jeff McWhirter on Wed, Mar 13th, 2013 at 3:21 PM
I put together a fix for the formatting problem. You can get a new version of the nlas tools release and see how to specify formatting here: http://tls.unavco.org/repository/entry/show?entryid=fd524b73-23d8-415d-a05e-6b7f7199ab2e
Comment by Jeff McWhirter on Wed, Mar 13th, 2013 at 2:14 PM
I will look into the duplicate line problem. As to the precision - this is a side effect of how the values are managed internally for text files. The numeric values in a shot are managed internally when processed as 8 byte doubles then the double value is written out. Likewise the RGB values are managed as doubles as well. Clearly 16 decimal places is too much. I will come up with a way to describe precision for the fields in a text file. Can you send me your metadata properties file and a couple line example data file? Thanks, Jeff
Comment by Vinton Valentine on Fri, Mar 8th, 2013 at 11:53 PM
When using lidar2csv to convert an ECEF file to LLE, resulting csv file contains 2 lines of duplicate ouput for each line of input. Also, longitude,latitude,altitude written with 16 decimal places when input had 2 decimal places and r,g,b,intensity values written with 1 decimal place when input was integer. WinXP system running the jar file using java 1.6.0_31 in command line.
Name
Email
Security Code Security Code
Related Articles RSS Feed
Coordinate Transformations with Geographic Calculator
Viewed 4109 times since Fri, Sep 4, 2015
Cyclone Scan Registration
Viewed 16091 times since Wed, Sep 9, 2015
Camera Calibration For Riegl VZ Series Scanners
Viewed 1243 times since Tue, May 12, 2015
Validation Manual For Riegl VZ Series Scanners
Viewed 733 times since Thu, Oct 1, 2015
Riegl TLS Field Operation Manual and Workflow
Viewed 11237 times since Fri, Jan 31, 2014
Georeferencing in PolyWorks
Viewed 1492 times since Fri, Sep 4, 2015
Coordinate transformations with GeoSysManager
Viewed 2063 times since Fri, Sep 26, 2014
Beginners Guide to PolyWorks
Viewed 1929 times since Fri, Sep 4, 2015
QT Modeler - Beginners' Resources
Viewed 2206 times since Fri, Sep 4, 2015
Global Mapper - Tutorials and Beginner Resources
Viewed 7780 times since Tue, Sep 8, 2015
MENU

Last modified: Monday, 12-May-2014 00:18:29 UTC