Context Navigation

Changes between Initial Version and Version 1 of Ticket #683, comment 9

initial	v1
17	17	Same to what we have in our config files from that year.
18	18
19		However, flightlines present offset likely caused for a wrong boresight value and in the case of Eagle line 5, an SCT error.
	19	However, flightlines present offset likely caused for a wrong boresight value applied to the hdf files (from where the navigation was extracted). I tried to process aplmap with boresight values 0.1, 0.2, -1.1 and variations in negative symbols but the best fit still for boresight 0, 0, 0 rather than any other meaning the above values were already applied to the hdf files (and the extracted nav files as it was expected).
	20
	21	In the case of Eagle line 5 there is a large SCT error causing wobbly geocorrection.