[gdal-dev] VICAR format

Thu Dec 4 14:53:31 PST 2014

Michael,
   For some PDS releases, you may find a PDS detached label (*.lbl)
pointing at a Vicar file. The PDS label contains a calculate-able
"skipbytes" amount to jump over the original vicar label so that it can get
to the start of the pixel stream. For your case, indeed the *.lbl is a PDS
label pointing inside the vicar image. The *.img is actually a fully formed
vicar file also renamed to a normal *.img extension. The Vicar file may
have originally had no extension, a *.img extension, or I have seen the
extension *.02 also.

Anyway, the GDAL PDS should be able to open this file using *.lbl but...

For others not familiar with planetary data, the image you mentioned is not
map projected (see gdalinfo run below). The PDS and ISIS readers were
really written for derived (map projected -- aka GIS-ready) images. The use
of "raw" even if calibrated images in GDAL may have limited uses besides
access to the pixels. Don't expect GDAL to be able to map project (or
orthorectify) this image. That is why ISIS and VICAR exist which contain
the camera models for many of the instruments used in planetary research.

-Trent

ast{86}> gdalinfo N1466584989_1_CALIB.LBL
Driver: PDS/NASA Planetary Data System
Files: N1466584989_1_CALIB.LBL
       N1466584989_1_CALIB.IMG
Size is 1024, 1024
Coordinate System is `'
Metadata:
  BANDWIDTH=
  CENTER_FILTER_WAVELENGTH=
  DATA_SET_ID="CO-S-ISSNA/ISSWA-2-EDR-V1.0"
  FILTER_NAME=("CL1","CL2")
  INSTRUMENT_ID="ISSNA"
  INSTRUMENT_NAME="IMAGING SCIENCE SUBSYSTEM NARROW ANGLE"
  MISSION_NAME="CASSINI-HUYGENS"
  NOTE=
  PRODUCER_INSTITUTION_NAME=
  PRODUCT_CREATION_TIME=2011-01-20T00:33:43
  PRODUCT_ID="1_N1466584989.132"
  PRODUCT_TYPE=
  SPACECRAFT_NAME=
  TARGET_NAME="MIMAS"
Corner Coordinates:
Upper Left  (    0.0,    0.0)
Lower Left  (    0.0, 1024.0)
Upper Right ( 1024.0,    0.0)
Lower Right ( 1024.0, 1024.0)
Center      (  512.0,  512.0)
Band 1 Block=1024x1 Type=Float32, ColorInterp=Undefined
  NoData Value=-3.40282265508890445e+38

On Thu, Dec 4, 2014 at 3:13 PM, K.-Michael Aye <kmichael.aye at gmail.com>
wrote:

>  I’m not sure now if this image (‘N1467346388_2_CALIB.IMG’) is actually a
> VICAR image.
> The unix `file` command recognizes it as a VICAR image:
>
>  ❯ file N1467346388_2_CALIB.IMG
>                 [3:12:31 PM]
> N1467346388_2_CALIB.IMG: VICAR image data
>
> but NASAView’s full label view shows me this:
>
>  OBJECT = IMAGE_HEADER<CR><LF>
>       INTERCHANGE_FORMAT = ASCII<CR><LF>
>       HEADER_TYPE = VICAR2<CR><LF>
>       BYTES = 4096<CR><LF>
>       RECORDS = 1<CR><LF>
>       DESCRIPTION = "Original VICAR2 header, updated by CISSCAL.”<CR><LF>
>
> So this sounds like maybe a previous VICAR image has been converted to a
> more standard PDS format?
> Maybe Trent knows more about this.
>
> Michael
>
>  —
> Michael Aye
> Cassini UVIS and MAVEN IUVS team
> LASP, Boulder CO
>
>  On Dec 4, 2014, at 2:47 PM, K.-Michael Aye <kmichael.aye at gmail.com>
> wrote:
>
> Apparently, the PDS reader works in this case, not sure if it would work
> on all VICAR images?
>
> Currently I’m trying to read Cassini ISS images and before I made the
> mistake to provide the .IMG file instead of the .LBL file to the reader.
> Opening the .LBL label file (that links to the .IMG file) is successful
> and I get the image out of it. I have confirmed via
> ds.GetDriver().GetDescription() that the PDS GDAL driver opened the file.
>
> Michael
> —
> Michael Aye
> Cassini UVIS and MAVEN IUVS team
> LASP, Boulder CO
>
>  On Dec 4, 2014, at 12:23 PM, Hare, Trent <thare at usgs.gov> wrote:
>
> Michael,
>    Yes - Sebastian Walters created one. I'm not clear if the driver will
> be pushed into the public version of GDAL? I know it is being used by the
> HRSC Team to convert to their VICAR products to GeoTiff (DEMs) and
> Jpeg2000.(images). If it does get pushed into GDAL then I would recommend
> the gdal/frmts/pds/ directory alongside other like formats.
>
> see page: 185
>  http://pubs.usgs.gov/of/2014/1056/pdf/ofr2014-1056.pdf
>  from: http://pubs.er.usgs.gov/publication/ofr20141056
>
> Probably worth asking Sebastian his intentions.
>
> Regards,
> Trent
>
> On Thu, Dec 4, 2014 at 12:21 PM, Frank Warmerdam<warmerdam at pobox.com>
> wrote:
>
>> Michael,
>>
>> I thought it existed, but digging around in the formats directory it
>> appears not to.  It would be nice to add.
>>
>> Best regards,
>> Frank
>>
>>
>>
>> On Thu, Dec 4, 2014 at 11:12 AM, K.-Michael Aye<kmichael.aye at gmail.com>
>> wrote:
>>
>>>   Hello all,
>>>
>>> Has anybody worked on implementing a VICAR reader yet?
>>>
>>> http://www-mipl.jpl.nasa.gov/external/vicar.html
>>>
>>> It’s pretty important for a bit older NASA data.
>>>
>>> Regards,
>>> Michael
>>>
>>> —
>>> Michael Aye
>>> Cassini UVIS and MAVEN IUVS team
>>> LASP, Boulder CO
>>>
>>> _______________________________________________
>>> gdal-dev mailing list
>>> gdal-dev at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>>>
>>
>>
>>
>> --
>>
>> ---------------------------------------+--------------------------------------
>> I set the clouds in motion - turn up   | Frank Warmerdam,
>> warmerdam at pobox.com
>> light and sound - activate the windows |http://pobox.com/~warmerdam
>> and watch the world go round - Rush    | Geospatial Software Developer
>>
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20141204/f92724ab/attachment.html>