| 165 | | -o: Final output filename for DEM, defaults to leaving in grass database[[BR]] |
| 166 | | -j: Filename to output a jpeg image of the DEM[[BR]] |
| 167 | | -g: Grass database to use, defaults to creating one[[BR]] |
| 168 | | -p: Projection of output tiles: proj4 string or UTM[utm_num(zero padded)](N|S) or UKBNG or ll[[BR]] |
| 169 | | -r: Resolution of output DEM, defaults to using resolution of ASTER tile[[BR]] |
| 170 | | -s: binary geoid-spheroid seperation file[[BR]] |
| 171 | | -m: Maximum size of output DEM in GB, will be overridden by specified resolution. Note this does change the output resolution[[BR]] |
| 172 | | -f: Do not fill nulls or smooth, i.e. do not run the command r.fillnulls and r.neighbours on the DEM before outputting[[BR]] |
| | 162 | -a: Directory containing ASTER tiles only. If not given then script[[BR]] |
| | 163 | calculates tiles to use[[BR]] |
| | 164 | -n: Navigation file to use, sbet or sol[[BR]] |
| | 165 | |
| 177 | | * Create an ASTER DEM jpg image from tiles in a directory: |
| 178 | | * {{{asterdem.sh -a aster_tiles/ -j a_dem_filename.jpg}}} |
| 179 | | * Project some ASTER tiles to a UKBNG projection and output the DEM to a_dem_filename.dem (Separation file uk_separation_file_WGS84LL.dem is used automatically): |
| 180 | | * {{{asterdem.sh -a aster_tiles/ -p UKBNG -o a_dem_filename.dem}}} |
| 181 | | * Project some ASTER tiles to a utm30n projection and output the DEM to a_dem_filename.dem: |
| 182 | | * {{{asterdem.sh -a aster_tiles/ -p UTM30N -o a_dem_filename.dem}}} |
| 183 | | * Project some ASTER tiles to a proj4 string projection: |
| 184 | | * {{{asterdem.sh -a aster_tiles/ -p "+proj=utm +zone=30 +ellps=WGS84 +datum=WGS84" -o a_dem_filename.dem}}} |
| 185 | | * Project some ASTER tiles to a proj4 projection using a separation file of your own making: |
| 186 | | * {{{asterdem.sh -a aster_tiles/ -p "+proj=utm +zone=30 +ellps=WGS84 +datum=WGS84" -o a_dem_filename.dem -s my_separation_file.dem}}} |
| 187 | | * Create an ASTER DEM in and leave it in a grass database and do not fill nulls or smooth the DEM: |
| 188 | | * {{{asterdem.sh -a aster_tiles/ -f}}} |
| 189 | | * Create an ASTER DEM and cap the maximum size of the DEM to 2 gigabytes: |
| 190 | | * {{{asterdem.sh -a aster_tiles/ -o a_dem_filename.dem -m 2}}} |
| 191 | | * Create an ASTER DEM and define the output resolution, where 2 is metres because of the UKBNG projection: |
| 192 | | * {{{asterdem.sh -a aster_tiles/ -p UKBNG -r 2.0 -o a_dem_filename.dem}}} |
| 204 | | ==== Using lidardem.sh ==== |
| 205 | | 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: |
| 206 | | |
| 207 | | lidardem.sh[[BR]] |
| 208 | | [[BR]] |
| 209 | | Generates a binary LiDAR DEM from LAS/ASCII files[[BR]] |
| 210 | | [[BR]] |
| 211 | | Arguments:[[BR]] |
| 212 | | -d: Directory containing LiDAR data[[BR]] |
| 213 | | or[[BR]] |
| 214 | | -f: LiDAR file to create DEM from[[BR]] |
| 215 | | (Optional)[[BR]] |
| 216 | | -h: Display usage and exit[[BR]] |
| 217 | | -o: Final output filename for DEM, defulats to leaving in grass database[[BR]] |
| 218 | | -c: Whether to use points of classification 7, defaults to just points of classification 1[[BR]] |
| 219 | | -a: Whether to use all returns, defaults to using first return only[[BR]] |
| 220 | | -r: Resolution to input LiDAR files with, defaults to 2[[BR]] |
| 221 | | -R: Resolution to output LiDAR files with, defaults to calculating from input resolution[[BR]] |
| 222 | | -j: Create a jpg image of the DEM[[BR]] |
| 223 | | -g: Grass database to use, defaults to creating a GRASS database locally[[BR]] |
| 224 | | -t: Whether to use ASCII files to create the DEM, defaults to using LAS files[[BR]] |
| 225 | | -z: Specify an input projection[[BR]] |
| 226 | | -p: Projection to output DEM in: proj4 string or UKBNG or ll or UTM[zero_padded_number](N|S)[[BR]] |
| 227 | | -s: geoid-spheroid separation file[[BR]] |
| 228 | | -m: Maximum size of output DEM in GB, will be overridden by specified resolution[[BR]] |
| 229 | | -N: North buffer, defaults to 2000[[BR]] |
| 230 | | -S: South buffer, defaults to 2000[[BR]] |
| 231 | | -E: East buffer, defaults to 2000[[BR]] |
| 232 | | -W: West buffer, defaults to 2000[[BR]] |
| 233 | | -F: Do not filter the DEM[[BR]] |
| 234 | | -E: Extrapolate the DEM, followed by the resolution to extrapolate at[[BR]] |
| 235 | | |
| 236 | | Examples: |
| 237 | | * Create a LiDAR DEM from UKBNG LAS files in the directory and output the a file called lidar_file.dem |
| 238 | | * {{{lidardem.sh -d las1.0 -o lidar_file.dem}}} |
| 239 | | * Create a LiDAR DEM from utm30n LAS files in the directory and output the a file called lidar_file.dem |
| 240 | | * {{{lidardem.sh -d las1.0 -z UTM30N -o lidar_file.dem}}} |
| 241 | | * Create a LiDAR DEM from lat/lon LAS files in the directory and output the a file called lidar_file.dem |
| 242 | | * {{{lidardem.sh -d las1.0 -z ll -o lidar_file.dem}}} |
| 243 | | * Create a LiDAR DEM from a proj4 string LAS files in the directory and output the a file called lidar_file.dem |
| 244 | | * {{{lidardem.sh -d las1.0 -z "+proj=utm +zone=30 +ellps=WGS84 +datum=WGS84" -o lidar_file.dem}}} |
| 245 | | * Create a LiDAR DEM from txt files and use points of all classification and return number |
| 246 | | * {{{lidardem.sh -d txt -t -c -a}}} |
| 247 | | * Create a LiDAR DEM from txt files using an input resolution of 3 and ouput of 10 |
| 248 | | * {{{lidardem.sh -d txt -t -r 3 -R 10}}} |
| 249 | | * Read in LAS files in projection UKBNG and project to ll (separation file uk_separation_file_UKBNG.dem is used by default) |
| 250 | | * {{{lidardem.sh -d las1.0 -p ll}}} |
| 251 | | * Read in a LAS file and extrapolate it with resolution 50 |
| 252 | | * {{{lidardem.sh -f las_file -E 50}}} |
| 253 | | |
| 277 | | -o: Final output filename for DEM, defulats to leaving in grass database[[BR]] |
| 278 | | -c: Whether to use points of classification 7, defaults to just points of classification 1[[BR]] |
| | 200 | -j: Create a jpg image of the DEM, followed by filename[[BR]] |
| | 201 | -t: Whether to use ASCII files to create the DEM, defaults to using LAS[[BR]] |
| | 202 | files. It is suggested to use this option if the las file are very[[BR]] |
| | 203 | large[[BR]] |
| | 204 | -b: Whether to calculate buffer, defaults to using NSEW buffer size of [[BR]] |
| | 205 | 2km (Projection may vary)[[BR]] |
| | 206 | -p: Projection to output DEM in:[[BR]] |
| | 207 | input proj4 string or UKBNG or ll or UTM[zero_padded_number](N|S)[[BR]] |
| | 208 | [[BR]] |
| | 209 | (Power Users)[[BR]] |
| | 210 | -c: Whether to use points of classification 7, defaults to just points [[BR]] |
| | 211 | of classification 1[[BR]] |
| 294 | | * 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 |
| 295 | | * {{{lidar_aster_dem.sh -d las1.0 -A aster_tiles -o a_dem_filename.dem}}} |
| 296 | | * 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 |
| 297 | | * {{{lidar_aster_dem.sh -d las1.0 -z UTM30N -A aster_tiles -o a_dem_filename.dem}}} |
| 298 | | * 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 |
| 299 | | * {{{lidar_aster_dem.sh -d las1.0 -A aster_tiles -N 100 -S 100 -E 100 -W 100-o a_dem_filename.dem}}} |
| 300 | | |
| 301 | | |
| 302 | | |
| 303 | | |
| 304 | | |
| 305 | | |
| 306 | | |
| 307 | | |
| 308 | | |
| 309 | | |
| 310 | | |
| 311 | | |
| 312 | | |
| 313 | | |
| 314 | | |
| 315 | | |
| 316 | | |
| 317 | | |
| | 233 | * 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_filename.dem (Uses default buffer size of 2000 in all directions |
| | 234 | * {{{lidar_aster_dem.sh -l las1.0 -A aster_tiles -o a_dem_filename.dem}}} |
| | 235 | * Create a LiDAR ASTER DEM by calculating ASTER tiles and utm30N las files in las1.0 and output to a file called dem_filename.dem (Uses default buffer size of 2000 in all directions |
| | 236 | * {{{lidar_aster_dem.sh -l las1.0 -z UTM30N -A aster_tiles -o a_dem_filename.dem}}} |
| | 237 | * Create a LiDAR ASTER DEM from tiles in directory aster_tiles and las file las_file.LAS and output to a file called dem_filename.dem, use buffer size of 100 in all directions |
| | 238 | * {{{lidar_aster_dem.sh -l las_file.LAS -A aster_tiles -N 100 -S 100 -E 100 -W 100 -o a_dem_filename.dem}}} |