gdal2tiles.py: generate_tilemapresource south/west should be west/south

[mj10777]

It seems that the original author made a mistake when writing this

At present it is:

<Origin x="%(south).14f" y="%(west).14f"/>

And should be:

<Origin x="%(west).14f" y="%(south).14f"/>

Even if this file is not really used, it should be corrected.

​http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification:

• sample of correct use:

<Origin x="-180" y="-90" />

[mj10777]

I have just noticed that also the BoundingBox code was also incorrect:

<BoundingBox minx="%(south).14f" miny="%(west).14f" maxx="%(north).14f" maxy="%(east).14f"/>

This should also be:

<BoundingBox minx="%(west).14f" miny="%(south).14f" maxx="%(east).14f" maxy="%(north).14f"/>

The final result looking like this:

<BoundingBox minx="-180.00000000000000" miny="-85.05113000000000" maxx="180.00000000000000" maxy="85.05113000000000"/>

[hamish]

patch to fix x & y swap in gdal2tiles.py

[hamish]

Hi,

patch against the latest gdal svn attached, it would be nice to have this one fixed as it causes problems for Geopaparazzi.

​https://github.com/geopaparazzi/geopaparazzi/wiki#gdal

see also ticket #4670 "gdal2tiles generates tilemapresource.xml with inconsistent SRS/Coordinates" (epsg 900913 vs 4326: should <SRS> match the coord bounds in BoundingBox or the native projection of the tile's image data?)

thanks, Hamish

[Even Rouault]

trunk r27348, branches/1.11 r27349 "gdal2tiles.py: fix inverted long/lat in BoundingBox and Origin elements of tilemapresource.xml (patch by hamish, #5336)"