The Tile API: Difference between revisions
mNo edit summary |
(fill in missing detail) |
||
| Line 3: | Line 3: | ||
While in principle we could use zoom levels from 1, the whole world, to a very large number, in practice the tiles for the University are only generated for levels 13 to 19, so the user should be constrained from going beyond these limits (zoom 19 is equivalent to a scale of about 1 tile to 46m, 0.18m per pixel or 0.66m per mm on a typical display). | While in principle we could use zoom levels from 1, the whole world, to a very large number, in practice the tiles for the University are only generated for levels 13 to 19, so the user should be constrained from going beyond these limits (zoom 19 is equivalent to a scale of about 1 tile to 46m, 0.18m per pixel or 0.66m per mm on a typical display). | ||
Similarly, we don't store tiles for the whole world. We only store | Similarly, we don't store tiles for the whole world. We only store an area about 8km square for each zoom level centred on western Cambridge covering most of the University's estate: | ||
<table class="wikitable"> | <table class="wikitable"> | ||
| Line 21: | Line 21: | ||
<strong>west</strong></td> | <strong>west</strong></td> | ||
<td> | <td> | ||
-0.0025440</td> | |||
<td> | <td> | ||
4086</td> | |||
<td> | <td> | ||
262141</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 31: | Line 31: | ||
<strong>east</strong></td> | <strong>east</strong></td> | ||
<td> | <td> | ||
0.1767487</td> | |||
<td> | <td> | ||
4099</td> | |||
<td> | <td> | ||
262401</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 41: | Line 41: | ||
<strong>north</strong></td> | <strong>north</strong></td> | ||
<td> | <td> | ||
52.2419705</td> | |||
<td> | <td> | ||
2697</td> | |||
<td> | <td> | ||
172607</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 51: | Line 51: | ||
<strong>south</strong></td> | <strong>south</strong></td> | ||
<td> | <td> | ||
52.1594374</td> | |||
<td> | <td> | ||
2699</td> | |||
<td> | <td> | ||
172802</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
Revision as of 11:33, 28 June 2012
The map is assembled from a grid of image "tiles", each a 256x256 pixel PNG format image representing a small portion of the map in spherical Mercator projection. This is so that as it is panned, images can be loaded or dropped to keep them relevant to the area on view and therefore keep browser memory, bandwidth and download times under control. There is a separate set of tiles for each zoom level. Each higher zoom level doubles the scale and quadruples the number of tiles needed to represent the same area.
While in principle we could use zoom levels from 1, the whole world, to a very large number, in practice the tiles for the University are only generated for levels 13 to 19, so the user should be constrained from going beyond these limits (zoom 19 is equivalent to a scale of about 1 tile to 46m, 0.18m per pixel or 0.66m per mm on a typical display).
Similarly, we don't store tiles for the whole world. We only store an area about 8km square for each zoom level centred on western Cambridge covering most of the University's estate:
| latitude / longitude | tile number at zoom 13 | tile number at zoom 19 | |
|---|---|---|---|
| west | -0.0025440 | 4086 | 262141 |
| east | 0.1767487 | 4099 | 262401 |
| north | 52.2419705 | 2697 | 172607 |
| south | 52.1594374 | 2699 | 172802 |
Map tiles can be retrieved using URLs thus:
http://map.cam.ac.uk/tile/z/x/y.png
where
- z is the zoom level
- x is the tile number in the east/west direction
- y is the tile number in the north/south direction
This is a conventional form adopted among others by OpenStreetMap for tile presentation. That page also gives the formulae for converting between latitude/longitude and tile number. Rather than managing tiles directly, one could instead present the map itself using an IFRAME as described in The Embedding API and the search/text information in a custom form using the The Database API. The same form of URL is also used by OpenLayers (amongst other interfaces) to display maps; most such interfaces let you plug in the prefix part of the url so that tiles can be obtained from arbitrary sources, and the URLs above are compatible with that. It is also be possible to overlay information on the tiles obtained from OpenStreetMap's tile server or even on a Google map (whose tiles also use the same projection and numbering scheme).
