= Read/Write driver for TMS tiles = 

This work is continuation of the SoC 2007 project [http://trac.osgeo.org/gdal/wiki/SoCTileDriver GDAL2Tiles].
The goal is to create a new driver for reading and writing maps in TMS tiled format.

== Data format ==

=== TMS tiled maps ===

The driver will operate on data in 
the [http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification#TileMap_Resource OSGeo TMS TileMap Resource] format
used already by GDAL2Tiles. In short, the map is described in one XML file. Image data is divided into
several zooming levels represented by directories containing tiles as individual files. 

=== Tiles ===

The TMS specification doesn't prescribe the format of tiles but PNG and JPEG are
the only useable formats in web setting. Both have existing drivers in GDAL.
The TMS driver will use only PNG tiles at first. Extending the support to
JPEG tiles as well is possible next step after implementing both reading and writing
functionality for PNG. 

== Work plan ==

The work is divided into several steps. First two are essential, all others
are optional.

=== Read driver ===

First step is to create a read-only driver. The `Open` method will be called on
the main XML file describing the map. The `<TileSet>` URLs will be expected to be
paths relative to the main file. This is the case with data produced by GDAL2Tiles.
When this expectation is not met, the driver could try to guess the names of directories
using the last part of the URL and the base directory of the file being opened.
Another approach is to use auxiliary file describing the layout, this is similar
to the way the WMS driver works.

Each zooming level will be registered as overview in the main raster band. 
This will allow the user to get the data from specific level of detail, if he wants to,
or to use `RasterIO` on the main raster band, which in turn will use the best 
fitting overview. 


=== Write driver ===

Next on plan is the writing part. The driver will support both `CreateCopy` and `Create` methods.
Creation options will include the dimensions of tiles, number of zooming levels and the zooming 
ratio between them. Upon writing, the `IRasterIO` method will load all affected tiles from all 
zooming levels into memory, perform the write operation and then write the tiles back to file system.

=== NODATA ===

The TMS tile structure doesn't neccesarily need to have all tiles available. Areas without
tiles are handled as NODATA areas. The driver will not write them to file system unless the 
user performs write operation on them. This way the map could be stored compactly.

=== Performance tuning ===

The reading strategy at this point will be probably quite simple -- creating new
datasets for appropriate tiles in the `IReadBlock` method and getting data from them. 
This could prove to be inefficient. There are several ways to solve this issue:

 * Holding all tiles opened -- could be wasting too much memory.
 * Managing a cache of recently used tiles.
 * Prefetching adjacent tiles into the cache.

These and other should be explored and the final solution selected based on measured performance.

=== HTTP Read driver ===

The TMS tiled maps are mostly used on web, so the ability to read the map from
http connection could be quite useful. This functionality will probably be a part
of the existing WMS driver.

== Student info ==

My name is Václav Klusák and I am a graduate student of Applied Informatics at 
[http://www.muni.cz Masaryk University] in Brno, Czech Republic. I can be 
reached by email (`keo@keo.cz`) or ICQ (247 160 335).