Changes between Version 14 and Version 15 of Processing/KnownProblems
- Timestamp:
- Nov 3, 2010, 5:25:15 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Processing/KnownProblems
v14 v15 120 120 121 121 Finally, doing that will shift a little bit of the data off the end of the flightline and you'll lose it. To recover this, take the offset you found in the previous step and add it on to the start time in the header file (we also add it to the end time, but actually I'm not sure that's necessary). You may want to back the header up first, or at least make a note of the old value. Once you've done that, re-run the processing with the -sSE option to azspec but with the -so option to aznav set to 0 (or omitted). 122 123 == Complaining about geoid-spheroid correction when there is none present == 124 125 {{{ 126 ** out of geoid-spheroid grid at c: -97 r: 110 cols: 83 rows: 90 127 ** rerun with full grid 128 129 ** DEM fatal error... 130 ** image corner out side geoid/spheroid limits 131 ** lat min: 49.75000 max: 60.87500 lng min: -7.50000 max: 2.75000 132 ** corner x: 569880.0 y: 7053870.0 lat: 63.60591 lng: -19.59104 133 ** gsep data covers UK only 134 }}} 135 136 You need to include `-es no` argument to azgcorr if there is no geoid-spheroid separation file needed.