Changes between Initial Version and Version 4 of Ticket #1501


Ignore:
Timestamp:
Mar 26, 2007, 9:56:00 PM (17 years ago)
Author:
warmerdam
Comment:

Quentin,

I appologise for the delay in addressing this. There is an undocumented option called GEODATA_USAGE which by default I set to NONE to suppress all the ECW SDK code to write coordinate systems. I do this because I prefer my own coordinate system writer for jpeg2000.

But if you set this to GML, the ECW SDK will be used to write ECW SDK style GML headers. 

eg.
 gdal_translate -of JP2ECW -co PROJ=GEODETIC -co DATUM=WGS84 1.tif out.jp2 -co GEODATA_USAGE=GML

In some cases you might even find you have to use the GEOJP2=OFF and GMLJP2=OFF creation options to supress GDAL's own coordinate system writers.

I'm hesitant to document this special option though as I think any documentation I prepare is going to be confusing to many users. I suppose though, I should remove the PROJ and DATUM creation options from the JP2ECW driver then.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1501

    • Property Priority highest → normal

  • Ticket #1501 – Description

    initial v4  
    1 {{{
    21When trying to assign a specific ERMapper projection/datum string to a JP2ECW file, the PROJ= and DATUM= creation options are ineffective.
    32The resulting jp2 file appears to have no projection info embedded.
    43
     4{{{
    55E.g. (src.tif being any baseline tiff + tfw file):
    66"gdal_translate -of JP2ECW -co PROJ=GEODETIC -co DATUM=WGS84 src.tif dest.jp2"
     7}}}
    78"gdalinfo dest.jp2" does not report any projection. Close examination of the binary/hex contents of the file suggests that none gets written.
    89
    … …  
    1213
    1314~Quentin S.
    14 }}}