[gdal-dev] Re: TMS BoundingBox/Origin coordinates always in
lat/lon using gdal2tiles.py?
Klokan Petr Přidal
klokan at klokan.cz
Thu Dec 11 19:19:12 EST 2008
I used a lot of the old code from old version of GDAL2Tiles when
implementing tilemapresource.xml generation, so it is possible there
are those bugs in it.
There is practically no software reading this xml file yet, so I did
not paid enough attention probably.
But it should be correct for sure once it is generated.. so I will patch it.
Can you please create a ticket for this issue in the GDAL trac? We can
continue with solution under that ticket.
Klokan Petr Pridal
On Thu, Dec 11, 2008 at 6:24 PM, Jason Beverage <jasonbeverage at gmail.com> wrote:
> I also just noticed that the lat and lon are reversed for the Origin and
> BoundingBox. x should correspond to longitude and y should correspond to
> latitude, but they are switched.
> On Thu, Dec 11, 2008 at 10:35 AM, Jason Beverage <jasonbeverage at gmail.com>
>> Hi all,
>> I've been playing around with gdal2tiles in the OSG4W distribution and
>> noticed that the BoundingBox and Origin elements of the generated
>> tilemapresource.xml file that is generated always seems to be in lat/lon
>> coordinates, even when the output map is in Mercator. Other TMS resources
>> I've seen keep the coordinates in meters if its mercator and lat/lon if it
>> is geodetic.
>> Is this a "bug" or a "feature"?:)
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
More information about the gdal-dev