Even,
I copied the newer data/cubewerx_extra.wkt over to the gdal 1.4.4 system
and that seems to have fixed the problem.
I'm curious why just adding 900913 to epsg did not work for gdal, but
did work for the mapserver which is projection the vectors on the fly.
-Steve
Even Rouault wrote:
Stephen Woodbridge wrote :
I added the 900913 definition to /usr/share/proj/epsg files as:
# Spherical Mercator - Google
<900913> +proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0
+x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgri...@null +no_defs
-Steve
Hello,
The official EPSG code for Googl
Even,
gdal 1.5.0 gives the correct result.
I added the 900913 definition to /usr/share/proj/epsg files as:
# Spherical Mercator - Google
<900913> +proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0
+x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgri...@null +no_defs
-Steve
Even Rouault wrote:
Step
Stephen,
Which version gives the right result ?
I've checked that GDAL SVN trunk (1.7.0dev) gives the same result as the one
you get with GDAL 1.5.2.
It looks like EPSG:900913 definition was added in data/cubewerx_extra.wkt for
GDAL 1.5.0. I've tested again with GDAL 1.4.4 and it doesn't even ma
Hi all,
I have a serious problem that you might be able to shed some light on.
I have a landsat geotif (actually lots of them) and when I projection
them on a systems with v1.5.2 and v1.4.4.0 I get very different results!
The image sizes are different, the projection info is different, the
p
