Changes between Version 15 and Version 16 of Help/DEM_scripts

Timestamp:

Feb 11, 2012, 3:32:03 PM (13 years ago)

Author:

adbe

Comment:

--

Help/DEM_scripts

@@ -202 +202 @@
 I would advise that the grass version be 6.3 as the script was written to work with this grass version.
 
-==== Using asterdem.sh ====
+==== Using lidardem.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:
 
@@ -252 +252 @@
      *  {{{lidardem.sh -f las_file -E 50}}}
 
-
-
+=== Creating a DEM from LiDAR and ASTER data using ''lidar_aster_dem.sh'' script ===
+==== Configuring lidar_aster_dem.sh ====
+To run lidar_aster_dem.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 lidar_aster_dem.sh ====
+This is a wrapper script for asterdem.sh and lidardem.sh, so the options are similar to those above. The script is configured for internal use, so here is a out of house usage:
+lidar_aster_dem.sh[[BR]]
+[[BR]]
+Generates a binary LiDAR ASTER DEM[[BR]]
+[[BR]]
+Arguments:[[BR]]
+   -d:      Directory containing LiDAR data
+or
+   -f:      LiDAR file to create DEM from
+   -A:   Directory containing raw unzipped ASTER data.[[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[[BR]]
+      -R:   Resolution of output DEM, defaults to 2[[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. It is suggested to use this option if the las file are very large[[BR]]
+      -z:   Specify an input projection of the LiDAR files[[BR]]
+      -p:   Projection to output DEM in: input proj4 string or UKBNG or ll or UTM[zero_padded_number](N|S)[[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]]
+      -S    geoid-spheroid seperation file[[BR]]
+
+Examples:
+  *  Create a LiDAR ASTER DEM from tiles in directory aster_tiles and UKBNG las files in las1.0 and output to a file called dem.dem (Uses default buffer size of 2000 in all directions
+     *  {{{lidar_aster_dem.sh -d las1.0 -A aster_tiles -o a_dem_filename.dem}}}
+  *  Create a LiDAR ASTER DEM from tiles in directory aster_tiles and utm30N las files in las1.0 and output to a file called dem.dem (Uses default buffer size of 2000 in all directions
+     *  {{{lidar_aster_dem.sh -d las1.0 -z UTM30N -A aster_tiles -o a_dem_filename.dem}}}
+  *  Create a LiDAR ASTER DEM from tiles in directory aster_tiles and las files in las1.0 and output to a file called dem.dem, use buffer size of 100 in all directions
+     *  {{{lidar_aster_dem.sh -d las1.0 -A aster_tiles -N 100 -S 100 -E 100 -W 100-o a_dem_filename.dem}}}