Tile Map Service (TMS)

The TMS driver provides access to  OSGeo Tile Map Service repositories.

You supply the URL to the TileMap? Resource which describes the data source. This is an XML file ([ http://labs.metacarta.com/wms-c/Basic.py/1.0.0/satellite-merc/ example) that describes the profile of the data. The TMS plugin can handle TMS repositories with global-geodetic, global-mercator and local/projected profiles.

Specs

Options

url URL to the TileMap? resource file. This file can exist locally on your machine or on the web. If pointing to a URL that will generate the TileMap Resource XML file via a service ( example), you must include a trailing / on the URL required
tms_type Specifies the type of TMS. If the value of the element is google, then it will be assumed that tile 0,0 is upper left corner of the map rather than the bottom left corner of the map. optional
format Format of the imagery (e.g. "jpg", "png"). This element is only used if no valid TMS file is found at the given URL optional
tile_size Tile size of the imagery. This element is only used if no valid TMS file is found at the given URL. optional

Example

  <image name="example" driver="tms">
      <url>http://labs.metacarta.com/wms-c/Basic.py/1.0.0/satellite-merc/</url>
  </image>

Notes

A tool for creating TMS-compatible datasets is  gdal2tiles. After running gdal2tiles on your dataset, you can point the TMS driver to the tilemapresource.xml file that it generates.

Please note: the BoundingBox? element of the tilemapresource.xml file generated by gdal2tiles has the x and y coordinates switched and you should manually swap them in order for the file to read correctly by a TMS client.

Driver list