MBTiles with ZXY-OSM Format is Not Supported?

[marhensa]

Hi, nice and awesome tool from you.. :)

I have a question.
Is it only supports MBTiles with TMS specification? --- The inverted Y one?

When I'm trying to use MBTiles with ZXY-OSM specification
(with normal Y from north to south), the map got upside down on each tile.

It seems TileServer.php automaticaly revert the Y order to the output:

• When the source is ZXY-TMS MBTiles (the reverted Y), the output on the map is correct.
• When the source is ZXY-OSM MBTiles (the normal Y), the output got upside down.

From my dummy-test MBTiles files, it would be seen like that.
The ZXY-TMS is got right, the ZXY-OSM got wrong. Both on z/x/y.jpg output and WMTS output.

---

It would be great if it supports both format, ZXY-TMS and ZXY-OSM in the future.

Because MBTiles will drop TMS format (inverted Y order, from south to north) in the future,
and start developing ZXY-OSM format (normal Y order from north to south).

As you can see here:
https://github.com/mapbox/mbtiles-spec#roadmap

"The MBTiles format will switch tile ordering to the XYZ schema popularized by OpenStreetMap and away from the Tile Map Service (TMS) specification."

[klokan]

TileServer is exposing XYZ out of the box. All clients speaks to TileServer in XYZ notation - not in TMS.

I don't know of any software which is producing the MBTiles format with internally XYZ addressing. Such MBTiles is in fact not MBTiles, because it is not according the MBTiles spec.

I think the XYZ tiles will come with the OGC GeoPackage - which would be great to support by TileServer.

[klokan]

@marhensa It would be great to have a sample file and a name of the software which produced it.

[marhensa]

okay, i'll link it later today.
i almost forgot how to create all these things.. :)

[klokan]

So far it is not part of the MBTiles specification - it is only mentioned on the roadmap.

Once the MBTiles spec contain officially the XYZ internal storage and there is a metadata value identifying this (version or something else) we can reopen this ticket again.