Changes between Version 11 and Version 12 of Processing/OptechGalaxy2000Procedure

Timestamp:

Sep 3, 2025, 3:37:34 PM (4 days ago)

Author:

mark1

Comment:

--

Processing/OptechGalaxy2000Procedure

@@ -36 +36 @@
 * Create a new project and save under the flight day processing/lidar/ directory. Make sure the "project" is in a projected coordinate system (e.g. UTM) and the "output" is a supported projection. There is a known bug when setting projection frames, and sometimes the program freezes - in this case need to wobble the reference frame window.
 
-* Create an instrument and open the sensor RES file and LCP file (located in the ~arsf/calibration tree). Make sure to use the version 4.5 (or allow it to convert from 4.4 to 4.5). We currently have copies of these files on the VM at `C:\optech_lidar_sensor_files\`:
- * `*.RES`
- * `*.LCP`
- * `*.TBL`
+* Create an instrument and open the sensor RES file and LCP file (located in the ~arsf/calibration tree). Make sure to use the version 4.5 (or allow it to convert from 4.4 to 4.5).  Note version number will be same as version of LMS that is running - so it may ask to convert version when you open the file.
+If using the IWR4 for full waveform processing then ensure you use a calibrated RES file - this will contain an updated time offset so that FW data aligns with discrete. Note these files on the VM / Laptop may not be up to date and refer to ones in ~arsf/calibration.
 
 * Add a mission to the project. This takes the post-processed SBET from PosPac and SurveyRange (raw lidar) file. Note, not only is the SBET file needed from PosPac, but the "smrmsg_xxx.out" file, which should be in mission/Extract within the project files. Note it's possible to create multiple missions per project. For trajectory select "is already processed". The digitiser type (if used) is IW4. Can use meterological data if available - this is an ASCII file with a time, temperature and air pressure. Usually do not use this. The Trajectory report tab within the mission shows details of the flightlines. The range file is the raw laser data and is (hopefully) found in the project lidar/range/*.RANGE location.