[gdal-dev] JAXAPalsar 1.0 & 1.1 extended metadata reading support

[Brent Fraser]

Has there been any progress in reading AVNIR2 data?  GDAL's ceos driver 
doesn't support georeferencing...

Best Regards,
Brent Fraser


On 6/27/2011 6:56 AM, Rodolfo Bonnin wrote:
> Hello Antonio,
>
> I'll read the specs regarding JaxaPalser type, out software is reading 
> those and they look well, but I didn't analyze the format in detail. 
> I've also added georeferencing (Calculating the affine transform based 
> on the 4 corners and assigning a coordinate system (WGS84 instead of 
> ITRF97 at the moment as we are based on 1.8.0) to the JaxaPalsar driver.
>
> For the time being, I'm writing new drivers for the PRISM and AVNIR2 
> sensors, based on the current JaxaPalsar driver, as we are constrained 
> in time, but I think that once I send the code, the diffing could be 
> useful when writing the new unified driver. I'm ready to collaborate 
> if you think another approach could more useful. The idea is to have 
> PRISM and AVNIR2 support ASAP.
>
> Regards,
> Rodolfo Bonnin.
>
> 2011/6/26 Antonio Valentino <antonio.valentino at tiscali.it 
> <mailto:antonio.valentino at tiscali.it>>:
> > Hi Frank,
> >
> > Il 26/06/2011 13:42, Frank Warmerdam ha scritto:
> >> On 11-06-26 06:34 AM, Antonio Valentino wrote:
> >>> Hi Frank,
> >
> > [...]
> >
> >>> Looking deeper into the ceos2 code it seems to me that the 
> "recipe" for
> >>> decoding ALOS-PALSAR products do not match at all specifications I can
> >>> find at
> >>>
> >>> http://www.eorc.jaxa.jp/ALOS/en/doc/fdata/PALSAR_L10_J_ENa.zip
> >>>
> >>> Does that recipe refers to another format specification document?
> >>
> >> Antonio,
> >>
> >> I don't know.
> >
> > well, in this case I guess it is not a good idea to modify that recipe
> > in any manner
> >
> >>> Also, regarding the ceos2 driver in general, I didn't find an obvious
> >>> way to support CEOS products with multiple image files (like multi
> >>> polarization PALSAR or ALOS PRISM).
> >>
> >> Ah, that may well have been part of Phil's rationale for handling
> >> multi-polarization data with custom drivers.  I don't know how hard
> >> it would be to do so within the existing SAR_CEOS driver.
> >
> > OK, thank you for confirming my analysis
> >
> >> Possibly you could set up a multi-polarization driver based on the
> >> low level ceos2 code but with a somewhat different recipe mechanism?
> >
> > Yes I could try.
> >
> > A new CEOS multi-band driver could be used for ALOS (all three sensors)
> > and Landsat.
> > There are other sensors that could be interesting to support?
> > Where can I find pointers and format spec?
> >
> > ciao
> >
> > --
> > Antonio Valentino
> > _______________________________________________
> > gdal-dev mailing list
> > gdal-dev at lists.osgeo.org <mailto:gdal-dev at lists.osgeo.org>
> > http://lists.osgeo.org/mailman/listinfo/gdal-dev
> >
>
>
>
> -- 
> Ing. Rodolfo Bonnin
> SUR Emprendimientos Tecnológicos
>
> Perú 345  Piso 5to Oficina "B" (C1067AAG)
> Ciudad de Buenos Aires, Argentina
> Tel. +54 (11) 4342-2976/84
> rodolfobonnin at suremptec.com.ar <mailto:rodolfobonnin at suremptec.com.ar>
> www.suremptec.com <http://www.suremptec.com>
>
>
>
> _______________________________________________
> 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/20120605/9802a287/attachment.html>