[gdal-dev] PDS Reader error

Yann Chemin ychemin at gmail.com
Mon Dec 8 20:52:59 PST 2014


Hi Trent,

Just wondering, as even ISIS does not import it, do you know any guys
actually reading the rings images? What software do they use?
It might be worth just clarifying how they actually read them, even just
for the sake of pds2isis and sanitizing the gdal driver ...

Cheers,
Yann

On 9 December 2014 at 10:10, Hare, Trent <thare at usgs.gov> wrote:

> Michael,
>    This is an odd hybrid PDS/ISIS2 label. Before seeing this label I have
> only ever seen the "QUBE" label object within an ISIS2 file. This was
> *not* one of the PDS label options -- at least when the gdal reader was
> written. For rasters files within PDS (v3), as far as I understood, only
> the "^IMAGE" or "^SPECTRAL_QUBE" were allowed. I don't know the heritage of
> this label or when it was implemented but it is a strange beast. This is
> one reason, among many others, that I have always placed a caveat on the
> GDAL PDS readers that it probably supports about 70% of PDS images. It
> obviously doesn't support this type or if the image section is compressed
> (e.g. MOC edrs), and it will always prefer if the image is map projected
> and the target is a planetary surface. This PDS label is not only an odd
> PDS/ISIS2 hybrid label it is an image of planetary rings(!) -- I think.
>
> As a check, the PDS importer in ISIS3 also fails.
> mag{8}> pds2isis from=FUV2004_183_03_24.LBL to=test.cub
> **PROGRAMMER ERROR** Unsupported axis order [AXIS_NAME = (BAND, LINE,
> SAMPLE)].
>
> Anyway, to possibly read the image you might be able to hack the label but
> this seems dangerous and would be probably still be missing something
> needed from the label (even though it kind-of works).
>
> change
> 1.) ^QUBE to ^IMAGE
> 2.) OBJECT = QUBE to OBJECT = IMAGE
> 3.) END_OBJECT = QUBE to END_OBJECT = IMAGE
>
> after
> 1.)  CORE_ITEM_BYTES               = 2
> SAMPLE_BITS = 16
>
> Again, gdalinfo will not fail but I have no idea if the data is being read
> correctly.
>
> For this hybrid label and the fact I think the target is planetary rings
> I'm not sure it would be worth trying to patch GDAL to support it...? Sorry
> - I haven't been much help.
>
> good luck!
> Trent
>
>
>
>
>
>
>
> On Mon, Dec 8, 2014 at 6:39 PM, K.-Michael Aye <kmichael.aye at gmail.com>
> wrote:
>
>>   An old bug (or lack of implementation) that supposedly was fixed in
>> GDAL 1.9.0 as mentioned in this message:
>>  http://lists.osgeo.org/pipermail/gdal-dev/2014-July/039508.html
>>
>> might have crept up again. Or, possibly, it is just another version of
>> the endless parameter space of the format of PDS3 binary files that the PDS
>> reader understandably could not yet account for until somebody tried it on
>> this older data.
>>
>> I am trying to read the Cassini UVIS data file in this linked zip:
>>
>> https://dl.dropboxusercontent.com/u/139035/PDSdata-2014-12-08T17-04-46-08-00.zip
>>
>> and am getting the same errors as mentioned in above forum post:
>>
>> In [8]: gdal.Open('./FUV2004_183_03_24.LBL')
>> ERROR 1: Sample_bits of 0 is not supported in this gdal PDS reader.
>>
>> In [9]: gdal.Open('./FUV2004_183_03_24.DAT')
>> ERROR 4: `./FUV2004_183_03_24.DAT' not recognised as a supported file
>> format.
>>
>>
>> In [10]: gdal.VersionInfo()
>> Out[10]: '1110100'
>>
>>
>> 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
>>
>
>
> _______________________________________________
> 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/20141209/3356deb5/attachment-0001.html>


More information about the gdal-dev mailing list