Changes between Version 87 and Version 88 of Procedures/EagleHawkProcessing
- Timestamp:
- Jun 19, 2015, 11:19:42 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/EagleHawkProcessing
v87 v88 85 85 === SCTs === 86 86 87 The script will have produced 21 iterations of each flightline, with a range of sct values. SCT is a timing offset which affects the position and geometry of the image. Currently they range from -0.1 to 0.1 seconds. A BIL file will have been produced for each version, which will be put in <project>/processing/hyperspectral/flightlines/georeferencing/mapped. You will need to go through these using [ wiki:Processing/tuiview tuiview] and find the BIL file that looks correct, and note down the sct value. You usually determine the correct image by the amount of wobble in the image. Lines with an incorrect offset will cause kinks in straight lines such as roads where the plane trajectory wobbles. Selecting the image with the straight road is usually what is required. You can use .sync file created together with the config file to store correct SCT values.87 The script will have produced 21 iterations of each flightline, with a range of sct values. SCT is a timing offset which affects the position and geometry of the image. Currently they range from -0.1 to 0.1 seconds. A BIL file will have been produced for each version, which will be put in <project>/processing/hyperspectral/flightlines/georeferencing/mapped. You will need to go through these using [https://arsf-dan.nerc.ac.uk/trac/wiki/Downloads/Processing/tuiview tuiview] and find the BIL file that looks correct, and note down the sct value. You usually determine the correct image by the amount of wobble in the image. Lines with an incorrect offset will cause kinks in straight lines such as roads where the plane trajectory wobbles. Selecting the image with the straight road is usually what is required. You can use .sync file created together with the config file to store correct SCT values. 88 88 89 89 Once you have the correct values, write them on the ticket for the relevant flight. If you wrote the values to the .sync file, the script 'sync_to_wiki_table.py' can help with this.