Custom Query (432 matches)
Results (388 - 390 of 432)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #279 | knpa | mark1 | fixed | GB09/05, flight day 278c, Leighton moss |
| Description |
Data location: ~arsf/arsf_data/2009/flight_data/uk/GB09_05-2009_278c_Leighton_moss Data arrived from ARSF via SATA disk LETTER L on 7th October 2009. Scientific objective: /users/rsg/arsf/arsf_data/2009/ARSF_Applications/GB09-05.pdf Priority: alpha-4-low PI: A. Blackburn Sensors:
|
|||
| #287 | benj | benj | fixed | Azspec adds extra blank lines to the end of some level 1 files |
| Description |
Some Eagle and Hawk lines, when processed through azspec, acquire extra blank lines on the end of the level 1 file. Header dimensions are correct for the file as expected (not as it actually is) and ENVI just silently truncates what it's displaying, so this hasn't been noticed before. Became noticeable using fastQC for delivery checking. The actual data values for the data in the file are unaffected (values are very similar to those obtained through CaliGeo). Fixed promptly by Bill when reported, working from azspec.1.2.10. Raising (and closing) this ticket purely for tracking purposes. Use dimfixer.py (attached) to chop blank lines off the end of affected level 1 BIL files. |
|||
| #298 | chrfi | chrfi | fixed | using fence causes flight line colours to change |
| Description |
build number : 2010.01.18.1 system : pmpc974 to reproduce, open a selection of files (tested with 2, 3, 4, and 5 files) with fence unticked and any number of skipped points. Then click fence and select and area of the lines, click file, open and then check the fence box and click refresh. the expected result is to see the fenced area of the lines appear identically to when they were displayed as part of the overall lines. However the fenced lines display with different flight line colours. |
|||