Changes between Version 1 and Version 2 of Processing/demcompare

Timestamp:

Sep 2, 2014, 11:59:00 AM (10 years ago)

Author:

stgo

Comment:

--

Processing/demcompare

@@ -6 +6 @@
 
 {{{
-demcompare.py -d lidarpatched.dem -n navfile.sol --lidar path/to/ascii
+demcompare.py -d lidarpatched.dem -n navfile.sol --lidar path/to/ascii -l projection
 }}}
+
+Unless you have an SSD available in your machine this will probably take a while.
 
 This will create a patched aster dem to compare to the lidar dem, this will not be smoothed and as such is the raw ASTER data. It will give 2 outputs on completion the first is only the area covered by the lidar files, the second is the area only covered by the lidar data. All outputs are in metres.
@@ -19 +21 @@
 }}}
 
-Which will skip the patching process and just give the dem outputs, if you ude identical dems the outputs will be 0.
+Which will skip the patching process and just give the dem outputs, if you use identical dems the outputs will be 0.
+
+There are a few other options for deeper analysis of dems, and analysis of trends over years