Changes between Version 20 and Version 21 of Procedures/DeliveryChecking


Ignore:
Timestamp:
Feb 23, 2011 12:00:30 PM (9 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryChecking

    v20 v21  
    2626 1. Only the PDF read me file should be present (no .tex, .out, .aux, .log files)
    2727 1. Ensure the text files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) (run unix2dos !ReadMe.txt)
    28  1. Check all the ASCII LIDAR files open/load, look OK and fit together
     28 1. Check all the ASCII LIDAR files open/load, look OK and fit together horizontally and vertically. Either:
    2929   * Use lag to view the data
    30    * OR use a scripted approach with Grass to check each line reads in and mosaic looks good. Either run import_ldr_txt_to_grass.sh from within Grass or run [wiki:Processing/CreateTifs make_lidardem_or_intensity.sh]. You need to generate these yourself from the ascii files, you can't just look at already created DEM/Screenshots.
    31    * Check that all lines look OK and the mosaic overlaps horizontally with no gaps
    32  1. Run the script check_ascii_lidar.sh which will read in the ascii files and check all points have the correct number of records (8) and report the min/max of the time/easting/northings.
     30   * Use a scripted approach with Grass. Either run import_ldr_txt_to_grass.sh from within Grass or run [wiki:Processing/CreateTifs make_lidardem_or_intensity.sh]. You need to generate these yourself from the ascii files, you can't just look at already created DEM/Screenshots.
     31 1. Run the script check_ascii_lidar.sh which will read in the ascii files and check all points have the correct number of records (8) and report the min/max of the time/easting/northings. **NOTE- this currently doesn't work as there are now 9 records per column. Fix script or skip this part :)**
    3332 1. Check the DEM contents look OK
    3433   * less <dem>