nsw_lidar
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
nsw_lidar [2019/02/10 13:59] – bushwalking | nsw_lidar [2020/08/31 22:31] – [Dumping Ground] allchin09 | ||
---|---|---|---|
Line 9: | Line 9: | ||
====== Resources ====== | ====== Resources ====== | ||
* [[https:// | * [[https:// | ||
- | * [[http:// | + | * [[http:// |
====== Topographic maps ====== | ====== Topographic maps ====== | ||
Line 24: | Line 24: | ||
The NSW DEM data is supplied in 2km squares. The squares need to be merged into a single DEM for further operations. | The NSW DEM data is supplied in 2km squares. The squares need to be merged into a single DEM for further operations. | ||
- | While this can be done in theory using a virtual raster, I have had poor performance with this. Any operation seems to result in screen redrawing, so moving around | + | Most of the eastern ranges, where a lot of bushwalking happens, are 2m DEMs. The coast is typically 1m, and the western slopes |
- | Instead, I generally use the the Raster- > Miscellaneous -> Merge... function | + | ==== Virtual Raster ==== |
+ | |||
+ | While merging can be done in theory using a Virtual Raster (Raster- > Miscellaneous -> Build Virtual Raster... ), I have had poor performance with this (including recent version 3.12 Bucuresti). Any operation seems to result in screen redrawing, so moving around and zooming in and out is slow and painful. | ||
+ | |||
+ | That said, if you are just using the Virtual Raster for future steps, then the limitations from the screen redrawing may not be important. | ||
+ | |||
+ | QGIS uses [[https:// | ||
+ | |||
+ | |||
+ | ==== Merge Raster ==== | ||
+ | |||
+ | I generally use the the Raster- > Miscellaneous -> Merge... function | ||
+ | |||
+ | |||
+ | QGIS uses [[https:// | ||
===== Fill Sinks ===== | ===== Fill Sinks ===== | ||
Line 62: | Line 76: | ||
For more options in compression, | For more options in compression, | ||
* GRASS : [[https:// | * GRASS : [[https:// | ||
+ | V.generalize can also be used to smooth contours - possibly best done prior to simplificiation | ||
==== Cleaning ==== | ==== Cleaning ==== | ||
Line 112: | Line 127: | ||
{{: | {{: | ||
- | The raster channel network can then be classified | + | ==== Classification ==== |
+ | |||
+ | For 1:25000 maps, I've had reasonable results from using the following formula in the Raster Calculator to classify the streams into categories. Different scales may need different bounds, | ||
+ | |||
+ | '' | ||
+ | |||
+ | * Intermittent: | ||
+ | * Minor: 6.15-7.4 | ||
+ | * Major: 7.4+ | ||
+ | |||
+ | ==== Convert to Vector and Simplify ==== | ||
+ | |||
+ | Convert | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The raw stream data is very jagged. Smooth using | ||
+ | * v.generalize | ||
+ | * Algorithm = Hermite (there are other options which can be used, but Hermite has the smoothed line passing through the points of the original) | ||
+ | * Maximal tolerance value = 20 (in m, obviously scale dependent) | ||
+ | |||
+ | Simplify using using: | ||
+ | * Vector geometry : Simplify | ||
+ | Tolerance:? | ||
===== Clifflines ===== | ===== Clifflines ===== | ||
- | The steps below have been tested | + | The steps below are being developed for use in the Blue Mountains, a region that has a significant number of relatively vertical sandstone cliffs. It may be less effective in different terrain. |
This is more a set of ideas than a fully fledged process. The main aims are to get a set of steps that can largely be automated, and that create cliffline vectors that are running in the correct direction. There is still some way to go on this! | This is more a set of ideas than a fully fledged process. The main aims are to get a set of steps that can largely be automated, and that create cliffline vectors that are running in the correct direction. There is still some way to go on this! | ||
Line 128: | Line 167: | ||
using DEM and [1] Maximum Triangle Slope (Tarboton (1997)). I haven' | using DEM and [1] Maximum Triangle Slope (Tarboton (1997)). I haven' | ||
- | Cliff areas can be identified using a range of 60-90 and 70-90 degrees on the Slope file. Using 60-90 degrees helps connect logical cliffs and avoid small breaks. | + | Cliff areas can be identified using a range of say 60-90 and 70-90 degrees on the Slope file. Using 60-90 degrees helps connect logical cliffs and avoid small breaks. |
==== Initial Cleaning ==== | ==== Initial Cleaning ==== | ||
Next convert data to 1 bit (1,2 not 0,1, as Sieve ignores 0s) using Raster Calculator. | Next convert data to 1 bit (1,2 not 0,1, as Sieve ignores 0s) using Raster Calculator. | ||
- | Formula is: (Slope > 0) + 1 | + | Formula is: (Slope > 60) + 1 |
Then Sieve resulting data using a Threshold of 100 and 8-connectedness to get rid of small non-connected cliffs. Note above that Sieve doesn' | Then Sieve resulting data using a Threshold of 100 and 8-connectedness to get rid of small non-connected cliffs. Note above that Sieve doesn' | ||
Line 179: | Line 218: | ||
Run v.clean: Cleaning Tool = rmdangle, Threshold = 5,10 | Run v.clean: Cleaning Tool = rmdangle, Threshold = 5,10 | ||
+ | ===== Dumping Ground ===== | ||
+ | [[https:// | ||
+ | [[https:// |
nsw_lidar.txt · Last modified: 2024/04/05 19:00 by bushwalking