| 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" 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. |
| 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, 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. |
| 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 data 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, use withheld bit and the LAS format). The tasks are fairly self-explanatory, |
| | 9 | == Preprocessing == |
| | 10 | |
| | 11 | * Process the LiDAR navigation system data normally in PosPac. See [https://nerc-arf-dan.pml.ac.uk/trac/wiki/Processing/POSPac]. **Note** this should be a separate system specific to the LiDAR, written by default to the `pos/` directory within the raw LiDAR data directory |
| | 12 | * Navigation output needs to be SBET with `*.out` extention |
| | 13 | * Consider whether SBET navigation data needs to be "flipped" on export |
| | 14 | * Also need to get the `smrmsg.out` file from `Mission/Extract/` within the PosPac project structure. |
| | 15 | |
| | 16 | == Processing == |
| | 17 | |
| | 18 | ** Full Waveform Extraction ** |
| | 19 | ** This isn't working yet ** |
| | 20 | |
| | 21 | Flightlines table file has serial number as 0. |
| | 22 | |
| | 23 | Serial numbers for the current (2022 - 2024) are: |
| | 24 | * Optech Galaxy 200: 5060465 |
| | 25 | * IWR4: 5720057 |
| | 26 | |
| | 27 | ** Processing in LMS ** |
| | 28 | |
| | 29 | * Log on to the windows VM and start up the LMS software (Lidar Mapping Solution). |
| | 30 | |
| | 31 | * 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. |
| | 32 | |
| | 33 | * 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) |
| | 34 | |
| | 35 | * 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. |
| | 36 | |
| | 37 | * 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. |
| | 38 | |
| | 39 | * 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). |
| | 40 | |
| | 41 | * Create the block. For production data select "production+sensor corrections" |
| | 42 | |
| | 43 | * 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, use withheld bit and the LAS format). The tasks are fairly self-explanatory, |