Of course, everyone knows that. The question is whether gdal2tiles, which explicitly calls 900913, will run at all without that 'fake' code being recognized by GDAL and its projection sources. And how to ensure that gdal2tiles does in fact run.
More recent versions seem to implement 900913 to ensure this, but I cannot get the latest stable (1.7.2) gdal to do so. Thank you though -- sorry if I was unclear in my request. On Wed, Jul 28, 2010 at 5:10 PM, Jean-Claude REPETTO <jrepe...@free.fr>wrote: > Le 28/07/2010 14:05, Jeffrey Warren a écrit : > > I'm getting this error when running gdal2tiles.py with even default >> parameters, on files which run fine on another separate machine: >> >> ERROR 6: EPSG PCS/GCS code 900913 not found in EPSG support files. Is >> this a valid EPSG coordinate system? >> >> > No, the correct code for Google Maps is EPSG:3857. > > < > http://www.epsg-registry.org/report.htm?type=selection&entity=urn:ogc:def:crs:EPSG::3857&reportDetail=short&style=urn:uuid:report-style:default-with-code&style_name=OGP%20Default%20With%20Code&title=EPSG:3857 > > > > Jean-Claude > _______________________________________________ > 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
