Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
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.valent...@tiscali.it mailto:antonio.valent...@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@lists.osgeo.org mailto:gdal-dev@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 rodolfobon...@suremptec.com.ar mailto:rodolfobon...@suremptec.com.ar www.suremptec.com http://www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
Hi Frank, Il 18/06/2011 14:38, Frank Warmerdam ha scritto: On 11-06-18 02:59 AM, Antonio Valentino wrote: [CUT] 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) [CUT] 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. 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? 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). Did I missed something? regards -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
On 11-06-26 06:34 AM, Antonio Valentino wrote: Hi Frank, Il 18/06/2011 14:38, Frank Warmerdam ha scritto: On 11-06-18 02:59 AM, Antonio Valentino wrote: [CUT] 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) [CUT] 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. 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. 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. Possibly you could set up a multi-polarization driver based on the low level ceos2 code but with a somewhat different recipe mechanism? Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com 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 gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
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@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
Hi Rodolfo, can you please confirm that the data type of PALSAR Level 1.5 products should be GDT_UInt16 and not GDT_Int16 as in current implementation? If so I will file a ticket with a patch for fixing the issue. thanks Il 17/06/2011 21:28, Rodolfo Bonnin ha scritto: Hello all, I'm just working with some JAXAPalsar images, and I've discovered that there is no retrieval of the coordinate system metadata retrieval in the current driver, the driver documentation says georeferencing is only supported in level 1.5. Has anyone tried to implement the feature for this lower level? I have gathered some good information about how this could be done, but in order to exempt myself to repeat effort, I prefer to consult the list beforehand. Many thanks in advance. -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
Hi,
Il 25/06/2011 12:48, Antonio Valentino ha scritto:
Hi Rodolfo,
can you please confirm that the data type of PALSAR Level 1.5 products
should be GDT_UInt16 and not GDT_Int16 as in current implementation?
If so I will file a ticket with a patch for fixing the issue.
thanks
... here it is the patch in case you want to give it a try
ciao
Il 17/06/2011 21:28, Rodolfo Bonnin ha scritto:
Hello all,
I'm just working with some JAXAPalsar images, and I've discovered that
there is no retrieval of the coordinate system metadata retrieval in
the current driver, the driver documentation says georeferencing is
only supported in level 1.5.
Has anyone tried to implement the feature for this lower level? I have
gathered some good information about how this could be done, but in
order to exempt myself to repeat effort, I prefer to consult the list
beforehand.
Many thanks in advance.
--
Antonio Valentino
Index: gdal/frmts/jaxapalsar/jaxapalsardataset.cpp
===
--- gdal/frmts/jaxapalsar/jaxapalsardataset.cpp (revisione 22579)
+++ gdal/frmts/jaxapalsar/jaxapalsardataset.cpp (copia locale)
@@ -232,7 +232,7 @@
nFileType = level_11;
}
else {
-eDataType = GDT_Int16;
+eDataType = GDT_UInt16;
nFileType = level_15;
}
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
I have another doubt regarding the adfGeoTransform to be employed. The JaxaPalsar has 8 coefficients to represent the mapping between pixel-line and the map projection frame of reference ( It includes de P L factor for X and Y, and gdal doesn't I think ). What should If the PL factor is not near 0? Should I generate additional control points? Thanks for your help. Regards, Rodolfo. 2011/6/20 Frank Warmerdam warmer...@pobox.com: On 11-06-18 12:59 PM, Antonio Valentino wrote: Regarding the JAXAPalsar driver, it is currently registered *after* the ceos2 driver so, if my understanding is correct, CEOS products should be opened with ceos2 and the JAXAPalsar should be used as a fallback. Is it correct? Antonio, Yes, if it is registered after the SAR_CEOS driver (frmts/ceos2) then it would only be used for datasets not recgonised by the SAR_CEOS driver. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com 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 gdal-dev@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 rodolfobon...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
On 11-06-22 04:31 PM, Rodolfo Bonnin wrote: Hello Antonio, Frank, I've now been able to read the false northing UTM parameter. The next step is the coordinate system, which is ITRF 97. As this is not a well known coordinate system, could this definition be enough to represent the standard? (from spatialreference.org): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ GEOCCS[ITRF97, DATUM[International Terrestrial Reference Frame 1997, SPHEROID[GRS 1980,6378137.0,298.257222101, AUTHORITY[EPSG,7019]], AUTHORITY[EPSG,6655]], PRIMEM[Greenwich,0.0, AUTHORITY[EPSG,8901]], UNIT[m,1.0], AXIS[Geocentric X,OTHER], AXIS[Geocentric Y,EAST], AXIS[Geocentric Z,NORTH], AUTHORITY[EPSG,4918]] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Rondolfo, In GDAL trunk I have added support for geocentric coordinate systems and the expansion of EPSG:4338 looks like: GEOCCS[ITRF97 (geocentric), DATUM[International_Terrestrial_Reference_Frame_1997, SPHEROID[GRS 1980,6378137,298.257222101, AUTHORITY[EPSG,7019]], AUTHORITY[EPSG,6655]], PRIMEM[Greenwich,0, AUTHORITY[EPSG,8901]], UNIT[metre,1, AUTHORITY[EPSG,9001]], AXIS[Geocentric X,OTHER], AXIS[Geocentric Y,OTHER], AXIS[Geocentric Z,NORTH], AUTHORITY[EPSG,4338]] I believe yours if functionally equivelent. Note that GDAL is unlikely to support geocentric coordinate systems in a useful fashion in 1.8 and earlier versions. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com 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 gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
Thanks Antonio, I've detected a way to at least read the UTM zone of the product, and will be back once I can get more data from the files, so we can think more carefully where the changes belong. Many thanks again. 2011/6/18 Antonio Valentino antonio.valent...@tiscali.it: Hi Frank, Il 18/06/2011 14:38, Frank Warmerdam ha scritto: 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. Thank you Frank. My basic idea was to propose an improvement of the ceos2 driver but I completely missed GetCeosField function. Sorry. Looking better to the code it seems that all tools for record decoding are already there, as you pointed out, so it is just a matter of getting more metadata. Regarding the JAXAPalsar driver, it is currently registered *after* the ceos2 driver so, if my understanding is correct, CEOS products should be opened with ceos2 and the JAXAPalsar should be used as a fallback. Is it correct? Any way I'm currently downloading some sample PALSAR product to see what happens. Best regards -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@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 rodolfobon...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
Hello Antonio, Frank, I've now been able to read the false northing UTM parameter. The next step is the coordinate system, which is ITRF 97. As this is not a well known coordinate system, could this definition be enough to represent the standard? (from spatialreference.org): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ GEOCCS[ITRF97, DATUM[International Terrestrial Reference Frame 1997, SPHEROID[GRS 1980,6378137.0,298.257222101, AUTHORITY[EPSG,7019]], AUTHORITY[EPSG,6655]], PRIMEM[Greenwich,0.0, AUTHORITY[EPSG,8901]], UNIT[m,1.0], AXIS[Geocentric X,OTHER], AXIS[Geocentric Y,EAST], AXIS[Geocentric Z,NORTH], AUTHORITY[EPSG,4918]] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Many thanks in advance. Best Regards, Ing. Rodolfo Bonnin 2011/6/22 Rodolfo Bonnin rodolfobon...@suremptec.com.ar: Thanks Antonio, I've detected a way to at least read the UTM zone of the product, and will be back once I can get more data from the files, so we can think more carefully where the changes belong. Many thanks again. 2011/6/18 Antonio Valentino antonio.valent...@tiscali.it: Hi Frank, Il 18/06/2011 14:38, Frank Warmerdam ha scritto: 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. Thank you Frank. My basic idea was to propose an improvement of the ceos2 driver but I completely missed GetCeosField function. Sorry. Looking better to the code it seems that all tools for record decoding are already there, as you pointed out, so it is just a matter of getting more metadata. Regarding the JAXAPalsar driver, it is currently registered *after* the ceos2 driver so, if my understanding is correct, CEOS products should be opened with ceos2 and the JAXAPalsar should be used as a fallback. Is it correct? Any way I'm currently downloading some sample PALSAR product to see what happens. Best regards -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@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 rodolfobon...@suremptec.com.ar www.suremptec.com -- 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 rodolfobon...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
On 11-06-18 12:59 PM, Antonio Valentino wrote: Regarding the JAXAPalsar driver, it is currently registered *after* the ceos2 driver so, if my understanding is correct, CEOS products should be opened with ceos2 and the JAXAPalsar should be used as a fallback. Is it correct? Antonio, Yes, if it is registered after the SAR_CEOS driver (frmts/ceos2) then it would only be used for datasets not recgonised by the SAR_CEOS driver. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com 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 gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
Hi Rodolfo, Il 17/06/2011 21:28, Rodolfo Bonnin ha scritto: Hello all, I'm just working with some JAXAPalsar images, and I've discovered that there is no retrieval of the coordinate system metadata retrieval in the current driver, the driver documentation says georeferencing is only supported in level 1.5. Has anyone tried to implement the feature for this lower level? I have gathered some good information about how this could be done, but in order to exempt myself to repeat effort, I prefer to consult the list beforehand. 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. 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. Best regards -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
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, warmer...@pobox.com 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 gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
Hi Frank, Il 18/06/2011 14:38, Frank Warmerdam ha scritto: 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. Thank you Frank. My basic idea was to propose an improvement of the ceos2 driver but I completely missed GetCeosField function. Sorry. Looking better to the code it seems that all tools for record decoding are already there, as you pointed out, so it is just a matter of getting more metadata. Regarding the JAXAPalsar driver, it is currently registered *after* the ceos2 driver so, if my understanding is correct, CEOS products should be opened with ceos2 and the JAXAPalsar should be used as a fallback. Is it correct? Any way I'm currently downloading some sample PALSAR product to see what happens. Best regards -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
[gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support
Hello all, I'm just working with some JAXAPalsar images, and I've discovered that there is no retrieval of the coordinate system metadata retrieval in the current driver, the driver documentation says georeferencing is only supported in level 1.5. Has anyone tried to implement the feature for this lower level? I have gathered some good information about how this could be done, but in order to exempt myself to repeat effort, I prefer to consult the list beforehand. Many thanks in advance. -- 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 rodolfobon...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
