Changes between Version 12 and Version 13 of Help/DEM_scripts

Timestamp:

Feb 11, 2012, 2:29:49 PM (13 years ago)

Author:

adbe

Comment:

--

Help/DEM_scripts

@@ -3 +3 @@
    '''lidardem.sh'''[[BR]]
    '''asterdem.sh'''[[BR]]
-   '''nextmapdem.sh'''[[BR]]
    '''lidar_aster_dem.sh'''
 The scripts listed are written in bash.
@@ -161 +160 @@
 [[BR]]
 Arguments:[[BR]]
+   -a:   Directory containing ASTER tiles only. If not given then script needs to be run within a project[[BR]]
    (Optional)[[BR]]
       -h:   Display usage and exit[[BR]]
       -o:   Final output filename for DEM, defaults to leaving in grass database[[BR]]
       -j:   Filename to output a jpeg image of the DEM[[BR]]
-      -a:   Directory containing ASTER tiles only. If not given then script needs to be run within a project[[BR]]
       -g:   Grass database to use, defaults to creating one[[BR]]
       -p:   Projection of output tiles: proj4 string or UTM[utm_num(zero padded)](N|S) or UKBNG or ll[[BR]]
@@ -193 +192 @@
      *  {{{asterdem.sh -a aster_tiles/ -p UKBNG -r 2.0 -o a_dem_filename.dem}}}
 
+=== Creating a DEM from LiDAR data using ''lidardem.sh'' script ===
+==== Configuring lidardem.sh ====
+To run lidardem.sh on your system the files listed above need to be configured in the script to point to the correct places. 
+For example, the template grass database in the script points to a place in the arsf directory and this needs to be changed to point to where your template grass database is located.
+Variables that need to be changed:
+  *  TEMPLATE_GRASS_DATABASE=/users/rsg/arsf/usr/share/grass_db_template/
+  *  WGS84LL_SEPARATION_FILE=/users/rsg/arsf/dems/aster/separation_files/uk_separation_file_WGS84LL.dem
+  *  GRASS_VERSION=grass63
+I would advise that the grass version be 6.3 as the script was written to work with this grass version.
+
+==== Using asterdem.sh ====
+The script is partly configured to be used in-house and so some options that are available are not applicable, as for example the navigation file is used to calculate the tiles to use by default. So here is a usage for out of house usage:
+
+lidardem.sh[[BR]]
+[[BR]]
+Generates a binary LiDAR DEM from LAS/ASCII files[[BR]]
+[[BR]]
+Arguments:[[BR]]
+   -d:      Directory containing LiDAR data[[BR]]
+   or[[BR]]
+   -f:      LiDAR file to create DEM from[[BR]]
+   (Optional)[[BR]]
+      -h:   Display usage and exit[[BR]]
+      -o:   Final output filename for DEM, defulats to leaving in grass database[[BR]]
+      -c:   Whether to use points of classification 7, defaults to just points of classification 1[[BR]]
+      -a:   Whether to use all returns, defaults to using first return only[[BR]]
+      -r:   Resolution to input LiDAR files with, defaults to 2[[BR]]
+      -R:   Resolution to output LiDAR files with, defaults to calculating from input resolution[[BR]]
+      -j:   Create a jpg image of the DEM[[BR]]
+      -g:   Grass database to use, defaults to creating a GRASS database locally[[BR]]
+      -t:   Whether to use ASCII files to create the DEM, defaults to using LAS files[[BR]]
+      -z:   Specify an input projection[[BR]]
+      -p:   Projection to output DEM in: proj4 string or UKBNG or ll or UTM[zero_padded_number](N|S)[[BR]]
+      -s:   geoid-spheroid separation file[[BR]]
+      -m:   Maximum size of output DEM in GB, will be overridden by specified resolution[[BR]]
+      -i:   Navigation file to use[[BR]]
+      -N:   North buffer, defaults to 2000[[BR]]
+      -S:   South buffer, defaults to 2000[[BR]]
+      -E:   East buffer, defaults to 2000[[BR]]
+      -W:   West buffer, defaults to 2000[[BR]]
+      -F:   Do not filter the DEM[[BR]]
+      -E:   Extrapolate the DEM, followed by the resolution to extrapolate at[[BR]]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+