On 11-06-18 02:59 AM, Antonio Valentino wrote:
I don't know if someone is currently working on the JAXAPalsar driver. Anyway I' very interested in extending driver for SAR products to get more metadata so I would be happy to help if you need.
Folks, Phil Vachon did most of the JAXA Palsar work but has moved on to non-geospatial pursuits, so anyone interested should feel free to dig in.
Palsar products are in CEOS format so IMHO it would be nice to setup a general mechanism to decode CEOS records (a similar job has been done for ENVISAT records recently) http://trac.osgeo.org/gdal/ticket/4105 http://trac.osgeo.org/gdal/attachment/ticket/4105/asar_metadata.patch The hard part (it is a very boring job) IMHO is to fill data structures that properly describe CEOS records for each sensor end product type. Anyway populating record descriptors is a job that can be done gradually and, hopefully, with the help of other users so we could start with the few metadata you are currently interested in and add other record descriptors later. The key is to setup a genereal (enough) framework for CEOS record decoding.
There is already a generic SAR CEOS driver (gdal/frmts/ceos2) with a CEOS record parsing mechanism. If that is what you want, please start from it. For reasons not immediately obvious to me Phil chose to build a specific JAXA Palsar driver but please think twice before building it out into a full generic CEOS driver duplicating what already exists. Best regards, -- ---------------------------------------+-------------------------------------- I set the clouds in motion - turn up | Frank Warmerdam, [email protected] light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush | Geospatial Programmer for Rent _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
