On 01/09/2011 14:23, Even Rouault wrote:
As I did not use DATUM and PROJ creation option GDAL don't add it!
Yes, the mapping between WKT representation and ECW DATUM/PROJ is not perfect,
especially in the WKT -> DATUM/PROJ direction (the other direction is simpler).
You could perhaps try the u
> I know why raster data made by GDAL show "RAW" string as projection
> information, documentation explain it:
> > When writing coordinate system information to ECW files, many less common
> > coordinate systems are not mapped properly. If you know the ECW name for
> the
> > coordinate system you c
Le jeudi 01 septembre 2011 10:39:50, Yves Jacolin a écrit :
> Le mercredi 31 août 2011 16:45:09, Jean-Claude Repetto a écrit :
> > Le 31/08/2011 14:13, Yves Jacolin a écrit :
> > > Another question: I have 2 000 ECW files (40 Mo each), 49 ECW files (1
> > > Go each) and 2 ECW files (2 Go each). I w
Le mercredi 31 août 2011 16:45:09, Jean-Claude Repetto a écrit :
> Le 31/08/2011 14:13, Yves Jacolin a écrit :
> > Another question: I have 2 000 ECW files (40 Mo each), 49 ECW files (1 Go
> > each) and 2 ECW files (2 Go each). I worked first on 2 Go ECW file, it
> > takes around 1 day to assign th
Le mercredi 31 août 2011 14:38:53, Even Rouault a écrit :
> It contains a possible workaround
> (altough you will find it quite ironic if you keep in memory what has been
> said previously in this thread about gdalwarp being slower than
> gdal_translate ;-)).
ouaaah, indeed it is really fast, the f
Le 31/08/2011 14:13, Yves Jacolin a écrit :
Another question: I have 2 000 ECW files (40 Mo each), 49 ECW files (1 Go each)
and 2 ECW files (2 Go each). I worked first on 2 Go ECW file, it takes around 1
day to assign the projection information in the files.
Do you think this is normal? How can
Hello Even,
Le mercredi 31 août 2011 14:38:53, Even Rouault a écrit :
> Selon Yves Jacolin :
> > List,
> >
> > I successfully assigned my projection information but still have some
> > difference in the file size. This is not so important but I wanted to
> > understand
> > the reason. Idea welcom
Selon Yves Jacolin :
> List,
>
> I successfully assigned my projection information but still have some
> difference in the file size. This is not so important but I wanted to
> understand
> the reason. Idea welcome :)
Yves,
You have a difference between the input file and the output file produced
Matt,
Thanks for the link but I already read this page and I have only one process
(assign projection information).
Anyway, this is always good to read this information !
List,
I successfully assigned my projection information but still have some
difference in the file size. This is not so im
Yves, it's best to use gdalwarp without any compression options and
then use gdal_translate as a last step to apply the compression. See
http://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp#GeoTIFFoutput-coCOMPRESSisbroken
for more.
cheers,
matt wilkie
--
t;
>
> - Original Message -----
> From: Yves Jacolin
> To: gdal-dev
> Cc:
> Sent: Tuesday, August 30, 2011 8:22:46 AM
> Subject: [gdal-dev] GTiff optimisation
>
> Hello,
>
> I am converting GTiff to GTiff in order to add projection and
> georeferencing
To: gdal-dev
Cc:
Sent: Tuesday, August 30, 2011 8:22:46 AM
Subject: [gdal-dev] GTiff optimisation
Hello,
I am converting GTiff to GTiff in order to add projection and georeferencing
information in the header. I am using gdalwarp with some flags, mailny -co
flags. I have some question about t
Hello,
I am converting GTiff to GTiff in order to add projection and georeferencing
information in the header. I am using gdalwarp with some flags, mailny -co
flags. I have some question about this.
Here is my command line:
gdalwarp -co "COMPRESS=PACKBITS" -co "PHOTOMETRIC=MINISWHITE" -co "NBI
13 matches
Mail list logo
