Does this apply to the 4.x read-only version of the ERDAS ECW/JP2 SDK as well as the old 3.3 SDK?
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Even Rouault Sent: Thursday, 1 September 2011 9:38 AM To: [email protected] Subject: Re: [gdal-dev] ECW writing (was GTiff optimisation) > > But the ecwhdr utility that Jean-Claude mentionned is really what you would > want to use, if you indeed just want to alter the projection info and/or > georeferenced bounds. I thought that there was only a Erdas utility to > achieve that, cool to see that it can be done with the SDK API. This gives > me the idea that the ECW driver could be enhanced to implement the > SetGeoTransform() and SetProjection() API, as well as some special > metadata (likely PROJ and DATUM to be consistant with the creation > options) through SetMetadataItem() to explicitely set the datum and > projection codes. Then a simple python script could use those new > capabilities to offer a service equivalent to the one of the ecwhdr > utility. This would have the advantage of being available through GDAL as > soon as the ECW driver has been compiled. I think I'm going to give it a > try. Implemented in http://trac.osgeo.org/gdal/ticket/4220 . Tested on Linux for now. If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments. Please consider the environment before printing this email. _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
