Custom Query (419 matches)


Show under each result:

Results (97 - 99 of 419)

Ticket Resolution Summary Owner Reporter
#287 fixed Azspec adds extra blank lines to the end of some level 1 files benj benj

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 (attached) to chop blank lines off the end of affected level 1 BIL files.

#303 fixed ASCII file reading default format code needed harg benj

It would be nice if the file > open dialog had the format code to match our ASCII files by default. Specifically: " txyzicr#"

Also the description of the format code needs to be made clearer.

#304 duplicate File appears black when opened harg benj

If you open /users/rsg/arsf/arsf_data/2009/flight_data/uk/UR09_01-2009_327_Flood_Cumbria/delivery/20100107/UR09_01/ascii_laser/LDR-UR09_01-200932701.txt in LAG, it doesn't produce an error but comes up blank. If you alter the point size it then comes back, but is apparently not the same problem as what happens if there's a point a long wway out of bounds.

Note: See TracQuery for help on using queries.