[Mass-Market-GEO] Status of (WMS) tiling specification at OGC and OSGEO?
Klokan Petr Přidal
klokan at klokan.cz
Sun Aug 10 16:58:00 EDT 2008
I try to describe the difference between specifications (it is
simplified a bit).
If we will speak about the most wanted tiles for "Spherical Mercator"
http://spatialreference.org/ref/user/epsg900913/), the key is
compatibility with Google Maps and similar services (Microsoft,
Yahoo), which all uses the same projection - tiles covering the same
area in the same zoom level. It means you can combine/overlay
different map-sources exactly as it is done for example in:
(OpenLayers does the job).
It means the extent of available tiles and zoom (number of pixels per
meter) is predefined for the whole Earth. The difference between
tiling standards (OSGEO/OGC) is only in the URL you need to use to
access particular tile. Another difference is in the xml format of
metadata related to the service (think equivalent of WMS's
TileCache.org projects implements two OSGEO standards: WMS-C and TMS.
GDAL2Tiles is a generator of tiles compatible with TMS.
Do you know about any implementations of OGC tiling standards?
WMS-C is a normal WMS with a recommendation for client query, there is
no extension on the standard. The server guarantee to (quickly) answer
only the requests for extents which are defined by tiling scheme (and
are therefore compatible with other tiles). Any WMS server is serving
also WMS-C, but a WMS client needs to be modified into WMS-C - to send
only requests in predefined extents. True WMS-C server (like
tilecache) is not able to return raster for any extent, only for
extents predefined by tiling profile.
Example (shorten) of a tile request looks like normal WMS (this is
epsg:4326 so Global Geodetic Profile):
OSGEO Tile Map Service - TMS:
Tiles are requested in the REST form, so both dynamic generation (a la
tilecache.org) and pre-generation into static tiles (a la gdal2tiles)
The geographic extent is addressed by zoom level and tile coordinates.
Documentation is at:
Request looks like:
or in general:
My notes to the TMS standard:
There is plenty of XML Metadata files, but nobody has ever used that
as I know (the are generated by tilecache, but no clients are parsing
them as I know but new Keo's GDAL TMS read driver from this year
GSoC). Origin of the tiles is bottom-left (IMHO it should be changed
to in the new version of TMS as it is causing a lot of implementation
troubles on both client and server side, some are using TMS but with
top-left origin tiles, for example OpenStreetMap. Google Maps is
naturally top-left, gdal is internally top-left, any computer raster
graphic is top-left).
OpenGIS Tiled WMS:
As I know it is a suggestion for extension of the WMS standard so the
tiles are access differently, there is extension of GetCapabilities,
Tiles are access in the form (shorten):
I have no clue if anybody implemented that.
Origin of tiles is top-left.
Documentation is available at:
Does it really bring something new, when compared to WMS-C which is
more or less only client based? I think server can make cacheing even
without changing anything on the WMS standard or not?
OpenGIS Web Map Tiling Service (WMTS)
OpenGIS is working on another service called WMTS. I think it should
be more or less the same like OSGEO TMS (I hope they are going to make
it RESTful). I haven't seen any documentation (where to get the
document: specification draft OGC 07-057r4 ?).
Other tile formats
There is plenty of application using tiles, both providers and
clients. Usually they define their own format.
Well known is format of Microsoft Quadkey (implemented by Virtual
Earth and by generator MapCruncher), format of NASA WorldWind
(implemented by tilecache as well) and several other. I summarized
some of them at:
The table could be longer, but i don't see any reason why to do that...
Comments are welcome
There is similarity between relation of an imageserver/zoomify and WMS/TMS.
TMS directly does not mean the the static files. I can imagine a
simplified tilecache project serving tiles directly based on TMS,
where the tiles are stored for example on Google BigTable (App Engine)
or Amazon S3 or in any other database/storage.
It would be even possible to write a patch for mapserver which will
add tms= argument and internally expand it to the standard WMS query.
More information about the Mass-Market-GEO