| | 1 | = Processing data from the Teledyne Optech Galaxy LIDAR system = |
| | 2 | |
| | 3 | == Global preferences == |
| | 4 | |
| | 5 | Options and preferences are set up globally, but can be edited either globally (to affect all following projects), within the project (to only affect this project) or per line (to only affect that line). |
| | 6 | |
| | 7 | The instrument RES and LCP files are specific for a sensor and calibration. In the RES file it is possible to change the settings under the RangeResolution (to fix PIA issues) and ipc_filter (to try and filter out atmospheric returns). In the IW4.RES file there is a RangeOffset to gives the time (range) difference between the waveform and discrete data. This needs to be set once (first time) and then should not need changing. The TBL file is for intensity decoding and should not be edited. The LCP file contains the correction parameters such as scan angle offset, boresight, leverarms and polynomials. The CCP file is similar but for the camera. For info, the scan-lag is the time between laser transmit and receive, time-sync is the offset between las point and trajectory, beam-roll/pitch is provided by Teledyne and droop-scanner-poly represents the edges of scan lines. |
| | 8 | |
| | 9 | == Steps to process == |
| | 10 | 1. Log on to the windows VM and start up the LMS software (Lidar Mapping Solution). |
| | 11 | 2. Create a new project and save under the flight day processing/lidar/ directory. Make sure the "project" 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. |
| | 12 | 3. 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) |
| | 13 | 4. Add a mission to the project. This takes the post-processed SBET from PosPac and SurveyRange (raw lidar) file. 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. |
| | 14 | 5. On the mission, there should be a selection of tabs, click the lidar lines tab which gives an overview of the lines. Select the area to process (use the +Polygon button), and then add the lines to the project (the >>> button followed by the tick). This should now have a list of lines added on the left hand panel. |
| | 15 | 6. For refined processing we need to add a block (for the block adjustment). Before doing this, ensure any cross lines are selected as "cross" rather than "production" (in the lines section). |
| | 16 | 7. Create the block. For production date select "production+sensor corrections" |
| | 17 | 8. You can select which tasks to perform for each line and block in the respective sections and click Set Task. Also check the Set Options pop up too. Ensure that in Las Output the correct options are selected (e.g. with classification, with extra bit and the LAS format). The tasks are fairly self-explanatory, |
| | 18 | * planar surfaces extraction -> extracts planes based on the options given in the preferences |
| | 19 | * planes to shapefile -> creates shapefiles for planar surfaces for QCing |
| | 20 | * Roof lines extraction -> from all planar surfaces, only find ones similar to roof of houses, for horizontal accuracy checks |
| | 21 | * Collect map statistics -> number of points per cell on regular grid (bmp format image) |
| | 22 | * RGB extract -> for camera data to assign colour to lidar return |
| | 23 | * Galaxy nose classification -> tool to identify noise in point cloud |
| | 24 | * LAS file output -> output LAS files |
| | 25 | * ASCII file output -> output ASCII files |
| | 26 | 9. Can run lines individually or grouped together. |
| | 27 | |
| | 28 | |
| | 29 | == Boresight processing == |
| | 30 | |
| | 31 | If you have control points you can add a control site. Use this for absolute accuracy report (not self calibration). The control site is an ASCII file with columns ID,X,Y,Z. |
| | 32 | |
| | 33 | When creating the block select "boresight+sensor correction". |
| | 34 | |
| | 35 | For the QC-ing the main 3 things to check are: |
| | 36 | * tie planes - should be less than 5cm. Also check the scatter plots (click analyze). They should be narrow (<5cm) and straight (horizontal). Curved ones suggest a poor scanner polynomial and slanted suggests poor boresight. It is possible to analyze in 3D to see where the tie planes are wrt other points. |
| | 37 | * roof lines - use this for horizontal accuracy checks. The RMS should be less than (altitude above ground / 10000). |
| | 38 | * height difference maps - in the output directory there is a PNG for the adjusted height difference. Check that it looks good (<5cm differences in the flat areas and across the images, trees etc will have higher). |
| | 39 | |
| | 40 | If there are problems then you can create a new instrument from the adjusted LCP file and reprocess, then do the QC again. |
| | 41 | |
| | 42 | There are "project shapefiles" in the project tab that allows you to see locations of tie planes and roof lines etc. |