| | 1 | === Q: When I geocorrect data, Azgcorr stops and complains that the flightline has a turn in it - how can I process my data? === |
| | 2 | |
| | 3 | '''A:'''[[BR]] |
| | 4 | This means that the aircraft turned without turning off the sensor. Azgcorr was designed to process reasonably straight single survey lines and is not intended for use on flights including large turns - attempting to process such lines causes problems. There are two solutions to this: |
| | 5 | |
| | 6 | 1. (Easy solution) Process the flightline with an extra "-bend" option to azgcorr. This will override the turn check and allow processing to proceed. Be aware that this may cause the processing to segfault, and if it doesn't then it may not produce correct positioning. You are advised to check your results against vectors or other known good data. |
| | 7 | |
| | 8 | 2. (Harder solution) Process the flightline in pieces and leave out the bit that's got the bend in it. The easiest way to do this is to process as in 1 above to determine where the bend is on the line, then use the scan line numbers given in the processing run and a bit of trial and error to cut out the bend using the -l option: |
| | 9 | |
| | 10 | azgcorr ... -l <start_line> <end_line> ... |
| | 11 | |
| | 12 | This will geocorrect those parts of the flight between start_line and end_line. If for example you had a flightline that was 20000 lines long and had a bend from lines 7500 - 7900, you'd use two azgcorr commands: |
| | 13 | |
| | 14 | azgcorr ... -l 0 7500 ... |
| | 15 | azgcorr ... -l 7900 20000 ... |
| | 16 | |
| | 17 | This would produce two geocorrected images, each with one part of the line. |