Changes between Version 14 and Version 15 of Processing/PixelSize

Timestamp:

Mar 14, 2014, 4:18:18 PM (11 years ago)

Author:

mark1

Comment:

--

Processing/PixelSize

@@ -16 +16 @@
 
 Logsheets provided by ARSF contain the altitude from GPS.  One must compensate for the average terrain height when using the reckoner above.  For example, if your data is over coast areas and thus at sea level, the numbers are fine as is.  If your data is over a mountain valley, one should subtract the average height of the terrain from the logsheet altitude, then use that ground-altitude in the table above.
+
+== APL pixel spacing information ==
+
+When you run through APL it will output some information on the average nadir pixel spacing, that will look similar to this from apltran:
+
+{{{
+Average nadir pixel sizes in along track, across track are: 5.344909793 2.543426218
+Average nadir pixel sizes in projected X,Y are: 3.934267472 4.212970885
+}}}
+
+and repeated in aplmap:
+
+{{{
+Average nadir pixel size East: 3.934267472 North: 4.212970885
+}}}
 
 == azgcorr-based pixel size ==