Nearmap provides access to its vertical imagery via a subset of the Tile Map Service (TMS) protocol. TMS splits a map into a pyramid of 256x256-pixel map tiles at multiple zoom levels. An application typically downloads a collection of adjacent tiles to cover a given region.
Only the Web Mercator projection is supported by Nearmap’s TMS (EPSG:3857; also known as EPSG:3785 and EPSG:900913). Nearmap’s Web Map Service (WMS) is recommended for other projections.
Access to Nearmap imagery is only available to authenticated subscribers. Tiles may be requested from Nearmap servers with an API Key. Please refer to the API Key Authentication guide for details on how to obtain and use an API Key.
Nearmap Tile API consists of a number of individual HTTPS APIs, which are used in conjunction with Coverage API
Tiles may be requested by URLs in the following formats:
Nearmap Tile API consists of a number of individual HTTPS APIs, which are used in conjunction with Coverage API:
|RC||string||The region code. For example, au or us.|
The domain rotation number. Valid numbers are 0-3.
Domain rotation is used to drive traffic from multiple domains to a single IP address.
|x||integer||The X tile coordinate (column). Uses the Google XYZ scheme.|
|y||integer||The Y tile coordinate (row). Uses the Google XYZ scheme.|
|z||integer||The zoom level. The highest resolution is typically 21. Uses the Google XYZ scheme.|
The orientation of the imagery:
The date in the format YYYYMMDD. For example, 20151031.
See Getting a List of Surveys by Date for a Location for instructions on retrieving options for setting this parameter.
|version||The version number. Must be set to 2.|
|httpauth||Boolean||Indicates whether the tile server should prompt for HTTP basic authentication. Set this to false (we no longer support HTTP basic authentication).|
|apikey||string||Your API key. See API Key Authentication for more information.|
The following examples show two typical URL requests, one over http, and the other over https: