In my opinion there is an problem with ECW driver in the Windows
version of GDAL and huge size of the input files.
I did not yet reproduce it on my hardware, but I have a report from
another user of GDAL2Tiles about the halt of the rendering after some
time in MapTiler for a huge ECW. Is that you case as well?
On my Linux based rendering infrastructure I have never seen it and I
was tiling compressed ECW with size over 2 GB
(uncompressed more then 30 GB) without any problems.
Would it be hard for you to test the rendering workflow under Linux or
another UNIX on your hardware?
We should report this as a bug to GDAL trac, there was a similar kind
of problem (but not the same) a couple of month ago documented here:
http://trac.osgeo.org/gdal/ticket/803
> gdal2tiles -v -s ESPG:2276 -z 10 [file] [dest]
>
> After running the above command line, I get a popup window "Python.exe has
> stopped working" and the following error on the command line...
>
> ERROR 6: No translation an empty SRS to PROJ.4 format is known
This sounds like if the definition of the epsg:2276 was not correctly
loaded from the epsg database of GDAL for some reason.
Can you try to use this instead?
gdal2tiles -v -s http://www.spatialreference.org/ref/epsg/2276/ -z 10
[file] [dest]
Best regards,
Klokan Petr Pridal
--
http://blog.klokan.cz/
http://www.maptiler.org/
http://www.oldmapsonline.org/