Upload
others
View
43
Download
0
Embed Size (px)
Citation preview
Map Tile APIDeveloper's Guide
Version 2.1.56.0
Map Tile API Developer's Guide 2► Contents
Contents
Legal Notices..........................................................................................................................................................5
Document Information.................................................................................................................................... 6
Chapter 1: Overview................................................................................................................................. 7What is the Map Tile API?.............................................................................................................................8
Why use the Map Tile API?...........................................................................................................................8
Chapter 2: Quick Start........................................................................................................................... 9Map Tile Resources......................................................................................................................................10
Making the First Request........................................................................................................................... 10
Chapter 3: User Guide......................................................................................................................... 15Acquiring Credentials...................................................................................................................................16
Constructing a Request.............................................................................................................................. 16
Customer Integration Testing.......................................................................................................22
Key Concepts.................................................................................................................................................23
Map Tile Resources and URL usage............................................................................................ 23
Information Request Usage...........................................................................................................23
Copyright Request Usage.............................................................................................................. 24
Mercator Projection.........................................................................................................................24
Using a Tile Address........................................................................................................................26
Requesting the Right Map Version.......................................................................................................... 26
Metainfo Tiles................................................................................................................................................28
Metainfo parameter usage............................................................................................................ 28
Metainfo tile format for metadata generation one.................................................................32
Metainfo tile format for metadata generation two................................................................. 39
Traffic Tiles....................................................................................................................................................51
Frequently asked questions.......................................................................................................................56
Map Tile API Developer's Guide 3► Contents
How do I request the right info?................................................................................................. 56
How do I request the right copyright information?................................................................ 57
How do I calculate the distance to the ground depending on the zoom level?................. 57
How do I know if a particular resource is available?............................................................... 58
Examples.........................................................................................................................................................58
Base Map Tile Examples.................................................................................................................58
Metainfo Tile Examples.................................................................................................................. 94
Aerial Map Tile Examples............................................................................................................. 140
Pano Map Tile Examples.............................................................................................................. 145
Traffic Map Tile Examples........................................................................................................... 148
Service Support..........................................................................................................................................152
Chapter 4: API Reference..............................................................................................................153Base Map Tile Resources......................................................................................................................... 154
Administrative Labels (alabeltile)............................................................................................... 154
Base Map Tile (basetile)............................................................................................................... 161
Label Tile (labeltile)....................................................................................................................... 166
Line Tile (linetile)............................................................................................................................173
Lines and Labels Tile (lltile).........................................................................................................178
Map Tile (maptile).......................................................................................................................... 185
Street Tile (streettile)................................................................................................................... 193
Truck Tile (trucktile)......................................................................................................................200
Truck Only Tile (truckonlytile).................................................................................................... 208
Extra Base Map Tile (xbasetile).................................................................................................. 213
Aerial Tile Resources.................................................................................................................................217
Administrative Labels (alabeltile)............................................................................................... 217
Base Map Tile (basetile)............................................................................................................... 225
Label Tile (labeltile)....................................................................................................................... 229
Line Tile (linetile)............................................................................................................................237
Lines and Labels Tile (lltile).........................................................................................................241
Map Tile (maptile).......................................................................................................................... 249
Street Tile (streettile)................................................................................................................... 256
Map Tile API Developer's Guide 4► Contents
Truck Tile (trucktile)......................................................................................................................264
Truck Only Tile (truckonlytile).................................................................................................... 271
Extra Base Map Tile (xbasetile).................................................................................................. 276
Panorama Tile Resources.........................................................................................................................281
Raster Coverage Distributed (rcdistonytile)............................................................................281
Raster Coverage Only Tile (rconlytile)...................................................................................... 284
Raster Coverage Tile (rctile)....................................................................................................... 289
Traffic Tile Resources...............................................................................................................................296
Flow Base Tile (flowbasetile).......................................................................................................297
Flow Label Tile (flowlabeltile)......................................................................................................301
Flow Tile (flowtile)..........................................................................................................................309
Traffic Tile (traffictile).................................................................................................................. 314
Information Resources............................................................................................................................. 322
Info.................................................................................................................................................... 322
Copyright......................................................................................................................................... 329
Version..............................................................................................................................................411
HTTP Status Codes....................................................................................................................................412
Map Tile API Developer's Guide 5► Legal Notices
Legal Notices© 2014 HERE. All rights reserved.
This material, including documentation and any related computer programs, is protected by
copyright controlled by HERE. All rights are reserved. Copying, including reproducing, storing,
adapting or translating, any or all of this material requires the prior written consent of HERE. This
material also contains confidential information, which may not be disclosed to others without the
prior written consent of HERE.
Trademark Acknowledgements
HERE and Nokia are trademarks or registered trademarks of Nokia Corporation in the United States
and other countries.
Other trade names are trademarks or registered trademarks of their owners.
Disclaimer
This content is provided "as-is" and without warranties of any kind, either express or implied,
including, but not limited to, the implied warranties of merchantability, fitness for a particular
purpose, satisfactory quality and non-infringement. Nokia does not warrant that the content is error
free and Nokia does not warrant or make any representations regarding the quality, correctness,
accuracy, or reliability of the content. You should therefore verify any information contained in the
content before acting on it.
To the furthest extent permitted by law, under no circumstances, including without limitation Nokia's
negligence, shall Nokia be liable for any damages, including, without limitation, direct, special,
indirect, punitive, consequential, exemplary and/ or incidental damages that result from the use or
application of this content, even if Nokia or an authorized representative has been advised of the
possibility of such damages.
Map Tile API Developer's Guide 6► Document Information
Document Information
Product
Name: Map Tile API
Version: Version 2.1.56.0
Document
Name: Map Tile API Developer's Guide
Id: e458186-1418127019
Status: DRAFT
Date: 2014-Dec-09, 12:11 (GMT)
Map Tile API Developer's Guide 7► Overview
Chapter
1
OverviewTopics:
• What is the Map Tile API?
• Why use the Map Tile API?
This document introduces the Map Tile API and:
• explains key concepts
• provides examples
• documents resources and query parameters
• documents response structures and data types
Map Tile API Developer's Guide 8► Overview
What is the Map Tile API?HERE Map Tile API is a RESTful API that retrieves map images for all regions of the world.
To get a map image, formulate a request that combines the URL and a set of parameters to specify
details such as position, format, zoom level, and the map type of the map image. You can embed the
resulting map image in web pages and applications.
Why use the Map Tile API?Map Tile API addresses the following high level use cases:
• get a map tile image
• specify the viewing scheme of a map tile image
• specify the zoom level of a map tile image
• specify the resolution of a map tile image
• identify different map versions
• retrieve map copyright information
• retrieve metadata information for a specific location
Map Tile API Developer's Guide 9► Quick Start
Chapter
2
Quick StartTopics:
• Map Tile Resources
• Making the First Request
This article demonstrates the simplest way to use the Map Tile API.
Map Tile API Developer's Guide 10► Quick Start
Map Tile ResourcesThe Map Tile API uses different URLs to provide different map tiles, depending on the specific use
case.
The resources are explained in detail in the Map Tile Resources and URL usage on page 23, but
here is a simple overview:
• Base: provides map tiles using the map as a background
• Aerial: provides map tiles using satellite images as a background
• Pano: provides map tiles using map and panorama coverage as a background
• Traffic: provides map tiles with a traffic flow overlay
Making the First RequestThe simplest request scenario is to obtain the most up-to-date day-time map image that includes a
particular location.
The Map Tile API uses a grid of map tiles that, combined, form a complete map of the world using the
Normalized Mercator projection.
Thus, a request corresponding to the simple scenario above must provide:
• the unique URL of the API resource that is to process the request for a map image
• path variables that specify the details of the request (zoom level, map tile location in the grid,etc.)
• authentication parameters
The authentication parameters are app_id and app_code. Their values are the authentication
credentials required for access to the API resources. Note that demo credentials are available and can
be used for testing, but application-specific credentials are required in commercial applications – see
Acquiring Credentials on page 16 for further information.
The examples below show requests for a map tile at zoom level 13, located in the 4400th column and
the 2686th row in the tile grid for the different URLs (to understand how these tile coordinates were
obtained, see Mercator Projection on page 24). The tile resolution is 256x256 pixels, and the tile
format is PNG8.
Map Tile API Developer's Guide 11► Quick Start
The responses show a tile for each of the supported URLs.
http://1.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/13/4400/2686/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
The response from the base URL delivers a map tile image of part of Berlin, Germany.
Figure 1: Map-based image of a location in Berlin, Germany from the base URL
http://1.aerial.maps.cit.api.here.com/maptile/2.1/maptile/newest/hybrid.day/13/4400/2686/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 12► Quick Start
The response from the aerial URL delivers a map tile image of part of Berlin, Germany.
Figure 2: Satellite-based image of a location in Berlin, Germany from the aerial URL
http://1.pano.maps.cit.api.here.com/maptile/2.1/rctile/newest/normal.day/13/4400/2686/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 13► Quick Start
The response from the pano URL delivers a map tile image of part of Berlin, Germany.
Figure 3: Panorama coverage image of a location in Berlin, Germany from the pano URL
http://1.traffic.maps.cit.api.here.com/maptile/2.1/traffictile/newest/normal.day/13/4400/2686/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 14► Quick Start
The response from the traffic URL delivers a map tile image including traffic for part of Berlin,
Germany.
Figure 4: A map-based image with traffic of a location in Berlin, Germany from the traffic URL
Map Tile API Developer's Guide 15► User Guide
Chapter
3
User GuideTopics:
• Acquiring Credentials
• Constructing a Request
• Key Concepts
• Requesting the Right Map Version
• Metainfo Tiles
• Traffic Tiles
• Frequently asked questions
• Examples
• Service Support
The articles in this section provide a guide to using the Map Tile
API.
Map Tile API Developer's Guide 16► User Guide
Acquiring CredentialsAll users of HERE APIs must obtain authentication and authorization credentials and provide them as
values for the parameters app_id and app_code. The credentials are assigned per application.
To obtain the credentials for an application, please visit http://developer.here.com/get-started for
more details.
Constructing a RequestA request to the Map Tile API includes the basic elements shown in the following table and, in
addition, it may contain resource-specific query parameters.
Tile requests must follow the pattern summarized by the following formula:
{Base URL}{Path}{resource (tile type)}/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
Information requests must follow the pattern summarized by the following formula:
{Base URL}{Path}{resource (tile type)}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
Copyright requests must follow the pattern summarized by the following formula:
{Base URL}{Path}copyright/{map id}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
Table 1: Basic request elements
Element Value/Example Note Description
Base URL Base Map Tiles
http://{1-4}.base.maps.api.here.com
Aerial Tiles
http://{1-4}.aerial.maps.api.here.com
See also Load
Balancing and URLs
on page 22
Production environment
Map Tile API Developer's Guide 17► User Guide
Element Value/Example Note Description
Traffic Tiles
http://{1-4}.traffic.maps.api.here.com
Pano Tiles
http://{1-4}.pano.maps.api.here.com
Base Map Tiles
http://{1-4}.base.maps.cit.api.here.com
Aerial Tiles
http://{1-4}.aerial.maps.cit.api.here.com
Traffic Tiles
http://{1-4}.traffic.maps.cit.api.here.com
Pano Tiles
http://{1-4}.pano.maps.cit.api.here.com
See also Load
Balancing and URLs
on page 22
CIT environment: see Customer
Integration Testing on page
22
Path /maptile/2.1/
Resource (tile
type)
maptile
basetile
xbasetile
alabeltile
labeltile
linetile
lltile
streettile
rctile
rconlytile
rcdistonlytile
trucktile
truckonlytile
info
copyright
version
traffictile
flowtile
[1]
[1]
[1]
[1]
[1]
[1]
[1]
[1]
[2]
[2]
[2]
[1]
[1]
[3]
[3]
[3]
[4]
[4]
GET only. See API Reference on
page 153, Info on page 322
or Copyright on page 329 for a
more detailed parameter list for
each resource.
Map id newest (example) Specifies the map version. It
can be:
• version id the map
version of the requested
map tile resource;
request the latest version
by using newest as map
id.
• hash A unique key,
unambiguously
Map Tile API Developer's Guide 18► User Guide
Element Value/Example Note Description
representing a specific
map version.
See Requesting the Right Map
Version on page 26 for more
information on map versions.
Scheme normal.day (example) Specifies the view scheme. A
complete list of the supported
schemes may be obtained by
using the Info on page 322.
The following schemes are
available:
• normal.day – for a
normal map view in
daylight mode
• normal.day.grey
– for a color-reduced
map view in daylight
mode (especially used for
background maps)
• normal.day.transit
– for a color-reduced
map view with a public
transport scheme in
daylight mode
• normal.traffic.day
– for a color-reduced
map view designed for
displaying traffic in
daylight mode
• normal.traffic.night
– for a color-reduced
map view designed for
displaying traffic in night
mode
• normal.day.custom –
for a normal map view in
daylight mode
• normal.night – for a
normal map view in night
mode
• normal.night.grey
– for a color-reduced
map view in night mode
(especially used for
background maps)
• pedestrian.day –
pedestrian map view in
daylight mode
Map Tile API Developer's Guide 19► User Guide
Element Value/Example Note Description
• pedestrian.day.mobile
– pedestrian map view in
daylight mode for mobile
usage
• pedestrian.night –
pedestrian map view in
night mode
• pedestrian.night.mobile
– pedestrian map view in
night mode for mobile
usage
• carnav.day.grey –
for a normal map view
in daylight mode for car
navigation
• normal.day.mobile
– mobile version of the
scheme
• normal.day.grey.mobile
– mobile version of the
scheme
• normal.day.transit.mobile
– mobile version of the
scheme
• normal.night.mobile
– mobile version of the
scheme
• normal.night.grey.mobile
– mobile version of the
scheme
• reduced.day – for a
reduced map view in
daylight mode with few
colors
• reduced.night – for a
reduced map view in night
mode with few colors
• terrain.day – for
a terrain map view in
daylight mode
• satellite.day – for
a satellite map view in
daylight mode
• hybrid.day – for a
satellite map view with
streets in daylight mode
Map Tile API Developer's Guide 20► User Guide
Element Value/Example Note Description
• hybrid.grey.day – for
a satellite map view with
streets in daylight mode
with few colors
• hybrid.traffic.day
– for a satellite map view
with streets designed for
traffic
• terrain.day.mobile
– mobile version of the
scheme
• hybrid.day.mobile
– mobile version of the
scheme
Note: Please be aware that
invalid combinations of
schemes and Tiles are rejected.
For all satellite, hybrid and
terrain schemes, the Aerial
Tiles base URL must be used
instead of the normal one. For
the hybrid.traffic.day
scheme, the Traffic Tiles base
URL must be used instead of
the normal one. The other
traffic related schemes
(normal.traffic.day,
normal.traffic.night)
are supported by Traffic Tiles
and Map Tiles. Originally they
are supposed to be used only
with Traffic Tiles, but in order
to properly support the traffic
overlay case where you would
request a transparent traffic tile
from Traffic Tiles and a base tile
from Map Tiles, the Map Tiles
also support these schemes.
Zoom 13 (example) Zoom level of the map image.
Minimum and maximum zoom
levels are specified in the Info
on page 322.
Column 4400 (example) col – can be any number
between 0 and number of
columns - 1, both inclusive.
The number of tiles per column
is a function of the zoom:
number of columns =
2zoom
Map Tile API Developer's Guide 21► User Guide
Element Value/Example Note Description
Row 2686 (example) row – can be any number
between 0 and number of rows
- 1, both inclusive.
The number of tiles per row is a
function of the zoom: number
of rows = 2zoom.
Size 256 (example) Returned image size. The
following sizes ([width, height])
are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width,
height]) are deprecated,
although usage is still accepted:
128 = [128, 128]
Note: Raster coverage tiles
(rctile, rconlytile and
rcdistonlytile) only
support 256 sizes.
Format png8 (example) Returned image format. The
following image formats are
supported:
png – PNG format, 24 bit,
RGB
png8 – PNG format, 8 bit,
indexed color
jpg – JPG format at 90%
quality
Please note that JPG is
recommended for satellite
and hybrid schemes only.
Application Id &app_id=DemoAppId01082013GAL Mandatory Query
Parameter
Substitute your own unique
app_id
Application Code ?app_code=AJKnXv84fjrb0KIHawS0Tg Mandatory Query
Parameter
Substitute your own unique
app_code
Resource
Specific
Parameters
&{parameter=value} Optional Query
Parameter
Please refer to the API
definition for values.
Notes:
Map Tile API Developer's Guide 22► User Guide
[1] Please use the right base URL depending on what kind of tiles you want to get. Keep in mind
that for some schemes you should use different base URLs. For more information, see the API
reference.
[2] Please use the pano tile base URL for this request.
[3] Please use the right base URL depending on which environment you want to get information
from.
[4] Please use the traffic tile base URL for this request.
Load Balancing and URLs
The servers that process requests against the Map Tile API resources are distributed for optimized
load balancing. Clients can take advantage of this and improve response times, especially when
submitting multiple simultaneous requests, by using URL prefixes (1 - 4). The numeric prefix must be
the first part of the request URL after "http://".
There are different ways to take advantage of this mechanism. No method is enforced from the
server, although the method used should ensure that your requests are distributed among the
different prefixes and do not use only one. We propose the following methods:
• Choose the prefix randomly.
• Choose the prefix depending on the parity of the row and column number:
1 – when both the row and the column number are even
2 – when the row number is even, the column number is odd
3 – when the row number is odd, the column number is even
4 – when both the row and the column number are odd
• Use a simple formula such as:
1 + ((row_number + column_number) % 4)
In this formula, % indicates modulo division.
Customer Integration TestingHERE is committed to maintain the best possible production service for all customers. Given that the
production environment is live and common to all API users, we request that you use the alternative
Map Tile API Developer's Guide 23► User Guide
Customer Integration Testing (CIT) environment when evaluating our products, running tests, making
changes in your code and altering the way you access our APIs.
The CIT environment also allows you to test your software against a newer version of the service
before HERE brings that version into production. CIT offers a fully functional environment for
customers to use for development and testing, but it does not support high loads or performance
testing in general.
Note that the same application id can be used in both environments, but CIT may require a dedicated
application code. If this is the case, please contact us as described under Service Support on page
152.
The CIT environment is not intended for general production use.
Key ConceptsThis section provides insights into the key concepts used throughout the Map Tile API.
Map Tile Resources and URL usageThe Map Tile API uses different URLs to provide different map tiles, depending on the specific use
case that needs to be solved.
Each Map Tile Resource is mapped to a different URL, see Constructing a Request on page 16 for
more details on how to construct a request.
Each Map Tile Resource provides a different set of possible combinations of tile types , schemes
and parameters in order to show different images.
• Base: provides map tiles using the map as a background, metadata text-based tiles with
information about the map and base64 encoded tiles.
• Aerial: provides map tiles using satellite images as a background
• Pano: provides map tiles using map and panorama coverage as a background
• Traffic: provides map tiles with a traffic flow overlay
Information Request UsageThe Map Tile API offers regularly updated maps. In order to know how to get the latest available map
and how to properly use that information, please check Requesting the Right Map Version on page
26
Map Tile API Developer's Guide 24► User Guide
Copyright Request UsageThe Map Tile API offers copyright information about the map that you need to include when
displaying a map composed out of map tiles. Please note that every resource offers its own
copyright information that you should query.
Mercator ProjectionThe Map Tile API serves map tiles obtained by mapping points on the surface of a sphere (the globe)
to points on a plane, using the normalized Mercator projection.
The basic Mercator projection formula is this:
{λ, φ} -> x[-1, 1] y [-1, 1]
In this formula:
λ = longitude
φ= latitude
x = λ / π
y = ln(tan(π/4 + φ/2)) / π
The plane represents the globe as a square grid of map tiles. The size of the grid depends on the map
zoom level. At the lowest zoom level, the world is contained in one map tile. At the next higher zoom
level, the world is two tiles wide and two tiles high (2x2), at the next level above that, the grid is 4x4,
then 8x8, 16x16, and so on up to the maximum zoom for a particular region. In other words, at each
zoom level the tiles that make up the complete map of the world form a grid in which the number of
tiles is equal to the zoom level raised to the power of two (2zoom).
The relationship between tiles at two consecutive zoom levels can be expressed as follows:
col1,z+1 = (2*colz) + 1row1,z+1 = (2*rowz) + 1
In this formula:
col = column number in the tile grid
row = row number in the tile grid
z = zoom level
Map Tile API Developer's Guide 25► User Guide
The diagram below demonstrates this graphically:
Figure 5: Tiles at different zoom levels
You can use this information to obtain the grid coordinates (row and column) of the map tile for a
particular geographic location in your application. The following pseudo code contains the complete
algorithm:
--- javascript ---var lat = 52.525439, // Latitudelon = 13.38727, // Longitudez = 12, // Zoom levellatRad,n,xTile,yTile;
latRad = lat * Math.PI / 180;n = Math.pow(2, z);xTile = n * ((lon + 180) / 360);yTile = n * (1-(Math.log(Math.tan(latRad) + 1/Math.cos(latRad)) /Math.PI)) / 2;
--- output ---lat_rad = 0.916n = 4096xTile = 2200.31 // ColumnyTile = 1343.20 // Row
The zoom level and tile row and column can be used as URL variables separated by the '/' character in
map tile requests. Note that they must be provided in this order: zoom/column/row. This is the [Z]/
[X]/[Y] addressing scheme.
Map Tile API Developer's Guide 26► User Guide
The map tile specification is typically preceded by other path variables and may be followed either by
further path variables and/or query parameters.
Using a Tile AddressA request that includes a tile address in the format zoom/column/row can be formulated as follows:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/12/2200/1343/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
In this case, the request obtains a map tile at zoom level 12 for part of Berlin, Germany:
Figure 6: A map tile for part of Berlin
Requesting the Right Map VersionThe Map Tile API offers:
• regularly updated maps
Map Tile API Developer's Guide 27► User Guide
• different map versions for certain regions of the world to meet the legal requirements in specific
countries
The response to an info request lists all the available map versions as elements named map, grouped
by the attribute region. The response identifies the most recent map version in each region with the
attribute id set to the value "newest". The following excerpt shows an example of a map version
list:
<map region="all" id="newest" /><map region="all" newest="true" id="8.30.53.109" hash="be9b70fa2c" />
When requesting map tiles, use URL variables to indicate the most recent map or a specific map
version:
• newest – to request the most recent map version available, for example:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/11/1202/843/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
• a hash value – to request a specific map version; the actual URL variable is the value of the
attribute hash from the response to a metadata request (see the response excerpt above), for
example; here is a map tile request that uses a hash value instead of /newest/.
Note that the hash values identifying map versions change as a result of software updates, even
if the map ids remain the same. To get a valid response to the query, make a metadata request
request first, and substitute a current map hash value for c376276c01 in the following URL:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/c376276c01/normal.day/11/1202/843/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Note: A traffic tile request (traffic or flow ) should always use the Traffic Tiles base URL, andthe URL variable newest to indicate map version. Although a hash value is accepted, it shouldnot be used as the life span of a traffic tile is too short. Invalid base URL and/or paramatercombinations are rejected.
Note: Use the the Aerial base URL for all satellite, terrain and hybrid schemes andthe Map base URL for any other requests.
Note: Metadata requests retrieve information specific to the base URLs they target. Thisinformation cannot be used in subsequent requests that use other base URLs. For example, toobtain a traffic map version, use metadata from the response to a request addressed to theTraffic Tiles base URL, but for a version of an aerial map, use metadata from the response to arequest addressed to the Aerial Tiles base URL.
Note: Using newest always ensures that the most recent map version available is returned,but it does not guarantee consistency. If for example there is an update in the map data in
Map Tile API Developer's Guide 28► User Guide
between a set of requests, some of those requests might return data from the previous mapand some from the new map, which might cause an inconsistent map experience. The onlyway to guarantee a fully consistent map is to use a particular hashcode. Every single requestthat uses the same hashcode is guaranteed to be consistent with any other request usingthe same hashcode. Therefore, the usage recommendation is to always use a hashcodein all tile requests. To ensure that the used hashcode is always up to date, we recommendquerying the info page at least every two hours and checking if the hashcode has changedcompared to the one previously used. Any particular map version (hashcode) will always besupported for at least 24 hours to ensure a consistent map experience. Please note that if themap or software is incorrect, its lifetime might be less than 24 hours to avoid any bad userexperiences.
Metainfo TilesMetainfo Tiles are used to obtain metadata information about specific tiles. This metadata can then
be used to enable interactivity, for example, or to obtain information about the labels or objects
rendered.
One possible use case would be getting a maptile for a certain location, requesting the metadata
for the same tile and then using the position of the labels to enable highlighting of certain labels on
the client side.
Another example would be showing only clickable roadsigns on top of a tile. You would request a
basetile, then request a metadata tile for the same location using mgen=2 and filter=1 to
obtain only the filtered out roadsigns and finally overlay the icons of those roadsigns that were
returned by the metadata request.
Note: Use the the Aerial base URL for all satellite, terrain and hybrid schemes andthe Map base URL for any other requests.
Metainfo parameter usageThe relevant parameters for metadata requests are:
Table 2: Metainfo request parameters
Parameter Type Description
callback_func String A function name that is wrapped around the JSON output. This technique allows
for a more secure way of parsing the output with JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Map Tile API Developer's Guide 29► User Guide
Parameter Type Description
Note: The value is url-decoded, but it is the responsibility of the
requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a metadata
response.
Note: This parameter only works in combination with the parameter
mgen.
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is automatically
enabled
metatile: both the requested image and the associated metadata are returned;
output=base64 is automatically on
Note: Optionally, the parameter callback_func can be used as well.
mgen String Specifies the metadata generation to use. This parameter accepts the following
values:
1: default
2: optimized out json format that filters empty values and allows the usage of
parameter filter, the output of this version might change between releases
as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for metadata
requests and output json.
Note: For info requests, this parameter is only available when using
output json.
output String Can only have the value base64, which indicates that the map tile is returned as
base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for traffic.
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if not
present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you want to see
POI information.
range String Only relevant if output=base64 is also specified as a parameter. range must be
one of 2x2, 3x3 or 4x4, which indicates the size of the array of tiles returned. The
Map Tile API Developer's Guide 30► User Guide
Parameter Type Description
tile specified by col and row is the top left of the array, and must divide by the
array size.
Usage of parameters for metainfo tiles
The parameter callback_func can be used in a JavaScript component to request that the callback
function be executed when the request comes back from the server and that a json object (the result)
be passed to it.
The parameter mgen stands for metadata generation. This is used to differentiate between
meatadata versions and between the capabilities on top of those versions. Version 1 includes street
labels, roadsigns shown as labels and city center labels. This version is deprecated as there are no
new features added to it. Version 2 is the current generation and it is still under development as new
features are added almost in every release. From the content side it includes the labels from Version
1 as well as other fields such as buildings, roadsigns, transit stops, transit access and POIs. If there
is no data available for a given empty it will be filtered out from the response. You can always use
latest to get the latest version of the metadata. The roadsign information contained in version
2 returns the uri to obtain the icon of the roadsign, thus enabling the use case explained in this
example.
The parameter filter can be used only with Version 2 of metadata generation to filter out
metadata from the resulting metainfo tile. Use of this parameter allows for the transfer of smaller
json objects and for the transfer of only the relevant information.
The parameter metadata is the most important parameter for metainfo tiles. It enables the output
of metadata information. When the value is metaonly, the response only includes the metadata
information. This means only the text (json) object is returned. When the value metatile is used,
then the encoded base64 tile is also returned in addition to the metadata information in the JSON
object. This enables the transfer of the image along with the metadata information.
The parameter output is used to generate base64 encoded values, useful when requesting several
tiles in one request with the parameter range, for example, or to request a tile for use as an input for
callback_func.
The parameter range is used to request several tiles in a single request. The tile specified by col and
row is the top left of the array and it must divide by the array size.
All parameters can be combined to create complex and highly customizable requests, for example
the following request:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/14/8799/5376/256/png8?app_id=DemoAppId01082013GAL
Map Tile API Developer's Guide 31► User Guide
&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metatile&mgen=2&filter=1&range=3x3&callback_func=parse_image
This request results in a JSON object that:
has nine tiles (range is 3x3),
has tiles that include the metadata and a base64 encoded image (metadata is metatile),
has generation two metadata information (mgen is 2), which means filtering is available,
has filtering enabled to show only roadsigns (filter is 1) and
indicates the function called when the request is received is parse_image (callback_func is
parse_image).
The output of this request is shown below (Note that the response has been simplified to only show
one tile out of nine and that the base64 images have been shortened for readability).
parse_image( [ { "image": "iVBORw0KGgoAAAANSUhEUgAAAQAAAAEACAMAAABrrFhUAAADAFBMVEUwMC6 ...", "metadata" : { "labels":[ { "name":"103", "type": "ROADSIGN", "bounding boxes": [ { "left":62, "top":198, "width":28, "height":20 } ], "region": "DEU", "category": 0, "route name": "A103", "route level": 2, "uri": "http://image.maps.cit.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A103&route_level=2&app_id=XXXXXXXXXXXXXXXXXXXX&app_code=XXXXXXXXXXXXXXXXXXXXXX" }, { "name":"100", "type": "ROADSIGN", "bounding boxes": [ { "left":212, "top":163, "width":28, "height":20 } ], "region": "DEU", "category": 0, "route name": "A100", "route level": 2,
Map Tile API Developer's Guide 32► User Guide
"uri": "http://image.maps.cit.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A100&route_level=2&app_id=XXXXXXXXXXXXXXXXXXXX&app_code=XXXXXXXXXXXXXXXXXXXXXX" }, { "name":"1", "type": "ROADSIGN", "bounding boxes": [ { "left":188, "top":73, "width":22, "height":15 } ], "region": "DEU", "category": 1, "route name": "B1", "route level": 3, "uri": "http://image.maps.cit.api.here.com/mia/1.6/roadsign?category=1®ion=DEU&label=B1&route_level=3&app_id=XXXXXXXXXXXXXXXXXXXX&app_code=XXXXXXXXXXXXXXXXXXXXXX" }, ] } }, ... (5 more tiles)] );
Metainfo tiles content
Table 3: Metainfo tiles content
Parameter Type Description
callback_id String (optional) If specified (associated with callback_func), the function wrapper
contains this id as its first parameter. This allows the user to check if
the response is actually the response to the request, and not some
maliciously injected code; for example
callback_id=1425
returns:
test( '1425', '{ ...}' );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
Metainfo tile format for metadata generation oneEvery metainfo tile displays the following information in a JSON structure
• metadata - container for the response
◦ street labels - array of street labels
▪ name
▪ font size
Map Tile API Developer's Guide 33► User Guide
▪ vertices - array of tile coordinates
▪ x
▪ y
◦ labels - array of labels
▪ name
▪ type
▪ bounding boxes - array of boxes
▪ left
▪ top
▪ width
▪ height
◦ city center labels - array of city center labels
▪ name
▪ text box
▪ left
▪ top
▪ width
▪ height
▪ bullet box
▪ left
▪ top
▪ width
▪ height
▪ city center info
▪ type
▪ name
▪ alternative names - array of names
▪ country code
▪ name
▪ country code
▪ position
Map Tile API Developer's Guide 34► User Guide
▪ latitude
▪ longitude
▪ population
The format is as follows:
{ "metadata": { "street labels": [], "labels": [], "city center labels": [] }}
Street labels
The street labels field displays an array of labels containing the name of the street, the font size
used to render it and an array of vertices to draw the polyline that represents the bounding box. The
format is as follows:
"name": "","font size": "","vertices: [ "x":, "y":]
Name Type Description
name String Name of the street
font size String Font size used to render the label, it is a number displayed as a string
vertices Array of tile coordinates Array containing all vertices needed to draw a polyline that creates a
bounding box on the street label.
Labels
This labels field only display information about roadsigns, including the name, the type and the
location (bounding box). The format is an array of labels, each one with the following format:
"name": "","type": "ROADSIGN","bounding boxes": []
Map Tile API Developer's Guide 35► User Guide
Name Type Description
name String Name of the city
type String One of the following types: Roadsign
bounding boxes Array of Bounding Box Array containing all the bounding boxes of the label
City Center Labels
This field displays an array of city center labels, each one including the name and location (bounding
box) of the name, location (bounding box) of the bullet box, which is the small square showing
the city center and the city center additional information, which shows the type of city, official
displayed name, the alternative names in different languages, the country code, position (latitude
and longitude) and population. The format is as follows:
"name": "","text box" : { "left": , "top": , "width": , "height":},"bullet box" : { "left": , "top": , "width": , "height":},"city center info": { "type": "", "name": "", "alternative names": [ [ "", "" ] ], "country code": "", "position": { "latitude":, "longitude": }, "population": }
Name Type Description
name String Name of the city
text box Bounding Box Location of the label in the tile
Map Tile API Developer's Guide 36► User Guide
Name Type Description
bullet box Bounding Box Location of the bullet in the tile
city center info Structure Structure containing additional information for a city
Common fields
Field Name Type Description
left Integer Location of the left coordinate in the tile
top Integer Location of the top coordinate in the tile
width Integer Width of the bounding box
Bounding Box
height Integer Height of the bounding box
latitude Float ( 6 decimals ) Latitude of the geo coordinateGeo coordinate
longitude Float ( 6 decimals ) Longitude of the geo coordinate
type String Type of city between National Capital, Provincial Capital and
Other
name String Official name of the city
alternative
names
Array of arrays Alternative names of the city, each array containing the
country code as String and the name as String
country code String Three letter country code following MARC coding
position Geo coordinate Location of the city center
City Center Info
population Integer Population of the city
x Integer Coordinate x of the tile coordinateTile Coordinate
y Integer Coordinate y of the tile coordinate
Two examples are provided in this section, both using mgen=1, to illustrate the format described
above. To get additional information about how to use it please check the Examples section.
This example shows a locatin in Berlin and the request looks like:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/9/275/167/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=1
The response looks like:
{ "metadata" : {"street labels":[
Map Tile API Developer's Guide 37► User Guide
],"labels":[{"name":"1", "type": "ROADSIGN", "bounding boxes": [ { "left":96, "top":240, "width":18, "height":12 } ] },{"name":"158", "type": "ROADSIGN", "bounding boxes": [ { "left":166, "top":129, "width":22, "height":12 } ] },{"name":"114", "type": "ROADSIGN", "bounding boxes": [ { "left":13, "top":158, "width":23, "height":16 } ] },{"name":"10", "type": "ROADSIGN", "bounding boxes": [ { "left":73, "top":173, "width":22, "height":16 } ] },{"name":"11", "type": "ROADSIGN", "bounding boxes": [ { "left":64, "top":153, "width":22, "height":16 } ] },{"name":"2", "type": "ROADSIGN", "bounding boxes": [ { "left":54, "top":172, "width":18, "height":12 } ] },{"name":"109", "type": "ROADSIGN", "bounding boxes": [ { "left":49, "top":28, "width":22, "height":12 } ] }],"city center labels":[{"name": "Berlin", "text box": { "left":9, "top":218, "width":49.45, "height":20.50 }, "bullet box": { "left":4, "top":234, "width":5, "height":5 }, "city center info": {"type":"NATIONAL CAPITAL", "name": "Berlin", "alternative names":[["ARA", "#####"], ["BAQ", "Berlin"], ["BUL", "######"], ["BUX", "Berlin"], ["CAT", "Berlín"], ["CHI", "##"], ["CHT", "##"], ["CZE", "Berlín"], ["CZX", "Berlin"], ["DAN", "Berlin"], ["DUT", "Berlijn"], ["ENG", "Berlin"], ["EST", "Berliin"], ["ESX", "Berliin"], ["FIN", "Berliini"], ["FRE", "Berlin"], ["GER", "Berlin"], ["GRE", "########"], ["GRX", "Verolino"], ["HIN", "######"], ["HIX", "Barlin"], ["HUN", "Berlin"], ["HUX", "Berlin"], ["ICE", "Berlín"], ["IND", "Berlin"], ["ITA", "Berlino"], ["JPN", "####"], ["JPX", "Berurin"], ["KOR", "###"], ["KOX", "Be Reul Rin"], ["LAV", "Berl#ne"], ["LAX", "Berline"], ["LIT", "Berlynas"], ["LIX", "Berlynas"], ["MAY", "Berlin"], ["NOR", "Berlin"], ["POL", "Berlin"], ["POR", "Berlim"], ["POX", "Berlin"], ["PYN", "Bo Lin"], ["RMX", "Berlin"], ["RUM", "Berlin"], ["RUS", "######"], ["RUX", "Berlin"], ["SCR", "Berlin"], ["SLO", "Berlín"], ["SLX", "Berlin"], ["SPA", "Berlín"], ["SRX", "Berlin"], ["SWE", "Berlin"], ["THA", "########"], ["TUR", "Berlin"], ["TUX", "Berlin"], ["UKR", "######"], ["UKX", "Berlin"]], "country code": "DEU", "position": {"latitude":52.514648, "longitude":13.375854}, "population": 3442675 } },{"name": "Eberswalde", "text box": { "left":167, "top":36, "width":58.22, "height":11.75 }, "bullet box": { "left":165, "top":45, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Eberswalde", "alternative names":[], "country code": "DEU", "position": {"latitude":52.833252, "longitude":13.815308}, "population": 41175 } },{"name": "Bernau bei Berlin", "text box": { "left":83, "top":117, "width":55.08, "height":22.75 }, "bullet box": { "left":81, "top":137, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Bernau bei Berlin", "alternative names":[], "country code": "DEU", "position": {"latitude":52.679443, "longitude":13.584595}, "population": 36154 } },{"name": "Strausberg", "text box": { "left":191, "top":192, "width":51.91, "height":10.50 }, "bullet box": { "left":189, "top":200, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Strausberg", "alternative names":[], "country code": "DEU", "position": {"latitude":52.575073, "longitude":13.881226}, "population": 26221 } },{"name": "Wandlitz", "text box": { "left":43, "top":83, "width":40.47, "height":10.50 }, "bullet box": { "left":41, "top":91, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Wandlitz", "alternative names":[], "country code": "DEU", "position": {"latitude":52.756348, "longitude":13.474731}, "population": 21530 } },{"name": "Neuenhagen bei Berlin", "text box": { "left":121, "top":211, "width":58.64, "height":20.50 }, "bullet box": { "left":119, "top":229, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Neuenhagen bei Berlin", "alternative names":[], "country code": "DEU", "position": {"latitude":52.525635, "longitude":13.688965}, "population": 16755 } },{"name": "Ahrensfelde", "text box": { "left":81, "top":192, "width":56.22, "height":10.50 }, "bullet box": { "left":79, "top":200, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Ahrensfelde", "alternative names":[], "country code": "DEU", "position": {"latitude":52.575073, "longitude":13.579102}, "population": 13114 } },{"name": "Bad Freienwalde (Oder)", "text box": { "left":165, "top":56, "width":75.83, "height":20.50 }, "bullet box": { "left":241, "top":74, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Bad Freienwalde (Oder)", "alternative names":[], "country code": "DEU", "position": {"latitude":52.783813, "longitude":14.024047}, "population": 12964 } },{"name": "Werneuchen", "text box": { "left":137, "top":159, "width":57.83, "height":10.50 }, "bullet box": { "left":135, "top":167, "width":2, "height":2 }, "city center info":
Map Tile API Developer's Guide 38► User Guide
{"type":"OTHER", "name": "Werneuchen", "alternative names":[], "country code": "DEU", "position": {"latitude":52.630004, "longitude":13.732910}, "population": 7943 } },{"name": "Biesenthal", "text box": { "left":105, "top":76, "width":49.03, "height":10.50 }, "bullet box": { "left":103, "top":84, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Biesenthal", "alternative names":[], "country code": "DEU", "position": {"latitude":52.767333, "longitude":13.645019}, "population": 5563 } },{"name": "Rehfelde", "text box": { "left":207, "top":218, "width":42.12, "height":10.50 }, "bullet box": { "left":205, "top":226, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Rehfelde", "alternative names":[], "country code": "DEU", "position": {"latitude":52.531127, "longitude":13.925170}, "population": 4462 } },{"name": "Liebenwalde", "text box": { "left":15, "top":13, "width":57.72, "height":10.50 }, "bullet box": { "left":13, "top":21, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Liebenwalde", "alternative names":[], "country code": "DEU", "position": {"latitude":52.871704, "longitude":13.397827}, "population": 4390 } },{"name": "Chorin", "text box": { "left":189, "top":0, "width":31.52, "height":10.50 }, "bullet box": { "left":187, "top":2, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Chorin", "alternative names":[], "country code": "DEU", "position": {"latitude":52.904663, "longitude":13.875732}, "population": 2430 } },{"name": "Oderberg", "text box": { "left":203, "top":17, "width":45.25, "height":10.50 }, "bullet box": { "left":249, "top":25, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Oderberg", "alternative names":[], "country code": "DEU", "position": {"latitude":52.866210, "longitude":14.046020}, "population": 2229 } },{"name": "Britz", "text box": { "left":139, "top":4, "width":23.19, "height":10.50 }, "bullet box": { "left":163, "top":12, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Britz", "alternative names":[], "country code": "DEU", "position": {"latitude":52.888183, "longitude":13.809814}, "population": 2201 } },{"name": "Rüdnitz", "text box": { "left":99, "top":103, "width":36.39, "height":10.50 }, "bullet box": { "left":97, "top":111, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Rüdnitz", "alternative names":[], "country code": "DEU", "position": {"latitude":52.723388, "longitude":13.628540}, "population": 1839 } },{"name": "Marienwerder", "text box": { "left":89, "top":30, "width":63.73, "height":10.50 }, "bullet box": { "left":87, "top":38, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Marienwerder", "alternative names":[], "country code": "DEU", "position": {"latitude":52.844238, "longitude":13.6010742}, "population": 1731 } },{"name": "Prötzel", "text box": { "left":210, "top":152, "width":34.09, "height":10.50 }, "bullet box": { "left":227, "top":164, "width":2, "height":2 }, "city center info": {"type":"OTHER", "name": "Prötzel", "alternative names":[], "country code": "DEU", "position": {"latitude":52.635498, "longitude":13.985595}, "population": 1143 } }]}}
This other example contains a metadata response for a close-up of a location in Berlin including
street labels. The request looks like:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/13/4402/2685/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=1
And the response looks like:
{ "metadata" : {"street labels":[{ "name":"Hansastraße", "font size":"11", "vertices": [ { "x": 163, "y": 118 }, { "x": 175, "y": 102 }, { "x": 178, "y": 98 }, { "x": 182, "y": 93 }, { "x": 187, "y": 90 }, { "x": 190, "y": 87 }, { "x": 194, "y": 84 }, { "x": 210, "y": 75 } ] },{ "name":"Weißenseer Weg", "font size":"11", "vertices": [ { "x": 147, "y": 240 }, { "x": 172, "y": 288 }, { "x": 176, "y": 297 }, { "x": 182, "y": 319 } ] }],"labels":[{"name":"Volkspark Prenzlauer Berg", "type": "TEXT", "bounding boxes": [ { "left":64, "top":243, "width":55.03, "height":37.75 } ] },
Map Tile API Developer's Guide 39► User Guide
{"name":"Weißenseepark", "type": "TEXT", "bounding boxes": [ { "left":55, "top":78, "width":77.97, "height":11.75 } ] },{"name":"Sportforum Hohenschönhausen", "type": "TEXT", "bounding boxes": [ { "left":167, "top":215, "width":11, "height":11 } ] },{"name":"Sportkomplex Buschallee", "type": "TEXT", "bounding boxes": [ { "left":237, "top":61, "width":11, "height":11 } ] },{"name":"Sportforum Hohenschönhausen", "type": "TEXT", "bounding boxes": [ { "left":123, "top":190, "width":99.55, "height":23.75 } ] },{"name":"Sportkomplex Buschallee", "type": "TEXT", "bounding boxes": [ { "left":207, "top":36, "width":71.56, "height":23.75 } ] }],"city center labels":[{"name": "Alt-Hohenschönhausen", "text box": { "left":248, "top":133, "width":126.09, "height":29.50 }, "city center info": {"type":"OTHER", "name": "Alt-Hohenschönhausen", "alternative names":[], "country code": "DEU", "position": {"latitude":52.547607, "longitude":13.500824}, "population": 0 } },{"name": "Weißensee", "text box": { "left":84, "top":8, "width":70.67, "height":15.50 }, "city center info": {"type":"OTHER", "name": "Weißensee", "alternative names":[], "country code": "DEU", "position": {"latitude":52.561340, "longitude":13.467865}, "population": 0 } }]}}
Metainfo tile format for metadata generation twoEvery metainfo tile displays the following information in a JSON structure.
• metadata - container for the response
◦ street labels - array of street labels
▪ name
▪ font size
▪ vertices - array of tile coordinates
◦ labels - array of labels
▪ name
▪ type
▪ bounding boxes - array of boxes
◦ city center labels - array of city center labels
▪ name
▪ text box
▪ bullet box
▪ city center info
▪ type
▪ name
▪ alternative names - array of names
Map Tile API Developer's Guide 40► User Guide
▪ country code
▪ name
▪ country code
▪ position
▪ latitude
▪ longitude
▪ population
◦ buildings - array of buildings
▪ id
▪ sectors - array of sectors
▪ info
▪ bottom height
▪ height
▪ vertices - array of vertices
▪ polygons - array of array of polygons
▪ outlines - array of outlines
◦ transit stops - array of transit stops
▪ name
▪ bounding boxes - array of bounding boxes
▪ icon box
▪ annotation box
▪ info - array of transit stop information
▪ geoposition
▪ latitude
▪ longitude
▪ official name
▪ informal name
▪ places id
▪ operating hours
▪ Monday
▪ Tuesday
Map Tile API Developer's Guide 41► User Guide
▪ Wednesday
▪ Thursday
▪ Friday
▪ Saturday
▪ Sunday
▪ Holiday
▪ parking size
▪ parking hours
▪ Monday
▪ Tuesday
▪ Wednesday
▪ Thursday
▪ Friday
▪ Saturday
▪ Sunday
▪ Holiday
◦ POIs - array of POIs (Points of Interest)
▪ name
▪ geoposition
▪ latitude
▪ longitude
▪ bounding boxes - array of bounding boxes
▪ icon box
▪ annotation box
▪ info - array of POI information
The format is as follows:
{ "metadata": { "street labels": [], "labels": [], "city center labels": [], "buildings": [], "transit stops": [], "POIs": []
Map Tile API Developer's Guide 42► User Guide
}}
Street labels
The street labels field displays an array of labels containing the name of the street, the font size
used to render it and an array of vertices to draw the polyline that represents the bounding box. The
format is as follows:
"name": "","font size": "","vertices: []
Name Type Description
name String Name of the street
font size String Font size used to render the label, it is a number displayed as a string
vertices Array of tile coordinates Array containing all vertices needed to draw a polyline that creates a
bounding box on the street label, an array of x/y values, as in [ x1, y1,
x2, y2 ... ]
Labels
Labels field displays information about labels that are not street labels, including the name, the type
and the location (bounding box). The format is an array of labels, each one with the following format:
"name": "","type": "","bounding boxes": []
Name Type Description
name String Name of the city
type String One of the following types: Mountain Peak, POI, Pedestrian Point, Text,
Transit Access, Transit Stop, Highway Exit Sign, Roadsign, City Center
When type is Roadsign there are additional fields:
1. region (ISO country code)
2. category
3. route name
4. route level
5. uri
Map Tile API Developer's Guide 43► User Guide
Name Type Description
bounding boxes Array of Bounding Box Array containing all the bounding boxes of the label, that can contain a
text box, icon box, bullet box or annotation box
City Center Labels
This field displays an array of city center labels, each one including the name and location (bounding
box) of the name, ,the city center additional information, which shows the type of city, official
displayed name, the alternative names in different languages, the country code, position (latitude
and longitude) and population. The format is as follows:
"name": "","text box" : [],"bullet box": [],"city center info": { "type": "", "name": "", "alternative names": [ [ "", "" ] ], "country code": "", "position": { "latitude":, "longitude": }, "population": }
Name Type Description
name String Name of the city
text box Bounding Box Location of the label in the tile
bullet box Bounding Box Location of the bullet (small icon next to the city name) in the tile
city center info Structure Structure containing additional information for a city
Buildings
The "buildings" field contains a list of buildings for current tile. Provided information allows to:
• identify buildings within single tile or across several tiles using unique building "id";
• define the shape of a building in order to select or highlight it on the map;
• render 3D buildings (including multi-level buildings) using "bottom height" and "height"
attributes.
Map Tile API Developer's Guide 44► User Guide
The shape of the builing provided as an array os sectors, each sector containing bottom height and
height values, arrays of vertices, polygons and outlines. The format is as follows:
"id": "","sectors": [ { "info": { "bottom height": , "height": }, "vertices": [], "polygons": [], "outlines": [] }]
Name Type Description
id String Internal id of the building
sectors Sector Array of sectors
Transit stops
The transit stop fields displays the name, bounding boxes and info.
Note: Empty fields are filtered out and not present in the output, such as informal name,
places id, operating hours, parking size, parking hours.
The format is as follows:
"name": "","bounding boxes": [ "icon box": [], "annotation box": []],"info": [ { "position": { "latitude": , "longitude": }, "official name": "", "informal name": "", "places id": "", "operating hours": { "Monday": [], "Tuesday": [], "Wednesday": [], "Thursday": [], "Friday": [],
Map Tile API Developer's Guide 45► User Guide
"Saturday": [], "Sunday": [], "Holiday": [] }, "parking size": "", "parking hours": { "Monday": [], "Tuesday": [], "Wednesday": [], "Thursday": [], "Friday": [], "Saturday": [], "Sunday": [], "Holiday": [] } }]
Name Type Description
name String Name of the building
bounding boxes Bounding box Array of bounding boxes (one of icon box or annotation box)
info Transit Stop Info Each transit stop info has:
1. position (latitude/longitude)
2. official name
3. informal name
4. Places id
5. operating hours
6. parking size (possible values: "5" (5 or less), "10" (10 or less),
"50" (50 or less), "200" (200 or less), "200+" (more than 200),
"unknown")
7. parking hours
Note: Parking information is provided for Transit Stations
(i.e., large Train & Bus Stations) so that users can have an
entry level understanding of whether they may be able to Park
& Ride at that location. There are two cases covered in the
content
• Parking Size = The number of parking spaces found on
location at the Transit Station.
• Parking Hours = Difference between whether or not
overnight parking is allowed.
POIs
Map Tile API Developer's Guide 46► User Guide
POIs field show information about different POIs in the map including the name, geoposition,
bounding boxes and an array of POI info objects. If you want to get information about POIs in the
metainfo tile you need to use the pois parameter. The format is as follows:
"name": "","geoposition": { "latitude": , "longitude":},"bounding boxes": [],"info": []
Name Type Description
name String Name of the POI
geoposition Geo Coordinate Location of the POI
bounding boxes Bounding box Array of bounding boxes (icon box or annotation box)
info Array of POI Info Each POI info object can have the following attributes:
• ADDR_COUNTRY CODE
• ADDR COUNTRY NAME
• ADDR STATE NAME
• ADDR STATE CODE
• ADDR PROVINCE NAME
• ADDR COUNTY NAME
• ADDR CITY NAME
• ADDR DISTRICT NAME
• ADDR POSTAL CODE
• ADDR TOWNSHIP NAME
• ADDR NEIGHBORHOOD NAME
• ADDR STREET NAME
• ADDR HOUSE NUMBER
• ADDR CONTINENT NAME
• ADDR TYPE NAME
• ADDR POPULATION
• ADDR BUILDING NAME
• ADDR BUILDING FLOOR
• ADDR BUILDING ROOM
• ADDR BUILDING ZONE
• PLACE NAME
Map Tile API Developer's Guide 47► User Guide
Name Type Description
• PLACE PRE NAME
• PLACE POST NAME
• PLACE TYPE
• PLACE CATEGORY
• PLACE CATEGORY ID
• PLACE DESCRIPTION
• PLACE_PHONE NUMBER
• PLACE URL
• PLACE PREMIUM URL ID
• PLACE PREMIUM NODE ID
• PLACE ADVERTISEMENT STRING
• TZ OFFSET MINUTES
• OTHER DATA
• PLACE ICON ID
• LOCATION TYPE
• LOCATION META
• LOCATION TEXT
• ADDR AREA ID
Common fields
Field Name Type Description
left Float Location of the left coordinate in the tile
top Float Location of the top coordinate in the tile
width Float Width of the bounding box
Bounding Box
height Float Height of the bounding box
latitude Float ( 6 decimals ) Latitude of the geo coordinateGeo coordinate
longitude Float ( 6 decimals ) Longitude of the geo coordinate
type String Type of city between National Capital, Provincial Capital and
Other
name String Official name of the city
alternative
names
Array of arrays Alternative names of the city, each array containing the
country code as String and the name as String
country code String Three letter country code following ISO
City Center Info
position Geo coordinate Location of the city center
Map Tile API Developer's Guide 48► User Guide
Field Name Type Description
population Integer Population of the city
x Integer Coordinate x of the tile coordinateTile Coordinate
y Integer Coordinate y of the tile coordinate
Sector info Sector Information Sector height information
Each sector has
1. info
2. vertices (an array of x/y values, as in [ x1, y1, x2, y2 ... ] )
3. polygons (an array of polygons, each polygon being a
set of indices of the vertices array)
4. outlines (an array of outlines, each outline being a set of
indices of the vertices array)
Two examples are provided in this section, both using mgen=2, to illustrate the format described
above. To get additional information about how to use it please check the Examples section.
This example shows a locatin in Berlin and the request looks like:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/9/275/167/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
The response looks like:
{ "metadata" : {"street labels":[ ],"labels":[{ "name": "1", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 96, 240.39, 18, 12 ] } ], "region": "DEU", "category": 1, "route name": "B1", "route level": 3, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=1®ion=DEU&label=B1&route_level=3&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" },{ "name": "158", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 166.38, 129.27, 22, 12 ] } ], "region": "DEU", "category": 1, "route name": "B158", "route level": 3, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=1®ion=DEU&label=B158&route_level=3&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" },{ "name": "114", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 13.38, 158.60, 23, 16 ] } ], "region": "DEU", "category": 0, "route name": "A114", "route level": 2, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A114&route_level=2&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" },{ "name": "10", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 73.62, 173.42, 22, 16 ] } ], "region": "DEU", "category": 0, "route name": "A10", "route level": 2, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A10&route_level=2&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" },{ "name": "11", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 64.25, 153.86, 22, 16 ] } ], "region": "DEU", "category": 0, "route name": "A11",
Map Tile API Developer's Guide 49► User Guide
"route level": 2, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A11&route_level=2&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" },{ "name": "2", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 54.88, 172.54, 18, 12 ] } ], "region": "DEU", "category": 1, "route name": "B2", "route level": 3, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=1®ion=DEU&label=B2&route_level=3&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" },{ "name": "109", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 49.88, 28.25, 22, 12 ] } ], "region": "DEU", "category": 1, "route name": "B109", "route level": 3, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=1®ion=DEU&label=B109&route_level=3&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" }],"city center labels":[{"name": "Berlin", "text box":[ 9, 218, 49.45, 20.50 ], "bullet box":[ 4, 234, 5, 5 ], "city center info": {"type":"NATIONAL CAPITAL", "name": "Berlin", "alternative names":[["ARA", "#####"], ["BAQ", "Berlin"], ["BUL", "######"], ["BUX", "Berlin"], ["CAT", "Berlín"], ["CHI", "##"], ["CHT", "##"], ["CZE", "Berlín"], ["CZX", "Berlin"], ["DAN", "Berlin"], ["DUT", "Berlijn"], ["ENG", "Berlin"], ["EST", "Berliin"], ["ESX", "Berliin"], ["FIN", "Berliini"], ["FRE", "Berlin"], ["GER", "Berlin"], ["GRE", "########"], ["GRX", "Verolino"], ["HIN", "######"], ["HIX", "Barlin"], ["HUN", "Berlin"], ["HUX", "Berlin"], ["ICE", "Berlín"], ["IND", "Berlin"], ["ITA", "Berlino"], ["JPN", "####"], ["JPX", "Berurin"], ["KOR", "###"], ["KOX", "Be Reul Rin"], ["LAV", "Berl#ne"], ["LAX", "Berline"], ["LIT", "Berlynas"], ["LIX", "Berlynas"], ["MAY", "Berlin"], ["NOR", "Berlin"], ["POL", "Berlin"], ["POR", "Berlim"], ["POX", "Berlin"], ["PYN", "Bo Lin"], ["RMX", "Berlin"], ["RUM", "Berlin"], ["RUS", "######"], ["RUX", "Berlin"], ["SCR", "Berlin"], ["SLO", "Berlín"], ["SLX", "Berlin"], ["SPA", "Berlín"], ["SRX", "Berlin"], ["SWE", "Berlin"], ["THA", "########"], ["TUR", "Berlin"], ["TUX", "Berlin"], ["UKR", "######"], ["UKX", "Berlin"]], "country code": "DEU", "position": {"latitude":52.514648, "longitude":13.375854}, "population": 3442675 } },{"name": "Eberswalde", "text box":[ 167, 36, 58.22, 11.75 ], "bullet box":[ 165, 45, 2, 2 ], "city center info": {"type":"OTHER", "name": "Eberswalde", "alternative names":[], "country code": "DEU", "position": {"latitude":52.833251, "longitude":13.815307}, "population": 41175 } },{"name": "Bernau bei Berlin", "text box":[ 83, 117, 55.08, 22.75 ], "bullet box":[ 81, 137, 2, 2 ], "city center info": {"type":"OTHER", "name": "Bernau bei Berlin", "alternative names":[], "country code": "DEU", "position": {"latitude":52.679443, "longitude":13.584594}, "population": 36154 } },{"name": "Strausberg", "text box":[ 191, 192, 51.91, 10.50 ], "bullet box":[ 189, 200, 2, 2 ], "city center info": {"type":"OTHER", "name": "Strausberg", "alternative names":[], "country code": "DEU", "position": {"latitude":52.575073, "longitude":13.881225}, "population": 26221 } },{"name": "Wandlitz", "text box":[ 43, 83, 40.47, 10.50 ], "bullet box":[ 41, 91, 2, 2 ], "city center info": {"type":"OTHER", "name": "Wandlitz", "alternative names":[], "country code": "DEU", "position": {"latitude":52.756347, "longitude":13.474731}, "population": 21530 } },{"name": "Neuenhagen bei Berlin", "text box":[ 121, 211, 58.64, 20.50 ], "bullet box":[ 119, 229, 2, 2 ], "city center info": {"type":"OTHER", "name": "Neuenhagen bei Berlin", "alternative names":[], "country code": "DEU", "position": {"latitude":52.525634, "longitude":13.688964}, "population": 16755 } },{"name": "Ahrensfelde", "text box":[ 81, 192, 56.22, 10.50 ], "bullet box":[ 79, 200, 2, 2 ], "city center info": {"type":"OTHER", "name": "Ahrensfelde", "alternative names":[], "country code": "DEU", "position": {"latitude":52.575073, "longitude":13.579101}, "population": 13114 } },{"name": "Bad Freienwalde (Oder)", "text box":[ 165.17, 56, 75.83, 20.50 ], "bullet box":[ 241, 74, 2, 2 ], "city center info": {"type":"OTHER", "name": "Bad Freienwalde (Oder)", "alternative names":[], "country code": "DEU", "position": {"latitude":52.783813, "longitude":14.024047}, "population": 12964 } },{"name": "Werneuchen", "text box":[ 137, 159, 57.83, 10.50 ], "bullet box":[ 135, 167, 2, 2 ], "city center info": {"type":"OTHER", "name": "Werneuchen", "alternative names":[], "country code": "DEU", "position": {"latitude":52.630004, "longitude":13.732910}, "population": 7943 } },{"name": "Biesenthal", "text box":[ 105, 76, 49.03, 10.50 ], "bullet box":[ 103, 84, 2, 2 ], "city center info": {"type":"OTHER", "name": "Biesenthal", "alternative names":[], "country code": "DEU", "position": {"latitude":52.767333, "longitude":13.645019}, "population": 5563 } },{"name": "Rehfelde", "text box":[ 207, 218, 42.12, 10.50 ], "bullet box":[ 205, 226, 2, 2 ], "city center info": {"type":"OTHER", "name": "Rehfelde", "alternative names":[], "country code": "DEU", "position": {"latitude":52.531127, "longitude":13.925170}, "population": 4462 } },
Map Tile API Developer's Guide 50► User Guide
{"name": "Liebenwalde", "text box":[ 15, 13, 57.72, 10.50 ], "bullet box":[ 13, 21, 2, 2 ], "city center info": {"type":"OTHER", "name": "Liebenwalde", "alternative names":[], "country code": "DEU", "position": {"latitude":52.871704, "longitude":13.397827}, "population": 4390 } },{"name": "Chorin", "text box":[ 189, 0, 31.52, 10.50 ], "bullet box":[ 187, 2, 2, 2 ], "city center info": {"type":"OTHER", "name": "Chorin", "alternative names":[], "country code": "DEU", "position": {"latitude":52.904663, "longitude":13.875732}, "population": 2430 } },{"name": "Oderberg", "text box":[ 203.75, 17, 45.25, 10.50 ], "bullet box":[ 249, 25, 2, 2 ], "city center info": {"type":"OTHER", "name": "Oderberg", "alternative names":[], "country code": "DEU", "position": {"latitude":52.866210, "longitude":14.046020}, "population": 2229 } },{"name": "Britz", "text box":[ 139.81, 4, 23.19, 10.50 ], "bullet box":[ 163, 12, 2, 2 ], "city center info": {"type":"OTHER", "name": "Britz", "alternative names":[], "country code": "DEU", "position": {"latitude":52.888183, "longitude":13.809814}, "population": 2201 } },{"name": "Rüdnitz", "text box":[ 99, 103, 36.39, 10.50 ], "bullet box":[ 97, 111, 2, 2 ], "city center info": {"type":"OTHER", "name": "Rüdnitz", "alternative names":[], "country code": "DEU", "position": {"latitude":52.723388, "longitude":13.628540}, "population": 1839 } },{"name": "Marienwerder", "text box":[ 89, 30, 63.73, 10.50 ], "bullet box":[ 87, 38, 2, 2 ], "city center info": {"type":"OTHER", "name": "Marienwerder", "alternative names":[], "country code": "DEU", "position": {"latitude":52.844238, "longitude":13.601074}, "population": 1731 } },{"name": "Prötzel", "text box":[ 210.95, 152, 34.09, 10.50 ], "bullet box":[ 227, 164, 2, 2 ], "city center info": {"type":"OTHER", "name": "Prötzel", "alternative names":[], "country code": "DEU", "position": {"latitude":52.635498, "longitude":13.985595}, "population": 1143 } }],"buildings":[ ],"transit stops":[ ],"POIs":[ ]}}
This other example contains a metadata response for a close-up of a location in Berlin including
street labels. The request looks like:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/13/4402/2685/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
And the response looks like:
{ "metadata" : {"street labels":[ { "name":"Hansastraße", "font size":"11", "vertices": [ 163.53, 118.07, 175.54, 102.83, 178.96, 98.49, 183, 93.89, 187.21, 90.07, 190.71, 87, 194.13, 84.78, 210.95, 75.05 ] },{ "name":"Weißenseer Weg", "font size":"11", "vertices": [ 147.11, 240.99, 172.97, 288.05, 176.49, 297.99, 182.69, 319.32 ] } ],"labels":[{ "name": "Volkspark Prenzlauer Berg", "type":"TEXT", "bounding boxes": [ { "annotation box":[ 64.67, 243, 55.03, 37.75 ] } ] },{ "name": "Weißenseepark", "type":"TEXT", "bounding boxes": [ { "annotation box":[ 55.70, 78.21, 77.97, 11.75 ] } ] },{ "name": "Sportforum Hohenschönhausen", "type":"TEXT", "bounding boxes": [ { "text box":[ 167.38, 215.11, 11, 11 ] } ] },{ "name": "Sportkomplex Buschallee", "type":"TEXT", "bounding boxes": [ { "text box":[ 237.88, 61.04, 11, 11 ] } ] },{ "name": "Sportforum Hohenschönhausen", "type":"TEXT", "bounding boxes": [ { "annotation box":[ 123.10, 190.11, 99.55, 23.75 ] } ] },{ "name": "Sportkomplex Buschallee", "type":"TEXT", "bounding boxes": [ { "annotation box":[ 207.59, 36.04, 71.56, 23.75 ] } ] }],"city center labels":[{"name": "Alt-Hohenschönhausen", "text box":[ 248.95, 133.43, 126.09, 29.50 ], "city center info": {"type":"OTHER", "name": "Alt-Hohenschönhausen",
Map Tile API Developer's Guide 51► User Guide
"alternative names":[], "country code": "DEU", "position": {"latitude":52.547607, "longitude":13.500823}, "population": 0 } },{"name": "Weißensee", "text box":[ 84.66, 8.86, 70.67, 15.50 ], "city center info": {"type":"OTHER", "name": "Weißensee", "alternative names":[], "country code": "DEU", "position": {"latitude":52.5613403, "longitude":13.467864}, "population": 0 } }],"buildings":[ ],"transit_stops":[ ],"POIs":[ ]}}
Traffic TilesTraffic related tiles are used to display the traffic flow on the road network and to highlight
congestion. This article provides basic information about traffic tiles, explains how to access them
and describes the available options. It also demonstrates the visual styles used by the different types
of traffic tiles.
Traffic tiles always display the current traffic information. This information reflects the traffic
congestion on the road network and is presented to the user by lines drawn along the affected
streets and roads. The displayed traffic congestion distinguishes between four congestion levels:
Free Flow (green): Road segments where the average speed of the traffic is around the expect-
ed free flow speed, mostly due to a small volume of cars.
Heavy (yellow): Road segments with a higher volume of cars, which would lead to an average
speed that is less than the expected free flow speed.
Queuing (red): Road segments with a very high volume of cars that would lead to an aver-
age speed closer to stopping and that would reduce the distance between 2
successive vehicles, which would have the effect of creating a queue.
Blocked (black): Road segments that are blocked, due to construction sites, accidents and
such.
The congestion levels are represented with different colors, as listed above.
Traffic Tile Types
There are various traffic related tile types that can be rendered which differ in the visual style of the
image. The images below demonstrate a range of possible types.
Map Tile API Developer's Guide 52► User Guide
Traffic Tile Flow Tile Flow Base Tile Flow and Label Tile
map tile with traffic flow transparent tile with only
traffic flow
base tile (no labels) with
traffic flow
tile with traffic flow and labels
Rendering by Traffic Congestion Levels
Based on the congestion levels listed above, it is possible to render traffic lines only for those road
segments where a certain minimum congestion level of traffic is reached.
heavy traffic and above queuing traffic and above
Validity of Traffic Data
It is important to bear in mind that traffic information remains valid only for a short period of time
(about 1-5 minutes). For this reason, client applications should not cache traffic tiles.
Traffic Coverage
Traffic data is available for a large number of countries and regions. In some countries availability
is limited to certain areas. The table below provides the countries and regions where traffic data is
available in general.
Table 4: Traffic data availability
Country name Availability
Austria all areas
Belgium all areas
Map Tile API Developer's Guide 53► User Guide
Country name Availability
Czech Republic all areas
Denmark all areas
Finland all areas
France all areas
Germany all areas
Greece all areas
Hungary all areas
Indonesia all areas
Ireland all areas
Italy all areas
Luxembourg all areas
Netherlands all areas
Norway all areas
Poland all areas
Portugal all areas
Puerto Rico all areas
Russia all areas
Singapore all areas
Spain all areas
Slovakia all areas
Slovenia all areas
Sweden all areas
Switzerland all areas
Turkey all areas
United Kingdom all areas
Ukraine all areas
Saudi Arabia all areas
South Africa all areas
UAE all areas
Argentina all areas
Map Tile API Developer's Guide 54► User Guide
Country name Availability
Brazil all areas
Canada Alberta:
Calgary
Edmonton
British Columbia:
Vancouver/Surrey/Burnaby
Windsor/Tecumseh/LaSalle/Lakeshore
Ontario:
Hamilton/Burlington
Kitchener/Cambridge/Waterloo
London
Oshawa/Whitby/Clarington
St.Catharines/Niagara Falls/Welland
Toronto/Mississauga
Quebec:
Montreal/Laval
Ottawa/Gatineau
Quebec City
Mexico Mexico City
Guadalajara
Monterrey
USA All states
Australia Canberra Metro
Sydney Metro
Melbourne Metro
Brisbane Metro
Adelaide Metro
Perth Metro
Hobart
Darwin
China Beijing
Changchun
Changsha
Map Tile API Developer's Guide 55► User Guide
Country name Availability
Chengdu
Chongqing
Dongguan
Foshan
Fuzhou
Guangzhou
Hangzhou
Kunming
Nanjing
Ningbo
Qingdao
Quanzhou
Shanghai
Shenyang
Shenzhen
Shijiazhuang
Suzhou
Taizhou
Tianjin
Wuhan
Wuxi
Xiamen
Zhongshan
Zhuhai
India Delhi NCR
Greater Mumbai
Bangalore
Malaysia all areas
New Zealand all areas
Taiwan Taichung, Taipei
Thailand all areas
It is important to note that even if traffic information is available for a specific country, not all of the
road network and road classes (for example, highways, main roads, local streets) are covered. The
Map Tile API Developer's Guide 56► User Guide
quality and range of traffic data for the covered areas and road classes varies between countries and
depends on the available traffic data sources and providers.
A Traffic Tile Request
The following example request obtains a basic traffic tile.
http://1.traffic.maps.cit.api.here.com/maptile/2.1/traffictile/newest/normal.traffic.day/12/2200/1343/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
See the API Reference for detailed information about the possible options.
Frequently asked questionsFrequently Asked Questions about the Map Tile API.
How do I request the right info?You always need to query the info resource of the same Base URL you are using.
Example: If you are using map tiles from the Base Map Tile Resources pool, you should query
the info page of that same URL. In other words, if you are creating requests as follows:
http://1.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/13/4400/2686/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
You need to query the info page as follows:
http://1.base.maps.cit.api.here.com/maptile/2.1/info?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Please check Requesting the Right Map Version on page 26 for more details.
If you use different map tile resources, you need to query all URLs separately as they contain
different information.
Map Tile API Developer's Guide 57► User Guide
How do I request the right copyright information?You always need to query the copyright resource of the same Base URL you are using.
Example: If you are using map tiles from the Base Map Tile Resources pool, you should query
the copyright page of that same URL. In other words, if you are creating requests as follows:
http://1.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/13/4400/2686/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
You need to query the copyright page as follows:
http://1.base.maps.cit.api.here.com/maptile/2.1/copyright/newest?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
If you use different map tile resources, you need to query all URLs separately as they may contain
different copyright information.
How do I calculate the distance to the grounddepending on the zoom level?When using a Mercator Projection on a tile based system, it is better to talk about how many meters a
pixel represents rather then to calculate the scale of the map at a certain zoom level.
Please remember that due to the limitations of Mercator Projection the ordinate y becomes infinite
at the poles and the map must be truncated at some latitude less than ninety degrees. This needs
to be done symmetrically. Our map is truncated at 80ºN and 66ºS with the result that European
countries are moved towards the centre of the map.
For example, at zoom level 0 where the whole world consists of a single tile 256 pixels wide, we can
calculate meters by pixel (m/px) using an Earth radius of 6372.7982km as 156,412. That would yield
an approximated scale of 1:500 Mill. (taking the scale as an approximate size comparison referring to
distances on the equator), as the map scale will depend on the monitor we have used a monitor with a
0.3 mm / pixel.
Nevertheless, you can use a formula to calculate the metres per pixel for 256 pixel tiles. The distance
represented by one pixel (S) is given by:
S=C*cos(y)/2^(z+8)
Map Tile API Developer's Guide 58► User Guide
where:
C is the equatorial circumference of the Earth
z is the zoom level
y is the latitude of where you are interested in the scale in degrees
Since the Earth is actually ellipsoidal, there will be a slight error in this calculation (0.3% maximum)
How do I know if a particular resource is available?You can always use the info page resource to query if a particular tile type or scheme is
available in the map tile resource URL you choose.
ExamplesThis section provides examples of requests against the Map Tile API resources along with the
corresponding results.
Note that all requests require the authentication credentials provided via the parameters app_id
and app_code (see Acquiring Credentials on page 16). The example requests in the following
articles show all the required parameters, but discuss only those specific to each request.
All examples in this document use newest as the hashcode value for the map but you should check
Requesting the Right Map Version on page 26 on how to request the right hashcode for your
application.
Base Map Tile ExamplesThis section provides examples using the base map tile resources.
Normal Day TileThis article shows how to make a request for a normal.day map tile.
User story
The user wants to obtain a full color street map image of Chicago. The tile requested uses the
normal.day map schema.
Map Tile API Developer's Guide 59► User Guide
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [11/525/761], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/11/525/761/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 60► User Guide
ResponseThe response to the request delivers the following full color street map image of Chicago:
Figure 7: Normal Day Tile
Normal Day Grey TileThis article shows a request for a color-reduced map tile in daylight mode (used for background
maps).
User story
The user wants to obtain an image showing a map of Chicago where the road network is displayed
in grey scale to remove the emphasis from the road network itself. The tile requested uses the
normal.day.grey map schema.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 61► User Guide
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day.grey], see also scheme
{zoom}/{column}/{row} [11/525/761], see also Mercator Projection on
page 24
{size} = 256, see also size
{format} = png8, see also format
RequestThe code block below demonstrates a complete request for a map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day.grey/11/525/761/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 62► User Guide
ResponseThe response to the request delivers the following grey scale street map image of Chicago:
Figure 8: Normal Day Grey Tile
Normal Day Transit Map TileThis article shows a request for a transit map tile.
User story
The user wants to obtain an image showing a transit map tile (public transport) for an area east of
Vincennes (a suburb of Paris). The tile requested uses the normal.day.transit map schema,
indicating public transport lines.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 63► User Guide
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day.transit], see also scheme
{zoom}/{column}/{row} [13/4152/2818], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a transit map tile.
http://1.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day.transit/13/4152/2818/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 64► User Guide
ResponseThe response to the request delivers the following image:
Figure 9: Normal Day Transit Map Tile
Reduced Day TileThis article shows how to make a request for a reduced.day map tile.
User story
The user wants to obtain a reduced color street map image of New York. The tile requested uses the
reduced.day map schema.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
Map Tile API Developer's Guide 65► User Guide
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [reduced.day], see also scheme
{zoom}/{column}/{row} [14/4823/6160], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/reduced.day/14/4823/6160/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 66► User Guide
ResponseThe response to the request delivers the following reduced color street map image of New York:
Figure 10: Reduced Day Tile
Pedestrian Day TileThis article shows how to make a request for a pedestrian.day map tile.
User story
The user wants to obtain a pedestrian color street map image of New York showing all relevant
information for pedestrians. The tile requested uses the pedestrian.day map schema.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
Map Tile API Developer's Guide 67► User Guide
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [pedestrian.day], see also scheme
{zoom}/{column}/{row} [16/19302/24625], see also Mercator Projection
on page 24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/pedestrian.day/16/19302/24625/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 68► User Guide
ResponseThe response to the request delivers the following street map image of New York showing
information relevant to pedestrians:
Figure 11: Pedestrian Day Tile
Fleet TileThis article shows a request for a fleet map tile.
User story
The user wants to obtain an image showing a fleet map tile for an area west of the central station in
Berlin, Germany. The tile is to show a normal day view of the map indicating public fleet information.
Note: Please note that the fleet tile use a custom map style.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 69► User Guide
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [16/35201/21491], see also Mercator Projection
on page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: style = ?style=fleet, see also style
RequestThe code block below demonstrates a complete request for a fleet map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/16/35201/21491/256/png8?style=fleet&app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 70► User Guide
ResponseThe response to the request delivers the following image:
Figure 12: Fleet Tile
Truck TileThis article shows requests for truck map tiles.
User story
The user wants to obtain two images showing a truck map tile for an area west of the central station
in Berlin, Germany. The first tile is to show a normal day view of the map indicating public truck
information, while the second tile is to show only those roads where trucks are allowed as well as
truck-related information (in other words, this tile is not to show truck information overlaid on a
normal map).
Map Tile API Developer's Guide 71► User Guide
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile = trucktile or truckonlytile, see also (resource) type
URL variables: {map id} = newest, see also Requesting the Right Map Version on page
26
{scheme} = normal.day, see also scheme
{zoom}/{column}/{row} = 16/35201/21491, see also Mercator Projection
on page 24
{size} = 256, see also size
{format} = png8, see also format
Parameters: None
Request for a Truck Map TileThe code block below demonstrates a complete request for a truck map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/trucktile/newest/normal.day/16/35201/21491/256/png8?style=fleet&app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 72► User Guide
Response to Truck Tile RequestThe response to the request delivers the following image:
Figure 13: Truck Tile
Request for a Truck-information-only TileThe code block below demonstrates a request for a truck-information-only tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/truckonlytile/newest/normal.day/16/35201/21491/256/png8?style=fleet&app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 73► User Guide
Response to Truck-information-only Tile RequestThe response contains the image below. Note that the tile contains a transparent background, which
is shown here in black.
Figure 14: Truck-only Tile
Congestion information TilesThis article shows requests for map tiles containing congestion and/or environmental zone
information.
User story
The user wants to obtain two images showing congestion information for an area northwest of Berlin,
Germany. The first tile is to show a normal map tile day view of the map showing the congestion zone,
while the second tile is to show a truck map tile day view of the same location with the congestion
zone as well.
Map Tile API Developer's Guide 74► User Guide
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile = maptile or trucktile, see also (resource) type
URL variables: {map id} = newest, see also Requesting the Right Map Version on page
26
{scheme} = normal.day, see also scheme
{zoom}/{column}/{row} = 11/1100/671, see also Mercator Projection on
page 24
{size} = 256, see also size
{format} = png8, see also format
Parameters: congestion = ?congestion, see also congestion
Request for a Map Tile with congestionThe code block below demonstrates a complete request for a map tile with congestion.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/11/1100/671/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&congestion
Map Tile API Developer's Guide 75► User Guide
Response to Map Tile with congestionThe response to the request delivers the following image:
Figure 15: Map Tile with congestion
Request for a Truck Tile with congestionThe code block below demonstrates a request for a truck tile with congestion.
http://2.base.maps.cit.api.here.com/maptile/2.1/trucktile/newest/normal.day/11/1100/671/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&congestion
Map Tile API Developer's Guide 76► User Guide
Response to a Truck Tile with congestion RequestThe response contains the image below.
Figure 16: Truck Tile with congestion
Base Map Day TileThis article shows how to make a request for a basetile map tile.
User story
The user wants to obtain a basemap image of Philadelphia without labels because he wants to overlay
his own information. The tile requested uses the basetile map tile.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [basetile], see also (resource) type
Map Tile API Developer's Guide 77► User Guide
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [114/4769/6203], see also Mercator Projection
on page 24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a basemap tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/basetile/newest/normal.day/14/4769/6203/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 78► User Guide
ResponseThe response to the request delivers the following base map image of Philadelphia:
Figure 17: Base Map Day Tile
Label tile Day TileThis article shows how to make a request for a labeltile map tile.
User story
The user wants to obtain a labeltile image of Philadelphia without background because he wants to
put it on top of his own content. The tile requested uses the labeltile map tile.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [labeltile], see also (resource) type
Map Tile API Developer's Guide 79► User Guide
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [14/4769/6203], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a labeltile tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/labeltile/newest/normal.day/14/4769/6203/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 80► User Guide
ResponseThe response to the request delivers the following labeltile map image of Philadelphia. Note that the
tile contains a transparent background, which is shown here in black.
Figure 18: Label Map Day Tile
Street tile Day TileThis article shows how to make a request for a streettile map tile.
User story
The user wants to obtain a streettile image of Philadelphia without background because he wants to
put it on top of his own content. The tile requested uses the streettile map tile.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 81► User Guide
Resource: maptile [streettile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [14/4769/6203], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a streettile tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/streettile/newest/normal.day/14/4769/6203/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 82► User Guide
ResponseThe response to the request delivers the following streettile map image of Philadelphia. Note that the
tile contains a transparent background, which is shown here in black.
Figure 19: Label Map Day Tile
Dual Label TileThis article shows how to make a request for a dual label map tile.
User story
The user wants to obtain a map image of Shanghai with the labels in English as the main language and
Simplified Chinese as the secondary language. The tile requested uses the lg and lg2 parameters.
Note: Any combination of maptile and scheme can be used for dual label, in the followingexample we have chosen the maptile map tile and the normal.day scheme.
Map Tile API Developer's Guide 83► User Guide
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [11/1715/836], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: lg = ENG, see also lg lg2 = CHI, see also lg2
RequestThe code block below demonstrates a complete request for a dual label tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/11/1715/836/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&lg=ENG&lg2=CHI
Map Tile API Developer's Guide 84► User Guide
ResponseThe response to the request delivers the following map tile of Shanghai.
Figure 20: Dual Label Map Tile
512 pixel Normal Day TileThis article shows how to make a request for a normal.day map tile of size 512 pixel by 512 pixel.
This kind of request can be used to minimize the number of tiles needed to create a map.
User story
The user wants to obtain a full color map image of Europe using a minimum number of tiles. The tile
requested uses the 512 size.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 85► User Guide
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [4/8/5], see also Mercator Projection on page
24
{size} [512], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/4/8/5/512/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 86► User Guide
ResponseThe response to the request delivers the following map image of central Europe:
Figure 21: 512 pixel Normal Day Tile
Hires Normal Day TileThis article shows how to make a request for a hires map tile.
This kind of request can be used for devices designed for hires.
Map Tile API Developer's Guide 87► User Guide
Use of the parameter ppi can be combined with tiles of size 512 by 512 512 pixel Normal Day Tile on
page 84
User story
The user wants to obtain a hires map image of the center of Madrid. The tile requested uses the
parameter ppi.
Note: Please note that the value used for ppi in this example is 320 which correspondswith hires but 250 is accepted as well and is recommended for mobile devices that are notdesigned for hires.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [18/128369/98837], see also Mercator
Projection on page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: ppi = ?ppi=320, see also ppi
RequestThe code block below demonstrates a complete request for a map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/18/128369/98837/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&ppi=320
Map Tile API Developer's Guide 88► User Guide
ResponseThe response to the request delivers the following map image of central Madrid:
Figure 22: Hires Normal Day Tile
Poi Map TileThis article shows how to make a request for a tile with POI specific information.
User story
The user wants to obtain a map image of the center of San Francisco with POI information. The tile
requested uses the pois parameter.
Note: Please note that the POI information shown in the tile is the one available at themoment of the creation of the map, it is not synchronized online with any other service.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 89► User Guide
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [19/83873/202622], see also Mercator
Projection on page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: pois = pois, see also pois
RequestThe code block below demonstrates a complete request for a poi map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/83873/202622/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&pois
Map Tile API Developer's Guide 90► User Guide
ResponseThe response to the request delivers the following map image of San Francisco:
Figure 23: Poi Map Tile
Custom Map Style TileThis article shows how to make a request for a custom map style tile.
This kind of request can be used to display special styles designed for an specific purpose.
User story
The user wants to obtain a map image of the center of Madrid in the specific style of the game
Dreamworks. The tile requested uses the style parameter.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 91► User Guide
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [14/8024/6177], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: style = ?style=dreamworks, see also style
RequestThe code block below demonstrates a complete request for a custom map style tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/14/8024/6177/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&style=dreamworks
Map Tile API Developer's Guide 92► User Guide
ResponseThe response to the request delivers the following map image of central Madrid:
Figure 24: Custom Map Style Tile
Range Tile RequestsRanged tile requests are used to request more than one tile in a single request.
This is achieved by using the parameter range. This parameter can either be 2x2, 3x3 or 4x4,
which indicates the size of the array of tiles returned.
When the parameter range is used, the parameter output=base64 must be used as well in order to
get encoded base64 tiles as a result in a JSON object.
Note: Ranged requests can be combined with any other parameter, for example, it is valid torequest a tile with pois and range=2x2 to get four tiles with poi information on them.
User story
The user wants to obtain several tiles in a single request.
Map Tile API Developer's Guide 93► User Guide
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [19/83870/202622], see also Mercator
Projection on page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: output = base64, see also output range = 2x2, see also range
RequestThe code block below demonstrates a complete request for ranged tiles.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/83870/202622/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&output=base64&range=2x2
ResponseThis request results in a JSON object that:
has four tiles (range is 2x2),
has base64 encoded tiles (output is base64).
The output of this request is shown below.
Note: The base64 images have been shorted for readability.
"iVBORw0KGgoAAAANSUhEUgAAAQAAAAEACAMAAABrrFhUAAADAFBMVEUnJyekpKT ...","iVBORw0KGgoAAAANSUhEUgAAAQAAAAEACAMAAABrrFhUAAADAFBMVEVIX2zg1tX ...","iVBORw0KGgoAAAANSUhEUgAAAQAAAAEACAMAAABrrFhUAAACnVBMVEUAAADZ0cz ...","iVBORw0KGgoAAAANSUhEUgAAAQAAAAEACAMAAABrrFhUAAADAFBMVEW3rq708/P ..."
Map Tile API Developer's Guide 94► User Guide
Metainfo Tile ExamplesThis section provides examples using the metainfo capabilities.
Note: The metainfo feature can be used with different resources (Base, Aerial, Pano)depending on the scheme and tile combination you need. Please note that most of theexamples are using base tiles but you could use areal for example by changing the scheme toget different results.
Metainfo TileThis article shows requests for metainfo tiles, also known as meta data tiles. Usage of the parameter
metadata renders a text based (json) tile with the relevant objects in it, such as street labels, city
labels, icons… Pixel coordinates are used to position some objects (bounding boxes), some others
have latitudes and longitudes associated with them, other kinds of objects have different properties
such as road icons that contain icon information indicating, for example, that the object is for
highway signs…
In many cases these requests are used together with callback_func.
User story
The user wants to parse the streets rendered in Chicago with the roadsigns used. The JSON text
based tile is to represent the relevant street names rendered with the road icons used for the
highway.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile or maptile, see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [13/4094/2724], see also Mercator Projection on
page 24
{size} [256], see also size
Map Tile API Developer's Guide 95► User Guide
{format} [png8], see also format
Request for a Metadata Map TileThe code block below demonstrates a complete request for a metadata map tile.
http://1.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/11/525/761/256/png8 ?app_id=DemoAppId01082013GAL &app_code=AJKnXv84fjrb0KIHawS0Tg &metadata=metaonly
Response to Metadata Map Tile RequestThe response contains the following text.
{ "metadata" : {"street labels":[],"labels":[{"name":"90", "type": "ROADSIGN", "bounding boxes": [ { "left":113, "top":204, "width":18, "height":18 } ] },{"name":"55", "type": "ROADSIGN", "bounding boxes": [ { "left":70, "top":110, "width":18, "height":18 } ] }],"city center labels":[{"name": "Chicago", "text box": { "left":78, "top":22, "width":82.0938, "height":25.5 }, "city center info": { "type": "OTHER", "name":"Chicago", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.885400, "longitude":-87.632400 } , "population": 2836658 }},{"name": "Archer Heights", "text box": { "left":-36, "top":167, "width":39, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Archer Heights", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.811200, "longitude":-87.725800 } , "population": 0 }},{"name": "Armour Square", "text box": { "left":101, "top":118, "width":37, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Armour Square", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.835900, "longitude":-87.632400 } , "population": 0 }},{"name": "Back of the Yards", "text box": { "left":47, "top":167, "width":58, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Back of the Yards", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.811200, "longitude":-87.662700 } , "population": 0 }},{"name": "East Garfield Park", "text box": { "left":-9, "top":32, "width":41, "height":33.75 }, "city center info": { "type": "OTHER", "name":"East Garfield Park", "alternative names": [ ], "country_code":
Map Tile API Developer's Guide 96► User Guide
"USA", "position": { "latitude":41.877100, "longitude":-87.706600 } , "population": 0 }},{"name": "East Village", "text box": { "left":42, "top":-5, "width":35, "height":22.75 }, "city center info": { "type": "OTHER", "name":"East Village", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.899100, "longitude":-87.673600 } , "population": 0 }},{"name": "Gage Park", "text box": { "left":14, "top":199, "width":27, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Gage Park", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.794700, "longitude":-87.695600 } , "population": 0 }},{"name": "Grand Boulevard", "text box": { "left":110, "top":172, "width":51, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Grand Boulevard", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.808500, "longitude":-87.621500 } , "population": 0 }},{"name": "Humboldt Park", "text box": { "left":-33, "top":-5, "width":49, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Humboldt Park", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.899100, "longitude":-87.720300 } , "population": 0 }},{"name": "Hyde Park", "text box": { "left":158, "top":199, "width":27, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Hyde Park", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.794700, "longitude":-87.596700 } , "population": 0 }},{"name": "Lawndale", "text box": { "left":-25, "top":70, "width":49, "height":11.75 }, "city center info": { "type": "OTHER", "name":"Lawndale", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.863400, "longitude":-87.714800 } , "population": 0 }},{"name": "Little Village", "text box": { "left":-14, "top":102, "width":35, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Little Village", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.844200, "longitude":-87.712100 } , "population": 0 }},{"name": "Lower West Side", "text box": { "left":34, "top":86, "width":59, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Lower West Side", "alternative names": [ [ "ENG", "Lower West Side" ]], "country_code": "USA", "position": { "latitude":41.852400, "longitude":-87.670900 } , "population": 0 }},{"name": "McKinley Park", "text box": { "left":36, "top":134, "width":47, "height":22.75 }, "city center info": { "type": "OTHER", "name":"McKinley Park", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.827700, "longitude":-87.673600 } , "population": 0 }},{"name": "Near South Side", "text box": { "left":100, "top":81, "width":56, "height":22.75 }, "city center info": { "type": "OTHER", "name":"Near South Side", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.855200, "longitude":-87.627000 } , "population": 0 }},{"name": "Oakland", "text box": { "left":138, "top":145, "width":43, "height":11.75 }, "city center info": { "type": "OTHER", "name":"Oakland", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.825000, "longitude":-87.605000 } , "population": 0 }},{"name": "Old Town", "text box": { "left":84, "top":-11, "width":47, "height":11.75 }, "city center info": { "type": "OTHER", "name":"Old Town", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.904600, "longitude":-87.640700 } , "population": 0 }},
Map Tile API Developer's Guide 97► User Guide
{"name": "West Elsdon", "text box": { "left":-29, "top":204, "width":34, "height":22.75 }, "city center info": { "type": "OTHER", "name":"West Elsdon", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.792000, "longitude":-87.723100 } , "population": 0 }},{"name": "West Englewood", "text box": { "left":40, "top":231, "width":55, "height":22.75 }, "city center info": { "type": "OTHER", "name":"West Englewood", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.778300, "longitude":-87.668200 } , "population": 0 }},{"name": "West Lawn", "text box": { "left":-26, "top":242, "width":28, "height":22.75 }, "city center info": { "type": "OTHER", "name":"West Lawn", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.772800, "longitude":-87.723100 } , "population": 0 }},{"name": "Woodlawn", "text box": { "left":138, "top":231, "width":52, "height":11.75 }, "city center info": { "type": "OTHER", "name":"Woodlawn", "alternative names": [ ], "country_code": "USA", "position": { "latitude":41.781000, "longitude":-87.602200 } , "population": 0 }}]}}
Metadata generation parameterThis article shows requests for metainfo map tiles.
User story
The user wants to obtain metadata information for an image showing a map tile for an area near
Friedenau in Berlin, Germany in order to know the position of the labels to enable interactivity.
Note: Two possible metainfo requests are shown as examples, using the mgen parameter.See also Metainfo Tiles on page 28 for more information about metainfo tile requests.
Original map tile
The tile that the user wants to find more information about is obtained by the following request:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/14/8799/5376/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 98► User Guide
The response to the request delivers the following image:
Figure 25: Map Tile
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [14/8799/5376], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: metadata [metaonly], see also metadata
Map Tile API Developer's Guide 99► User Guide
RequestThe code block below demonstrates a complete request for a metadata map tile.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/14/8799/5376/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly
ResponseThe response to the request delivers the following Meta Info Tile as a JSON object:
{ "metadata" : {"street labels":[{ "name":"Hauptstraße", "font size":"13", "vertices": [ { "x": 139, "y": 0 }, { "x": 177, "y": -35 }, { "x": 183, "y": -40 }, { "x": 196, "y": -49 } ] },{ "name":"Hauptstraße", "font size":"12", "vertices": [ { "x": 15, "y": 158 }, { "x": 20, "y": 152 }, { "x": 24, "y": 147 }, { "x": 28, "y": 141 }, { "x": 32, "y": 136 }, { "x": 42, "y": 123 }, { "x": 45, "y": 119 }, { "x": 49, "y": 115 }, { "x": 59, "y": 104 } ] },],"labels":[{"name":"Friedenau", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":31, "top":240, "width":12, "height":12 } ] },{"name":"Schöneberg", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":157, "top":40, "width":12, "height":12 } ] },{"name":"Innsbrucker Platz", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":55, "top":85, "width":24, "height":12 } ] },{"name":"Friedenau", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":12, "top":227, "width":51, "height":11 } ] },{"name":"Schöneberg", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":134, "top":27, "width":59, "height":11 } ] },{"name":"Innsbrucker Platz", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":23, "top":72, "width":87, "height":11 } ] },{"name":"Cheruskerpark", "type": "TEXT", "bounding boxes": [ { "left":182, "top":0, "width":74, "height":11 } ] },{"name":"Dominicus-Sportplatz", "type": "TEXT", "bounding boxes": [ { "left":179, "top":123, "width":57, "height":24 } ] },{"name":"103", "type": "ROADSIGN", "bounding boxes": [ { "left":62, "top":198, "width":28, "height":20 } ] },{"name":"100", "type": "ROADSIGN", "bounding boxes": [ { "left":212, "top":163, "width":28, "height":20 } ] },{"name":"1", "type": "ROADSIGN", "bounding boxes": [ { "left":188, "top":73, "width":22, "height":15 } ] },{"name":"Friedhof Eisackstraße", "type": "TEXT", "bounding boxes": [ { "left":71, "top":113, "width":65, "height":24 } ] }],"city center labels":[]}}
Map Tile API Developer's Guide 100► User Guide
Request SummaryThe following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [14/8799/5376], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: metadata [metaonly], see also metadata
mgen [2], see also mgen
Request with mgen=2The code block below demonstrates a complete request for a metadata map tile with the parameter
mgen.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/14/8799/5376/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Response with mgen=2The response to the request delivers the following Meta Info Tile as a JSON object:
{ "metadata" : {"street labels":[{ "name":"Hauptstraße", "font size":"13", "vertices": [ { "x": 139, "y": 0 }, { "x": 177, "y": -35 }, { "x": 183, "y": -40 }, { "x": 196, "y": -49 } ] },{ "name":"Hauptstraße", "font size":"12", "vertices": [ { "x": 15, "y": 158 }, { "x": 20, "y": 152 }, { "x": 24, "y": 147 }, { "x": 28, "y": 141 }, { "x": 32, "y": 136 }, { "x": 42, "y": 123 }, { "x": 45, "y": 119 }, { "x": 49, "y": 115 }, { "x": 59, "y": 104 } ] },],"labels":[
Map Tile API Developer's Guide 101► User Guide
{"name":"Friedenau", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":31, "top":240, "width":12, "height":12 } ] },{"name":"Schöneberg", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":157, "top":40, "width":12, "height":12 } ] },{"name":"Innsbrucker Platz", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":55, "top":85, "width":24, "height":12 } ] },{"name":"Friedenau", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":12, "top":227, "width":51, "height":11 } ] },{"name":"Schöneberg", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":134, "top":27, "width":59, "height":11 } ] },{"name":"Innsbrucker Platz", "type": "TRANSIT_STOP", "bounding boxes": [ { "left":23, "top":72, "width":87, "height":11 } ] },{"name":"Cheruskerpark", "type": "TEXT", "bounding boxes": [ { "left":182, "top":0, "width":74, "height":11 } ] },{"name":"Dominicus-Sportplatz", "type": "TEXT", "bounding boxes": [ { "left":179, "top":123, "width":57, "height":24 } ] },{"name":"103", "type": "ROADSIGN", "bounding boxes": [ { "left":62, "top":198, "width":28, "height":20 } ], "region": "DEU", "category": 0, "label": "A103", "uri": "http://image.maps.cit.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A103" },{"name":"100", "type": "ROADSIGN", "bounding boxes": [ { "left":212, "top":163, "width":28, "height":20 } ], "region": "DEU", "category": 0, "label": "A100", "uri": "http://image.maps.cit.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A100" },{"name":"1", "type": "ROADSIGN", "bounding boxes": [ { "left":188, "top":73, "width":22, "height":15 } ], "region": "DEU", "category": 1, "label": "B1", "uri": "http://image.maps.cit.api.here.com/mia/1.6/roadsign?category=1®ion=DEU&label=B1" },{"name":"Friedhof Eisackstraße", "type": "TEXT", "bounding boxes": [ { "left":71, "top":113, "width":65, "height":24 } ] }],"city center labels":[]}}
Extruded BuildingsThis article shows example usage of matainfo tile for selecting or highlighting buildings.
User story
In order to make buildings on the map interactive (highlight upon selection, etc.) user obtains
metadata information about an image, showing a map tile that includes an extruded building.
Original map tile
Given the following request:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/281707/171901/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 102► User Guide
The response to the request delivers the following image:
Figure 26: Map tile with building
This tile contains a fragment of a building near the bottom left corner. When the user wants to find
out more information about it they can use the following request:
Metainfo Tile Request SummaryThe following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [19/281707/171901], see also Mercator
Projection on page 24
{size} [256], see also size
{format} [png8], see also format
Map Tile API Developer's Guide 103► User Guide
Parameters: metadata [metaonly], see also metadata
mgen [2], see also mgen
Metainfo Tile RequestThe code block below demonstrates a complete request for a metadata map tile with extruded
buildings:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/281707/171901/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Processing Metainfo Tile ResponseThe response to the request delivers the following Metainfo Tile as a JSON object:
{ "metadata": { "street labels": [], "labels": [], "city center labels": [], "buildings": [ { "id": "1609441356716643099", "sectors": [ { "info": { "bottom height": 0, "height": 6.125 }, "vertices": [ 0, 142.78, 0, 189.18, 18, 199.50, 37, 161.69 ], "polygons": [ [ 0, 1, 2, 3] ], "outlines": [ [ 0, 3, 2, 1 ] ] } ] } ], "transit stops":[], "POIs": [] }}
In the response, the building has just one sector with the bottom height at 0 and height at 6.125. This
sector has an array of values describing a zero-indexed array of vertices using the top left of the tile
as the origin of the coordinate system. There are four vertices described in counterclockwise order
starting from the one closest to the top left corner (0, 142.78).
The metadata also contains two arrays, "polygons" and "outlines", each containing arrays of indices
that reference the given array of vertices. In our case, we only have one polygon that has the vertex
indices (0, 1, 2, 3), which represents the contour of our building fragment.
Map Tile API Developer's Guide 104► User Guide
Using this information we can draw a polygon reflecting current building's shape, e.g. with HTML5
canvas:
<canvas id="building_canvas" width="256" height="256" style="border:1px solid #d3d3d3;" /><script> // Assuming we have metadata from described request var vertices = [ 0, 142.78, 0, 189.18, 18, 199.50, 37, 161.69 ] var polygon = [ 0, 1, 2, 3]
var building_canvas = document.getElementById('building_canvas').getContext('2d'); building_canvas.fillStyle = '#f00';
building_canvas.beginPath();
// Move to start point var point = vertices.slice(2 * polygon[0], 2); building_canvas.moveTo(point[0], point[1]); // Draw rest of the points for (var idx = 1; idx < polygon.length; idx++) { point = vertices.slice(2*polygon[idx], 2*polygon[idx]+2); building_canvas.lineTo(point[0], point[1]); }
// Finalyze polygon building_canvas.closePath(); building_canvas.fill();
Map Tile API Developer's Guide 105► User Guide
</script>
Figure 27: Building shape reflected using metadata
In this example we only consider one part of the building. See also Combining Building Metainfo from
Several Tiles.
Combine Building Metainfo from Several TilesThis article shows exaple of combining building metainfo from several tiles.
User story
In order to make buildings on the map interactive (highlight upon selection, etc.) user obtains
metadata information about images, containing different parts of the same building.
Original map tiles
In most of the cases buildings are splitted between several tiles, e.g building from Metainfo Tile with
Extruded Buildings example consist of two parts (original tile and tile to the left from it):
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/281707/171901/256/png8
Map Tile API Developer's Guide 106► User Guide
?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/281706/171901/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 107► User Guide
To find out that those two parts are actually connected (belong to the same building), user needs torequest metainfo for original tile and for the neighbouring tiles as well.
See Metainfo Tile with Extruded Buildings for metainfo request details.
Processing Metainfo Tile ResponseAssuming the response to the request for original tile delivered the following Metainfo Tile as a JSON
object:
{ "metadata": { "street labels": [], "labels": [], "city center labels": [], "buildings": [ { "id": "1609441356716643099", "sectors": [ { "info": { "bottom height": 0, "height": 6.125 }, "vertices": [ 0, 142.78, 0, 189.18, 18, 199.50, 37, 161.69 ], "polygons": [ [ 0, 1, 2, 3] ], "outlines": [ [ 0, 3, 2, 1 ] ] } ] } ], "transit stops":[], "POIs": [] }}
Map Tile API Developer's Guide 108► User Guide
One can see that a single polygon for the building is cut at the left border of the tile. That meas that
the building might have other parts on the tile to the left from original one.
Given the fact that in buildig JSON objects from different tiles will share the same "id" if they belong
to the same building, it is easy to identify whether there are other parts of the buildings:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/281706/171901/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
{ "metadata": { "street labels": [], "labels": [], "city center labels": [], "buildings": [ { "id": "1609441356716643099", "sectors": [ { "info": { "bottom height": 0, "height": 6.125 }, "vertices": [ 248, 138.69, 243, 146.91, 231, 174.84, 256, 189.18, 256, 142.78, 219, 197.88, 125, 82.78, 99, 132.09 ], "polygons": [ [ 0, 1, 2, 3, 4], [ 5, 2, 1, 6, 7] ], "outlines": [ [ 2, 5, 7, 6, 1, 0, 4 ], [ 3, 2 ] ] } ] } ], "transit stops": [], "POIs": [] }}
Now it is easy to perform search within "buildings" array and find out that it contains JSON object
with the same "id" value ("1609441356716643099").
This way you can combine polygons from both tiles and reflect the whole building's shape, merging
polygons:
<canvas id="building_canvas" width="512" height="256" style="border:1px solid #d3d3d3;" /><script> var vertices_one = [ 0, 142.78, 0, 189.18, 18, 199.50, 37, 161.69 ] var polygons_one = [[ 0, 1, 2, 3]]
var vertices_two = [ 248, 138.69, 243, 146.91, 231, 174.84, 256, 189.18, 256, 142.78, 219, 197.88, 125, 82.78, 99, 132.09 ] var polygons_two = [[ 0, 1, 2, 3, 4], [ 5, 2, 1, 6, 7]]
Map Tile API Developer's Guide 109► User Guide
// Move center to the left right corner of the second tile // and shift coordinates of the first tile by 256 pixels to the left vertices_one = shiftLeft(256) // => [ 256, 142.78, 256, 189.18, 274, 199.50, 293, 161.69 ] // Calculate actual polylines from vertices and polygons for both tiles var polygons = [] polygons.push(getPolyline(polygons_one[0], vertices_one)) // => [ [256, 142.78], [256, 189.18], [274, 199.50], [293, 161.69] ] polygons.push(getPolyline(polygons_two[0], vertices_two)) // => [ [248, 138.69], [243, 146.91], [231, 174.84], [256, 189.18], [256, 142.78] ] polygons.push(getPolyline(polygons_two[1], vertices_two)) // => [ [219, 197.88], [243, 146.91], [248, 138.69], [125, 82.78], [99, 132.09] ] // Calculate final polyline var result = mergePolygons(polygons) // => [ [219, 197.88], [243, 146.91], [231, 174.84], [256, 189.18], [256, 142.78], [256, 189.18], [274, 199.50], [293, 161.69], [256, 142.78], [248, 138.69], [243, 146.91], [125, 82.78], [99, 132.09] ] var building_canvas = document.getElementById('building_canvas').getContext('2d'); building_canvas.fillStyle = '#f00';
building_canvas.beginPath();
// Move to start point building_canvas.result(point[0][0], result[0][1]); // Draw rest of the points for (var idx = 1; idx < result.length; idx++) { point = [, ]; building_canvas.lineTo(result[idx][0], result[idx][1]); }
// Finalyze polygon building_canvas.closePath(); building_canvas.fill();
Map Tile API Developer's Guide 110► User Guide
</script>
Figure 28: Building shape reflected using metadata
Figure 29: Original building image (2 tiles)
Figure 30: Example of a highlighted building image
Map Tile API Developer's Guide 111► User Guide
Metainfo for Multilevel BuildingsThis article shows example of using metainfo for multilevel buildings.
User story
In order to make multilevel buildings on the map interactive (highlight upon selection, etc.) user
obtains metadata information about images, containing building with several levels.
Original map tiles
Some buildings are multi-level, e.g.:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/154417/197021/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
If building has several levels one on top of the other, its metadata will contain several sectors withdifferent "bottom height" attribute values. This allows to reflect building's shape correctly, using onlyground-floor sectors with "bottom height" equals 0.
See Metainfo Tile with Extruded Buildings for metainfo request details.
Map Tile API Developer's Guide 112► User Guide
Processing Metainfo Tile ResponseConsider the building with id "1571706624457538485" from metatile for location above:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/154417/197021/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
{ "metadata" : { ..., "buildings":[ ..., { "id": "1571706624457538485", "sectors": [ { "info": { "bottom height": 0, "height": 48 }, "vertices": [ ... ], "polygons": [ ... ], "outlines": [ ... ] }, { "info": { "bottom height": 48, "height": 56.75 }, "vertices": [ ... ], "polygons": [ ... ], "outlines": [ ... ] } ] } ] }}
The building has two sectors: one which is on the ground ("bottom height" = 0) and one on top of the
first ("bottom height" = 48).
That allows us to:
• highlight the building correctly using only its footprint (ground sector);
• render 3D building image since we have third dimension (height) for each of building's sectors.
Map Tile API Developer's Guide 113► User Guide
Selecting Public Transit StopsThis article shows how to make a request with metadata parameter to get the name of a a public
transit stop and make it interactive (clickable).
User story
The user wants to obtain the name of a Public Transit Stop and create a clickable area on top of it so
that an interaction can be created on that area, to react to requests for additional information on the
public transit stop.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
Map Tile API Developer's Guide 114► User Guide
{zoom}/{column}/{row} [16/35205/21495], see also Mercator Projection
on page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: metadata=metaonly, see also metadata mgen=2, see also mgen
RequestThe code block below demonstrates a complete request for the public transit stop.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/16/35205/21495/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Map Tile API Developer's Guide 115► User Guide
ResponseThe image shown by this tile request not using metadata would be as follows.
Figure 31: Public Transit Map Tile
The response to the request delivers the following json object.
{ "metadata" : {"street labels":[ { "name":"Friedrichstraße", "font size":"13", "vertices": [ 119.61, -34.58, 120.93, -20.78, 121.61, -13.72, 122.38, -6.20, 122.84, -1.66, 124.57, 15.08, 125.21, 21.34, 125.73, 26.38, 126.19, 30.97, 127.06, 52.27 ] },{ "name":"Leipziger Straße", "font size":"13", "vertices": [ -41.27, 213.12, 6.82, 208.59, 17.87, 207.52, 25.20, 206.74, 30.25, 206.17, 34.81, 205.66, 56.11, 204.52 ] },{ "name":"Mauerstraße", "font size":"12", "vertices": [ 44.63, 234.27, 62.36, 262.41, 65.42, 267.27, 67.99, 271.23, 70.42, 274.61, 80.91, 291.29 ] },{ "name":"Krausenstraße", "font size":"12", "vertices": [ 81.81, 268.82, 88.97, 268.08, 93.19, 267.64, 99.47, 266.96, 106.20, 266.33, 139.90, 263.15, 146.14, 262.57, 159.58, 262.34 ] },{ "name":"Charlottenstraße", "font size":"12", "vertices": [ 231.10, 179.99, 231.79, 187.54, 232.50, 194.21, 235.21, 219.10, 235.72, 223.74, 236.46, 230.28, 237.15, 237.05, 237.71, 242.84, 238.16, 247.49, 238.56, 251.66, 239.35, 257.93, 239.87, 271.29 ] },{ "name":"Charlottenstraße", "font size":"12", "vertices": [ 214.28, -2.21, 215.16, 5.20, 215.95, 11.95, 216.65, 18.25, 217.05, 22.46, 218.95, 41.57, 219.58, 48.13, 220.15, 54.91, 220.59, 60.76, 221.46, 89.33 ] },{ "name":"Kronenstraße", "font size":"12", "vertices": [ 11.35, 138.35, 83.98, 132.52 ] },{ "name":"Kronenstraße", "font size":"12", "vertices": [ 188.92, 120.44, 213.96, 117.83, 220.48, 117.14, 227.22, 116.44, 233.01, 115.87, 261.53, 114.14 ] },{ "name":"Mohrenstraße", "font size":"12", "vertices": [ 5.83, 70.03, 80.66, 63.38 ] } ],"labels":[],"city center labels":[],"buildings":[omitted],
Map Tile API Developer's Guide 116► User Guide
"transit stops":[ { "name": "Stadtmitte", "bounding boxes": [ { "icon box":[ 136.50, 177.02, 14, 14 ] }, { "annotation box":[ 113.22, 163.02, 60.56, 13 ] } ], "info": [ { "position": {"latitude":52.510474, "longitude":13.389919}, "official name": "Stadtmitte", "operating hours": { "Monday":[["0:0:0","1:0:0"], ["4:0:0","0:0:0"]], "Tuesday":[["0:0:0","1:0:0"], ["4:0:0","0:0:0"]], "Wednesday":[["0:0:0","0:0:0"]], "Thursday":[["0:0:0","0:0:0"]], "Friday":[["0:0:0","0:0:0"]], "Saturday":[["0:0:0","0:0:0"]], "Sunday":[["0:0:0","0:0:0"]], "Holiday":[["0:0:0","0:0:0"]] } } ]} ],"POIs":[ ]}}
Out of this object there following properties are of interest to show the name:
• name: contains the name used in the map for the transit stop
• official name: contains the official name that must be used for the transit stop
• informal name: the name by which you can refer to the transit stop or might be known to users
For example places where the official name and the name used in the map will differe are airports
where the IATA code is used instead of the official name. See example below where the name is ERF
and official name is Erfurt-Weimar-Airport.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/11/1086/685/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
In order to select the area where the public transit stop is located there is another property of
interest in the object:
• bounding boxes: it contains an array of bounding boxes that can be used
• icon box: this bounding box contains the icon used in the map to represent the public transit
stop
• annotation box: this bounding box contains the labels attached to the icon to represent the
name of the transit stop in the map
The values of the bounding boxes can be used to select a rectangular area of the tile. In this example
the tile is 256x256, the bounding box for the icon will be left: 41.31, top: 104.01, width: 10, height:
10. The bounding box for the attached label will be left: 37.02, top: 92.01, width: 18.58, height:
10.50.
Public Transit GeolocationThis article shows how to make a request with metadata parameter to get the geo location of a
public transit stop.
Map Tile API Developer's Guide 117► User Guide
Note: Please refer to Selecting Public Transit Stops on page 113 to get additional
information on how to create selectable area.
User story
The user wants to obtain the location of a Public Transit Stop so that it can be used to retrieve
additional information.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [16/35205/21495], see also Mercator Projection
on page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: metadata=metaonly, see also metadata mgen=2, see also mgen
RequestThe code block below demonstrates a complete request for the public transit stop.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/16/35205/21495/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Map Tile API Developer's Guide 118► User Guide
ResponseThe image shown by this tile request not using metadata would be as follows.
Figure 32: Public Transit Map Tile
The response to the request delivers the following json object.
{ "metadata" : {"street labels":[ { "name":"Friedrichstraße", "font size":"13", "vertices": [ 119.61, -34.58, 120.93, -20.78, 121.61, -13.72, 122.38, -6.20, 122.84, -1.66, 124.57, 15.08, 125.21, 21.34, 125.73, 26.38, 126.19, 30.97, 127.06, 52.27 ] },{ "name":"Leipziger Straße", "font size":"13", "vertices": [ -41.27, 213.12, 6.82, 208.59, 17.87, 207.52, 25.20, 206.74, 30.25, 206.17, 34.81, 205.66, 56.11, 204.52 ] },{ "name":"Mauerstraße", "font size":"12", "vertices": [ 44.63, 234.27, 62.36, 262.41, 65.42, 267.27, 67.99, 271.23, 70.42, 274.61, 80.91, 291.29 ] },{ "name":"Krausenstraße", "font size":"12", "vertices": [ 81.81, 268.82, 88.97, 268.08, 93.19, 267.64, 99.47, 266.96, 106.20, 266.33, 139.90, 263.15, 146.14, 262.57, 159.58, 262.34 ] },{ "name":"Charlottenstraße", "font size":"12", "vertices": [ 231.10, 179.99, 231.79, 187.54, 232.50, 194.21, 235.21, 219.10, 235.72, 223.74, 236.46, 230.28, 237.15, 237.05, 237.71, 242.84, 238.16, 247.49, 238.56, 251.66, 239.35, 257.93, 239.87, 271.29 ] },{ "name":"Charlottenstraße", "font size":"12", "vertices": [ 214.28, -2.21, 215.16, 5.20, 215.95, 11.95, 216.65, 18.25, 217.05, 22.46, 218.95, 41.57, 219.58, 48.13, 220.15, 54.91, 220.59, 60.76, 221.46, 89.33 ] },{ "name":"Kronenstraße", "font size":"12", "vertices": [ 11.35, 138.35, 83.98, 132.52 ] },{ "name":"Kronenstraße", "font size":"12", "vertices": [ 188.92, 120.44, 213.96, 117.83, 220.48, 117.14, 227.22, 116.44, 233.01, 115.87, 261.53, 114.14 ] },{ "name":"Mohrenstraße", "font size":"12", "vertices": [ 5.83, 70.03, 80.66, 63.38 ] } ],"labels":[],"city center labels":[],"buildings":[omitted],
Map Tile API Developer's Guide 119► User Guide
"transit stops":[ { "name": "Stadtmitte", "bounding boxes": [ { "icon box":[ 136.50, 177.02, 14, 14 ] }, { "annotation box":[ 113.22, 163.02, 60.56, 13 ] } ], "info": [ { "position": {"latitude":52.510474, "longitude":13.389919}, "official name": "Stadtmitte", "operating hours": { "Monday":[["0:0:0","1:0:0"], ["4:0:0","0:0:0"]], "Tuesday":[["0:0:0","1:0:0"], ["4:0:0","0:0:0"]], "Wednesday":[["0:0:0","0:0:0"]], "Thursday":[["0:0:0","0:0:0"]], "Friday":[["0:0:0","0:0:0"]], "Saturday":[["0:0:0","0:0:0"]], "Sunday":[["0:0:0","0:0:0"]], "Holiday":[["0:0:0","0:0:0"]] } } ]} ],"POIs":[ ]}}
Out of this object there following properties are of interest to get the geo location:
• position: contains the geo coordinates
• latitude: contains the latitude of the public transit stop
• longitude: contains the longitude of the public transit stop
Public Transit Additional InformationThis article shows how to make a request with metadata parameter to get additional information of
a public transit stop, such as:
• places id
• operating hours
• parking size
• parking hours
Note: Please refer to Selecting Public Transit Stops on page 113 to get additional
information on how to create selectable area.
User story
The user wants to obtain additional information of a Public Transit Stop so that it can be displayed in
text mode.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
Map Tile API Developer's Guide 120► User Guide
{zoom}/{column}/{row} [16/35205/21495], see also Mercator Projection
on page 24
{size} [256], see also size
{format} [png8], see also format
Parameters: metadata=metaonly, see also metadata mgen=2, see also mgen
RequestThe code block below demonstrates a complete request for the public transit stop.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/16/35205/21495/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Map Tile API Developer's Guide 121► User Guide
ResponseThe image shown by this tile request not using metadata would be as follows.
Figure 33: Public Transit Map Tile
The response to the request delivers the following json object.
{ "metadata" : {"street labels":[ { "name":"Friedrichstraße", "font size":"13", "vertices": [ 119.61, -34.58, 120.93, -20.78, 121.61, -13.72, 122.38, -6.20, 122.84, -1.66, 124.57, 15.08, 125.21, 21.34, 125.73, 26.38, 126.19, 30.97, 127.06, 52.27 ] },{ "name":"Leipziger Straße", "font size":"13", "vertices": [ -41.27, 213.12, 6.82, 208.59, 17.87, 207.52, 25.20, 206.74, 30.25, 206.17, 34.81, 205.66, 56.11, 204.52 ] },{ "name":"Mauerstraße", "font size":"12", "vertices": [ 44.63, 234.27, 62.36, 262.41, 65.42, 267.27, 67.99, 271.23, 70.42, 274.61, 80.91, 291.29 ] },{ "name":"Krausenstraße", "font size":"12", "vertices": [ 81.81, 268.82, 88.97, 268.08, 93.19, 267.64, 99.47, 266.96, 106.20, 266.33, 139.90, 263.15, 146.14, 262.57, 159.58, 262.34 ] },{ "name":"Charlottenstraße", "font size":"12", "vertices": [ 231.10, 179.99, 231.79, 187.54, 232.50, 194.21, 235.21, 219.10, 235.72, 223.74, 236.46, 230.28, 237.15, 237.05, 237.71, 242.84, 238.16, 247.49, 238.56, 251.66, 239.35, 257.93, 239.87, 271.29 ] },{ "name":"Charlottenstraße", "font size":"12", "vertices": [ 214.28, -2.21, 215.16, 5.20, 215.95, 11.95, 216.65, 18.25, 217.05, 22.46, 218.95, 41.57, 219.58, 48.13, 220.15, 54.91, 220.59, 60.76, 221.46, 89.33 ] },{ "name":"Kronenstraße", "font size":"12", "vertices": [ 11.35, 138.35, 83.98, 132.52 ] },{ "name":"Kronenstraße", "font size":"12", "vertices": [ 188.92, 120.44, 213.96, 117.83, 220.48, 117.14, 227.22, 116.44, 233.01, 115.87, 261.53, 114.14 ] },{ "name":"Mohrenstraße", "font size":"12", "vertices": [ 5.83, 70.03, 80.66, 63.38 ] } ],"labels":[],"city center labels":[],"buildings":[omitted],
Map Tile API Developer's Guide 122► User Guide
"transit stops":[ { "name": "Stadtmitte", "bounding boxes": [ { "icon box":[ 136.50, 177.02, 14, 14 ] }, { "annotation box":[ 113.22, 163.02, 60.56, 13 ] } ], "info": [ { "position": {"latitude":52.510474, "longitude":13.389919}, "official name": "Stadtmitte", "operating hours": { "Monday":[["0:0:0","1:0:0"], ["4:0:0","0:0:0"]], "Tuesday":[["0:0:0","1:0:0"], ["4:0:0","0:0:0"]], "Wednesday":[["0:0:0","0:0:0"]], "Thursday":[["0:0:0","0:0:0"]], "Friday":[["0:0:0","0:0:0"]], "Saturday":[["0:0:0","0:0:0"]], "Sunday":[["0:0:0","0:0:0"]], "Holiday":[["0:0:0","0:0:0"]] } } ]} ],"POIs":[ ]}}
Out of this object there following properties are of interest to get the geo location:
• places id: contains the places identificator of the transit stop
• operating hours: contains an array of days and times when the public transit stop operates
• parking size: contains the parking size (if applicable)
• parking hours: contains the allowed parking hours (if applicable)
Note: Please note this additional information might not be included when it is not available, so
the response might be shorter than what is shown in the example.
Although it is not easy to find locations at the moment that contain places id as a property, the
coverage is growing. Mainly the locations in the US contain places id. See example below of a public
transit stop in Chicago.
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/16/16815/24358/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Metainfo Tiles with POIsThis article shows example usage of matainfo tile for displaying and ineraction with POIs.
User story
In order to make POIs on the map interactive (display additional info upon selection, etc.) user
obtains metadata information about an image, showing a map tile that includes POIs.
Original map tile
Given the following request:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/281563/171971/256/png8
Map Tile API Developer's Guide 123► User Guide
?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&pois
The response to the request delivers the following image:
Figure 34: Map tile with POI
This tile contains a POI - Zoological Garden in Berlin (near the top left corner). When the user wants to
find out more information about it they can use the following request:
Metainfo Tile RequestThe code block below demonstrates a complete request for a metadata map tile:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/19/281563/171971/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2&pois
Map Tile API Developer's Guide 124► User Guide
Processing Metainfo Tile ResponseThe response to the request delivers the following Metainfo tile as a JSON object (response is
suppresed to show only relevant POIs data):
{ "metadata": { "street labels": [ ... ], "city center labels": [ ... ], "buildings": [ ... ], "transit stops": [ ... ], "POIs": [ { "name": "Zoological Garden", "geoposition": { "latitude": 52.508211, "longitude": 13.334569 }, "bounding boxes": [ { "icon box": [ 217, 35.75, 14, 14 ] }, { "annotation box": [ 199.86, 13.75, 48.28, 20.50 ] } ], "info": [ { "PLACE NAME": "Zoological Garden", "PLACE CATEGORY": "TOURIST_ATTRACTION", "PLACE_PHONE NUMBER": "+(49)-30-254010" } ] } ] }}
This information allows to locate POI's icon and label in order to make them interactive. For this
you can use elements of "bounding boxes" array: "icon box" describes a bounding box for icon,
"annotation box" describes a bounding box for text label.
Geographical coordinates of POI is exposed as a "geoposition" object of metainfo JSON. This can be
used to obtain the address of POI, e.g. using Reverse Geocoding:
http://reverse.geocoder.cit.api.here.com/6.2/reversegeocode.xml?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&gen=7&prox=52.508211135864258,13.334569931030273,100&mode=retrieveAddresses
<Address> <Label>Hardenbergplatz, 10623 Berlin, Deutschland</Label> <Country>DEU</Country> <State>Berlin</State> <County>Berlin</County> <City>Berlin</City> <District>Charlottenburg</District> <Street>Hardenbergplatz</Street> <PostalCode>10623</PostalCode> <AdditionalData key="CountryName">Deutschland</AdditionalData>
Map Tile API Developer's Guide 125► User Guide
<AdditionalData key="StateName">Berlin</AdditionalData></Address>
One can also display some additional information regarding POI (e.g. using info bubble). This
information is provided by "info" JSON object:
• name ("PLACE NAME" attribute)
• category ("PLACE CATEGORY" attribute)
• phone number ("PLACE_PHONE NUMBER" attribute)
Metainfo Tiles with City Center LabelsThis article shows example usage of matainfo tile for displaying and ineraction with city center labels.
User story
In order to make city center labels on the map interactive (display additional info upon selection, etc.)
user obtains metadata information about an image, showing a map tile that includes city center label.
Original map tile
Given the following request:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/5/5/10/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 126► User Guide
The response to the request delivers the following image:
Figure 35: Map tile with city center labels
This tile contains some city center labels: Calgary, Edmonton, Vancouver. When the user wants to find
out more information they can use the following request:
Metainfo Tile RequestThe code block below demonstrates a complete request for a metadata map tile:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/5/5/10/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Processing Metainfo Tile ResponseThe response to the request delivers the following Metainfo tile as a JSON object (response is
suppresed to show only relevant city center data):
{ "metadata": { "street labels": [],
Map Tile API Developer's Guide 127► User Guide
"labels": [ ... ], "city center labels": [ { "name": "Calgary", "text box": [ 165.64, 165, 52.36, 16.75 ], "bullet box": [ 218, 178, 5, 5 ], "city center info": { "type": "OTHER", "name": "Calgary", "alternative names": [], "country code": "CAN", "position": { "latitude": 51.064453, "longitude": -114.082031 }, "population": 1096830 } }, { "name": "Edmonton", "text box": [ 168.45, 76, 62.55, 14.25 ], "bullet box": [ 231, 87, 4, 4 ], "city center info": { "type": "PROVINCIAL CAPITAL", "name": "Edmonton", "alternative names": [ ["ENG", "Edmonton"], ["FRE", "Edmonton"], ["SPA", "Edmonton"] ], "country code": "CAN", "position": { "latitude": 53.525390, "longitude": -113.510742 }, "population": 812200 } }, ... ], "buildings": [], "transit stops": [], "POIs": [] }}
This information allows to locate city center's icon and label in order to make them interactive. For
this you can use "bullet box" (describes a bounding box for icon), "text box" (describes a bounding
box for text label).
City center icon also can differ depending on the particular city type (e.g. capital cities can have
different icons). The information about city type provided with "type" attribute of "city center info"
JSON object: that could be "NATIONAL CAPITAL", "PROVINCIAL CAPITAL" or "OTHER".
If the label is localized for several languages (e.g. label for Edmonton from example above), relative
information is provided as "alternative names" array of "city center info" JSON object.
There is also some additional information wich can be displayed, e.g. in info bubble: "country code"
and "population".
Geographical coordinates of a city are provided as "position" attribute of "city center info" JSON
object.That information can be used for example for reverse geocoding.
Map Tile API Developer's Guide 128► User Guide
Metainfo Tiles with Street LabelsThis article shows example usage of matainfo tile for displaying and ineraction with street labels.
User story
In order to make street labels on the map interactive (display additional info upon selection, etc.) user
obtains metadata information about an image, showing a map tile that includes street label.
Original map tile
Given the following request:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/14/8818/5384/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
The response to the request delivers the following image:
Figure 36: Map tile with street label
Map Tile API Developer's Guide 129► User Guide
This tile contains street label for Berliner Ring. When the user wants to find out more information
they can use the following request:
Metainfo Tile RequestThe code block below demonstrates a complete request for a metadata map tile:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/14/8818/5384/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Processing Metainfo Tile ResponseThe response to the request delivers the following Metainfo tile as a JSON object (response is
suppresed to show only relevant street labels data):
{ "metadata": { "street labels": [ { "name": "Berliner Ring", "font size": "15", "vertices": [ 82.37, 214.71, 90.65, 189.39, 91.80, 185.92, 94.70, 177.84, 97.71, 170.13, 103.47, 155.49, 118.07, 127.86 ] } ], "labels": [ ... ], "city center labels": [], "buildings": [], "transit stops": [], "POIs": [] }}
This information allows to locate street label in order to make it interactive. Metainfo tile provides
array of "vertices", representing street segment's polyline, as well as font size.
I.e. one can draw fat line with HTML5 canvas:
<canvas id="street_canvas" width="256" height="256" style="border:1px solid #d3d3d3;" /><script> // Assuming we have metadata from described request var vertices = [ 82.37, 214.71, 90.65, 189.39, 91.80, 185.92, 94.70, 177.84, 97.71, 170.13, 103.47, 155.49, 118.07, 127.86 ] var font_size = 15
var street_canvas = document.getElementById('street_canvas').getContext('2d');
Map Tile API Developer's Guide 130► User Guide
street_canvas.lineWidth = font_size; street_canvas.beginPath();
// Move to start point var point = vertices.slice(0, 2); street_canvas.moveTo(point[0], point[1]); // Draw rest of the points for (var idx = 2; idx < vertices.length; idx+=2) { point = vertices.slice(idx, idx+2); street_canvas.lineTo(point[0], point[1]); }
// Finalyze street_canvas.stroke();</script>
Figure 37: Reflected street label polyline
Metainfo Tiles with Road SignsThis article shows example usage of matainfo tile for displaying and ineraction with road signs.
Map Tile API Developer's Guide 131► User Guide
User story
In order to make road signs on the map interactive (display additional info upon selection, etc.) user
obtains metadata information about an image, showing a map tile that includes road sign.
Original map tile
Given the following request:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/13/4410/2694/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
The response to the request delivers the following image:
Figure 38: Map tile with road sign
This tile contains road sign for route A12 in Germany. When the user wants to find out more
information they can use the following request:
Map Tile API Developer's Guide 132► User Guide
Metainfo Tile RequestThe code block below demonstrates a complete request for a metadata map tile:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/13/4410/2694/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
Processing Metainfo Tile ResponseThe response to the request delivers the following Metainfo tile as a JSON object (response is
suppresed to show only relevant road signs data):
{ "metadata": { "street labels": [], "labels": [ { "name": "12", "type": "ROADSIGN", "bounding boxes": [ { "icon box":[ 41.62, 71.52, 24, 18 ] } ], "region": "DEU", "category": 0, "route name": "A12", "route level": 2, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A12&route_level=2&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" } ], "city center labels":[], "buildings": [], "transit stops": [], "POIs": [] }}
This information allows to locate road sign in order to make it interactive.
Road sign labels belong to "labels" array of metadata JSON object and have a "type" equals
"ROADSINGN". Metainfo provides "icon box" array for road signs in the following format: [x, y, width,
heght], representing road sign's bounding box.
There is also some additional information for road signes provided:
• country region
• road sign category
Map Tile API Developer's Guide 133► User Guide
• route name
• route level
You can also retreive road sign icon using "url" attribute of a label, e.g.:
http://image.maps.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A12&route_level=2&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg
Figure 39: Road sign icon
Filter Only Metainfo for Road SignsThere is also an option to filter only mateinfo for road sign labels (excule all other kinds of labels from
JSON response). E.g. for tile that contains a lot of different labels:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/11/1102/673/256/png8?app_id=DemoAppId01082013GAL
Map Tile API Developer's Guide 134► User Guide
&app_code=AJKnXv84fjrb0KIHawS0Tg
Figure 40: Tile with several labels
Metainfo tile will contain a lot of city center labels. Using additional request parameter "filter=1" one
can request only roadsign labels for current tile:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/11/1102/673/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2&filter=1
{ "metadata": { "labels": [ { "name": "12", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 46.38, 110.68, 22, 16 ] } ], "region": "DEU", "category": 0, "route name": "A12", "route level": 2,
Map Tile API Developer's Guide 135► User Guide
"uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A12&route_level=2&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" }, { "name": "10", "type":"ROADSIGN", "bounding boxes": [ { "icon box":[ 7, 115.18, 22, 16 ] } ], "region": "DEU", "category": 0, "route name": "A10", "route level": 2, "uri": "http://image.maps.api.here.com/mia/1.6/roadsign?category=0®ion=DEU&label=A10&route_level=2&app_id=MbYgbCa05HulUfkHSiHb&app_code=7NN96MmPNca-bVDfVuyXEg" } ] }}
Metainfo Tiles with LabelsThis article shows example usage of matainfo tile for displaying and ineraction with different kinds of
labels.
User story
In order to make labels on the map interactive (display additional info upon selection, etc.) user
obtains metadata information about an image, showing a map tiles that include different kinds of
labels.
Mountain Peak LabelsSome tiles contain mountain peak labels, e.g. Vesuvius Volcano in Italy:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/17/70789/49227/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 136► User Guide
The response to the request delivers the following image:
Figure 41: Map tile with mountain peak label
The code block below demonstrates a complete request for a metadata map tile:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/17/70789/49227/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
The response to the request delivers the following Metainfo tile as a JSON object:
{ "metadata": { "street labels": [], "labels": [ { "name": "Mount Vesuvius", "type": "MOUNTAIN_PEAK", "bounding boxes": [ { "icon box":[ 106, 226.80, 10, 10 ] }, { "annotation box":[ 90, 195.80, 41.53, 31 ] } ] } ], "city center labels": [],
Map Tile API Developer's Guide 137► User Guide
"buildings": [], "transit stops": [], "POIs": [] }}
This information allows to locate mountain peak label in order to make it interactive.
Mountain peak labels belong to "labels" array of metadata JSON object and have a "type" equals
"MOUNTAIN_PEAK". Metainfo provides "icon box" array for mountain peak icon in the following
format: [x, y, width, heght], representing icon's bounding box. "annotation box" represents bounding
box for text label in the same manner.
Pedestrian Point LabelsSome tiles contain pedestrian point labels, e.g. in Kiev:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/pedestrian.day/19/306646/176817/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
The response to the request delivers the following image:
Figure 42: Map tile with pedestrian point label
Map Tile API Developer's Guide 138► User Guide
The code block below demonstrates a complete request for a metadata map tile:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/pedestrian.day/19/306646/176817/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
The response to the request delivers the following Metainfo tile as a JSON object:
{ "metadata": { "street labels": [], "labels": [ { "name": "", "type": "PEDESTRIAN_POINT", "bounding boxes": [ { "icon box":[ 113, 183.03, 14, 14 ] } ] } ], "city center labels": [], "buildings": [ ... ], "transit stops": [], "POIs": [] }}
This information allows to locate pedestrian point label in order to make it interactive.
Pedestrian point labels belong to "labels" array of metadata JSON object and have a "type" equals
"PEDESTRIAN_POINT". Metainfo provides "icon box" array for pedestrian point icon in the following
format: [x, y, width, heght], representing icon's bounding box.
Other (Unclassified) LabelsThere are also a lot of of objects with other kinds of labels on the map tiles: landuse objects (i.e.
parks), hydro labels (oceans, seas, rivers, lakes), country names, continet names, etc. All of them are
represented by "labels" array of metainfo tile JSON object and have type "TEXT".
In order to make these labels interactive, one can use "text box" array in the following format: [x, y,
width, heght], representing label's bounding box.
I.e. thise is a tile containing countries of Asia-Pacific region:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/3/6/3/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 139► User Guide
The response to the request delivers the following image:
Figure 43: Map tile with country name labels
The code block below demonstrates a complete request for a metadata map tile:
http://2.base.maps.cit.api.here.com/maptile/2.1/maptile/newest/normal.day/3/6/3/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&metadata=metaonly&mgen=2
The response to the request delivers the following Metainfo tile as a JSON object:
{ "metadata": { "street labels": [], "labels": [ { "name": "China", "type":"TEXT", "bounding boxes": [ { "text box":[ 32.30, 41.16, 41.47, 15.50 ] } ] }, { "name": "Myanmar", "type":"TEXT", "bounding boxes": [ { "text box":[ 12.84, 127.76, 52.39, 11.75 ] } ] }, { "name": "Thailand", "type":"TEXT", "bounding boxes": [ { "text box":[ 44, 159.43, 52.38, 11.75 ] } ] }, { "name": "Philippines", "type":"TEXT", "bounding boxes": [ { "text box":[ 156.96, 179.50, 62.20, 11.75 ] } ] }, { "name": "Japan", "type":"TEXT", "bounding boxes": [ { "text box":[ 236.23, 37.80, 33.80, 11.75 ] } ] } ],
Map Tile API Developer's Guide 140► User Guide
"city center labels": [], "buildings": [], "transit stops": [], "POIs": [] }}
Aerial Map Tile ExamplesThis section provides examples using the aerial map tile resources.
Terrain Map TileThis article shows a request for a terrain map tile.
User story
The user wants to obtain an image showing the terrain of Eastern Switzerland, emphasising the shape
and features of the mountains of the Alps. The tile requested uses the terrain.day map schema.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [terrain.day], see also scheme
{zoom}/{column}/{row} [7/66/45], see also Mercator Projection on page
24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a terrain map tile.
http://1.aerial.maps.cit.api.here.com/maptile/2.1/maptile/newest/terrain.day/7/66/45/256/png8
Map Tile API Developer's Guide 141► User Guide
?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
ResponseThe response to the request delivers the following topographical map image of Eastern Switzerland:
Figure 44: Terrain Map Tile
Satellite Map TileThis article shows a request for a satellite map tile.
User story
The user wants to obtain satellite imagery of Southern Spain and Morocco. The tile requested uses
the satellite.day map schema.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 142► User Guide
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [satellite.day], see also scheme
{zoom}/{column}/{row} [5/15/12], see also Mercator Projection on page
24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a satellite map tile.
http://2.aerial.maps.cit.api.here.com/maptile/2.1/maptile/newest/satellite.day/5/15/12/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 143► User Guide
ResponseThe response to the request delivers the following image of the western end of the Mediterranean
Sea showing the southern half of the Iberian Peninsula and the North African coast of Morocco across
the Strait of Gibraltar:
Figure 45: Satellite Tile
Hybrid Map TileThis article shows a request for a hybrid map tile.
User story
The user wants to obtain a hybrid map image of Florida. The tile combines the road network and
labels over satellite imagery. The tile requested uses the hybrid.day map schema.
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Map Tile API Developer's Guide 144► User Guide
Resource: maptile [maptile], see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [hybrid.day], see also scheme
{zoom}/{column}/{row} [5/8/13], see also Mercator Projection on page
24
{size} [256], see also size
{format} [png8], see also format
RequestThe code block below demonstrates a complete request for a hybrid map tile.
http://2.aerial.maps.cit.api.here.com/maptile/2.1/maptile/newest/hybrid.day/5/8/13/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 145► User Guide
ResponseThe response to the request delivers the following image of Florida:
Figure 46: Hybrid Tile
Pano Map Tile ExamplesThis section provides examples using the pano map tile resources.
Panorama TileThis article shows requests for map tiles that contain panorama information.
User story
The user wants to see the current panorama coverage of London. The tile represents the parts of
London currently covered with panoramas as an overlay on top of the normal map tile.
Map Tile API Developer's Guide 146► User Guide
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: rctile or rconlytile, see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [13/4094/2724], see also Mercator Projection on
page 24
{size} [256], see also size
{format} [png8], see also format
Request for a Panorama Map TileThe code block below demonstrates a complete request for a panorama map tile.
http://1.pano.maps.cit.api.here.com/maptile/2.1/rctile/newest/normal.day/13/4094/2724/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 147► User Guide
Response to Panorama Map Tile RequestThe response contains the following image.
Figure 47: Panorama tile for a part of London
Request for a Panorama Only TileThe code block below demonstrates a request for a panorama tile, using the rconlytile resource.
http://1.pano.maps.cit.api.here.com/maptile/2.1/rconlytile/newest/normal.day/13/4094/2724/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 148► User Guide
Response to Panorama Only Tile RequestThe response contains the image below. Note that the tile contains a transparent background, which
is shown here in black.
Figure 48: Transparent panorama only tile for a part of London
Traffic Map Tile ExamplesThis section provides examples using the traffic map tile resources.
Traffic TileThis article shows requests for map tiles that contain traffic information.
User story
The user wants to obtain a map tile displaying the current traffic conditions in a part of London and
another tile that displays the same location, but this time with only traffic conditions and no map in
the background.
Map Tile API Developer's Guide 149► User Guide
Request Summary
The following list summarizes the elements required to create a request matching the user story
and shows, in square brackets, how those elements are used in the example(s) below. Note that the
request example also uses the authentication parameters.
Resource: maptile [traffictile] or flowtile, see also (resource) type
URL variables: {map id} [newest], see also Requesting the Right Map Version on page 26
{scheme} [normal.day], see also scheme
{zoom}/{column}/{row} [15/16358/10898], see also Mercator Projection
on page 24
{size} [256], see also size
{format} [png8], see also format
Request for a Traffic Map TileThe code block below demonstrates a complete request for a traffic map tile.
http://1.traffic.maps.cit.api.here.com/maptile/2.1/traffictile/newest/normal.day/15/16358/10898/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 150► User Guide
Response to Traffic Map Tile RequestThe response contains the following image.
Figure 49: Traffic tile for a part of London
Request for a Traffic Only TileThe code block below demonstrates a request for a traffic tile, using the flowtile resource.
http://1.traffic.maps.cit.api.here.com/maptile/2.1/flowtile/newest/normal.day/15/16358/10898/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Map Tile API Developer's Guide 151► User Guide
Response to Traffic Only Tile RequestThe response contains the image below. Note that the tile contains a transparent background, which
is shown here in black.
Figure 50: Transparent traffic tile for a part of London
Request for a Traffic Map Tile with Minimum Traffic CongestionLevelThe code block below demonstrates a complete request for a traffic map tile where no free flow is
rendered.
http://1.traffic.maps.cit.api.here.com/maptile/2.1/traffictile/newest/normal.day/14/8683/5379/256/png8?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&min_traffic_congestion=heavy
Map Tile API Developer's Guide 152► User Guide
Response to Traffic Map Tile Request with Minimum TrafficCongestion LevelThe response contains the following image.
Figure 51: Traffic tile with mininum traffic congestion level "heavy"
Service SupportIf you need assistance with this or other HERE products, please contact your HERE representative or
Technical Customer Support.
Map Tile API Developer's Guide 153► API Reference
Chapter
4
API ReferenceTopics:
• Base Map Tile Resources
• Aerial Tile Resources
• Panorama Tile Resources
• Traffic Tile Resources
• Information Resources
• HTTP Status Codes
This section provides a comprehensive reference to the HERE Map
Tile API and the parameters supported by those resources.
Map Tile API Developer's Guide 154► API Reference
Base Map Tile ResourcesThe base map tile resources are responsible for requests with a variety of map tile types that differ in
terms of the information they include and consequently also in terms of the visual style. A response
delivers a single map tile image or a set of four, nine or sixteen map tiles encoded as text.
Check the info request of the base map tile resource to get a list of all the tile types and
schemes supported.
Administrative Labels (alabeltile)Description
Returns a tile that contains only administrative labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/alabeltile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 5: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Map Tile API Developer's Guide 155► API Reference
Parameter Type Description
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
Map Tile API Developer's Guide 156► API Reference
Parameter Type Description
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Map Tile API Developer's Guide 157► API Reference
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 6: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 7: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
Map Tile API Developer's Guide 158► API Reference
Parameter Type Description
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 8: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
Map Tile API Developer's Guide 159► API Reference
Parameter Type Description
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
Map Tile API Developer's Guide 160► API Reference
Parameter Type Description
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
Map Tile API Developer's Guide 161► API Reference
Parameter Type Description
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Base Map Tile (basetile)Description
Returns a base map tile, which is an image that shows the map and streets, but no labels.
Format
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/basetile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Map Tile API Developer's Guide 162► API Reference
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 9: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
Map Tile API Developer's Guide 163► API Reference
Parameter Type Description
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Map Tile API Developer's Guide 164► API Reference
Parameter Type Description
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 10: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 11: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Map Tile API Developer's Guide 165► API Reference
Parameter Type Description
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Map Tile API Developer's Guide 166► API Reference
Label Tile (labeltile)Description
Returns a tile that contains only labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/labeltile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 12: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
Map Tile API Developer's Guide 167► API Reference
Parameter Type Description
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
Map Tile API Developer's Guide 168► API Reference
Parameter Type Description
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Map Tile API Developer's Guide 169► API Reference
Table 13: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 14: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Map Tile API Developer's Guide 170► API Reference
Parameter Type Description
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 15: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
Map Tile API Developer's Guide 171► API Reference
Parameter Type Description
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
Map Tile API Developer's Guide 172► API Reference
Parameter Type Description
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Map Tile API Developer's Guide 173► API Reference
Parameter Type Description
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Line Tile (linetile)Description
Returns a line tile image, which contains only street lines, no labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/linetile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Map Tile API Developer's Guide 174► API Reference
Table 16: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
Map Tile API Developer's Guide 175► API Reference
Parameter Type Description
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
Map Tile API Developer's Guide 176► API Reference
Parameter Type Description
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 17: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 18: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
Map Tile API Developer's Guide 177► API Reference
Parameter Type Description
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Map Tile API Developer's Guide 178► API Reference
Lines and Labels Tile (lltile)Description
Returns a tile image, which shows street lines, city center labels and item labels, but no street labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/lltile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 19: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
Map Tile API Developer's Guide 179► API Reference
Parameter Type Description
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
Map Tile API Developer's Guide 180► API Reference
Parameter Type Description
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Map Tile API Developer's Guide 181► API Reference
Table 20: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 21: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Map Tile API Developer's Guide 182► API Reference
Parameter Type Description
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 22: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
Map Tile API Developer's Guide 183► API Reference
Parameter Type Description
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
Map Tile API Developer's Guide 184► API Reference
Parameter Type Description
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Map Tile API Developer's Guide 185► API Reference
Parameter Type Description
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Map Tile (maptile)Description
Returns a map tile image.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/maptile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Map Tile API Developer's Guide 186► API Reference
Table 23: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
Map Tile API Developer's Guide 187► API Reference
Parameter Type Description
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
Map Tile API Developer's Guide 188► API Reference
Parameter Type Description
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 24: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 25: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
Map Tile API Developer's Guide 189► API Reference
Parameter Type Description
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Map Tile API Developer's Guide 190► API Reference
Optional Query Parameters
Table 26: Optional Query parameters
Parameter Type Description
congestion Boolean Flag that enables congestion and environmental zone display, if
available for the requested tile.
Available for the following tiles
• maptile
• traffictile
• rctile
• trucktile
• truckonlytile
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
Map Tile API Developer's Guide 191► API Reference
Parameter Type Description
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
Map Tile API Developer's Guide 192► API Reference
Parameter Type Description
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Map Tile API Developer's Guide 193► API Reference
Parameter Type Description
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Street Tile (streettile)Description
Returns an image that contains only street lines and labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/streettile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 27: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
Map Tile API Developer's Guide 194► API Reference
Parameter Type Description
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
Map Tile API Developer's Guide 195► API Reference
Parameter Type Description
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Map Tile API Developer's Guide 196► API Reference
Parameter Type Description
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 28: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 29: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
Map Tile API Developer's Guide 197► API Reference
Parameter Type Description
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 30: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
Map Tile API Developer's Guide 198► API Reference
Parameter Type Description
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
Map Tile API Developer's Guide 199► API Reference
Parameter Type Description
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
Map Tile API Developer's Guide 200► API Reference
Parameter Type Description
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Truck Tile (trucktile)Description
Returns map tiles that include road signs specifically for trucks and fleet providers.
Map Tile API Developer's Guide 201► API Reference
Format
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/trucktile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 31: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
Map Tile API Developer's Guide 202► API Reference
Parameter Type Description
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
Map Tile API Developer's Guide 203► API Reference
Parameter Type Description
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 32: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Map Tile API Developer's Guide 204► API Reference
Parameter Type Description
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 33: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
Map Tile API Developer's Guide 205► API Reference
Parameter Type Description
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 34: Optional Query parameters
Parameter Type Description
congestion Boolean Flag that enables congestion and environmental zone display, if
available for the requested tile.
Available for the following tiles
• maptile
• traffictile
• rctile
• trucktile
• truckonlytile
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
Map Tile API Developer's Guide 206► API Reference
Parameter Type Description
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
Map Tile API Developer's Guide 207► API Reference
Parameter Type Description
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
Map Tile API Developer's Guide 208► API Reference
Parameter Type Description
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Truck Only Tile (truckonlytile)Description
Returns a tile that shows only the truck specific road signs without a background.
Format
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/truckonlytile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Map Tile API Developer's Guide 209► API Reference
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 35: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
Map Tile API Developer's Guide 210► API Reference
Parameter Type Description
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Map Tile API Developer's Guide 211► API Reference
Parameter Type Description
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 36: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 37: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Map Tile API Developer's Guide 212► API Reference
Parameter Type Description
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Map Tile API Developer's Guide 213► API Reference
Extra Base Map Tile (xbasetile)Description
Returns a base map image, which is an image that shows the map, but neither streets nor labels.
Format
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/xbasetile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 38: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
Map Tile API Developer's Guide 214► API Reference
Parameter Type Description
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
Map Tile API Developer's Guide 215► API Reference
Parameter Type Description
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Map Tile API Developer's Guide 216► API Reference
Table 39: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 40: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Map Tile API Developer's Guide 217► API Reference
Parameter Type Description
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Aerial Tile ResourcesThe aerial tile resources are responsible for delivering satellite, terrain and hybrid tile images. In this
context, hybrid refers to an image that contains satellite imagery along with labels and such.
These resources always use satellite or terrain as a background, when requested, otherwise
no background is used. That means that the only available schemes for these resources are
satellite, hybrid or terrain.
Check the info request of the base map tile resource to get a list of all the tile types and
schemes supported.
Administrative Labels (alabeltile)Description
Returns a tile that contains only administrative labels.
Format
Map Tile API Developer's Guide 218► API Reference
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/alabeltile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 41: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
Map Tile API Developer's Guide 219► API Reference
Parameter Type Description
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Map Tile API Developer's Guide 220► API Reference
Parameter Type Description
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 42: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Map Tile API Developer's Guide 221► API Reference
Table 43: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Map Tile API Developer's Guide 222► API Reference
Parameter Type Description
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 44: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
Map Tile API Developer's Guide 223► API Reference
Parameter Type Description
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Map Tile API Developer's Guide 224► API Reference
Parameter Type Description
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Map Tile API Developer's Guide 225► API Reference
Parameter Type Description
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Base Map Tile (basetile)Description
Returns a base map tile, which is an image that shows the map and streets, but no labels.
Format
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/basetile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 45: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Map Tile API Developer's Guide 226► API Reference
Parameter Type Description
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
Map Tile API Developer's Guide 227► API Reference
Parameter Type Description
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Map Tile API Developer's Guide 228► API Reference
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 46: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 47: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
Map Tile API Developer's Guide 229► API Reference
Parameter Type Description
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Label Tile (labeltile)Description
Returns a tile that contains only labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/labeltile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
Map Tile API Developer's Guide 230► API Reference
The following table lists the URI parameters that are common for all requests.
Table 48: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
Map Tile API Developer's Guide 231► API Reference
Parameter Type Description
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Map Tile API Developer's Guide 232► API Reference
Parameter Type Description
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 49: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 50: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Map Tile API Developer's Guide 233► API Reference
Parameter Type Description
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Map Tile API Developer's Guide 234► API Reference
Optional Query Parameters
Table 51: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
Map Tile API Developer's Guide 235► API Reference
Parameter Type Description
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
Map Tile API Developer's Guide 236► API Reference
Parameter Type Description
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
Map Tile API Developer's Guide 237► API Reference
Parameter Type Description
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Line Tile (linetile)Description
Returns a line tile image, which contains only street lines, no labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/linetile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 52: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
Map Tile API Developer's Guide 238► API Reference
Parameter Type Description
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
Map Tile API Developer's Guide 239► API Reference
Parameter Type Description
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Map Tile API Developer's Guide 240► API Reference
Table 53: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 54: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Map Tile API Developer's Guide 241► API Reference
Parameter Type Description
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Lines and Labels Tile (lltile)Description
Returns a tile image, which shows street lines, city center labels and item labels, but no street labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/lltile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Map Tile API Developer's Guide 242► API Reference
Table 55: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
Map Tile API Developer's Guide 243► API Reference
Parameter Type Description
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
Map Tile API Developer's Guide 244► API Reference
Parameter Type Description
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 56: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 57: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
Map Tile API Developer's Guide 245► API Reference
Parameter Type Description
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Map Tile API Developer's Guide 246► API Reference
Optional Query Parameters
Table 58: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
Map Tile API Developer's Guide 247► API Reference
Parameter Type Description
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
Map Tile API Developer's Guide 248► API Reference
Parameter Type Description
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
Map Tile API Developer's Guide 249► API Reference
Parameter Type Description
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Map Tile (maptile)Description
Returns a map tile image.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/maptile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 59: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
Map Tile API Developer's Guide 250► API Reference
Parameter Type Description
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
Map Tile API Developer's Guide 251► API Reference
Parameter Type Description
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Map Tile API Developer's Guide 252► API Reference
Table 60: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 61: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Map Tile API Developer's Guide 253► API Reference
Parameter Type Description
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 62: Optional Query parameters
Parameter Type Description
congestion Boolean Flag that enables congestion and environmental zone display, if
available for the requested tile.
Available for the following tiles
• maptile
• traffictile
• rctile
• trucktile
• truckonlytile
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
Map Tile API Developer's Guide 254► API Reference
Parameter Type Description
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
Map Tile API Developer's Guide 255► API Reference
Parameter Type Description
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
Map Tile API Developer's Guide 256► API Reference
Parameter Type Description
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Street Tile (streettile)Description
Returns an image that contains only street lines and labels.
Format
Map Tile API Developer's Guide 257► API Reference
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/streettile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 63: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
Map Tile API Developer's Guide 258► API Reference
Parameter Type Description
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Map Tile API Developer's Guide 259► API Reference
Parameter Type Description
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 64: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Map Tile API Developer's Guide 260► API Reference
Table 65: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Map Tile API Developer's Guide 261► API Reference
Parameter Type Description
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 66: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
Map Tile API Developer's Guide 262► API Reference
Parameter Type Description
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Map Tile API Developer's Guide 263► API Reference
Parameter Type Description
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Map Tile API Developer's Guide 264► API Reference
Parameter Type Description
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Truck Tile (trucktile)Description
Returns map tiles that include road signs specifically for trucks and fleet providers.
Format
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/trucktile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 67: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Map Tile API Developer's Guide 265► API Reference
Parameter Type Description
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
Map Tile API Developer's Guide 266► API Reference
Parameter Type Description
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Map Tile API Developer's Guide 267► API Reference
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 68: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 69: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
Map Tile API Developer's Guide 268► API Reference
Parameter Type Description
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 70: Optional Query parameters
Parameter Type Description
congestion Boolean Flag that enables congestion and environmental zone display, if
available for the requested tile.
Available for the following tiles
• maptile
• traffictile
• rctile
• trucktile
• truckonlytile
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
Map Tile API Developer's Guide 269► API Reference
Parameter Type Description
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
Map Tile API Developer's Guide 270► API Reference
Parameter Type Description
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
Map Tile API Developer's Guide 271► API Reference
Parameter Type Description
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Truck Only Tile (truckonlytile)Description
Returns a tile that shows only the truck specific road signs without a background.
Map Tile API Developer's Guide 272► API Reference
Format
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/truckonlytile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 71: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
Map Tile API Developer's Guide 273► API Reference
Parameter Type Description
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
Map Tile API Developer's Guide 274► API Reference
Parameter Type Description
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 72: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Map Tile API Developer's Guide 275► API Reference
Parameter Type Description
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 73: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
Map Tile API Developer's Guide 276► API Reference
Parameter Type Description
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Extra Base Map Tile (xbasetile)Description
Returns a base map image, which is an image that shows the map, but neither streets nor labels.
Format
Requests against the resource must follow the pattern summarized by the following formula:
http://{1-4}.aerial.maps.cit.api.here.com/maptile/2.1/xbasetile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 74: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
Map Tile API Developer's Guide 277► API Reference
Parameter Type Description
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
Map Tile API Developer's Guide 278► API Reference
Parameter Type Description
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
Map Tile API Developer's Guide 279► API Reference
Parameter Type Description
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 75: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 76: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
Map Tile API Developer's Guide 280► API Reference
Parameter Type Description
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Map Tile API Developer's Guide 281► API Reference
Panorama Tile ResourcesThe panorama tile resources deliver map tiles with panorama coverage information as an overlay. The
panorama coverage shows areas where there is some Street Level Imagery available.
Check the info request of the base map tile resource to get a list of all the tile types and
schemes supported.
Raster Coverage Distributed (rcdistonytile)Description
Returns original coverage for panoramatiles not post-processed to be blended into a single coverage
blob.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.pano.maps.cit.api.here.com/maptile/2.1/rcdistonlytile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 77: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Map Tile API Developer's Guide 282► API Reference
Parameter Type Description
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
Map Tile API Developer's Guide 283► API Reference
Parameter Type Description
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Map Tile API Developer's Guide 284► API Reference
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 78: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 79: Optional Query parameters
Parameter Type Description
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
Raster Coverage Only Tile (rconlytile)Description
Returns only the panorama coverage blob without the map background and labels.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/rconlytile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
Map Tile API Developer's Guide 285► API Reference
The following table lists the URI parameters that are common for all requests.
Table 80: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
Map Tile API Developer's Guide 286► API Reference
Parameter Type Description
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Map Tile API Developer's Guide 287► API Reference
Parameter Type Description
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 81: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Query Parameters
Table 82: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Map Tile API Developer's Guide 288► API Reference
Parameter Type Description
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Map Tile API Developer's Guide 289► API Reference
Raster Coverage Tile (rctile)Description
Returns a maptile with panorama coverage on top, shown as a blob covering an area where Street
Level Imagery is available.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.pano.maps.cit.api.here.com/maptile/2.1/rctile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 83: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
Map Tile API Developer's Guide 290► API Reference
Parameter Type Description
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
Map Tile API Developer's Guide 291► API Reference
Parameter Type Description
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Map Tile API Developer's Guide 292► API Reference
Table 84: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Optional Metadata Specific Query Parameters
Table 85: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Map Tile API Developer's Guide 293► API Reference
Parameter Type Description
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Optional Query Parameters
Table 86: Optional Query parameters
Parameter Type Description
congestion Boolean Flag that enables congestion and environmental zone display, if
available for the requested tile.
Available for the following tiles
• maptile
• traffictile
• rctile
• trucktile
• truckonlytile
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
Map Tile API Developer's Guide 294► API Reference
Parameter Type Description
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
Map Tile API Developer's Guide 295► API Reference
Parameter Type Description
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
Map Tile API Developer's Guide 296► API Reference
Parameter Type Description
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Traffic Tile ResourcesThe traffic tile resources are responsible for delivering tiles that contain visualization for the current
traffic situation (traffic flow) on the roads.
Check the info request of the base map tile resource to get a list of all the tile types and
schemes supported.
Map Tile API Developer's Guide 297► API Reference
Flow Base Tile (flowbasetile)Description
Returns a base map tile (no labels) with traffic flow.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.traffic.maps.cit.api.here.com/maptile/2.1/flowbasetile/newest/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 87: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
Map Tile API Developer's Guide 298► API Reference
Parameter Type Description
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
Map Tile API Developer's Guide 299► API Reference
Parameter Type Description
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Map Tile API Developer's Guide 300► API Reference
Table 88: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Traffic Specific Query Parameters
The following table lists parameters for traffic options.
Table 89: Traffic Specific Query Parameters
Parameter Type Description
min_traffic_congestionString (optional) Specifies the the minimum traffic congestion level to use for rendering
traffic flow. It accepts the following values:
free (default) – renders all traffic lines, which includes free flow,
heavy, queuing and blocked traffic lines.
heavy – renders all heavy traffic, queuing traffic and blocked roads.
queuing – renders the queuing traffic and blocked traffic lines.
blocked – renders only the black traffic lines for blocked roads.
Optional Query Parameters
Table 90: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
Map Tile API Developer's Guide 301► API Reference
Parameter Type Description
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Flow Label Tile (flowlabeltile)Description
Returns a transparent image with traffic flow and labels.
Map Tile API Developer's Guide 302► API Reference
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.traffic.maps.cit.api.here.com/maptile/2.1/flowlabeltile/newest/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 91: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
Map Tile API Developer's Guide 303► API Reference
Parameter Type Description
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
Map Tile API Developer's Guide 304► API Reference
Parameter Type Description
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 92: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Map Tile API Developer's Guide 305► API Reference
Parameter Type Description
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Traffic Specific Query Parameters
The following table lists parameters for traffic options.
Table 93: Traffic Specific Query Parameters
Parameter Type Description
min_traffic_congestionString (optional) Specifies the the minimum traffic congestion level to use for rendering
traffic flow. It accepts the following values:
free (default) – renders all traffic lines, which includes free flow,
heavy, queuing and blocked traffic lines.
heavy – renders all heavy traffic, queuing traffic and blocked roads.
queuing – renders the queuing traffic and blocked traffic lines.
blocked – renders only the black traffic lines for blocked roads.
Optional Query Parameters
Table 94: Optional Query parameters
Parameter Type Description
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
Map Tile API Developer's Guide 306► API Reference
Parameter Type Description
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
Map Tile API Developer's Guide 307► API Reference
Parameter Type Description
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
Map Tile API Developer's Guide 308► API Reference
Parameter Type Description
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Optional Metadata Specific Query Parameters
Table 95: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Map Tile API Developer's Guide 309► API Reference
Parameter Type Description
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Flow Tile (flowtile)Description
Returns a transparent image with only traffic flow.
Format
Map Tile API Developer's Guide 310► API Reference
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.traffic.maps.cit.api.here.com/maptile/2.1/flowtile/newest/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Table 96: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
Map Tile API Developer's Guide 311► API Reference
Parameter Type Description
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Map Tile API Developer's Guide 312► API Reference
Parameter Type Description
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 97: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Traffic Specific Query Parameters
The following table lists parameters for traffic options.
Map Tile API Developer's Guide 313► API Reference
Table 98: Traffic Specific Query Parameters
Parameter Type Description
min_traffic_congestionString (optional) Specifies the the minimum traffic congestion level to use for rendering
traffic flow. It accepts the following values:
free (default) – renders all traffic lines, which includes free flow,
heavy, queuing and blocked traffic lines.
heavy – renders all heavy traffic, queuing traffic and blocked roads.
queuing – renders the queuing traffic and blocked traffic lines.
blocked – renders only the black traffic lines for blocked roads.
Optional Query Parameters
Table 99: Optional Query parameters
Parameter Type Description
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Map Tile API Developer's Guide 314► API Reference
Parameter Type Description
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Traffic Tile (traffictile)Description
Returns a map image with traffic flow.
Format
Requests against this resource must follow the pattern summarized by the following formula:
http://{1-4}.traffic.maps.cit.api.here.com/maptile/2.1/traffictile/newest/{scheme}/{zoom}/{column}/{row}/{size}/{format}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
For information on how to construct the request, see Constructing a Request on page 16
Common URI Parameters
The following table lists the URI parameters that are common for all requests.
Map Tile API Developer's Guide 315► API Reference
Table 100: Common URI Parameters
Parameter Type Description
col Integer (required) col – can be any number between 0 and number of columns - 1,
both inclusive.
The number of tiles per column is a function of the zoom:
number of columns = 2zoom
format String (required) Returned image format. The following image formats are supported:
png – PNG format, 24 bit, RGB
png8 – PNG format, 8 bit, indexed color
jpg – JPG format at 90% quality
Please note that JPG is recommended for satellite and hybrid
schemes only.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
See Requesting the Right Map Version on page 26 for more information
on map versions.
row Integer (required) row – can be any number between 0 and number of rows - 1, both
inclusive.
The number of tiles per row is a function of the zoom: number of
rows = 2zoom.
scheme String (required) Specifies the view scheme. A complete list of the supported schemes
may be obtained by using the Info on page 322. The following schemes
are available:
• normal.day – for a normal map view in daylight mode
• normal.day.grey – for a color-reduced map view in daylight
mode (especially used for background maps)
• normal.day.transit – for a color-reduced map view with a
public transport scheme in daylight mode
• normal.traffic.day – for a color-reduced map view designed
for displaying traffic in daylight mode
• normal.traffic.night – for a color-reduced map view
designed for displaying traffic in night mode
• normal.day.custom – for a normal map view in daylight mode
• normal.night – for a normal map view in night mode
Map Tile API Developer's Guide 316► API Reference
Parameter Type Description
• normal.night.grey – for a color-reduced map view in night
mode (especially used for background maps)
• pedestrian.day – pedestrian map view in daylight mode
• pedestrian.day.mobile – pedestrian map view in daylight
mode for mobile usage
• pedestrian.night – pedestrian map view in night mode
• pedestrian.night.mobile – pedestrian map view in night
mode for mobile usage
• carnav.day.grey – for a normal map view in daylight mode for
car navigation
• normal.day.mobile – mobile version of the scheme
• normal.day.grey.mobile – mobile version of the scheme
• normal.day.transit.mobile – mobile version of the scheme
• normal.night.mobile – mobile version of the scheme
• normal.night.grey.mobile – mobile version of the scheme
• reduced.day – for a reduced map view in daylight mode with few
colors
• reduced.night – for a reduced map view in night mode with few
colors
• terrain.day – for a terrain map view in daylight mode
• satellite.day – for a satellite map view in daylight mode
• hybrid.day – for a satellite map view with streets in daylight
mode
• hybrid.grey.day – for a satellite map view with streets in
daylight mode with few colors
• hybrid.traffic.day – for a satellite map view with streets
designed for traffic
• terrain.day.mobile – mobile version of the scheme
• hybrid.day.mobile – mobile version of the scheme
Note: Please be aware that invalid combinations of schemes and Tiles
are rejected. For all satellite, hybrid and terrain schemes, the
Aerial Tiles base URL must be used instead of the normal one. For the
hybrid.traffic.day scheme, the Traffic Tiles base URL must be
used instead of the normal one. The other traffic related schemes
(normal.traffic.day, normal.traffic.night) are supported by
Traffic Tiles and Map Tiles. Originally they are supposed to be used only
with Traffic Tiles, but in order to properly support the traffic overlay
case where you would request a transparent traffic tile from Traffic
Tiles and a base tile from Map Tiles, the Map Tiles also support these
schemes.
Map Tile API Developer's Guide 317► API Reference
Parameter Type Description
size Integer (required) Returned image size. The following sizes ([width, height]) are supported:
256 = [256, 256]
512 = [512, 512]
The following sizes ([width, height]) are deprecated, although usage is
still accepted:
128 = [128, 128]
Note: Raster coverage tiles (rctile, rconlytile and
rcdistonlytile) only support 256 sizes.
zoom Integer (required) Zoom level of the map image. Minimum and maximum zoom levels are
specified in the Info on page 322.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 101: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Traffic Specific Query Parameters
The following table lists parameters for traffic options.
Table 102: Traffic Specific Query Parameters
Parameter Type Description
min_traffic_congestionString (optional) Specifies the the minimum traffic congestion level to use for rendering
traffic flow. It accepts the following values:
free (default) – renders all traffic lines, which includes free flow,
heavy, queuing and blocked traffic lines.
heavy – renders all heavy traffic, queuing traffic and blocked roads.
queuing – renders the queuing traffic and blocked traffic lines.
Map Tile API Developer's Guide 318► API Reference
Parameter Type Description
blocked – renders only the black traffic lines for blocked roads.
Optional Query Parameters
Table 103: Optional Query parameters
Parameter Type Description
congestion Boolean Flag that enables congestion and environmental zone display, if
available for the requested tile.
Available for the following tiles
• maptile
• traffictile
• rctile
• trucktile
• truckonlytile
lg String The MARC three-letter language code for requesting a map tile
rendered in a specific language. If the given language is not available,
the default language eng is used.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
Map Tile API Developer's Guide 319► API Reference
Parameter Type Description
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
lg2 String This parameter can be used to provide a second language for use in
dual labeling, it follows the same behaviour as the parameter lg.
The following languages are supported for the international version:
ara – Arabic
chi – Chinese (simplified)
cht – Chinese (traditional)
dut – Dutch
eng – English
fre – French
ger – German
gle – Gaelic
gre – Greek
heb – Hebrew
hin – Hindi
ind – Indonesian
ita – Italian
per – Persian
pol – Polish
por – Portuguese
rus – Russian
sin – Sinhalese
spa – Spanish
tha – Thai
tur – Turkish
ukr – Ukranian
urd – Urdu
vie – Vietnamese
Map Tile API Developer's Guide 320► API Reference
Parameter Type Description
wel – Welsh
The following languages are supported for the Chinese version:
chi – Chinese (simplified)
cht – Chinese (traditional)
eng – English
pois Boolean If present, pois are shown at a zoom level greater than or equal to 15, if
not present, regular tiles are shown.
Note: In metainfo tiles you must use this parameter if you
want to see POI information.
ppi Integer Pixels per inch. Resolution that can be requested, valid values are:
72 – normal, used by default if no value provided
250 – mobile
320 – hi-res
Note: This parameter is not accepted for carnav scheme, for mobile
schemes only mobile ppi value can be used, for hi-res schemes
only hi-res ppi value can be used. For normal.day.custom only
normal ppi is accepted.
range String Only relevant if output=base64 is also specified as a parameter.
range must be one of 2x2, 3x3 or 4x4, which indicates the size of the
array of tiles returned. The tile specified by col and row is the top left
of the array, and must divide by the array size.
style String If present, selects the style to use to render the tile. The possible
values are:
default
alps
fleet
wings
dreamworks
flame
mini
Note: Only a subset of the schemes are available for the
styles, which is checked at runtime. If the scheme is not
available for the given style, a 400 Error is generated.
Note: Each of these styles has been developed for specific
customers and very concrete uses cases so if you are not one
of those customers you should not use these map styles. The
only exception is default, which always exists and is used
Map Tile API Developer's Guide 321► API Reference
Parameter Type Description
for the default style. Adding this style to the url or not using
any style parameter renders the same results.
Note: Fleet only supports normal.day, hybrid.day and
terrain.day.
Note: Wings only supports normal.day, reduced.day,
normal.night and normal.night.grey.
Note: Dreamworks only support normal.day.
Note: Flame only supports normal.day and hybrid.day.
Note: Alps and Mini only support normal.day,
normal.day.grey, normal.day.transit,
normal.day.custom, normal.night,
normal.night.grey, terrain.day, satellite.day,
hybrid.day, pedestrian.day, pedestrian.night,
carnav.day.grey, and reduced.day.
Optional Metadata Specific Query Parameters
Table 104: Optional Metadata Query parameters
Parameter Type Description
metadata String Type of metadata to generate, valid values are:
metaonly: only metadata are returned; output=base64 is
automatically enabled
metatile: both the requested image and the associated metadata
are returned; output=base64 is automatically on
Note: Optionally, the parameter callback_func can be
used as well.
output String Can only have the value base64, which indicates that the map tile is
returned as base64 encoded text instead of as a stand alone image.
Note: Please be aware that this feature is not available for
traffic.
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Map Tile API Developer's Guide 322► API Reference
Parameter Type Description
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
filter String This parameter accepts two values:
0 (no effect)
1 (filter out only roadsigns)
Note: This parameter only filters out information in a
metadata response.
Note: This parameter only works in combination with the
parameter mgen.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
Information ResourcesThis chapter lists additional information resources.
Infoinfo is a resource that retrieves information about the map rendering service available on the server
(metadata about the service), including the available map versions, map tile formats, resolutions, map
view schemes, supported map languages, etc.
Metadata requests retrieve information specific to the base URLs they target. This information
cannot be used in subsequent requests that use other base URLs. For example, to obtain a traffic
map version, use metadata from the response to a request addressed to the Traffic Tiles base URL,
but for a version of an aerial map, use metadata from the response to a request addressed to the
Aerial Tiles base URL.
Map Tile API Developer's Guide 323► API Reference
Note: Info requests are sometimes referred to as metadata info requests, please note thatthey are not the same as metadata requests using the parameter metadata.
Note: Please see Requesting the Right Map Version on page 26 for information on how to usehashcodes.
The following example shows a request to this resource.
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/info?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 105: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Information Specific Query Parameters
Table 106: Information Specific Query parameters
Parameter Type Description
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
callback_id String If specified (associated with callback_func), the function wrapper
contains this id as the first parameter. This allows the user to check
Map Tile API Developer's Guide 324► API Reference
Parameter Type Description
if the response is actually the response to the request, and not some
maliciously injected code; for example
callback_id=1425
returns:
test( '1425', '{ ...}' );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
hash_for String Note: The usage of this parameter is deprecated
Used to obtain information about a specific map version. This
parameter is only valid if output is set to header. This parameter is
designed to offer automated caches a simple way to relate map version
strings to their current hash. The valid values of the parameter are:
"newest" – indicates the most recent map version
a string containing the map version ID – indicates that the hash for
this specific version is to be retrieved
If the parameter is used, the response header contains a key, maphash,
with a hash value identifying the specified map version.
mgen String Specifies the metadata generation to use. This parameter accepts the
following values:
1: default
2: optimized out json format that filters empty values and allows
the usage of parameter filter, the output of this version might
change between releases as it is still under development
latest: always takes the latest version available
Note: For maptile, this parameter is only available for
metadata requests and output json.
Note: For info requests, this parameter is only available
when using output json.
output String Output specifier. The API supports the following output specifier values
(and output formats):
• xml – delivers the API metadata in XML format according to the
XSD (this is the default).
• json – delivers the API metadata in JSON format; for JSONP
requests see the parameter callback_func/callback_id
• xsd – delivers the specific XML schema (XSD) of the API metadata
to process and to verify the Service Meta Data Response.
Map Tile API Developer's Guide 325► API Reference
Metadata Request
The following example shows a request for metadata in XML format. An alternative output format is
JSON. This is just an example and might not be up to date.
Note: Please be aware that json output allows usage of the parameter mgen to get the latestformat available.
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/info?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Metadata Response
The XML response to the above request contains the following data:
<?xml version="1.0" encoding="UTF-8"?><response> <maps> <map region="all" id="newest" /> <map region="all" newest="true" id="8.30.53.109" hash="be9b70fa2c" /> </maps> <resolutions> <resolution id="512" height="512" width="512" /> <resolution id="256" height="256" width="256" /> <resolution id="128" height="128" width="128" /> </resolutions> <formats> <format encoding="png" bbp="24" id="png" /> <format encoding="png8" bbp="8" id="png8" /> <format encoding="jpg" bbp="24" id="jpg" /> </formats> <schemes> <scheme id="normal.day" /> <scheme id="normal.day.grey" /> <scheme id="normal.day.transit" /> <scheme id="normal.day.custom" /> <scheme id="normal.night" /> <scheme id="normal.night.grey" /> <scheme id="pedestrian.day" /> <scheme id="pedestrian.night" /> <scheme id="carnav.day.grey" /> <scheme id="normal.day.mobile" /> <scheme id="normal.day.grey.mobile" /> <scheme id="normal.day.transit.mobile" /> <scheme id="normal.night.mobile" /> <scheme id="normal.night.grey.mobile" /> <scheme id="reduced.day" /> <scheme id="terrain.day" /> <scheme id="satellite.day" /> <scheme id="hybrid.day" /> <scheme id="terrain.day.mobile" />
Map Tile API Developer's Guide 326► API Reference
<scheme id="hybrid.day.mobile" /> </schemes> <styles> <style id="default"> <scheme id="normal.day"/> <scheme id="normal.day.grey"/> <scheme id="normal.day.transit"/> <scheme id="normal.day.custom"/> <scheme id="normal.night"/> <scheme id="normal.night.grey"/> <scheme id="terrain.day"/> <scheme id="satellite.day"/> <scheme id="hybrid.day"/> <scheme id="hybrid.grey.day"/> <scheme id="pedestrian.day"/> <scheme id="pedestrian.night"/> <scheme id="carnav.day.grey"/> <scheme id="reduced.day"/> <scheme id="reduced.night"/> <scheme id="normal.traffic.day"/> <scheme id="normal.day.mobile"/> <scheme id="normal.day.grey.mobile"/> <scheme id="normal.day.transit.mobile"/> <scheme id="normal.night.mobile"/> <scheme id="normal.night.grey.mobile"/> <scheme id="terrain.day.mobile"/> <scheme id="hybrid.day.mobile"/> <scheme id="pedestrian.day.mobile"/> <scheme id="pedestrian.night.mobile"/> <scheme id="normal.traffic.night"/> </style> <style id="fleet"> <scheme id="normal.day"/> <scheme id="terrain.day"/> <scheme id="hybrid.day"/> </style> <style id="dreamworks"> <scheme id="normal.day"/> </style> <style id="wings"> <scheme id="normal.day"/> <scheme id="reduced.day"/> </style> <style id="flame"> <scheme id="normal.day"/> <scheme id="hybrid.day"/> </style> <style id="alps"> <scheme id="normal.day"/> <scheme id="normal.day.grey"/> <scheme id="normal.day.transit"/> <scheme id="normal.day.custom"/> <scheme id="normal.night"/> <scheme id="normal.night.grey"/> <scheme id="terrain.day"/> <scheme id="satellite.day"/>
Map Tile API Developer's Guide 327► API Reference
<scheme id="hybrid.day"/> <scheme id="pedestrian.day"/> <scheme id="pedestrian.night"/> <scheme id="carnav.day.grey"/> <scheme id="reduced.day"/> </style> <style id="mini"> <scheme id="normal.day"/> <scheme id="normal.day.grey"/> <scheme id="normal.day.transit"/> <scheme id="normal.day.custom"/> <scheme id="normal.night"/> <scheme id="normal.night.grey"/> <scheme id="terrain.day"/> <scheme id="satellite.day"/> <scheme id="hybrid.day"/> <scheme id="pedestrian.day"/> <scheme id="pedestrian.night"/> <scheme id="carnav.day.grey"/> <scheme id="reduced.day"/> </style> </styles> <tiletypes> <tiletype id="maptile" /> <tiletype id="basetile" /> <tiletype id="xbasetile" /> <tiletype id="alabeltile" /> <tiletype id="labeltile" /> <tiletype id="linetile" /> <tiletype id="streettile" /> <tiletype id="lltile" /> <tiletype id="trucktile" /> <tiletype id="truckonlytile" /> <tiletype id="rctile" /> <tiletype id="rconlytile" /> <tiletype id="rcdistonlytile" /> </tiletypes> <languages> <language id="ARA" /> <language id="CHI" /> <language id="CHT" /> <language id="DUT" /> <language id="ENG" /> <language id="FRE" /> <language id="GER" /> <language id="GLE" /> <language id="GRE" /> <language id="HEB" /> <language id="HIN" /> <language id="IND" /> <language id="ITA" /> <language id="PER" /> <language id="POL" /> <language id="POR" /> <language id="RUS" /> <language id="SIN" />
Map Tile API Developer's Guide 328► API Reference
<language id="SPA" /> <language id="THA" /> <language id="TUR" /> <language id="UKR" /> <language id="URD" /> <language id="VIE" /> <language id="ENG" /> </languages> <zoomLevels min="0" max="20" /></response>
The table below describes the XML elements in this output.
Table 107: Elements in the output
Element Description
maps Available maps. A map has the following attributes:
region: the region of the world where the map is valid, currently only all (world) is supported.
id: the map version, newest always refers to the latest map version. Several latest map versions
for different regions are possible.
newest: identifies the newest hash used in the server, it will be true for just one hash of the
possible list.
hash: the unique key used to reference the specific map version in the map id parameter of a map
tile request, see Requesting the Right Map Version on page 26.
isbn: unique identifier used for validated chinese maps, it will either be empty or not present for
international maps.
resolutions Supported map tile image resolutions. A resolution has the following attributes:
id: used to reference the resolution in the size parameter of a map tile request.
height: the height of the supported image resolution.
width: the width of the supported image resolution.
formats Supported image formats. A format has the following attributes:
encoding: the image encoding format, one of: png, png8 or jpg.
bbp: bytes per pixel, 8 bbp refers to a palette based image format, 24 bbp is a true RGB image
format.
id: used to reference the format in the format parameter of a map tile request.
schemes List of all supported map tile schemes. A scheme has the following attribute:
id: used to reference the scheme in the scheme parameter of a map tile request.
styles List of all supported styles. Every style supports certain schemes, A style has the following
attribute:
id: used to reference the style in the style parameter of a map tile request.
Map Tile API Developer's Guide 329► API Reference
Element Description
List of schemes supported for that style following the same format as the previous entry for
schemes.
tiletypes Supported map tile types. A tiletype has the following attribute:
id: used to reference the scheme in the type parameter of a map tile request.
languages Supported languages for rendered map tiles. A language has the following attribute:
id: a MARC three-letter code used to reference the language in the lg parameter of a map tile
request.
zoomLevels Minimum and maximum values for the zoom parameter in a map tile request.
min: minimum possible map tile zoom.
max: maximum possible map tile zoom.
CopyrightThe resource named copyright handles requests for copyright information about different map
tiles.
A typical request against this resource must comply with the following formula.
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/copyright/{map id}?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Note: Metadata requests retrieve information specific to the base URLs they target. This
information cannot be used in subsequent requests that use other base URLs. For example, to
obtain a traffic map version, use metadata from the response to a request addressed to the
Traffic Tiles base URL, but for a version of an aerial map, use metadata from the response to a
request addressed to the Aerial Tiles base URL.
In both output formats (XML and JSON), the copyright information associated with the different view
schemes, zoom level ranges, and geographical areas is shown. Variant copyrights are defined by the
bounding boxes and the relevant zoom level range. The default copyright information of the view
scheme has no restriction elements and is therefore valid for all remaining areas and zoom levels.
The map id used in the request should be the same one as the one used for making the requests.
For example it can be a hash value or newest.
The copyright information must be retrieved for every pool separately.
The table below describes the parameters that can be used to formulate a copyright information
request.
Map Tile API Developer's Guide 330► API Reference
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 108: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Table 109: Copyright Specific Query paramaters
Parameter Type Description
callback_func String A function name that is wrapped around the JSON output. This
technique allows for a more secure way of parsing the output with
JavaScript, for example:
&callback_func=test
returns:
test( [ ... ] );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
callback_id String If specified (associated with callback_func), the function wrapper
contains this id as the first parameter. This allows the user to check
if the response is actually the response to the request, and not some
maliciously injected code; for example
callback_id=1425
returns:
test( '1425', '{ ...}' );
Note: The value is url-decoded, but it is the responsibility of
the requestor to provide a value that is JavaScript correct.
map id String (required) Specifies the map version. It can be:
• version id the map version of the requested map tile resource;
request the latest version by using newest as map id.
• hash A unique key, unambiguously representing a specific map
version.
Map Tile API Developer's Guide 331► API Reference
Parameter Type Description
See Requesting the Right Map Version on page 26 for more information
on map versions.
output String Output specifier. The API supports the following output specifier values
(and output formats):
• xml – delivers the API metadata in XML format according to the
XSD (this is the default).
• json – delivers the API metadata in JSON format; for JSONP
requests see the parameter callback_func/callback_id
• xsd – delivers the specific XML schema (XSD) of the API metadata
to process and to verify the Service Meta Data Response.
Example Copyright Request in XML
The following example requests copyright information in XML:
http://1.base.maps.cit.api.here.com/maptile/2.1/copyright/newest?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&output=xml
Example Copyright Response in XML
The following code block shows the XML response for base flavour, please be aware that this is only
an example and does not represent the latest information.
<?xml version="1.0" encoding="UTF-8"?><copyrights xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="nokia:maptiler:copyright:1.0" xsi:schemaLocation="nokia:maptiler:copyright:1.0 CopyrightInfo.xsd"> <providers> <provider name="IGM"> <text>IGM</text> <full>INSTITUTO GEOGRAFICO MILITAR DEL ECUADOR AUTORIZACION No IGM-2011-01- PCO-01 DEL 25 DE ENERO DE 2011</full> </provider> <provider name="IGN"> <text>IGN</text> <full>copyright IGN 2009 - BD TOPO</full> </provider> <provider name="EuroGeographics"> <text>EuroGeographics</text> <full>copyright EuroGeographics</full> </provider> <provider name="SWISSTOPO"> <text>Swisstopo</text> <full>Topografische Grundlage: copyright Bundesamt fur Landestopographie</full> </provider> <provider name="PSMA"> <text>PSMA</text> <full>Copyright. Based on data provided under license from PSMA Australia Limited. Product incorporates data which is 2014 Telstra Corporation Limited, GM Holden Limited,
Map Tile API Developer's Guide 332► API Reference
Intelematics Australia Pty Ltd, HERE International LLC, Sentinel Content Pty Limited and Continental Pty Ltd</full> <link>http://www.psma.com.au</link> </provider> <provider name="NEPAL"> <text>Nepal</text> <full>Copyright Survey Department, Government of Nepal</full> </provider> <provider name="Jordan"> <text>Jordan</text> <full>Royal Jordanian Geographic Centre</full> </provider> <provider name="LANTMATERIET"> <text>Lantmateriet</text> <full>Based upon electronic data National Land Survey Sweden.</full> </provider> <provider name="CNIG"> <text>CNIG</text> <full>Informacion geografica propiedad del CNIG</full> </provider> <provider name="GER"> <text>Deutschland</text> <full>Die Grundlagendaten wurden mit Genehmigung der zustandigen Behorden entnommen</full> </provider> <provider name="OGL"> <text>OGL</text> <full>Open Government Licence v.1.0.</full> <link>http://www.nationalarchives.gov.uk/doc/open-government-licence/</link> </provider> <provider name="SOI"> <text>SOI</text> <full>Survey of Israel data source</full> </provider> <provider name="BEV"> <text>BEV</text> <full>copyright Bundesamt fur Eich- und Vermessungswesen</full> </provider> <provider name="ITA"> <text>ITA</text> <full>La Banca Dati Italiana e stata prodotta usando quale riferimento anche cartografia numerica ed al tratto prodotta e fornita dalla Regione Toscana</full> </provider> <provider name="CAN"> <text>Canada</text> <full>This data includes information taken with permission from Canadian authorities, including Her Majesty, Queens Printer for Ontario, Canada Post, GeoBase, Department of Natural Resources Canada. All rights reserved</full> </provider> <provider name="USPS"> <text>USPS</text> <full>copyright United States Postal Service 2014. Prices are not established, controlled or approved by the United States Postal Service. The following trademarks and registrations are owned by the USPS: United States Postal Service, USPS, and ZIP+4</full> </provider> <provider name="Cenacarta"> <text>Cenacarta</text> <full>Certain Data for Mozambique provided by Cenacarta 2014 by Cenacarta</full> </provider> <provider name="IGN_France"> <text>IGN</text> <full>copyright IGN France 2009 BD TOPO</full> </provider> <provider name="Geomatics"> <text>Geomatics</text> <full>Copyright Geomatics Ltd.</full> </provider> <provider name="THTC"> <text>2014 THTC</text> <full>copyright 2014 Iran Maps provided by THTC</full>
Map Tile API Developer's Guide 333► API Reference
</provider> <provider name="Statkart"> <text>Statkart</text> <full>Copyright 2000; Norwegian Mapping Authority</full> </provider> <provider name="SRLANKA"> <text>Sri Lanka</text> <full>This product incorporates original source digital data obtained from the Survey Department of Sri Lanka. 2009 Survey Department of Sri Lanka The data has been used with the permission of the Survey Department of Sri Lanka</full> </provider> <provider name="IGN_Guatemala"> <text>IGN Guatemala</text> <full>Aprobado por el INSTITUTO GEOGRAFICO NACIONAL Resolucion del IGN No 186-2011</full> </provider> <provider name="NavInfo"> <text>2014 NavInfo</text> <full>copyright 2014 NavInfo Co Ltd. All Rights Reserved</full> <link>http://www.nav2.com.cn/</link> </provider> <provider name="INEGI"> <text>INEGI</text> <full>Fuente: INEGI (Instituto Nacional de Estadistica y Geografia)</full> </provider> <provider name="IgeoE"> <text>IgeoE</text> <full>IgeoE - Portugal</full> </provider> </providers> <areas> <area name="Canada"> <geoRect left="-101.0000" bottom="78.0000" right="-69.0000" top="82.0000" /> <geoRect left="-115.0000" bottom="78.0000" right="-101.0000" top="80.0000" /> <geoRect left="-77.0000" bottom="70.0000" right="-67.0000" top="74.0000" /> <geoRect left="-69.0000" bottom="80.0000" right="-61.0000" top="82.0000" /> <geoRect left="-141.0000" bottom="62.0000" right="-63.0000" top="70.0000" /> <geoRect left="-83.0000" bottom="41.9986" right="-77.4271" top="44.0238" /> <geoRect left="-81.0000" bottom="56.0000" right="-63.0000" top="62.0000" /> <geoRect left="-57.0000" bottom="50.0000" right="-55.0000" top="54.0000" /> <geoRect left="-129.0000" bottom="48.0000" right="-57.0000" top="56.0000" /> <geoRect left="-63.0000" bottom="56.0000" right="-61.0000" top="68.0000" /> <geoRect left="-125.9042" bottom="70.0000" right="-77.0000" top="78.0000" /> <geoRect left="-135.0000" bottom="56.0000" right="-87.0000" top="58.0000" /> <geoRect left="-87.5736" bottom="46.0000" right="-57.0000" top="48.0357" /> <geoRect left="-135.0000" bottom="52.0000" right="-129.0000" top="56.0000" /> <geoRect left="-91.0000" bottom="82.0000" right="-61.0000" top="84.0000" /> <geoRect left="-57.0167" bottom="46.3831" right="-50.9810" top="49.9905" /> <geoRect left="-141.0000" bottom="58.0000" right="-91.0000" top="62.0000" /> <geoRect left="-85.0026" bottom="44.0000" right="-59.0000" top="46.0536" /> </area> <area name="Portugal"> <geoRect left="-6.5519" bottom="41.2304" right="-6.1811" top="41.7009" /> <geoRect left="-7.5899" bottom="39.3941" right="-6.9850" top="39.6663" /> <geoRect left="-7.3532" bottom="40.9842" right="-6.5519" top="41.2705" /> <geoRect left="-32.0392" bottom="36.5482" right="-23.6635" top="40.4124" /> <geoRect left="-17.3686" bottom="32.2747" right="-15.9142" top="33.1907" /> <geoRect left="-7.2357" bottom="41.7211" right="-6.5050" top="42.0048" /> <geoRect left="-7.5520" bottom="39.6540" right="-6.7565" top="40.2572" /> <geoRect left="-9.0081" bottom="36.9392" right="-7.2449" top="38.4418" /> <geoRect left="-8.4431" bottom="39.4153" right="-7.2126" top="41.9675" /> <geoRect left="-7.2522" bottom="37.9667" right="-6.8808" top="38.3853" /> <geoRect left="-8.9260" bottom="38.4418" right="-6.7321" top="39.5144" /> <geoRect left="-15.8830" bottom="30.1318" right="-15.8445" top="30.1622" /> <geoRect left="-9.1848" bottom="39.4801" right="-7.8729" top="42.1722" /> <geoRect left="-9.5593" bottom="38.1864" right="-8.8950" top="39.5271" /> <geoRect left="-7.4841" bottom="40.1168" right="-6.7565" top="40.9984" /> <geoRect left="-7.3100" bottom="41.2304" right="-6.5183" top="41.7633" /> </area> <area name="Australia"> <geoRect left="158.0863" bottom="-32.5901" right="160.0863" top="-30.5901" />
Map Tile API Developer's Guide 334► API Reference
<geoRect left="113.0000" bottom="-32.0000" right="151.0000" top="-20.0000" /> <geoRect left="141.0000" bottom="-14.0000" right="145.0000" top="-8.0000" /> <geoRect left="167.0381" bottom="-30.0761" right="169.0381" top="-28.0761" /> <geoRect left="129.0000" bottom="-14.0000" right="137.0000" top="-10.0000" /> <geoRect left="135.0000" bottom="-38.0000" right="151.0000" top="-32.0000" /> <geoRect left="151.0000" bottom="-34.0000" right="155.0000" top="-24.0000" /> <geoRect left="127.0000" bottom="-34.0000" right="135.0000" top="-32.0000" /> <geoRect left="95.8626" bottom="-13.1672" right="97.8626" top="-11.1672" /> <geoRect left="123.0000" bottom="-20.0000" right="147.0000" top="-14.0000" /> <geoRect left="104.6728" bottom="-11.5539" right="106.6728" top="-9.5539" /> <geoRect left="141.0000" bottom="-44.0000" right="149.0000" top="-38.0000" /> <geoRect left="115.0000" bottom="-36.0000" right="127.0000" top="-32.0000" /> <geoRect left="121.0000" bottom="-20.0000" right="123.0000" top="-16.0000" /> </area> <area name="Switzerland"> <geoRect left="10.0312" bottom="46.2473" right="10.1820" top="46.3547" /> <geoRect left="6.8641" bottom="45.8206" right="7.3171" top="47.4100" /> <geoRect left="6.9280" bottom="47.4100" right="7.3171" top="47.5272" /> <geoRect left="9.5821" bottom="47.2863" right="9.6893" top="47.5004" /> <geoRect left="8.5106" bottom="46.0972" right="8.6761" top="46.2180" /> <geoRect left="8.6761" bottom="46.0193" right="9.1291" top="46.2180" /> <geoRect left="8.7540" bottom="45.7831" right="9.1167" top="46.0193" /> <geoRect left="9.4435" bottom="46.2703" right="9.8658" top="46.4166" /> <geoRect left="6.4111" bottom="46.4166" right="6.8641" top="47.0127" /> <geoRect left="8.2231" bottom="46.2180" right="9.1291" top="46.4166" /> <geoRect left="10.2370" bottom="46.5237" right="10.4882" top="46.6153" /> <geoRect left="10.0449" bottom="46.2131" right="10.1820" top="46.2643" /> <geoRect left="5.9453" bottom="46.1195" right="6.3156" top="46.2180" /> <geoRect left="9.5821" bottom="47.0127" right="9.9106" top="47.0721" /> <geoRect left="9.5821" bottom="46.6153" right="10.4882" top="47.0127" /> <geoRect left="8.6761" bottom="47.6087" right="9.4309" top="47.8074" /> <geoRect left="10.0351" bottom="46.4140" right="10.1740" top="46.6153" /> <geoRect left="9.5821" bottom="46.4166" right="10.0351" top="46.6153" /> <geoRect left="6.7620" bottom="46.1024" right="6.8641" top="46.4166" /> <geoRect left="7.3171" bottom="46.4166" right="9.5821" top="47.6087" /> <geoRect left="9.8639" bottom="46.3513" right="10.0351" top="46.4166" /> <geoRect left="6.1662" bottom="46.6153" right="6.4111" top="46.7577" /> <geoRect left="6.6305" bottom="47.0127" right="6.8641" top="47.1914" /> <geoRect left="10.0312" bottom="46.3367" right="10.1725" top="46.4166" /> <geoRect left="8.2231" bottom="47.6087" right="8.6761" top="47.8074" /> <geoRect left="9.1291" bottom="46.1180" right="9.3037" top="46.4166" /> <geoRect left="7.3171" bottom="46.0193" right="8.2231" top="46.4166" /> <geoRect left="7.3171" bottom="45.8846" right="8.0455" top="46.0193" /> <geoRect left="9.9778" bottom="46.2654" right="10.0368" top="46.3547" /> <geoRect left="5.9581" bottom="46.2180" right="6.4111" top="46.6153" /> </area> <area name="Ecuador"> <geoRect left="-78.4796" bottom="0.8202" right="-78.0677" top="1.1441" /> <geoRect left="-78.4796" bottom="0.4963" right="-77.2440" top="0.8202" /> <geoRect left="-76.4202" bottom="-2.4189" right="-76.0083" top="-2.0950" /> <geoRect left="-80.9509" bottom="-2.7428" right="-80.5390" top="1.1441" /> <geoRect left="-80.5390" bottom="-4.6863" right="-78.4796" top="1.1441" /> <geoRect left="-78.0677" bottom="-3.0667" right="-77.2440" top="-2.7428" /> <geoRect left="-78.4796" bottom="-2.0950" right="-75.5964" top="0.4963" /> <geoRect left="-75.5964" bottom="-1.4472" right="-75.1846" top="0.1724" /> <geoRect left="-81.3628" bottom="-2.7428" right="-80.9509" top="-0.7994" /> <geoRect left="-78.4796" bottom="-3.7146" right="-78.0677" top="-2.0950" /> <geoRect left="-79.7153" bottom="-5.0102" right="-78.8915" top="-4.6863" /> <geoRect left="-78.0677" bottom="-2.7428" right="-76.4202" top="-2.0950" /> <geoRect left="-79.3034" bottom="1.1441" right="-78.4796" top="1.4680" /> </area> <area name="Iraq"> <geoRect left="40.2408" bottom="34.0557" right="46.4809" top="35.7256" /> <geoRect left="40.2408" bottom="29.0724" right="45.6538" top="34.0557" /> <geoRect left="38.7937" bottom="29.8076" right="43.8802" top="34.0739" /> <geoRect left="45.6538" bottom="29.0724" right="47.9928" top="34.0557" /> <geoRect left="42.7138" bottom="35.7168" right="46.4809" top="37.3779" /> <geoRect left="47.1930" bottom="29.9029" right="48.5938" top="31.4399" /> <geoRect left="41.2402" bottom="35.7168" right="42.7138" top="37.3779" /> </area>
Map Tile API Developer's Guide 335► API Reference
<area name="Republic of Moldova"> <geoRect left="29.2256" bottom="46.5465" right="30.0376" top="46.8365" /> <geoRect left="28.2568" bottom="45.7302" right="29.2353" top="47.4471" /> <geoRect left="29.2282" bottom="46.7892" right="29.9684" top="47.4471" /> <geoRect left="28.5878" bottom="45.7302" right="29.0637" top="46.2901" /> <geoRect left="26.5110" bottom="46.8530" right="29.3448" top="48.6163" /> <geoRect left="29.2029" bottom="46.3002" right="30.2333" top="46.5592" /> <geoRect left="28.0701" bottom="45.4102" right="28.5878" top="46.4249" /> <geoRect left="28.0081" bottom="45.4154" right="28.4224" top="46.1325" /> <geoRect left="28.0753" bottom="46.4187" right="29.3100" top="47.9267" /> </area> <area name="Islamic Republic of Iran"> <geoRect left="54.2859" bottom="37.3605" right="59.0624" top="38.2982" /> <geoRect left="61.7923" bottom="25.7411" right="61.8881" top="26.2083" /> <geoRect left="60.8423" bottom="29.9265" right="61.9599" top="31.5665" /> <geoRect left="44.2983" bottom="38.2632" right="46.5449" top="39.0496" /> <geoRect left="53.8979" bottom="25.7433" right="61.7923" top="37.6020" /> <geoRect left="60.4947" bottom="31.5665" right="60.9660" top="34.0374" /> <geoRect left="46.9254" bottom="39.0244" right="48.3969" top="39.7910" /> <geoRect left="60.4678" bottom="29.8177" right="60.9671" top="31.5665" /> <geoRect left="46.5449" bottom="38.1617" right="48.0120" top="39.1950" /> <geoRect left="46.0457" bottom="32.9515" right="46.2203" top="33.1362" /> <geoRect left="62.3114" bottom="26.5239" right="62.6364" top="26.5998" /> <geoRect left="60.8544" bottom="25.7433" right="61.9791" top="29.9265" /> <geoRect left="61.8391" bottom="26.4634" right="62.9147" top="28.6155" /> <geoRect left="44.4164" bottom="35.8416" right="47.5346" top="38.8818" /> <geoRect left="45.2424" bottom="32.9552" right="47.3873" top="35.8416" /> <geoRect left="44.1806" bottom="35.7409" right="46.0286" top="38.2632" /> <geoRect left="47.3792" bottom="25.7783" right="56.2187" top="32.0891" /> <geoRect left="44.0023" bottom="38.4003" right="45.4530" top="39.8596" /> <geoRect left="63.1942" bottom="27.0181" right="63.3436" top="27.2641" /> <geoRect left="46.2203" bottom="26.1964" right="57.1922" top="38.4489" /> <geoRect left="61.8081" bottom="25.7411" right="61.9006" top="25.9431" /> <geoRect left="48.0120" bottom="38.8953" right="48.3415" top="39.0229" /> <geoRect left="60.5115" bottom="34.1048" right="61.5751" top="36.6543" /> <geoRect left="59.0624" bottom="33.8976" right="61.1473" top="37.6020" /> <geoRect left="59.9152" bottom="31.4968" right="60.8423" top="34.0374" /> <geoRect left="61.8221" bottom="26.2013" right="62.3152" top="26.5448" /> <geoRect left="46.0286" bottom="35.3974" right="48.8454" top="38.8972" /> <geoRect left="47.5269" bottom="38.8972" right="48.3741" top="39.2823" /> <geoRect left="57.1430" bottom="24.9003" right="61.8081" top="26.1964" /> <geoRect left="62.8691" bottom="26.8134" right="63.2960" top="27.2641" /> <geoRect left="62.9016" bottom="26.6245" right="63.2208" top="26.8405" /> </area> <area name="Norway"> <geoRect left="16.8944" bottom="67.8075" right="25.1741" top="71.3965" /> <geoRect left="27.8446" bottom="68.8789" right="32.1402" top="71.4071" /> <geoRect left="24.6595" bottom="68.4773" right="26.3932" top="71.3952" /> <geoRect left="6.1059" bottom="61.0315" right="18.0586" top="70.9952" /> <geoRect left="15.2505" bottom="66.1997" right="16.3893" top="67.3135" /> <geoRect left="13.0203" bottom="63.9575" right="14.7214" top="65.6822" /> <geoRect left="25.9972" bottom="69.6571" right="28.8856" top="71.4071" /> <geoRect left="9.9664" bottom="59.2422" right="13.0634" top="63.2018" /> <geoRect left="2.9492" bottom="56.4440" right="12.0640" top="63.9455" /> </area> <area name="Estonia"> <geoRect left="25.5161" bottom="57.4400" right="27.8981" top="58.0205" /> <geoRect left="27.4528" bottom="58.0107" right="27.6501" top="58.7552" /> <geoRect left="24.2950" bottom="57.8526" right="24.7904" top="57.9554" /> <geoRect left="27.4413" bottom="58.7436" right="28.2525" top="59.4859" /> <geoRect left="21.7448" bottom="57.8968" right="23.4580" top="59.3645" /> <geoRect left="23.4390" bottom="57.9301" right="27.4650" top="59.7909" /> <geoRect left="23.1887" bottom="57.7540" right="23.2957" top="57.8411" /> </area> <area name="French Guiana"> <geoRect left="-54.2990" bottom="3.5684" right="-51.6174" top="5.7509" /> <geoRect left="-54.0010" bottom="2.1134" right="-52.5112" top="3.5684" /> <geoRect left="-54.6066" bottom="2.1062" right="-54.0010" top="3.5684" /> <geoRect left="-52.5112" bottom="2.6665" right="-52.0258" top="3.5742" /> <geoRect left="-54.5201" bottom="3.9930" right="-54.2990" top="5.2588" />
Map Tile API Developer's Guide 336► API Reference
</area> <area name="Swaziland"> <geoRect left="30.9615" bottom="-27.3832" right="32.0286" top="-26.5576" /> <geoRect left="31.4364" bottom="-27.3403" right="32.0286" top="-26.7719" /> <geoRect left="30.7201" bottom="-27.0738" right="31.5422" top="-26.2624" /> <geoRect left="32.0275" bottom="-26.8455" right="32.1475" top="-26.7719" /> <geoRect left="30.8723" bottom="-26.8359" right="32.1739" top="-25.6938" /> </area> <area name="Poland"> <geoRect left="14.0753" bottom="49.0148" right="20.2333" top="55.0681" /> <geoRect left="19.3708" bottom="49.1699" right="23.8452" top="52.6479" /> <geoRect left="23.7940" bottom="50.3804" right="24.1242" top="50.6141" /> <geoRect left="18.2346" bottom="51.6271" right="24.1071" top="55.0681" /> <geoRect left="23.3995" bottom="50.3495" right="24.1571" top="51.0366" /> <geoRect left="23.1726" bottom="51.0366" right="23.7360" top="52.2145" /> <geoRect left="14.0896" bottom="52.7337" right="14.3477" top="53.0647" /> <geoRect left="22.2773" bottom="49.5714" right="23.7502" top="51.4811" /> <geoRect left="23.3995" bottom="50.8016" right="24.1714" top="51.5813" /> <geoRect left="21.8835" bottom="48.9384" right="22.9603" top="49.9277" /> </area> <area name="Cyprus"> <geoRect left="32.2293" bottom="34.3756" right="33.7589" top="35.5938" /> <geoRect left="33.5454" bottom="35.1525" right="34.6339" top="35.7340" /> <geoRect left="33.6276" bottom="34.8444" right="34.1041" top="35.2760" /> </area> <area name="China"> <geoRect left="75.5576" bottom="35.7754" right="78.5576" top="36.7754" /> <geoRect left="106.5576" bottom="20.7754" right="113.5576" top="22.7754" /> <geoRect left="93.5576" bottom="28.6334" right="94.0161" top="28.7754" /> <geoRect left="111.5576" bottom="42.7754" right="115.5576" top="45.7754" /> <geoRect left="120.5576" bottom="32.7754" right="120.8986" top="33.5701" /> <geoRect left="113.5576" bottom="21.7754" right="116.5576" top="22.7754" /> <geoRect left="79.5576" bottom="42.7754" right="94.5576" top="45.7754" /> <geoRect left="117.5576" bottom="23.7754" right="118.5576" top="24.7754" /> <geoRect left="94.5576" bottom="42.7754" right="96.5576" top="44.7754" /> <geoRect left="98.5576" bottom="21.7754" right="104.5576" top="22.7754" /> <geoRect left="82.5576" bottom="28.7754" right="98.5576" top="29.7754" /> <geoRect left="117.5576" bottom="24.7754" right="119.5576" top="25.7754" /> <geoRect left="120.5576" bottom="38.7754" right="124.5576" top="39.7754" /> <geoRect left="120.5576" bottom="29.7754" right="122.5576" top="32.7754" /> <geoRect left="79.2585" bottom="41.7754" right="79.5576" top="41.8535" /> <geoRect left="122.5576" bottom="29.7754" right="123.5576" top="31.7754" /> <geoRect left="91.7865" bottom="27.6769" right="92.1101" top="27.7754" /> <geoRect left="117.5576" bottom="27.7754" right="122.5576" top="29.7754" /> <geoRect left="108.5576" bottom="18.7754" right="111.5576" top="20.7754" /> <geoRect left="79.5576" bottom="29.7754" right="120.5576" top="42.7754" /> <geoRect left="121.5576" bottom="36.7754" right="123.5576" top="37.7754" /> <geoRect left="86.6922" bottom="48.7754" right="88.1056" top="49.2494" /> <geoRect left="120.5576" bottom="40.7754" right="128.5576" top="42.7754" /> <geoRect left="117.5576" bottom="25.7754" right="120.5576" top="26.7754" /> <geoRect left="85.4858" bottom="47.7754" right="90.1507" top="48.7754" /> <geoRect left="127.5576" bottom="49.7754" right="128.5576" top="50.7754" /> <geoRect left="78.5576" bottom="30.7754" right="79.5576" top="36.7754" /> <geoRect left="97.5576" bottom="23.7754" right="98.5576" top="28.7754" /> <geoRect left="117.5576" bottom="26.7754" right="121.5576" top="27.7754" /> <geoRect left="98.5576" bottom="22.7754" right="117.5576" top="29.7754" /> <geoRect left="99.5576" bottom="20.7754" right="102.5576" top="21.7754" /> <geoRect left="110.3934" bottom="42.7754" right="111.5576" top="44.7820" /> <geoRect left="73.5576" bottom="36.7754" right="79.5576" top="40.7754" /> <geoRect left="118.4027" bottom="49.7754" right="119.5576" top="50.9802" /> <geoRect left="119.5576" bottom="25.1912" right="119.9120" top="25.7754" /> <geoRect left="84.5576" bottom="27.7754" right="93.5576" top="28.7754" /> <geoRect left="108.5576" bottom="17.7754" right="110.5576" top="18.7754" /> <geoRect left="118.5576" bottom="24.5027" right="118.8161" top="24.7754" /> <geoRect left="119.9835" bottom="52.7754" right="126.1939" top="53.5719" /> <geoRect left="78.3965" bottom="32.2241" right="78.5576" top="32.6363" /> <geoRect left="120.5576" bottom="35.7754" right="121.5576" top="38.7754" /> <geoRect left="76.5576" bottom="40.7754" right="79.5576" top="41.7754" /> <geoRect left="115.5576" bottom="42.7754" right="131.5576" top="49.7754" /> <geoRect left="131.5576" bottom="44.8404" right="134.8631" top="48.4334" />
Map Tile API Developer's Guide 337► API Reference
<geoRect left="115.4373" bottom="47.9285" right="115.5576" top="48.2230" /> <geoRect left="82.3630" bottom="45.7754" right="82.5576" top="46.2212" /> <geoRect left="82.5576" bottom="45.7754" right="91.5576" top="47.7754" /> <geoRect left="128.5576" bottom="41.7754" right="131.5576" top="42.7754" /> <geoRect left="119.5576" bottom="49.7754" right="127.5576" top="52.7754" /> <geoRect left="77.1449" bottom="35.4169" right="78.5576" top="35.7754" /> <geoRect left="88.7706" bottom="27.2614" right="89.2653" top="27.7754" /> <geoRect left="96.2409" bottom="28.2004" right="97.5576" top="28.7754" /> <geoRect left="120.5576" bottom="39.7754" right="126.5576" top="40.7754" /> </area> <area name="France"> <geoRect left="7.4449" bottom="43.9532" right="7.7612" top="44.1819" /> <geoRect left="-2.0366" bottom="48.7889" right="2.7484" top="51.1937" /> <geoRect left="6.2593" bottom="44.8560" right="7.2498" top="45.8136" /> <geoRect left="6.6907" bottom="44.5968" right="7.1016" top="45.0132" /> <geoRect left="0.3773" bottom="42.2486" right="6.8232" top="46.1891" /> <geoRect left="6.8518" bottom="45.7944" right="7.1168" top="46.1046" /> <geoRect left="-5.2986" bottom="46.5120" right="-2.1006" top="48.9033" /> <geoRect left="7.1095" bottom="47.3484" right="7.8910" top="48.6757" /> <geoRect left="5.9584" bottom="45.8114" right="6.9032" top="46.5615" /> <geoRect left="8.4823" bottom="41.3454" right="9.6779" top="43.1241" /> <geoRect left="-2.1077" bottom="42.5367" right="2.1618" top="46.5120" /> <geoRect left="6.1405" bottom="46.5513" right="7.0066" top="47.3535" /> <geoRect left="-2.1077" bottom="45.8812" right="6.7118" top="48.9033" /> <geoRect left="6.3526" bottom="47.2548" right="7.5496" top="48.6954" /> <geoRect left="2.4444" bottom="48.6676" right="8.2326" top="51.1937" /> <geoRect left="4.3116" bottom="42.8343" right="7.6780" top="45.2796" /> </area> <area name="Austria"> <geoRect left="12.7411" bottom="47.8668" right="12.9642" top="48.2248" /> <geoRect left="16.3752" bottom="48.7534" right="16.7250" top="48.8317" /> <geoRect left="12.6822" bottom="46.5375" right="13.3457" top="46.6390" /> <geoRect left="10.4415" bottom="46.8181" right="10.6752" top="46.9033" /> <geoRect left="12.9642" bottom="47.6962" right="13.3457" top="48.2248" /> <geoRect left="13.3457" bottom="46.3748" right="14.8717" top="46.6390" /> <geoRect left="11.0567" bottom="46.7953" right="11.1249" top="46.9033" /> <geoRect left="14.8717" bottom="48.7534" right="16.0162" top="49.0177" /> <geoRect left="12.9642" bottom="48.2248" right="13.3457" top="48.3571" /> <geoRect left="13.3457" bottom="47.6962" right="17.1607" top="48.7534" /> <geoRect left="9.9561" bottom="46.8219" right="10.2682" top="46.9033" /> <geoRect left="12.2012" bottom="46.6390" right="16.0162" top="46.9033" /> <geoRect left="12.8955" bottom="47.6962" right="12.9642" top="47.8109" /> <geoRect left="10.6752" bottom="46.6390" right="11.0567" top="46.9033" /> <geoRect left="9.5307" bottom="46.9033" right="16.7792" top="47.6962" /> <geoRect left="16.0162" bottom="46.8266" right="16.1893" top="46.9033" /> </area> <area name="Latvia"> <geoRect left="24.1704" bottom="55.3689" right="28.4487" top="58.1269" /> <geoRect left="21.6724" bottom="56.3085" right="23.3336" top="57.8204" /> <geoRect left="20.7407" bottom="55.9347" right="21.8250" top="57.7144" /> <geoRect left="23.0950" bottom="56.1948" right="24.2779" top="57.2653" /> </area> <area name="Mozambique"> <geoRect left="34.9389" bottom="-18.8084" right="41.2432" top="-15.0611" /> <geoRect left="30.1219" bottom="-16.0985" right="33.7148" top="-13.9704" /> <geoRect left="31.1878" bottom="-22.9890" right="36.5975" top="-18.8084" /> <geoRect left="33.6194" bottom="-15.9653" right="41.2432" top="-10.3973" /> <geoRect left="31.8425" bottom="-18.8203" right="36.5975" top="-15.6508" /> <geoRect left="31.1878" bottom="-26.8763" right="35.7659" top="-22.4084" /> <geoRect left="34.2964" bottom="-24.9908" right="35.6707" top="-23.3847" /> <geoRect left="30.7148" bottom="-16.3417" right="34.9419" top="-14.0950" /> <geoRect left="38.6588" bottom="-17.1457" right="40.2757" top="-15.8415" /> </area> <area name="Ukraine"> <geoRect left="28.1410" bottom="44.9794" right="29.5592" top="46.8240" /> <geoRect left="38.4346" bottom="47.4754" right="40.3587" top="50.1112" /> <geoRect left="23.7808" bottom="47.7796" right="30.3909" top="52.3053" /> <geoRect left="30.3873" bottom="45.8550" right="37.3686" top="51.8685" /> <geoRect left="23.0400" bottom="47.9979" right="23.1187" top="48.0552" /> <geoRect left="34.6660" bottom="50.7773" right="35.5437" top="51.2858" />
Map Tile API Developer's Guide 338► API Reference
<geoRect left="23.6071" bottom="47.7796" right="25.5225" top="50.6001" /> <geoRect left="29.5592" bottom="44.0324" right="37.3686" top="46.3547" /> <geoRect left="29.0356" bottom="44.9794" right="30.3873" top="47.9080" /> <geoRect left="23.4548" bottom="50.5207" right="24.4370" top="51.7557" /> <geoRect left="34.3051" bottom="51.6941" right="34.4588" top="51.9267" /> <geoRect left="30.5067" bottom="51.7797" right="34.3366" top="52.4699" /> <geoRect left="34.8806" bottom="46.3547" right="38.6386" top="50.8793" /> <geoRect left="23.1767" bottom="47.9624" right="23.5211" top="48.1330" /> <geoRect left="22.1323" bottom="48.3302" right="22.5012" top="49.0508" /> <geoRect left="22.4364" bottom="47.9128" right="23.9830" top="50.5207" /> <geoRect left="22.1347" bottom="47.9209" right="23.2256" top="48.5886" /> <geoRect left="24.7422" bottom="47.7060" right="25.2039" top="47.8394" /> </area> <area name="Lithuania"> <geoRect left="25.2612" bottom="54.0863" right="25.9464" top="54.5213" /> <geoRect left="22.4807" bottom="53.8757" right="24.5276" top="55.1024" /> <geoRect left="22.6378" bottom="54.2630" right="23.1253" top="54.6908" /> <geoRect left="20.8924" bottom="54.9394" right="23.4230" top="56.5027" /> <geoRect left="22.5790" bottom="53.8579" right="24.9113" top="56.5027" /> <geoRect left="24.5937" bottom="53.8579" right="26.8994" top="56.4848" /> </area> <area name="Guadeloupe"> <geoRect left="-61.9309" bottom="15.6985" right="-61.0013" top="16.5953" /> </area> <area name="Israel"> <geoRect left="35.5239" bottom="32.9351" right="35.9089" top="33.3538" /> <geoRect left="34.2346" bottom="29.3724" right="35.4573" top="31.5477" /> <geoRect left="35.0912" bottom="32.6825" right="35.7566" top="33.1130" /> <geoRect left="35.3798" bottom="32.7247" right="35.9089" top="33.1257" /> <geoRect left="34.4766" bottom="30.9701" right="35.6655" top="33.1256" /> </area> <area name="Sweden"> <geoRect left="10.7702" bottom="55.2659" right="17.3803" top="62.8658" /> <geoRect left="17.3803" bottom="58.0209" right="19.7075" top="62.5323" /> <geoRect left="17.7151" bottom="56.8124" right="19.8137" top="58.4792" /> <geoRect left="13.7838" bottom="55.2659" right="17.4660" top="58.0209" /> <geoRect left="11.5126" bottom="58.0209" right="17.4803" top="64.3169" /> <geoRect left="15.7813" bottom="62.5323" right="25.2754" top="69.3138" /> <geoRect left="12.3680" bottom="55.1529" right="13.7838" top="56.6521" /> <geoRect left="13.0830" bottom="60.9048" right="18.3797" top="68.0183" /> </area> <area name="Slovenia"> <geoRect left="15.9891" bottom="46.3859" right="16.6217" top="46.8915" /> <geoRect left="13.7142" bottom="45.4520" right="16.3044" top="46.8284" /> <geoRect left="13.5675" bottom="45.4418" right="13.6734" top="45.5366" /> <geoRect left="13.6570" bottom="45.4125" right="13.9833" top="45.6003" /> <geoRect left="14.0533" bottom="45.4543" right="14.6924" top="45.7004" /> <geoRect left="14.6795" bottom="45.5239" right="14.7057" top="45.5557" /> <geoRect left="14.5931" bottom="45.5557" right="15.7955" top="46.1463" /> <geoRect left="15.9827" bottom="46.8276" right="16.2706" top="46.8786" /> <geoRect left="13.5988" bottom="45.5318" right="13.6380" top="45.5394" /> <geoRect left="13.3628" bottom="45.5366" right="13.9372" top="46.5230" /> <geoRect left="14.6924" bottom="45.3439" right="15.4262" top="45.7418" /> </area> <area name="Martinique"> <geoRect left="-61.2546" bottom="14.3135" right="-60.7258" top="14.9680" /> </area> <area name="Guatemala"> <geoRect left="-89.0225" bottom="14.9642" right="-88.2215" top="16.1868" /> <geoRect left="-91.8261" bottom="13.7417" right="-89.8235" top="14.1492" /> <geoRect left="-90.6686" bottom="16.4730" right="-90.6245" top="16.5943" /> <geoRect left="-89.8235" bottom="14.0259" right="-89.6796" top="14.1492" /> <geoRect left="-90.6245" bottom="14.1492" right="-89.0225" top="16.5943" /> <geoRect left="-91.4256" bottom="16.5943" right="-89.0225" top="17.8168" /> <geoRect left="-92.2266" bottom="14.1492" right="-90.6245" top="16.1868" /> </area> <area name="United Kingdom"> <geoRect left="-2.2141" bottom="59.6771" right="-0.2247" top="60.8451" /> <geoRect left="-5.3731" bottom="51.5011" right="-5.1981" top="52.6691" /> <geoRect left="-8.1821" bottom="53.8371" right="-1.2194" top="59.6771" />
Map Tile API Developer's Guide 339► API Reference
<geoRect left="-5.1981" bottom="50.3331" right="-1.2194" top="53.8371" /> <geoRect left="-1.2194" bottom="50.3331" right="1.7646" top="55.0051" /> <geoRect left="-7.9476" bottom="49.1651" right="-1.9796" top="50.3331" /> </area> <area name="Spain"> <geoRect left="-9.7829" bottom="41.6479" right="-6.3517" top="43.8119" /> <geoRect left="-6.8623" bottom="37.3120" right="0.2290" top="39.3980" /> <geoRect left="3.0662" bottom="38.2202" right="5.1739" top="40.2854" /> <geoRect left="-7.5399" bottom="36.8976" right="-6.5372" top="41.6961" /> <geoRect left="-7.6437" bottom="39.3438" right="-7.2643" top="39.7836" /> <geoRect left="-2.9815" bottom="35.2569" right="-2.9161" top="35.3232" /> <geoRect left="-7.0220" bottom="35.6142" right="-1.2109" top="37.9317" /> <geoRect left="-18.2990" bottom="27.4138" right="-13.2707" top="29.4228" /> <geoRect left="-5.3870" bottom="35.8628" right="-5.2772" top="35.9199" /> <geoRect left="-6.7340" bottom="38.4150" right="3.4915" top="43.7683" /> <geoRect left="-18.2990" bottom="27.4138" right="-13.2707" top="29.4228" /> </area> <area name="Nicaragua"> <geoRect left="-85.4570" bottom="14.1788" right="-83.8745" top="14.8768" /> <geoRect left="-85.8099" bottom="10.6629" right="-83.3936" top="12.9543" /> <geoRect left="-82.9224" bottom="14.2095" right="-82.6012" top="14.5307" /> <geoRect left="-87.1376" bottom="11.0412" right="-83.1509" top="14.6525" /> <geoRect left="-87.8420" bottom="12.3118" right="-84.9162" top="14.2011" /> <geoRect left="-85.8103" bottom="13.6161" right="-83.0464" top="15.1814" /> </area> <area name="Germany"> <geoRect left="13.2064" bottom="54.2771" right="14.1232" top="55.0556" /> <geoRect left="6.7881" bottom="51.9414" right="7.7050" top="53.8624" /> <geoRect left="7.7050" bottom="47.2702" right="13.2064" top="55.0556" /> <geoRect left="13.2064" bottom="48.0487" right="13.9895" top="49.6058" /> <geoRect left="13.2064" bottom="50.3844" right="15.0401" top="54.2771" /> <geoRect left="5.8712" bottom="48.8273" right="7.7050" top="51.9414" /> </area> <area name="Croatia"> <geoRect left="13.3057" bottom="44.1837" right="15.8226" top="45.5704" /> <geoRect left="13.8789" bottom="44.8976" right="18.1295" top="46.5835" /> <geoRect left="14.4853" bottom="42.1231" right="18.6541" top="44.8976" /> <geoRect left="15.6655" bottom="42.5705" right="17.0432" top="43.3251" /> <geoRect left="16.5981" bottom="44.8126" right="19.5169" top="45.7845" /> <geoRect left="16.1850" bottom="44.9955" right="16.4761" top="45.1490" /> <geoRect left="18.1216" bottom="45.4199" right="19.1392" top="45.9726" /> </area> <area name="Italy"> <geoRect left="16.0831" bottom="39.6269" right="18.8269" top="42.3234" /> <geoRect left="12.8285" bottom="45.5627" right="13.9860" top="46.6783" /> <geoRect left="11.8869" bottom="36.6566" right="12.1816" top="36.8801" /> <geoRect left="6.6130" bottom="44.1083" right="7.2468" top="45.2558" /> <geoRect left="13.5406" bottom="39.2141" right="16.4857" top="43.0524" /> <geoRect left="6.8008" bottom="45.6248" right="6.9794" top="45.8575" /> <geoRect left="13.3581" bottom="42.6396" right="14.0461" top="43.6743" /> <geoRect left="10.3931" bottom="46.7941" right="11.6257" top="47.0561" /> <geoRect left="11.8034" bottom="35.3758" right="19.4309" top="40.0397" /> <geoRect left="6.8824" bottom="38.1821" right="14.1446" top="47.2069" /> </area> <area name="Greece"> <geoRect left="20.3320" bottom="38.1449" right="20.3984" top="38.3325" /> <geoRect left="20.3974" bottom="34.8037" right="26.5331" top="41.0512" /> <geoRect left="22.8393" bottom="41.0512" right="24.4931" top="41.6370" /> <geoRect left="26.5331" bottom="38.9765" right="26.6201" top="39.1817" /> <geoRect left="21.9014" bottom="41.0512" right="22.4426" top="41.1740" /> <geoRect left="29.5552" bottom="36.1209" right="29.6034" top="36.1723" /> <geoRect left="24.4883" bottom="41.0512" right="26.5489" top="41.8654" /> <geoRect left="22.4426" bottom="41.0512" right="22.8625" top="41.3788" /> <geoRect left="19.3748" bottom="38.9687" right="20.3974" top="40.3571" /> <geoRect left="26.5331" bottom="35.1058" right="28.2956" top="37.9255" /> <geoRect left="26.5380" bottom="41.2829" right="26.6501" top="41.6486" /> </area> <area name="Microsoft"> <geoRect left="-3.3866" bottom="59.0000" right="-3.0000" top="59.3848" /> <geoRect left="-9.0000" bottom="43.0000" right="-1.4871" top="43.8368" />
Map Tile API Developer's Guide 340► API Reference
<geoRect left="17.0000" bottom="47.6659" right="17.1796" top="48.1870" /> <geoRect left="-3.0000" bottom="49.0000" right="7.0000" top="53.0000" /> <geoRect left="-83.0000" bottom="25.0000" right="-80.0000" top="43.0000" /> <geoRect left="15.0000" bottom="54.9700" right="15.2079" top="55.4090" /> <geoRect left="16.9798" bottom="58.8191" right="19.3105" top="60.0219" /> <geoRect left="-95.1748" bottom="49.0000" right="-94.7155" top="49.4171" /> <geoRect left="-81.8753" bottom="24.4342" right="-80.0000" top="25.0000" /> <geoRect left="-3.0000" bottom="53.0000" right="-1.0000" top="61.0000" /> <geoRect left="13.0000" bottom="51.0000" right="15.0000" top="57.0000" /> <geoRect left="23.9754" bottom="59.8274" right="26.0308" top="61.0338" /> <geoRect left="-77.0000" bottom="43.0000" right="-71.4874" top="45.1041" /> <geoRect left="-70.7166" bottom="45.9934" right="-67.7111" top="47.5037" /> <geoRect left="15.0000" bottom="51.1463" right="15.0019" top="51.1538" /> <geoRect left="-86.0000" bottom="28.0000" right="-83.0000" top="49.0000" /> <geoRect left="-125.0000" bottom="37.0000" right="-86.0000" top="49.0000" /> <geoRect left="3.0000" bottom="41.7315" right="3.3548" top="43.0000" /> <geoRect left="13.0000" bottom="45.5418" right="13.9644" top="47.0000" /> <geoRect left="4.6555" bottom="53.0000" right="7.0000" top="53.7627" /> <geoRect left="8.3413" bottom="38.8500" right="9.0932" top="39.0000" /> <geoRect left="-80.0000" bottom="34.0000" right="-74.0000" top="43.0000" /> <geoRect left="-1.0000" bottom="43.0000" right="7.0000" top="49.0000" /> <geoRect left="-105.6275" bottom="29.2540" right="-104.0000" top="31.0000" /> <geoRect left="-11.0000" bottom="49.0000" right="-3.0000" top="59.0000" /> <geoRect left="13.0000" bottom="50.4136" right="14.4285" top="51.0000" /> <geoRect left="-8.0082" bottom="36.9570" right="-7.8011" top="37.0000" /> <geoRect left="17.0000" bottom="38.8376" right="17.2421" top="39.5206" /> <geoRect left="13.0000" bottom="47.0000" right="17.0000" top="49.0000" /> <geoRect left="13.0000" bottom="43.0000" right="13.8986" top="43.8815" /> <geoRect left="17.0000" bottom="39.6609" right="18.6364" top="41.1153" /> <geoRect left="-79.1238" bottom="43.0000" right="-76.7251" top="43.5219" /> <geoRect left="13.3861" bottom="46.2245" right="16.5913" top="47.0000" /> <geoRect left="1.1578" bottom="38.4332" right="4.6176" top="40.4985" /> <geoRect left="-1.0000" bottom="53.0000" right="0.5000" top="54.7773" /> <geoRect left="-9.3240" bottom="42.9741" right="-8.9859" top="43.3001" /> <geoRect left="-9.5302" bottom="38.2126" right="-9.0000" top="39.9011" /> <geoRect left="-5.1628" bottom="48.3914" right="-5.0000" top="48.5056" /> <geoRect left="-6.6631" bottom="35.9238" right="-1.8450" top="37.0000" /> <geoRect left="15.0000" bottom="51.1642" right="15.0580" top="51.3263" /> <geoRect left="-100.1176" bottom="25.6957" right="-96.8387" top="28.0000" /> <geoRect left="-74.0000" bottom="40.0000" right="-68.0000" top="43.0000" /> <geoRect left="-80.0000" bottom="32.5516" right="-77.7120" top="34.0000" /> <geoRect left="14.5069" bottom="50.8137" right="14.9382" top="51.0000" /> <geoRect left="13.0000" bottom="37.0000" right="17.0000" top="43.0000" /> <geoRect left="-83.0000" bottom="43.0000" right="-82.3613" top="44.1708" /> <geoRect left="-1.0000" bottom="60.2720" right="-0.7110" top="60.8841" /> <geoRect left="-8.9533" bottom="36.9926" right="-8.9311" top="37.0000" /> <geoRect left="-5.0000" bottom="47.0000" right="-1.0000" top="49.0000" /> <geoRect left="12.0022" bottom="37.4381" right="13.0000" top="38.2529" /> <geoRect left="-9.0000" bottom="37.0000" right="1.0000" top="43.0000" /> <geoRect left="1.0000" bottom="41.0000" right="3.0000" top="43.0000" /> <geoRect left="-122.0000" bottom="31.0000" right="-86.0000" top="37.0000" /> <geoRect left="7.0000" bottom="39.0000" right="13.0000" top="61.0000" /> <geoRect left="13.0000" bottom="49.0000" right="13.4222" top="49.3287" /> <geoRect left="11.8529" bottom="35.4007" right="14.7297" top="37.0069" /> <geoRect left="-68.0009" bottom="44.3159" right="-66.8902" top="45.9940" /> <geoRect left="-1.5690" bottom="43.0000" right="-1.0000" top="46.2402" /> <geoRect left="-9.3240" bottom="42.4435" right="-9.0000" top="43.0000" /> <geoRect left="-2.6007" bottom="46.2340" right="-1.0000" top="47.0000" /> <geoRect left="-71.5231" bottom="43.0000" right="-68.0000" top="46.0000" /> <geoRect left="-104.0000" bottom="28.0000" right="-86.0000" top="31.0000" /> <geoRect left="14.3209" bottom="36.6258" right="15.2989" top="37.0000" /> </area> <area name="Nepal"> <geoRect left="81.0976" bottom="27.3853" right="83.8816" top="30.1502" /> <geoRect left="81.3961" bottom="30.1502" right="82.2540" top="30.4719" /> <geoRect left="81.6782" bottom="27.4329" right="82.8798" top="27.9426" /> <geoRect left="79.7937" bottom="28.2854" right="82.2540" top="30.6642" /> <geoRect left="83.0964" bottom="26.4858" right="85.7994" top="29.4459" /> <geoRect left="85.5710" bottom="26.2669" right="88.2408" top="28.4465" /> </area>
Map Tile API Developer's Guide 341► API Reference
<area name="Réunion"> <geoRect left="55.1479" bottom="-21.4740" right="55.9393" top="-20.7728" /> </area> <area name="Mexico"> <geoRect left="-103.0000" bottom="28.0000" right="-101.0000" top="30.0000" /> <geoRect left="-95.0000" bottom="18.0000" right="-87.0000" top="20.0000" /> <geoRect left="-91.0000" bottom="17.4060" right="-88.7349" top="18.0000" /> <geoRect left="-101.0000" bottom="28.0000" right="-99.9666" top="29.4004" /> <geoRect left="-117.1817" bottom="32.0000" right="-113.1649" top="32.7325" /> <geoRect left="-97.9326" bottom="15.5643" right="-95.2581" top="16.0000" /> <geoRect left="-113.0000" bottom="24.0000" right="-97.0000" top="26.0000" /> <geoRect left="-91.0000" bottom="16.0000" right="-90.3434" top="16.9491" /> <geoRect left="-115.0000" bottom="18.0000" right="-109.0000" top="20.0000" /> <geoRect left="-119.0000" bottom="28.0000" right="-103.0000" top="32.0000" /> <geoRect left="-94.2111" bottom="14.4031" right="-91.0000" top="16.0000" /> <geoRect left="-117.0000" bottom="26.0000" right="-99.0000" top="28.0000" /> <geoRect left="-90.6669" bottom="20.0000" right="-86.6669" top="22.0000" /> <geoRect left="-99.0000" bottom="26.0000" right="-97.5566" top="26.4261" /> <geoRect left="-103.0000" bottom="16.0000" right="-91.0000" top="18.0000" /> <geoRect left="-111.0000" bottom="22.0000" right="-97.0000" top="24.0000" /> <geoRect left="-107.0000" bottom="18.0000" right="-95.0000" top="22.0000" /> </area> <area name="Sri Lanka"> <geoRect left="79.5067" bottom="5.8461" right="82.0121" top="9.9652" /> </area> <area name="Jordan"> <geoRect left="36.8242" bottom="31.3679" right="39.3159" top="33.3996" /> <geoRect left="35.2899" bottom="30.8890" right="37.3047" top="32.3179" /> <geoRect left="35.2899" bottom="29.2293" right="38.0203" top="31.3679" /> <geoRect left="35.4964" bottom="31.8515" right="36.8242" top="32.7823" /> <geoRect left="34.9258" bottom="29.2293" right="35.9751" top="30.8890" /> </area> </areas> <schemes> <scheme name="carnav"> <copyright zoomMin="10" zoomMax="20" area="Swaziland">Navteq</copyright> <copyright zoomMin="6" zoomMax="20" area="Australia">PSMA</copyright> <copyright zoomMin="9" zoomMax="20" area="Portugal">IgeoE</copyright> <copyright zoomMin="10" zoomMax="20" area="Israel">SOI</copyright> <copyright zoomMin="9" zoomMax="20" area="Ecuador">IGM</copyright> <copyright zoomMin="10" zoomMax="20" area="Greece">Geomatics</copyright> <copyright zoomMin="11" zoomMax="20" area="France">IGN</copyright> <copyright zoomMin="9" zoomMax="20" area="United Kingdom">OGL</copyright> <copyright zoomMin="9" zoomMax="20" area="Switzerland">Swisstopo</copyright> <copyright zoomMin="9" zoomMax="20" area="Mozambique">Cenacarta</copyright> <copyright zoomMin="11" zoomMax="20" area="Republic of Moldova">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Norway">Statkart</copyright> <copyright zoomMin="9" zoomMax="20" area="Latvia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Germany">Deutschland</copyright> <copyright zoomMin="9" zoomMax="20" area="Sri Lanka">Sri Lanka</copyright> <copyright zoomMin="9" zoomMax="20" area="Sweden">Lantmateriet</copyright> <copyright zoomMin="9" zoomMax="20" area="Italy">ITA</copyright> <copyright zoomMin="6" zoomMax="20" area="China">2014 NavInfo</copyright> <copyright zoomMin="9" zoomMax="20" area="Mexico">INEGI</copyright> <copyright zoomMin="6" zoomMax="20" area="Canada">Canada</copyright> <copyright zoomMin="11" zoomMax="20" area="Réunion">IGN</copyright> <copyright zoomMin="6" zoomMax="20" area="Iraq">Navteq</copyright> <copyright zoomMin="10" zoomMax="20" area="Croatia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Nepal">Nepal</copyright> <copyright zoomMin="9" zoomMax="20" area="Islamic Republic of Iran">2014 THTC</copyright> <copyright zoomMin="10" zoomMax="20" area="Guatemala">IGN Guatemala</copyright> <copyright zoomMin="9" zoomMax="20" area="Lithuania">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="Cyprus">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Poland">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="French Guiana">IGN</copyright> <copyright zoomMin="11" zoomMax="20" area="Guadeloupe">IGN</copyright> <copyright zoomMin="9" zoomMax="20" area="Martinique">IGN</copyright> <copyright zoomMin="10" zoomMax="20" area="Jordan">Jordan</copyright> <copyright zoomMin="9" zoomMax="20" area="Austria">BEV</copyright>
Map Tile API Developer's Guide 342► API Reference
<copyright zoomMin="10" zoomMax="20" area="Estonia">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="Nicaragua">Navteq</copyright> <copyright zoomMin="10" zoomMax="20" area="Slovenia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Ukraine">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Spain">CNIG</copyright> </scheme> <scheme name="normal"> <copyright zoomMin="10" zoomMax="20" area="Swaziland">Navteq</copyright> <copyright zoomMin="6" zoomMax="20" area="Australia">PSMA</copyright> <copyright zoomMin="9" zoomMax="20" area="Portugal">IgeoE</copyright> <copyright zoomMin="10" zoomMax="20" area="Israel">SOI</copyright> <copyright zoomMin="9" zoomMax="20" area="Ecuador">IGM</copyright> <copyright zoomMin="10" zoomMax="20" area="Greece">Geomatics</copyright> <copyright zoomMin="11" zoomMax="20" area="France">IGN</copyright> <copyright zoomMin="9" zoomMax="20" area="United Kingdom">OGL</copyright> <copyright zoomMin="9" zoomMax="20" area="Switzerland">Swisstopo</copyright> <copyright zoomMin="9" zoomMax="20" area="Mozambique">Cenacarta</copyright> <copyright zoomMin="11" zoomMax="20" area="Republic of Moldova">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Norway">Statkart</copyright> <copyright zoomMin="9" zoomMax="20" area="Latvia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Germany">Deutschland</copyright> <copyright zoomMin="9" zoomMax="20" area="Sri Lanka">Sri Lanka</copyright> <copyright zoomMin="9" zoomMax="20" area="Sweden">Lantmateriet</copyright> <copyright zoomMin="9" zoomMax="20" area="Italy">ITA</copyright> <copyright zoomMin="6" zoomMax="20" area="China">2014 NavInfo</copyright> <copyright zoomMin="9" zoomMax="20" area="Mexico">INEGI</copyright> <copyright zoomMin="6" zoomMax="20" area="Canada">Canada</copyright> <copyright zoomMin="11" zoomMax="20" area="Réunion">IGN</copyright> <copyright zoomMin="6" zoomMax="20" area="Iraq">Navteq</copyright> <copyright zoomMin="10" zoomMax="20" area="Croatia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Nepal">Nepal</copyright> <copyright zoomMin="9" zoomMax="20" area="Islamic Republic of Iran">2014 THTC</copyright> <copyright zoomMin="10" zoomMax="20" area="Guatemala">IGN Guatemala</copyright> <copyright zoomMin="9" zoomMax="20" area="Lithuania">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="Cyprus">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Poland">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="French Guiana">IGN</copyright> <copyright zoomMin="11" zoomMax="20" area="Guadeloupe">IGN</copyright> <copyright zoomMin="9" zoomMax="20" area="Martinique">IGN</copyright> <copyright zoomMin="10" zoomMax="20" area="Jordan">Jordan</copyright> <copyright zoomMin="9" zoomMax="20" area="Austria">BEV</copyright> <copyright zoomMin="10" zoomMax="20" area="Estonia">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="Nicaragua">Navteq</copyright> <copyright zoomMin="10" zoomMax="20" area="Slovenia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Ukraine">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Spain">CNIG</copyright> </scheme> <scheme name="pedestrian"> <copyright zoomMin="10" zoomMax="20" area="Swaziland">Navteq</copyright> <copyright zoomMin="6" zoomMax="20" area="Australia">PSMA</copyright> <copyright zoomMin="9" zoomMax="20" area="Portugal">IgeoE</copyright> <copyright zoomMin="10" zoomMax="20" area="Israel">SOI</copyright> <copyright zoomMin="9" zoomMax="20" area="Ecuador">IGM</copyright> <copyright zoomMin="10" zoomMax="20" area="Greece">Geomatics</copyright> <copyright zoomMin="11" zoomMax="20" area="France">IGN</copyright> <copyright zoomMin="9" zoomMax="20" area="United Kingdom">OGL</copyright> <copyright zoomMin="9" zoomMax="20" area="Switzerland">Swisstopo</copyright> <copyright zoomMin="9" zoomMax="20" area="Mozambique">Cenacarta</copyright> <copyright zoomMin="11" zoomMax="20" area="Republic of Moldova">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Norway">Statkart</copyright> <copyright zoomMin="9" zoomMax="20" area="Latvia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Germany">Deutschland</copyright> <copyright zoomMin="9" zoomMax="20" area="Sri Lanka">Sri Lanka</copyright> <copyright zoomMin="9" zoomMax="20" area="Sweden">Lantmateriet</copyright> <copyright zoomMin="9" zoomMax="20" area="Italy">ITA</copyright> <copyright zoomMin="6" zoomMax="20" area="China">2014 NavInfo</copyright> <copyright zoomMin="9" zoomMax="20" area="Mexico">INEGI</copyright> <copyright zoomMin="6" zoomMax="20" area="Canada">Canada</copyright>
Map Tile API Developer's Guide 343► API Reference
<copyright zoomMin="11" zoomMax="20" area="Réunion">IGN</copyright> <copyright zoomMin="6" zoomMax="20" area="Iraq">Navteq</copyright> <copyright zoomMin="10" zoomMax="20" area="Croatia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Nepal">Nepal</copyright> <copyright zoomMin="9" zoomMax="20" area="Islamic Republic of Iran">2014 THTC</copyright> <copyright zoomMin="10" zoomMax="20" area="Guatemala">IGN Guatemala</copyright> <copyright zoomMin="9" zoomMax="20" area="Lithuania">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="Cyprus">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Poland">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="French Guiana">IGN</copyright> <copyright zoomMin="11" zoomMax="20" area="Guadeloupe">IGN</copyright> <copyright zoomMin="9" zoomMax="20" area="Martinique">IGN</copyright> <copyright zoomMin="10" zoomMax="20" area="Jordan">Jordan</copyright> <copyright zoomMin="9" zoomMax="20" area="Austria">BEV</copyright> <copyright zoomMin="10" zoomMax="20" area="Estonia">EuroGeographics</copyright> <copyright zoomMin="10" zoomMax="20" area="Nicaragua">Navteq</copyright> <copyright zoomMin="10" zoomMax="20" area="Slovenia">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Ukraine">EuroGeographics</copyright> <copyright zoomMin="9" zoomMax="20" area="Spain">CNIG</copyright> </scheme> </schemes></copyrights>
This XML response contains the following elements:
Table 110: Response elements
Element Description
provider The map provider name with the following description elements:
text: copyright text to display after the copyright symbol on the map.
full: verbose copyright text of the label to display by mouse over label or info menu entry.
link: link to the map provider website.
icon: logo of the map provider that can be optionally added to the map. Specified by the URL
(src), dimensions (width, height) and the mimetype.
area The name, size and shape of a geographical area with a particular copyright. The area is specified by
geoRect: The bounding boxes (bottom - latitude, left - longitude, top - latitude, right -
longitude).
scheme The view schemes and corresponding copyrights are defined here.
copyright: Map provider or list of providers for a particular view scheme. Copyrights are defined
by the given geographical area and the relevant zoom level range (zoomMin, zoomMax). The default
copyright is the one that has no geographical restriction and is therefore valid for all other areas.
All relevant copyrights of the map view must be displayed. Different areas may contribute by
overriding or adding to the copyright text depending on whether the view is contained completely
within one of these areas or overlaps partially one or more of them. If there are parts of several
areas in the view, check the composite list of providers to avoiding duplicate entries with the
different copyright data.
For example, using a hybrid.day view scheme, the default copyright will be shown and then all the
relevant ones that are inside of the area of the bounding box currently being displayed.
Map Tile API Developer's Guide 344► API Reference
Example Copyright Response in JSON
In the example below, the request for copyright information does not indicate the output format.
http://1.base.maps.cit.api.here.com/maptile/2.1/copyright/newest?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
Example Copyright Response in XML
The default output format is JSON and this is the format delivered by the response to the above
request:
{ "carnav": [ { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [-27.3403, 31.4364, -26.7719, 32.0286], [-27.0738, 30.7201, -26.2624, 31.5422], [-26.8455, 32.0275, -26.7719, 32.1475], [-26.8359, 30.8723, -25.6938, 32.1739] ] }, { "minLevel": 6, "maxLevel": 20, "label": "PSMA", "alt": "Copyright. Based on data provided under license from PSMA Australia Limited. Product incorporates data which is 2014 Telstra Corporation Limited, GM Holden Limited, Intelematics Australia Pty Ltd, HERE International LLC, Sentinel Content Pty Limited and Continental Pty Ltd", "boxes": [ [-32.0000, 113.0000, -20.0000, 151.0000], [-14.0000, 141.0000, -8.0000, 145.0000], [-30.0761, 167.0381, -28.0761, 169.0381], [-14.0000, 129.0000, -10.0000, 137.0000], [-38.0000, 135.0000, -32.0000, 151.0000], [-34.0000, 151.0000, -24.0000, 155.0000], [-34.0000, 127.0000, -32.0000, 135.0000], [-13.1672, 95.8626, -11.1672, 97.8626], [-20.0000, 123.0000, -14.0000, 147.0000], [-11.5539, 104.6728, -9.5539, 106.6728], [-44.0000, 141.0000, -38.0000, 149.0000], [-36.0000, 115.0000, -32.0000, 127.0000], [-20.0000, 121.0000, -16.0000, 123.0000] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IgeoE", "alt": "IgeoE - Portugal", "boxes": [ [39.3941, -7.5899, 39.6663, -6.9850],
Map Tile API Developer's Guide 345► API Reference
[40.9842, -7.3532, 41.2705, -6.5519], [36.5482, -32.0392, 40.4124, -23.6635], [32.2747, -17.3686, 33.1907, -15.9142], [41.7211, -7.2357, 42.0048, -6.5050], [39.6540, -7.5520, 40.2572, -6.7565], [36.9392, -9.0081, 38.4418, -7.2449], [39.4153, -8.4431, 41.9675, -7.2126], [37.9667, -7.2522, 38.3853, -6.8808], [38.4418, -8.9260, 39.5144, -6.7321], [30.1318, -15.8830, 30.1622, -15.8445], [39.4801, -9.1848, 42.1722, -7.8729], [38.1864, -9.5593, 39.5271, -8.8950], [40.1168, -7.4841, 40.9984, -6.7565], [41.2304, -7.3100, 41.7633, -6.5183] ] }, { "minLevel": 10, "maxLevel": 20, "label": "SOI", "alt": "Survey of Israel data source", "boxes": [ [29.3724, 34.2346, 31.5477, 35.4573], [32.6825, 35.0912, 33.1130, 35.7566], [32.7247, 35.3798, 33.1257, 35.9089], [30.9701, 34.4766, 33.1256, 35.6655] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGM", "alt": "INSTITUTO GEOGRAFICO MILITAR DEL ECUADOR AUTORIZACION No IGM-2011-01- PCO-01 DEL 25 DE ENERO DE 2011", "boxes": [ [0.4963, -78.4796, 0.8202, -77.2440], [-2.4189, -76.4202, -2.0950, -76.0083], [-2.7428, -80.9509, 1.1441, -80.5390], [-4.6863, -80.5390, 1.1441, -78.4796], [-3.0667, -78.0677, -2.7428, -77.2440], [-2.0950, -78.4796, 0.4963, -75.5964], [-1.4472, -75.5964, 0.1724, -75.1846], [-2.7428, -81.3628, -0.7994, -80.9509], [-3.7146, -78.4796, -2.0950, -78.0677], [-5.0102, -79.7153, -4.6863, -78.8915], [-2.7428, -78.0677, -2.0950, -76.4202], [1.1441, -79.3034, 1.4680, -78.4796] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Geomatics", "alt": "Copyright Geomatics Ltd.", "boxes": [ [34.8037, 20.3974, 41.0512, 26.5331], [41.0512, 22.8393, 41.6370, 24.4931], [38.9765, 26.5331, 39.1817, 26.6201], [41.0512, 21.9014, 41.1740, 22.4426], [36.1209, 29.5552, 36.1723, 29.6034], [41.0512, 24.4883, 41.8654, 26.5489], [41.0512, 22.4426, 41.3788, 22.8625], [38.9687, 19.3748, 40.3571, 20.3974], [35.1058, 26.5331, 37.9255, 28.2956], [41.2829, 26.5380, 41.6486, 26.6501] ] },
Map Tile API Developer's Guide 346► API Reference
{ "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN France 2009 BD TOPO", "boxes": [ [48.7889, -2.0366, 51.1937, 2.7484], [44.8560, 6.2593, 45.8136, 7.2498], [44.5968, 6.6907, 45.0132, 7.1016], [42.2486, 0.3773, 46.1891, 6.8232], [45.7944, 6.8518, 46.1046, 7.1168], [46.5120, -5.2986, 48.9033, -2.1006], [47.3484, 7.1095, 48.6757, 7.8910], [45.8114, 5.9584, 46.5615, 6.9032], [41.3454, 8.4823, 43.1241, 9.6779], [42.5367, -2.1077, 46.5120, 2.1618], [46.5513, 6.1405, 47.3535, 7.0066], [45.8812, -2.1077, 48.9033, 6.7118], [47.2548, 6.3526, 48.6954, 7.5496], [48.6676, 2.4444, 51.1937, 8.2326], [42.8343, 4.3116, 45.2796, 7.6780] ] }, { "minLevel": 9, "maxLevel": 20, "label": "OGL", "alt": "Open Government Licence v.1.0.", "boxes": [ [51.5011, -5.3731, 52.6691, -5.1981], [53.8371, -8.1821, 59.6771, -1.2194], [50.3331, -5.1981, 53.8371, -1.2194], [50.3331, -1.2194, 55.0051, 1.7646], [49.1651, -7.9476, 50.3331, -1.9796] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Swisstopo", "alt": "Topografische Grundlage: copyright Bundesamt fur Landestopographie", "boxes": [ [45.8206, 6.8641, 47.4100, 7.3171], [47.4100, 6.9280, 47.5272, 7.3171], [47.2863, 9.5821, 47.5004, 9.6893], [46.0972, 8.5106, 46.2180, 8.6761], [46.0193, 8.6761, 46.2180, 9.1291], [45.7831, 8.7540, 46.0193, 9.1167], [46.2703, 9.4435, 46.4166, 9.8658], [46.4166, 6.4111, 47.0127, 6.8641], [46.2180, 8.2231, 46.4166, 9.1291], [46.5237, 10.2370, 46.6153, 10.4882], [46.2131, 10.0449, 46.2643, 10.1820], [46.1195, 5.9453, 46.2180, 6.3156], [47.0127, 9.5821, 47.0721, 9.9106], [46.6153, 9.5821, 47.0127, 10.4882], [47.6087, 8.6761, 47.8074, 9.4309], [46.4140, 10.0351, 46.6153, 10.1740], [46.4166, 9.5821, 46.6153, 10.0351], [46.1024, 6.7620, 46.4166, 6.8641], [46.4166, 7.3171, 47.6087, 9.5821], [46.3513, 9.8639, 46.4166, 10.0351], [46.6153, 6.1662, 46.7577, 6.4111], [47.0127, 6.6305, 47.1914, 6.8641], [46.3367, 10.0312, 46.4166, 10.1725], [47.6087, 8.2231, 47.8074, 8.6761], [46.1180, 9.1291, 46.4166, 9.3037],
Map Tile API Developer's Guide 347► API Reference
[46.0193, 7.3171, 46.4166, 8.2231], [45.8846, 7.3171, 46.0193, 8.0455], [46.2654, 9.9778, 46.3547, 10.0368], [46.2180, 5.9581, 46.6153, 6.4111] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Cenacarta", "alt": "Certain Data for Mozambique provided by Cenacarta 2014 by Cenacarta", "boxes": [ [-16.0985, 30.1219, -13.9704, 33.7148], [-22.9890, 31.1878, -18.8084, 36.5975], [-15.9653, 33.6194, -10.3973, 41.2432], [-18.8203, 31.8425, -15.6508, 36.5975], [-26.8763, 31.1878, -22.4084, 35.7659], [-24.9908, 34.2964, -23.3847, 35.6707], [-16.3417, 30.7148, -14.0950, 34.9419], [-17.1457, 38.6588, -15.8415, 40.2757] ] }, { "minLevel": 11, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.7302, 28.2568, 47.4471, 29.2353], [46.7892, 29.2282, 47.4471, 29.9684], [45.7302, 28.5878, 46.2901, 29.0637], [46.8530, 26.5110, 48.6163, 29.3448], [46.3002, 29.2029, 46.5592, 30.2333], [45.4102, 28.0701, 46.4249, 28.5878], [45.4154, 28.0081, 46.1325, 28.4224], [46.4187, 28.0753, 47.9267, 29.3100] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Statkart", "alt": "Copyright 2000; Norwegian Mapping Authority", "boxes": [ [68.8789, 27.8446, 71.4071, 32.1402], [68.4773, 24.6595, 71.3952, 26.3932], [61.0315, 6.1059, 70.9952, 18.0586], [66.1997, 15.2505, 67.3135, 16.3893], [63.9575, 13.0203, 65.6822, 14.7214], [69.6571, 25.9972, 71.4071, 28.8856], [59.2422, 9.9664, 63.2018, 13.0634], [56.4440, 2.9492, 63.9455, 12.0640] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [56.3085, 21.6724, 57.8204, 23.3336], [55.9347, 20.7407, 57.7144, 21.8250], [56.1948, 23.0950, 57.2653, 24.2779] ] },
Map Tile API Developer's Guide 348► API Reference
{ "minLevel": 9, "maxLevel": 20, "label": "Deutschland", "alt": "Die Grundlagendaten wurden mit Genehmigung der zustandigen Behorden entnommen", "boxes": [ [51.9414, 6.7881, 53.8624, 7.7050], [47.2702, 7.7050, 55.0556, 13.2064], [48.0487, 13.2064, 49.6058, 13.9895], [50.3844, 13.2064, 54.2771, 15.0401], [48.8273, 5.8712, 51.9414, 7.7050] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Sri Lanka", "alt": "This product incorporates original source digital data obtained from the Survey Department of Sri Lanka. 2009 Survey Department of Sri Lanka The data has been used with the permission of the Survey Department of Sri Lanka", "boxes": [ [5.8461, 79.5067, 9.9652, 82.0121] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Lantmateriet", "alt": "Based upon electronic data National Land Survey Sweden.", "boxes": [ [58.0209, 17.3803, 62.5323, 19.7075], [56.8124, 17.7151, 58.4792, 19.8137], [55.2659, 13.7838, 58.0209, 17.4660], [58.0209, 11.5126, 64.3169, 17.4803], [62.5323, 15.7813, 69.3138, 25.2754], [55.1529, 12.3680, 56.6521, 13.7838], [60.9048, 13.0830, 68.0183, 18.3797] ] }, { "minLevel": 9, "maxLevel": 20, "label": "ITA", "alt": "La Banca Dati Italiana e stata prodotta usando quale riferimento anche cartografia numerica ed al tratto prodotta e fornita dalla Regione Toscana", "boxes": [ [45.5627, 12.8285, 46.6783, 13.9860], [36.6566, 11.8869, 36.8801, 12.1816], [44.1083, 6.6130, 45.2558, 7.2468], [39.2141, 13.5406, 43.0524, 16.4857], [45.6248, 6.8008, 45.8575, 6.9794], [42.6396, 13.3581, 43.6743, 14.0461], [46.7941, 10.3931, 47.0561, 11.6257], [35.3758, 11.8034, 40.0397, 19.4309], [38.1821, 6.8824, 47.2069, 14.1446] ] }, { "minLevel": 6, "maxLevel": 20, "label": "2014 NavInfo", "alt": "copyright 2014 NavInfo Co Ltd. All Rights Reserved", "boxes": [ [20.7754, 106.5576, 22.7754, 113.5576],
Map Tile API Developer's Guide 349► API Reference
[28.6334, 93.5576, 28.7754, 94.0161], [42.7754, 111.5576, 45.7754, 115.5576], [32.7754, 120.5576, 33.5701, 120.8986], [21.7754, 113.5576, 22.7754, 116.5576], [42.7754, 79.5576, 45.7754, 94.5576], [23.7754, 117.5576, 24.7754, 118.5576], [42.7754, 94.5576, 44.7754, 96.5576], [21.7754, 98.5576, 22.7754, 104.5576], [28.7754, 82.5576, 29.7754, 98.5576], [24.7754, 117.5576, 25.7754, 119.5576], [38.7754, 120.5576, 39.7754, 124.5576], [29.7754, 120.5576, 32.7754, 122.5576], [41.7754, 79.2585, 41.8535, 79.5576], [29.7754, 122.5576, 31.7754, 123.5576], [27.6769, 91.7865, 27.7754, 92.1101], [27.7754, 117.5576, 29.7754, 122.5576], [18.7754, 108.5576, 20.7754, 111.5576], [29.7754, 79.5576, 42.7754, 120.5576], [36.7754, 121.5576, 37.7754, 123.5576], [48.7754, 86.6922, 49.2494, 88.1056], [40.7754, 120.5576, 42.7754, 128.5576], [25.7754, 117.5576, 26.7754, 120.5576], [47.7754, 85.4858, 48.7754, 90.1507], [49.7754, 127.5576, 50.7754, 128.5576], [30.7754, 78.5576, 36.7754, 79.5576], [23.7754, 97.5576, 28.7754, 98.5576], [26.7754, 117.5576, 27.7754, 121.5576], [22.7754, 98.5576, 29.7754, 117.5576], [20.7754, 99.5576, 21.7754, 102.5576], [42.7754, 110.3934, 44.7820, 111.5576], [36.7754, 73.5576, 40.7754, 79.5576], [49.7754, 118.4027, 50.9802, 119.5576], [25.1912, 119.5576, 25.7754, 119.9120], [27.7754, 84.5576, 28.7754, 93.5576], [17.7754, 108.5576, 18.7754, 110.5576], [24.5027, 118.5576, 24.7754, 118.8161], [52.7754, 119.9835, 53.5719, 126.1939], [32.2241, 78.3965, 32.6363, 78.5576], [35.7754, 120.5576, 38.7754, 121.5576], [40.7754, 76.5576, 41.7754, 79.5576], [42.7754, 115.5576, 49.7754, 131.5576], [44.8404, 131.5576, 48.4334, 134.8631], [47.9285, 115.4373, 48.2230, 115.5576], [45.7754, 82.3630, 46.2212, 82.5576], [45.7754, 82.5576, 47.7754, 91.5576], [41.7754, 128.5576, 42.7754, 131.5576], [49.7754, 119.5576, 52.7754, 127.5576], [35.4169, 77.1449, 35.7754, 78.5576], [27.2614, 88.7706, 27.7754, 89.2653], [28.2004, 96.2409, 28.7754, 97.5576], [39.7754, 120.5576, 40.7754, 126.5576] ] }, { "minLevel": 9, "maxLevel": 20, "label": "INEGI", "alt": "Fuente: INEGI (Instituto Nacional de Estadistica y Geografia)", "boxes": [ [18.0000, -95.0000, 20.0000, -87.0000], [17.4060, -91.0000, 18.0000, -88.7349], [28.0000, -101.0000, 29.4004, -99.9666], [32.0000, -117.1817, 32.7325, -113.1649], [15.5643, -97.9326, 16.0000, -95.2581], [24.0000, -113.0000, 26.0000, -97.0000], [16.0000, -91.0000, 16.9491, -90.3434], [18.0000, -115.0000, 20.0000, -109.0000], [28.0000, -119.0000, 32.0000, -103.0000], [14.4031, -94.2111, 16.0000, -91.0000],
Map Tile API Developer's Guide 350► API Reference
[26.0000, -117.0000, 28.0000, -99.0000], [20.0000, -90.6669, 22.0000, -86.6669], [26.0000, -99.0000, 26.4261, -97.5566], [16.0000, -103.0000, 18.0000, -91.0000], [22.0000, -111.0000, 24.0000, -97.0000], [18.0000, -107.0000, 22.0000, -95.0000] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Canada", "alt": "This data includes information taken with permission from Canadian authorities, including Her Majesty, Queens Printer for Ontario, Canada Post, GeoBase, Department of Natural Resources Canada. All rights reserved", "boxes": [ [78.0000, -115.0000, 80.0000, -101.0000], [70.0000, -77.0000, 74.0000, -67.0000], [80.0000, -69.0000, 82.0000, -61.0000], [62.0000, -141.0000, 70.0000, -63.0000], [41.9986, -83.0000, 44.0238, -77.4271], [56.0000, -81.0000, 62.0000, -63.0000], [50.0000, -57.0000, 54.0000, -55.0000], [48.0000, -129.0000, 56.0000, -57.0000], [56.0000, -63.0000, 68.0000, -61.0000], [70.0000, -125.9042, 78.0000, -77.0000], [56.0000, -135.0000, 58.0000, -87.0000], [46.0000, -87.5736, 48.0357, -57.0000], [52.0000, -135.0000, 56.0000, -129.0000], [82.0000, -91.0000, 84.0000, -61.0000], [46.3831, -57.0167, 49.9905, -50.9810], [58.0000, -141.0000, 62.0000, -91.0000], [44.0000, -85.0026, 46.0536, -59.0000] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [-21.4740, 55.1479, -20.7728, 55.9393] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [29.0724, 40.2408, 34.0557, 45.6538], [29.8076, 38.7937, 34.0739, 43.8802], [29.0724, 45.6538, 34.0557, 47.9928], [35.7168, 42.7138, 37.3779, 46.4809], [29.9029, 47.1930, 31.4399, 48.5938], [35.7168, 41.2402, 37.3779, 42.7138] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [44.8976, 13.8789, 46.5835, 18.1295], [42.1231, 14.4853, 44.8976, 18.6541],
Map Tile API Developer's Guide 351► API Reference
[42.5705, 15.6655, 43.3251, 17.0432], [44.8126, 16.5981, 45.7845, 19.5169], [44.9955, 16.1850, 45.1490, 16.4761], [45.4199, 18.1216, 45.9726, 19.1392] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Nepal", "alt": "Copyright Survey Department, Government of Nepal", "boxes": [ [30.1502, 81.3961, 30.4719, 82.2540], [27.4329, 81.6782, 27.9426, 82.8798], [28.2854, 79.7937, 30.6642, 82.2540], [26.4858, 83.0964, 29.4459, 85.7994], [26.2669, 85.5710, 28.4465, 88.2408] ] }, { "minLevel": 9, "maxLevel": 20, "label": "2014 THTC", "alt": "copyright 2014 Iran Maps provided by THTC", "boxes": [ [25.7411, 61.7923, 26.2083, 61.8881], [29.9265, 60.8423, 31.5665, 61.9599], [38.2632, 44.2983, 39.0496, 46.5449], [25.7433, 53.8979, 37.6020, 61.7923], [31.5665, 60.4947, 34.0374, 60.9660], [39.0244, 46.9254, 39.7910, 48.3969], [29.8177, 60.4678, 31.5665, 60.9671], [38.1617, 46.5449, 39.1950, 48.0120], [32.9515, 46.0457, 33.1362, 46.2203], [26.5239, 62.3114, 26.5998, 62.6364], [25.7433, 60.8544, 29.9265, 61.9791], [26.4634, 61.8391, 28.6155, 62.9147], [35.8416, 44.4164, 38.8818, 47.5346], [32.9552, 45.2424, 35.8416, 47.3873], [35.7409, 44.1806, 38.2632, 46.0286], [25.7783, 47.3792, 32.0891, 56.2187], [38.4003, 44.0023, 39.8596, 45.4530], [27.0181, 63.1942, 27.2641, 63.3436], [26.1964, 46.2203, 38.4489, 57.1922], [25.7411, 61.8081, 25.9431, 61.9006], [38.8953, 48.0120, 39.0229, 48.3415], [34.1048, 60.5115, 36.6543, 61.5751], [33.8976, 59.0624, 37.6020, 61.1473], [31.4968, 59.9152, 34.0374, 60.8423], [26.2013, 61.8221, 26.5448, 62.3152], [35.3974, 46.0286, 38.8972, 48.8454], [38.8972, 47.5269, 39.2823, 48.3741], [24.9003, 57.1430, 26.1964, 61.8081], [26.8134, 62.8691, 27.2641, 63.2960], [26.6245, 62.9016, 26.8405, 63.2208] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN Guatemala", "alt": "Aprobado por el INSTITUTO GEOGRAFICO NACIONAL Resolucion del IGN No 186-2011", "boxes": [ [13.7417, -91.8261, 14.1492, -89.8235], [16.4730, -90.6686, 16.5943, -90.6245], [14.0259, -89.8235, 14.1492, -89.6796],
Map Tile API Developer's Guide 352► API Reference
[14.1492, -90.6245, 16.5943, -89.0225], [16.5943, -91.4256, 17.8168, -89.0225], [14.1492, -92.2266, 16.1868, -90.6245] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [53.8757, 22.4807, 55.1024, 24.5276], [54.2630, 22.6378, 54.6908, 23.1253], [54.9394, 20.8924, 56.5027, 23.4230], [53.8579, 22.5790, 56.5027, 24.9113], [53.8579, 24.5937, 56.4848, 26.8994] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [35.1525, 33.5454, 35.7340, 34.6339], [34.8444, 33.6276, 35.2760, 34.1041] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [49.1699, 19.3708, 52.6479, 23.8452], [50.3804, 23.7940, 50.6141, 24.1242], [51.6271, 18.2346, 55.0681, 24.1071], [50.3495, 23.3995, 51.0366, 24.1571], [51.0366, 23.1726, 52.2145, 23.7360], [52.7337, 14.0896, 53.0647, 14.3477], [49.5714, 22.2773, 51.4811, 23.7502], [50.8016, 23.3995, 51.5813, 24.1714], [48.9384, 21.8835, 49.9277, 22.9603] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [2.1134, -54.0010, 3.5684, -52.5112], [2.1062, -54.6066, 3.5684, -54.0010], [2.6665, -52.5112, 3.5742, -52.0258], [3.9930, -54.5201, 5.2588, -54.2990] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [15.6985, -61.9309, 16.5953, -61.0013] ]
Map Tile API Developer's Guide 353► API Reference
}, { "minLevel": 9, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [14.3135, -61.2546, 14.9680, -60.7258] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Jordan", "alt": "Royal Jordanian Geographic Centre", "boxes": [ [30.8890, 35.2899, 32.3179, 37.3047], [29.2293, 35.2899, 31.3679, 38.0203], [31.8515, 35.4964, 32.7823, 36.8242], [29.2293, 34.9258, 30.8890, 35.9751] ] }, { "minLevel": 9, "maxLevel": 20, "label": "BEV", "alt": "copyright Bundesamt fur Eich- und Vermessungswesen", "boxes": [ [48.7534, 16.3752, 48.8317, 16.7250], [46.5375, 12.6822, 46.6390, 13.3457], [46.8181, 10.4415, 46.9033, 10.6752], [47.6962, 12.9642, 48.2248, 13.3457], [46.3748, 13.3457, 46.6390, 14.8717], [46.7953, 11.0567, 46.9033, 11.1249], [48.7534, 14.8717, 49.0177, 16.0162], [48.2248, 12.9642, 48.3571, 13.3457], [47.6962, 13.3457, 48.7534, 17.1607], [46.8219, 9.9561, 46.9033, 10.2682], [46.6390, 12.2012, 46.9033, 16.0162], [47.6962, 12.8955, 47.8109, 12.9642], [46.6390, 10.6752, 46.9033, 11.0567], [46.9033, 9.5307, 47.6962, 16.7792], [46.8266, 16.0162, 46.9033, 16.1893] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [58.0107, 27.4528, 58.7552, 27.6501], [57.8526, 24.2950, 57.9554, 24.7904], [58.7436, 27.4413, 59.4859, 28.2525], [57.8968, 21.7448, 59.3645, 23.4580], [57.9301, 23.4390, 59.7909, 27.4650], [57.7540, 23.1887, 57.8411, 23.2957] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [
Map Tile API Developer's Guide 354► API Reference
[10.6629, -85.8099, 12.9543, -83.3936], [14.2095, -82.9224, 14.5307, -82.6012], [11.0412, -87.1376, 14.6525, -83.1509], [12.3118, -87.8420, 14.2011, -84.9162], [13.6161, -85.8103, 15.1814, -83.0464] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.4520, 13.7142, 46.8284, 16.3044], [45.4418, 13.5675, 45.5366, 13.6734], [45.4125, 13.6570, 45.6003, 13.9833], [45.4543, 14.0533, 45.7004, 14.6924], [45.5239, 14.6795, 45.5557, 14.7057], [45.5557, 14.5931, 46.1463, 15.7955], [46.8276, 15.9827, 46.8786, 16.2706], [45.5318, 13.5988, 45.5394, 13.6380], [45.5366, 13.3628, 46.5230, 13.9372], [45.3439, 14.6924, 45.7418, 15.4262] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [47.4754, 38.4346, 50.1112, 40.3587], [47.7796, 23.7808, 52.3053, 30.3909], [45.8550, 30.3873, 51.8685, 37.3686], [47.9979, 23.0400, 48.0552, 23.1187], [50.7773, 34.6660, 51.2858, 35.5437], [47.7796, 23.6071, 50.6001, 25.5225], [44.0324, 29.5592, 46.3547, 37.3686], [44.9794, 29.0356, 47.9080, 30.3873], [50.5207, 23.4548, 51.7557, 24.4370], [51.6941, 34.3051, 51.9267, 34.4588], [51.7797, 30.5067, 52.4699, 34.3366], [46.3547, 34.8806, 50.8793, 38.6386], [47.9624, 23.1767, 48.1330, 23.5211], [48.3302, 22.1323, 49.0508, 22.5012], [47.9128, 22.4364, 50.5207, 23.9830], [47.9209, 22.1347, 48.5886, 23.2256], [47.7060, 24.7422, 47.8394, 25.2039] ] }, { "minLevel": 9, "maxLevel": 20, "label": "CNIG", "alt": "Informacion geografica propiedad del CNIG", "boxes": [ [37.3120, -6.8623, 39.3980, 0.2290], [38.2202, 3.0662, 40.2854, 5.1739], [36.8976, -7.5399, 41.6961, -6.5372], [39.3438, -7.6437, 39.7836, -7.2643], [35.2569, -2.9815, 35.3232, -2.9161], [35.6142, -7.0220, 37.9317, -1.2109], [27.4138, -18.2990, 29.4228, -13.2707], [35.8628, -5.3870, 35.9199, -5.2772], [38.4150, -6.7340, 43.7683, 3.4915], [27.4138, -18.2990, 29.4228, -13.2707] ]
Map Tile API Developer's Guide 355► API Reference
} ], "hybrid": [ { "minLevel": 0, "maxLevel": 20, "label": "2014 DigitalGlobe", "alt": "copyright 2014 DigitalGlobe, Inc." }, { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [-27.3403, 31.4364, -26.7719, 32.0286], [-27.0738, 30.7201, -26.2624, 31.5422], [-26.8455, 32.0275, -26.7719, 32.1475], [-26.8359, 30.8723, -25.6938, 32.1739] ] }, { "minLevel": 6, "maxLevel": 20, "label": "PSMA", "alt": "Copyright. Based on data provided under license from PSMA Australia Limited. Product incorporates data which is 2014 Telstra Corporation Limited, GM Holden Limited, Intelematics Australia Pty Ltd, HERE International LLC, Sentinel Content Pty Limited and Continental Pty Ltd", "boxes": [ [-32.0000, 113.0000, -20.0000, 151.0000], [-14.0000, 141.0000, -8.0000, 145.0000], [-30.0761, 167.0381, -28.0761, 169.0381], [-14.0000, 129.0000, -10.0000, 137.0000], [-38.0000, 135.0000, -32.0000, 151.0000], [-34.0000, 151.0000, -24.0000, 155.0000], [-34.0000, 127.0000, -32.0000, 135.0000], [-13.1672, 95.8626, -11.1672, 97.8626], [-20.0000, 123.0000, -14.0000, 147.0000], [-11.5539, 104.6728, -9.5539, 106.6728], [-44.0000, 141.0000, -38.0000, 149.0000], [-36.0000, 115.0000, -32.0000, 127.0000], [-20.0000, 121.0000, -16.0000, 123.0000] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IgeoE", "alt": "IgeoE - Portugal", "boxes": [ [39.3941, -7.5899, 39.6663, -6.9850], [40.9842, -7.3532, 41.2705, -6.5519], [36.5482, -32.0392, 40.4124, -23.6635], [32.2747, -17.3686, 33.1907, -15.9142], [41.7211, -7.2357, 42.0048, -6.5050], [39.6540, -7.5520, 40.2572, -6.7565], [36.9392, -9.0081, 38.4418, -7.2449], [39.4153, -8.4431, 41.9675, -7.2126], [37.9667, -7.2522, 38.3853, -6.8808], [38.4418, -8.9260, 39.5144, -6.7321], [30.1318, -15.8830, 30.1622, -15.8445], [39.4801, -9.1848, 42.1722, -7.8729], [38.1864, -9.5593, 39.5271, -8.8950], [40.1168, -7.4841, 40.9984, -6.7565], [41.2304, -7.3100, 41.7633, -6.5183]
Map Tile API Developer's Guide 356► API Reference
] }, { "minLevel": 10, "maxLevel": 20, "label": "SOI", "alt": "Survey of Israel data source", "boxes": [ [29.3724, 34.2346, 31.5477, 35.4573], [32.6825, 35.0912, 33.1130, 35.7566], [32.7247, 35.3798, 33.1257, 35.9089], [30.9701, 34.4766, 33.1256, 35.6655] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGM", "alt": "INSTITUTO GEOGRAFICO MILITAR DEL ECUADOR AUTORIZACION No IGM-2011-01- PCO-01 DEL 25 DE ENERO DE 2011", "boxes": [ [0.4963, -78.4796, 0.8202, -77.2440], [-2.4189, -76.4202, -2.0950, -76.0083], [-2.7428, -80.9509, 1.1441, -80.5390], [-4.6863, -80.5390, 1.1441, -78.4796], [-3.0667, -78.0677, -2.7428, -77.2440], [-2.0950, -78.4796, 0.4963, -75.5964], [-1.4472, -75.5964, 0.1724, -75.1846], [-2.7428, -81.3628, -0.7994, -80.9509], [-3.7146, -78.4796, -2.0950, -78.0677], [-5.0102, -79.7153, -4.6863, -78.8915], [-2.7428, -78.0677, -2.0950, -76.4202], [1.1441, -79.3034, 1.4680, -78.4796] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Geomatics", "alt": "Copyright Geomatics Ltd.", "boxes": [ [34.8037, 20.3974, 41.0512, 26.5331], [41.0512, 22.8393, 41.6370, 24.4931], [38.9765, 26.5331, 39.1817, 26.6201], [41.0512, 21.9014, 41.1740, 22.4426], [36.1209, 29.5552, 36.1723, 29.6034], [41.0512, 24.4883, 41.8654, 26.5489], [41.0512, 22.4426, 41.3788, 22.8625], [38.9687, 19.3748, 40.3571, 20.3974], [35.1058, 26.5331, 37.9255, 28.2956], [41.2829, 26.5380, 41.6486, 26.6501] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN France 2009 BD TOPO", "boxes": [ [48.7889, -2.0366, 51.1937, 2.7484], [44.8560, 6.2593, 45.8136, 7.2498], [44.5968, 6.6907, 45.0132, 7.1016], [42.2486, 0.3773, 46.1891, 6.8232], [45.7944, 6.8518, 46.1046, 7.1168], [46.5120, -5.2986, 48.9033, -2.1006], [47.3484, 7.1095, 48.6757, 7.8910],
Map Tile API Developer's Guide 357► API Reference
[45.8114, 5.9584, 46.5615, 6.9032], [41.3454, 8.4823, 43.1241, 9.6779], [42.5367, -2.1077, 46.5120, 2.1618], [46.5513, 6.1405, 47.3535, 7.0066], [45.8812, -2.1077, 48.9033, 6.7118], [47.2548, 6.3526, 48.6954, 7.5496], [48.6676, 2.4444, 51.1937, 8.2326], [42.8343, 4.3116, 45.2796, 7.6780] ] }, { "minLevel": 9, "maxLevel": 20, "label": "OGL", "alt": "Open Government Licence v.1.0.", "boxes": [ [51.5011, -5.3731, 52.6691, -5.1981], [53.8371, -8.1821, 59.6771, -1.2194], [50.3331, -5.1981, 53.8371, -1.2194], [50.3331, -1.2194, 55.0051, 1.7646], [49.1651, -7.9476, 50.3331, -1.9796] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Swisstopo", "alt": "Topografische Grundlage: copyright Bundesamt fur Landestopographie", "boxes": [ [45.8206, 6.8641, 47.4100, 7.3171], [47.4100, 6.9280, 47.5272, 7.3171], [47.2863, 9.5821, 47.5004, 9.6893], [46.0972, 8.5106, 46.2180, 8.6761], [46.0193, 8.6761, 46.2180, 9.1291], [45.7831, 8.7540, 46.0193, 9.1167], [46.2703, 9.4435, 46.4166, 9.8658], [46.4166, 6.4111, 47.0127, 6.8641], [46.2180, 8.2231, 46.4166, 9.1291], [46.5237, 10.2370, 46.6153, 10.4882], [46.2131, 10.0449, 46.2643, 10.1820], [46.1195, 5.9453, 46.2180, 6.3156], [47.0127, 9.5821, 47.0721, 9.9106], [46.6153, 9.5821, 47.0127, 10.4882], [47.6087, 8.6761, 47.8074, 9.4309], [46.4140, 10.0351, 46.6153, 10.1740], [46.4166, 9.5821, 46.6153, 10.0351], [46.1024, 6.7620, 46.4166, 6.8641], [46.4166, 7.3171, 47.6087, 9.5821], [46.3513, 9.8639, 46.4166, 10.0351], [46.6153, 6.1662, 46.7577, 6.4111], [47.0127, 6.6305, 47.1914, 6.8641], [46.3367, 10.0312, 46.4166, 10.1725], [47.6087, 8.2231, 47.8074, 8.6761], [46.1180, 9.1291, 46.4166, 9.3037], [46.0193, 7.3171, 46.4166, 8.2231], [45.8846, 7.3171, 46.0193, 8.0455], [46.2654, 9.9778, 46.3547, 10.0368], [46.2180, 5.9581, 46.6153, 6.4111] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Cenacarta", "alt": "Certain Data for Mozambique provided by Cenacarta 2014 by Cenacarta", "boxes": [
Map Tile API Developer's Guide 358► API Reference
[-16.0985, 30.1219, -13.9704, 33.7148], [-22.9890, 31.1878, -18.8084, 36.5975], [-15.9653, 33.6194, -10.3973, 41.2432], [-18.8203, 31.8425, -15.6508, 36.5975], [-26.8763, 31.1878, -22.4084, 35.7659], [-24.9908, 34.2964, -23.3847, 35.6707], [-16.3417, 30.7148, -14.0950, 34.9419], [-17.1457, 38.6588, -15.8415, 40.2757] ] }, { "minLevel": 11, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.7302, 28.2568, 47.4471, 29.2353], [46.7892, 29.2282, 47.4471, 29.9684], [45.7302, 28.5878, 46.2901, 29.0637], [46.8530, 26.5110, 48.6163, 29.3448], [46.3002, 29.2029, 46.5592, 30.2333], [45.4102, 28.0701, 46.4249, 28.5878], [45.4154, 28.0081, 46.1325, 28.4224], [46.4187, 28.0753, 47.9267, 29.3100] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Statkart", "alt": "Copyright 2000; Norwegian Mapping Authority", "boxes": [ [68.8789, 27.8446, 71.4071, 32.1402], [68.4773, 24.6595, 71.3952, 26.3932], [61.0315, 6.1059, 70.9952, 18.0586], [66.1997, 15.2505, 67.3135, 16.3893], [63.9575, 13.0203, 65.6822, 14.7214], [69.6571, 25.9972, 71.4071, 28.8856], [59.2422, 9.9664, 63.2018, 13.0634], [56.4440, 2.9492, 63.9455, 12.0640] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [56.3085, 21.6724, 57.8204, 23.3336], [55.9347, 20.7407, 57.7144, 21.8250], [56.1948, 23.0950, 57.2653, 24.2779] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Deutschland", "alt": "Die Grundlagendaten wurden mit Genehmigung der zustandigen Behorden entnommen", "boxes": [ [51.9414, 6.7881, 53.8624, 7.7050], [47.2702, 7.7050, 55.0556, 13.2064], [48.0487, 13.2064, 49.6058, 13.9895], [50.3844, 13.2064, 54.2771, 15.0401], [48.8273, 5.8712, 51.9414, 7.7050] ]
Map Tile API Developer's Guide 359► API Reference
}, { "minLevel": 9, "maxLevel": 20, "label": "Sri Lanka", "alt": "This product incorporates original source digital data obtained from the Survey Department of Sri Lanka. 2009 Survey Department of Sri Lanka The data has been used with the permission of the Survey Department of Sri Lanka", "boxes": [ [5.8461, 79.5067, 9.9652, 82.0121] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Lantmateriet", "alt": "Based upon electronic data National Land Survey Sweden.", "boxes": [ [58.0209, 17.3803, 62.5323, 19.7075], [56.8124, 17.7151, 58.4792, 19.8137], [55.2659, 13.7838, 58.0209, 17.4660], [58.0209, 11.5126, 64.3169, 17.4803], [62.5323, 15.7813, 69.3138, 25.2754], [55.1529, 12.3680, 56.6521, 13.7838], [60.9048, 13.0830, 68.0183, 18.3797] ] }, { "minLevel": 9, "maxLevel": 20, "label": "ITA", "alt": "La Banca Dati Italiana e stata prodotta usando quale riferimento anche cartografia numerica ed al tratto prodotta e fornita dalla Regione Toscana", "boxes": [ [45.5627, 12.8285, 46.6783, 13.9860], [36.6566, 11.8869, 36.8801, 12.1816], [44.1083, 6.6130, 45.2558, 7.2468], [39.2141, 13.5406, 43.0524, 16.4857], [45.6248, 6.8008, 45.8575, 6.9794], [42.6396, 13.3581, 43.6743, 14.0461], [46.7941, 10.3931, 47.0561, 11.6257], [35.3758, 11.8034, 40.0397, 19.4309], [38.1821, 6.8824, 47.2069, 14.1446] ] }, { "minLevel": 6, "maxLevel": 20, "label": "2014 NavInfo", "alt": "copyright 2014 NavInfo Co Ltd. All Rights Reserved", "boxes": [ [20.7754, 106.5576, 22.7754, 113.5576], [28.6334, 93.5576, 28.7754, 94.0161], [42.7754, 111.5576, 45.7754, 115.5576], [32.7754, 120.5576, 33.5701, 120.8986], [21.7754, 113.5576, 22.7754, 116.5576], [42.7754, 79.5576, 45.7754, 94.5576], [23.7754, 117.5576, 24.7754, 118.5576], [42.7754, 94.5576, 44.7754, 96.5576], [21.7754, 98.5576, 22.7754, 104.5576], [28.7754, 82.5576, 29.7754, 98.5576], [24.7754, 117.5576, 25.7754, 119.5576], [38.7754, 120.5576, 39.7754, 124.5576], [29.7754, 120.5576, 32.7754, 122.5576], [41.7754, 79.2585, 41.8535, 79.5576], [29.7754, 122.5576, 31.7754, 123.5576],
Map Tile API Developer's Guide 360► API Reference
[27.6769, 91.7865, 27.7754, 92.1101], [27.7754, 117.5576, 29.7754, 122.5576], [18.7754, 108.5576, 20.7754, 111.5576], [29.7754, 79.5576, 42.7754, 120.5576], [36.7754, 121.5576, 37.7754, 123.5576], [48.7754, 86.6922, 49.2494, 88.1056], [40.7754, 120.5576, 42.7754, 128.5576], [25.7754, 117.5576, 26.7754, 120.5576], [47.7754, 85.4858, 48.7754, 90.1507], [49.7754, 127.5576, 50.7754, 128.5576], [30.7754, 78.5576, 36.7754, 79.5576], [23.7754, 97.5576, 28.7754, 98.5576], [26.7754, 117.5576, 27.7754, 121.5576], [22.7754, 98.5576, 29.7754, 117.5576], [20.7754, 99.5576, 21.7754, 102.5576], [42.7754, 110.3934, 44.7820, 111.5576], [36.7754, 73.5576, 40.7754, 79.5576], [49.7754, 118.4027, 50.9802, 119.5576], [25.1912, 119.5576, 25.7754, 119.9120], [27.7754, 84.5576, 28.7754, 93.5576], [17.7754, 108.5576, 18.7754, 110.5576], [24.5027, 118.5576, 24.7754, 118.8161], [52.7754, 119.9835, 53.5719, 126.1939], [32.2241, 78.3965, 32.6363, 78.5576], [35.7754, 120.5576, 38.7754, 121.5576], [40.7754, 76.5576, 41.7754, 79.5576], [42.7754, 115.5576, 49.7754, 131.5576], [44.8404, 131.5576, 48.4334, 134.8631], [47.9285, 115.4373, 48.2230, 115.5576], [45.7754, 82.3630, 46.2212, 82.5576], [45.7754, 82.5576, 47.7754, 91.5576], [41.7754, 128.5576, 42.7754, 131.5576], [49.7754, 119.5576, 52.7754, 127.5576], [35.4169, 77.1449, 35.7754, 78.5576], [27.2614, 88.7706, 27.7754, 89.2653], [28.2004, 96.2409, 28.7754, 97.5576], [39.7754, 120.5576, 40.7754, 126.5576] ] }, { "minLevel": 9, "maxLevel": 20, "label": "INEGI", "alt": "Fuente: INEGI (Instituto Nacional de Estadistica y Geografia)", "boxes": [ [18.0000, -95.0000, 20.0000, -87.0000], [17.4060, -91.0000, 18.0000, -88.7349], [28.0000, -101.0000, 29.4004, -99.9666], [32.0000, -117.1817, 32.7325, -113.1649], [15.5643, -97.9326, 16.0000, -95.2581], [24.0000, -113.0000, 26.0000, -97.0000], [16.0000, -91.0000, 16.9491, -90.3434], [18.0000, -115.0000, 20.0000, -109.0000], [28.0000, -119.0000, 32.0000, -103.0000], [14.4031, -94.2111, 16.0000, -91.0000], [26.0000, -117.0000, 28.0000, -99.0000], [20.0000, -90.6669, 22.0000, -86.6669], [26.0000, -99.0000, 26.4261, -97.5566], [16.0000, -103.0000, 18.0000, -91.0000], [22.0000, -111.0000, 24.0000, -97.0000], [18.0000, -107.0000, 22.0000, -95.0000] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Canada",
Map Tile API Developer's Guide 361► API Reference
"alt": "This data includes information taken with permission from Canadian authorities, including Her Majesty, Queens Printer for Ontario, Canada Post, GeoBase, Department of Natural Resources Canada. All rights reserved", "boxes": [ [78.0000, -115.0000, 80.0000, -101.0000], [70.0000, -77.0000, 74.0000, -67.0000], [80.0000, -69.0000, 82.0000, -61.0000], [62.0000, -141.0000, 70.0000, -63.0000], [41.9986, -83.0000, 44.0238, -77.4271], [56.0000, -81.0000, 62.0000, -63.0000], [50.0000, -57.0000, 54.0000, -55.0000], [48.0000, -129.0000, 56.0000, -57.0000], [56.0000, -63.0000, 68.0000, -61.0000], [70.0000, -125.9042, 78.0000, -77.0000], [56.0000, -135.0000, 58.0000, -87.0000], [46.0000, -87.5736, 48.0357, -57.0000], [52.0000, -135.0000, 56.0000, -129.0000], [82.0000, -91.0000, 84.0000, -61.0000], [46.3831, -57.0167, 49.9905, -50.9810], [58.0000, -141.0000, 62.0000, -91.0000], [44.0000, -85.0026, 46.0536, -59.0000] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [-21.4740, 55.1479, -20.7728, 55.9393] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [29.0724, 40.2408, 34.0557, 45.6538], [29.8076, 38.7937, 34.0739, 43.8802], [29.0724, 45.6538, 34.0557, 47.9928], [35.7168, 42.7138, 37.3779, 46.4809], [29.9029, 47.1930, 31.4399, 48.5938], [35.7168, 41.2402, 37.3779, 42.7138] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [44.8976, 13.8789, 46.5835, 18.1295], [42.1231, 14.4853, 44.8976, 18.6541], [42.5705, 15.6655, 43.3251, 17.0432], [44.8126, 16.5981, 45.7845, 19.5169], [44.9955, 16.1850, 45.1490, 16.4761], [45.4199, 18.1216, 45.9726, 19.1392] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Nepal", "alt": "Copyright Survey Department, Government of Nepal", "boxes":
Map Tile API Developer's Guide 362► API Reference
[ [30.1502, 81.3961, 30.4719, 82.2540], [27.4329, 81.6782, 27.9426, 82.8798], [28.2854, 79.7937, 30.6642, 82.2540], [26.4858, 83.0964, 29.4459, 85.7994], [26.2669, 85.5710, 28.4465, 88.2408] ] }, { "minLevel": 9, "maxLevel": 20, "label": "2014 THTC", "alt": "copyright 2014 Iran Maps provided by THTC", "boxes": [ [25.7411, 61.7923, 26.2083, 61.8881], [29.9265, 60.8423, 31.5665, 61.9599], [38.2632, 44.2983, 39.0496, 46.5449], [25.7433, 53.8979, 37.6020, 61.7923], [31.5665, 60.4947, 34.0374, 60.9660], [39.0244, 46.9254, 39.7910, 48.3969], [29.8177, 60.4678, 31.5665, 60.9671], [38.1617, 46.5449, 39.1950, 48.0120], [32.9515, 46.0457, 33.1362, 46.2203], [26.5239, 62.3114, 26.5998, 62.6364], [25.7433, 60.8544, 29.9265, 61.9791], [26.4634, 61.8391, 28.6155, 62.9147], [35.8416, 44.4164, 38.8818, 47.5346], [32.9552, 45.2424, 35.8416, 47.3873], [35.7409, 44.1806, 38.2632, 46.0286], [25.7783, 47.3792, 32.0891, 56.2187], [38.4003, 44.0023, 39.8596, 45.4530], [27.0181, 63.1942, 27.2641, 63.3436], [26.1964, 46.2203, 38.4489, 57.1922], [25.7411, 61.8081, 25.9431, 61.9006], [38.8953, 48.0120, 39.0229, 48.3415], [34.1048, 60.5115, 36.6543, 61.5751], [33.8976, 59.0624, 37.6020, 61.1473], [31.4968, 59.9152, 34.0374, 60.8423], [26.2013, 61.8221, 26.5448, 62.3152], [35.3974, 46.0286, 38.8972, 48.8454], [38.8972, 47.5269, 39.2823, 48.3741], [24.9003, 57.1430, 26.1964, 61.8081], [26.8134, 62.8691, 27.2641, 63.2960], [26.6245, 62.9016, 26.8405, 63.2208] ] }, { "minLevel": 0, "maxLevel": 20, "label": "2014 Microsoft Corp", "alt": "Copyright 2014 Microsoft Corp (Photographer)", "boxes": [ [43.0000, -9.0000, 43.8368, -1.4871], [47.6659, 17.0000, 48.1870, 17.1796], [49.0000, -3.0000, 53.0000, 7.0000], [25.0000, -83.0000, 43.0000, -80.0000], [54.9700, 15.0000, 55.4090, 15.2079], [58.8191, 16.9798, 60.0219, 19.3105], [49.0000, -95.1748, 49.4171, -94.7155], [24.4342, -81.8753, 25.0000, -80.0000], [53.0000, -3.0000, 61.0000, -1.0000], [51.0000, 13.0000, 57.0000, 15.0000], [59.8274, 23.9754, 61.0338, 26.0308], [43.0000, -77.0000, 45.1041, -71.4874], [45.9934, -70.7166, 47.5037, -67.7111], [51.1463, 15.0000, 51.1538, 15.0019], [28.0000, -86.0000, 49.0000, -83.0000], [37.0000, -125.0000, 49.0000, -86.0000],
Map Tile API Developer's Guide 363► API Reference
[41.7315, 3.0000, 43.0000, 3.3548], [45.5418, 13.0000, 47.0000, 13.9644], [53.0000, 4.6555, 53.7627, 7.0000], [38.8500, 8.3413, 39.0000, 9.0932], [34.0000, -80.0000, 43.0000, -74.0000], [43.0000, -1.0000, 49.0000, 7.0000], [29.2540, -105.6275, 31.0000, -104.0000], [49.0000, -11.0000, 59.0000, -3.0000], [50.4136, 13.0000, 51.0000, 14.4285], [36.9570, -8.0082, 37.0000, -7.8011], [38.8376, 17.0000, 39.5206, 17.2421], [47.0000, 13.0000, 49.0000, 17.0000], [43.0000, 13.0000, 43.8815, 13.8986], [39.6609, 17.0000, 41.1153, 18.6364], [43.0000, -79.1238, 43.5219, -76.7251], [46.2245, 13.3861, 47.0000, 16.5913], [38.4332, 1.1578, 40.4985, 4.6176], [53.0000, -1.0000, 54.7773, 0.5000], [42.9741, -9.3240, 43.3001, -8.9859], [38.2126, -9.5302, 39.9011, -9.0000], [48.3914, -5.1628, 48.5056, -5.0000], [35.9238, -6.6631, 37.0000, -1.8450], [51.1642, 15.0000, 51.3263, 15.0580], [25.6957, -100.1176, 28.0000, -96.8387], [40.0000, -74.0000, 43.0000, -68.0000], [32.5516, -80.0000, 34.0000, -77.7120], [50.8137, 14.5069, 51.0000, 14.9382], [37.0000, 13.0000, 43.0000, 17.0000], [43.0000, -83.0000, 44.1708, -82.3613], [60.2720, -1.0000, 60.8841, -0.7110], [36.9926, -8.9533, 37.0000, -8.9311], [47.0000, -5.0000, 49.0000, -1.0000], [37.4381, 12.0022, 38.2529, 13.0000], [37.0000, -9.0000, 43.0000, 1.0000], [41.0000, 1.0000, 43.0000, 3.0000], [31.0000, -122.0000, 37.0000, -86.0000], [39.0000, 7.0000, 61.0000, 13.0000], [49.0000, 13.0000, 49.3287, 13.4222], [35.4007, 11.8529, 37.0069, 14.7297], [44.3159, -68.0009, 45.9940, -66.8902], [43.0000, -1.5690, 46.2402, -1.0000], [42.4435, -9.3240, 43.0000, -9.0000], [46.2340, -2.6007, 47.0000, -1.0000], [43.0000, -71.5231, 46.0000, -68.0000], [28.0000, -104.0000, 31.0000, -86.0000], [36.6258, 14.3209, 37.0000, 15.2989] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN Guatemala", "alt": "Aprobado por el INSTITUTO GEOGRAFICO NACIONAL Resolucion del IGN No 186-2011", "boxes": [ [13.7417, -91.8261, 14.1492, -89.8235], [16.4730, -90.6686, 16.5943, -90.6245], [14.0259, -89.8235, 14.1492, -89.6796], [14.1492, -90.6245, 16.5943, -89.0225], [16.5943, -91.4256, 17.8168, -89.0225], [14.1492, -92.2266, 16.1868, -90.6245] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes":
Map Tile API Developer's Guide 364► API Reference
[ [53.8757, 22.4807, 55.1024, 24.5276], [54.2630, 22.6378, 54.6908, 23.1253], [54.9394, 20.8924, 56.5027, 23.4230], [53.8579, 22.5790, 56.5027, 24.9113], [53.8579, 24.5937, 56.4848, 26.8994] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [35.1525, 33.5454, 35.7340, 34.6339], [34.8444, 33.6276, 35.2760, 34.1041] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [49.1699, 19.3708, 52.6479, 23.8452], [50.3804, 23.7940, 50.6141, 24.1242], [51.6271, 18.2346, 55.0681, 24.1071], [50.3495, 23.3995, 51.0366, 24.1571], [51.0366, 23.1726, 52.2145, 23.7360], [52.7337, 14.0896, 53.0647, 14.3477], [49.5714, 22.2773, 51.4811, 23.7502], [50.8016, 23.3995, 51.5813, 24.1714], [48.9384, 21.8835, 49.9277, 22.9603] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [2.1134, -54.0010, 3.5684, -52.5112], [2.1062, -54.6066, 3.5684, -54.0010], [2.6665, -52.5112, 3.5742, -52.0258], [3.9930, -54.5201, 5.2588, -54.2990] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [15.6985, -61.9309, 16.5953, -61.0013] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [14.3135, -61.2546, 14.9680, -60.7258] ] },
Map Tile API Developer's Guide 365► API Reference
{ "minLevel": 10, "maxLevel": 20, "label": "Jordan", "alt": "Royal Jordanian Geographic Centre", "boxes": [ [30.8890, 35.2899, 32.3179, 37.3047], [29.2293, 35.2899, 31.3679, 38.0203], [31.8515, 35.4964, 32.7823, 36.8242], [29.2293, 34.9258, 30.8890, 35.9751] ] }, { "minLevel": 9, "maxLevel": 20, "label": "BEV", "alt": "copyright Bundesamt fur Eich- und Vermessungswesen", "boxes": [ [48.7534, 16.3752, 48.8317, 16.7250], [46.5375, 12.6822, 46.6390, 13.3457], [46.8181, 10.4415, 46.9033, 10.6752], [47.6962, 12.9642, 48.2248, 13.3457], [46.3748, 13.3457, 46.6390, 14.8717], [46.7953, 11.0567, 46.9033, 11.1249], [48.7534, 14.8717, 49.0177, 16.0162], [48.2248, 12.9642, 48.3571, 13.3457], [47.6962, 13.3457, 48.7534, 17.1607], [46.8219, 9.9561, 46.9033, 10.2682], [46.6390, 12.2012, 46.9033, 16.0162], [47.6962, 12.8955, 47.8109, 12.9642], [46.6390, 10.6752, 46.9033, 11.0567], [46.9033, 9.5307, 47.6962, 16.7792], [46.8266, 16.0162, 46.9033, 16.1893] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [58.0107, 27.4528, 58.7552, 27.6501], [57.8526, 24.2950, 57.9554, 24.7904], [58.7436, 27.4413, 59.4859, 28.2525], [57.8968, 21.7448, 59.3645, 23.4580], [57.9301, 23.4390, 59.7909, 27.4650], [57.7540, 23.1887, 57.8411, 23.2957] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [10.6629, -85.8099, 12.9543, -83.3936], [14.2095, -82.9224, 14.5307, -82.6012], [11.0412, -87.1376, 14.6525, -83.1509], [12.3118, -87.8420, 14.2011, -84.9162], [13.6161, -85.8103, 15.1814, -83.0464] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics",
Map Tile API Developer's Guide 366► API Reference
"alt": "copyright EuroGeographics", "boxes": [ [45.4520, 13.7142, 46.8284, 16.3044], [45.4418, 13.5675, 45.5366, 13.6734], [45.4125, 13.6570, 45.6003, 13.9833], [45.4543, 14.0533, 45.7004, 14.6924], [45.5239, 14.6795, 45.5557, 14.7057], [45.5557, 14.5931, 46.1463, 15.7955], [46.8276, 15.9827, 46.8786, 16.2706], [45.5318, 13.5988, 45.5394, 13.6380], [45.5366, 13.3628, 46.5230, 13.9372], [45.3439, 14.6924, 45.7418, 15.4262] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [47.4754, 38.4346, 50.1112, 40.3587], [47.7796, 23.7808, 52.3053, 30.3909], [45.8550, 30.3873, 51.8685, 37.3686], [47.9979, 23.0400, 48.0552, 23.1187], [50.7773, 34.6660, 51.2858, 35.5437], [47.7796, 23.6071, 50.6001, 25.5225], [44.0324, 29.5592, 46.3547, 37.3686], [44.9794, 29.0356, 47.9080, 30.3873], [50.5207, 23.4548, 51.7557, 24.4370], [51.6941, 34.3051, 51.9267, 34.4588], [51.7797, 30.5067, 52.4699, 34.3366], [46.3547, 34.8806, 50.8793, 38.6386], [47.9624, 23.1767, 48.1330, 23.5211], [48.3302, 22.1323, 49.0508, 22.5012], [47.9128, 22.4364, 50.5207, 23.9830], [47.9209, 22.1347, 48.5886, 23.2256], [47.7060, 24.7422, 47.8394, 25.2039] ] }, { "minLevel": 9, "maxLevel": 20, "label": "CNIG", "alt": "Informacion geografica propiedad del CNIG", "boxes": [ [37.3120, -6.8623, 39.3980, 0.2290], [38.2202, 3.0662, 40.2854, 5.1739], [36.8976, -7.5399, 41.6961, -6.5372], [39.3438, -7.6437, 39.7836, -7.2643], [35.2569, -2.9815, 35.3232, -2.9161], [35.6142, -7.0220, 37.9317, -1.2109], [27.4138, -18.2990, 29.4228, -13.2707], [35.8628, -5.3870, 35.9199, -5.2772], [38.4150, -6.7340, 43.7683, 3.4915], [27.4138, -18.2990, 29.4228, -13.2707] ] } ], "normal": [ { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [
Map Tile API Developer's Guide 367► API Reference
[-27.3403, 31.4364, -26.7719, 32.0286], [-27.0738, 30.7201, -26.2624, 31.5422], [-26.8455, 32.0275, -26.7719, 32.1475], [-26.8359, 30.8723, -25.6938, 32.1739] ] }, { "minLevel": 6, "maxLevel": 20, "label": "PSMA", "alt": "Copyright. Based on data provided under license from PSMA Australia Limited. Product incorporates data which is 2014 Telstra Corporation Limited, GM Holden Limited, Intelematics Australia Pty Ltd, HERE International LLC, Sentinel Content Pty Limited and Continental Pty Ltd", "boxes": [ [-32.0000, 113.0000, -20.0000, 151.0000], [-14.0000, 141.0000, -8.0000, 145.0000], [-30.0761, 167.0381, -28.0761, 169.0381], [-14.0000, 129.0000, -10.0000, 137.0000], [-38.0000, 135.0000, -32.0000, 151.0000], [-34.0000, 151.0000, -24.0000, 155.0000], [-34.0000, 127.0000, -32.0000, 135.0000], [-13.1672, 95.8626, -11.1672, 97.8626], [-20.0000, 123.0000, -14.0000, 147.0000], [-11.5539, 104.6728, -9.5539, 106.6728], [-44.0000, 141.0000, -38.0000, 149.0000], [-36.0000, 115.0000, -32.0000, 127.0000], [-20.0000, 121.0000, -16.0000, 123.0000] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IgeoE", "alt": "IgeoE - Portugal", "boxes": [ [39.3941, -7.5899, 39.6663, -6.9850], [40.9842, -7.3532, 41.2705, -6.5519], [36.5482, -32.0392, 40.4124, -23.6635], [32.2747, -17.3686, 33.1907, -15.9142], [41.7211, -7.2357, 42.0048, -6.5050], [39.6540, -7.5520, 40.2572, -6.7565], [36.9392, -9.0081, 38.4418, -7.2449], [39.4153, -8.4431, 41.9675, -7.2126], [37.9667, -7.2522, 38.3853, -6.8808], [38.4418, -8.9260, 39.5144, -6.7321], [30.1318, -15.8830, 30.1622, -15.8445], [39.4801, -9.1848, 42.1722, -7.8729], [38.1864, -9.5593, 39.5271, -8.8950], [40.1168, -7.4841, 40.9984, -6.7565], [41.2304, -7.3100, 41.7633, -6.5183] ] }, { "minLevel": 10, "maxLevel": 20, "label": "SOI", "alt": "Survey of Israel data source", "boxes": [ [29.3724, 34.2346, 31.5477, 35.4573], [32.6825, 35.0912, 33.1130, 35.7566], [32.7247, 35.3798, 33.1257, 35.9089], [30.9701, 34.4766, 33.1256, 35.6655] ] }, { "minLevel": 9,
Map Tile API Developer's Guide 368► API Reference
"maxLevel": 20, "label": "IGM", "alt": "INSTITUTO GEOGRAFICO MILITAR DEL ECUADOR AUTORIZACION No IGM-2011-01- PCO-01 DEL 25 DE ENERO DE 2011", "boxes": [ [0.4963, -78.4796, 0.8202, -77.2440], [-2.4189, -76.4202, -2.0950, -76.0083], [-2.7428, -80.9509, 1.1441, -80.5390], [-4.6863, -80.5390, 1.1441, -78.4796], [-3.0667, -78.0677, -2.7428, -77.2440], [-2.0950, -78.4796, 0.4963, -75.5964], [-1.4472, -75.5964, 0.1724, -75.1846], [-2.7428, -81.3628, -0.7994, -80.9509], [-3.7146, -78.4796, -2.0950, -78.0677], [-5.0102, -79.7153, -4.6863, -78.8915], [-2.7428, -78.0677, -2.0950, -76.4202], [1.1441, -79.3034, 1.4680, -78.4796] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Geomatics", "alt": "Copyright Geomatics Ltd.", "boxes": [ [34.8037, 20.3974, 41.0512, 26.5331], [41.0512, 22.8393, 41.6370, 24.4931], [38.9765, 26.5331, 39.1817, 26.6201], [41.0512, 21.9014, 41.1740, 22.4426], [36.1209, 29.5552, 36.1723, 29.6034], [41.0512, 24.4883, 41.8654, 26.5489], [41.0512, 22.4426, 41.3788, 22.8625], [38.9687, 19.3748, 40.3571, 20.3974], [35.1058, 26.5331, 37.9255, 28.2956], [41.2829, 26.5380, 41.6486, 26.6501] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN France 2009 BD TOPO", "boxes": [ [48.7889, -2.0366, 51.1937, 2.7484], [44.8560, 6.2593, 45.8136, 7.2498], [44.5968, 6.6907, 45.0132, 7.1016], [42.2486, 0.3773, 46.1891, 6.8232], [45.7944, 6.8518, 46.1046, 7.1168], [46.5120, -5.2986, 48.9033, -2.1006], [47.3484, 7.1095, 48.6757, 7.8910], [45.8114, 5.9584, 46.5615, 6.9032], [41.3454, 8.4823, 43.1241, 9.6779], [42.5367, -2.1077, 46.5120, 2.1618], [46.5513, 6.1405, 47.3535, 7.0066], [45.8812, -2.1077, 48.9033, 6.7118], [47.2548, 6.3526, 48.6954, 7.5496], [48.6676, 2.4444, 51.1937, 8.2326], [42.8343, 4.3116, 45.2796, 7.6780] ] }, { "minLevel": 9, "maxLevel": 20, "label": "OGL", "alt": "Open Government Licence v.1.0.", "boxes": [
Map Tile API Developer's Guide 369► API Reference
[51.5011, -5.3731, 52.6691, -5.1981], [53.8371, -8.1821, 59.6771, -1.2194], [50.3331, -5.1981, 53.8371, -1.2194], [50.3331, -1.2194, 55.0051, 1.7646], [49.1651, -7.9476, 50.3331, -1.9796] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Swisstopo", "alt": "Topografische Grundlage: copyright Bundesamt fur Landestopographie", "boxes": [ [45.8206, 6.8641, 47.4100, 7.3171], [47.4100, 6.9280, 47.5272, 7.3171], [47.2863, 9.5821, 47.5004, 9.6893], [46.0972, 8.5106, 46.2180, 8.6761], [46.0193, 8.6761, 46.2180, 9.1291], [45.7831, 8.7540, 46.0193, 9.1167], [46.2703, 9.4435, 46.4166, 9.8658], [46.4166, 6.4111, 47.0127, 6.8641], [46.2180, 8.2231, 46.4166, 9.1291], [46.5237, 10.2370, 46.6153, 10.4882], [46.2131, 10.0449, 46.2643, 10.1820], [46.1195, 5.9453, 46.2180, 6.3156], [47.0127, 9.5821, 47.0721, 9.9106], [46.6153, 9.5821, 47.0127, 10.4882], [47.6087, 8.6761, 47.8074, 9.4309], [46.4140, 10.0351, 46.6153, 10.1740], [46.4166, 9.5821, 46.6153, 10.0351], [46.1024, 6.7620, 46.4166, 6.8641], [46.4166, 7.3171, 47.6087, 9.5821], [46.3513, 9.8639, 46.4166, 10.0351], [46.6153, 6.1662, 46.7577, 6.4111], [47.0127, 6.6305, 47.1914, 6.8641], [46.3367, 10.0312, 46.4166, 10.1725], [47.6087, 8.2231, 47.8074, 8.6761], [46.1180, 9.1291, 46.4166, 9.3037], [46.0193, 7.3171, 46.4166, 8.2231], [45.8846, 7.3171, 46.0193, 8.0455], [46.2654, 9.9778, 46.3547, 10.0368], [46.2180, 5.9581, 46.6153, 6.4111] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Cenacarta", "alt": "Certain Data for Mozambique provided by Cenacarta 2014 by Cenacarta", "boxes": [ [-16.0985, 30.1219, -13.9704, 33.7148], [-22.9890, 31.1878, -18.8084, 36.5975], [-15.9653, 33.6194, -10.3973, 41.2432], [-18.8203, 31.8425, -15.6508, 36.5975], [-26.8763, 31.1878, -22.4084, 35.7659], [-24.9908, 34.2964, -23.3847, 35.6707], [-16.3417, 30.7148, -14.0950, 34.9419], [-17.1457, 38.6588, -15.8415, 40.2757] ] }, { "minLevel": 11, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [
Map Tile API Developer's Guide 370► API Reference
[45.7302, 28.2568, 47.4471, 29.2353], [46.7892, 29.2282, 47.4471, 29.9684], [45.7302, 28.5878, 46.2901, 29.0637], [46.8530, 26.5110, 48.6163, 29.3448], [46.3002, 29.2029, 46.5592, 30.2333], [45.4102, 28.0701, 46.4249, 28.5878], [45.4154, 28.0081, 46.1325, 28.4224], [46.4187, 28.0753, 47.9267, 29.3100] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Statkart", "alt": "Copyright 2000; Norwegian Mapping Authority", "boxes": [ [68.8789, 27.8446, 71.4071, 32.1402], [68.4773, 24.6595, 71.3952, 26.3932], [61.0315, 6.1059, 70.9952, 18.0586], [66.1997, 15.2505, 67.3135, 16.3893], [63.9575, 13.0203, 65.6822, 14.7214], [69.6571, 25.9972, 71.4071, 28.8856], [59.2422, 9.9664, 63.2018, 13.0634], [56.4440, 2.9492, 63.9455, 12.0640] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [56.3085, 21.6724, 57.8204, 23.3336], [55.9347, 20.7407, 57.7144, 21.8250], [56.1948, 23.0950, 57.2653, 24.2779] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Deutschland", "alt": "Die Grundlagendaten wurden mit Genehmigung der zustandigen Behorden entnommen", "boxes": [ [51.9414, 6.7881, 53.8624, 7.7050], [47.2702, 7.7050, 55.0556, 13.2064], [48.0487, 13.2064, 49.6058, 13.9895], [50.3844, 13.2064, 54.2771, 15.0401], [48.8273, 5.8712, 51.9414, 7.7050] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Sri Lanka", "alt": "This product incorporates original source digital data obtained from the Survey Department of Sri Lanka. 2009 Survey Department of Sri Lanka The data has been used with the permission of the Survey Department of Sri Lanka", "boxes": [ [5.8461, 79.5067, 9.9652, 82.0121] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Lantmateriet",
Map Tile API Developer's Guide 371► API Reference
"alt": "Based upon electronic data National Land Survey Sweden.", "boxes": [ [58.0209, 17.3803, 62.5323, 19.7075], [56.8124, 17.7151, 58.4792, 19.8137], [55.2659, 13.7838, 58.0209, 17.4660], [58.0209, 11.5126, 64.3169, 17.4803], [62.5323, 15.7813, 69.3138, 25.2754], [55.1529, 12.3680, 56.6521, 13.7838], [60.9048, 13.0830, 68.0183, 18.3797] ] }, { "minLevel": 9, "maxLevel": 20, "label": "ITA", "alt": "La Banca Dati Italiana e stata prodotta usando quale riferimento anche cartografia numerica ed al tratto prodotta e fornita dalla Regione Toscana", "boxes": [ [45.5627, 12.8285, 46.6783, 13.9860], [36.6566, 11.8869, 36.8801, 12.1816], [44.1083, 6.6130, 45.2558, 7.2468], [39.2141, 13.5406, 43.0524, 16.4857], [45.6248, 6.8008, 45.8575, 6.9794], [42.6396, 13.3581, 43.6743, 14.0461], [46.7941, 10.3931, 47.0561, 11.6257], [35.3758, 11.8034, 40.0397, 19.4309], [38.1821, 6.8824, 47.2069, 14.1446] ] }, { "minLevel": 6, "maxLevel": 20, "label": "2014 NavInfo", "alt": "copyright 2014 NavInfo Co Ltd. All Rights Reserved", "boxes": [ [20.7754, 106.5576, 22.7754, 113.5576], [28.6334, 93.5576, 28.7754, 94.0161], [42.7754, 111.5576, 45.7754, 115.5576], [32.7754, 120.5576, 33.5701, 120.8986], [21.7754, 113.5576, 22.7754, 116.5576], [42.7754, 79.5576, 45.7754, 94.5576], [23.7754, 117.5576, 24.7754, 118.5576], [42.7754, 94.5576, 44.7754, 96.5576], [21.7754, 98.5576, 22.7754, 104.5576], [28.7754, 82.5576, 29.7754, 98.5576], [24.7754, 117.5576, 25.7754, 119.5576], [38.7754, 120.5576, 39.7754, 124.5576], [29.7754, 120.5576, 32.7754, 122.5576], [41.7754, 79.2585, 41.8535, 79.5576], [29.7754, 122.5576, 31.7754, 123.5576], [27.6769, 91.7865, 27.7754, 92.1101], [27.7754, 117.5576, 29.7754, 122.5576], [18.7754, 108.5576, 20.7754, 111.5576], [29.7754, 79.5576, 42.7754, 120.5576], [36.7754, 121.5576, 37.7754, 123.5576], [48.7754, 86.6922, 49.2494, 88.1056], [40.7754, 120.5576, 42.7754, 128.5576], [25.7754, 117.5576, 26.7754, 120.5576], [47.7754, 85.4858, 48.7754, 90.1507], [49.7754, 127.5576, 50.7754, 128.5576], [30.7754, 78.5576, 36.7754, 79.5576], [23.7754, 97.5576, 28.7754, 98.5576], [26.7754, 117.5576, 27.7754, 121.5576], [22.7754, 98.5576, 29.7754, 117.5576], [20.7754, 99.5576, 21.7754, 102.5576], [42.7754, 110.3934, 44.7820, 111.5576], [36.7754, 73.5576, 40.7754, 79.5576],
Map Tile API Developer's Guide 372► API Reference
[49.7754, 118.4027, 50.9802, 119.5576], [25.1912, 119.5576, 25.7754, 119.9120], [27.7754, 84.5576, 28.7754, 93.5576], [17.7754, 108.5576, 18.7754, 110.5576], [24.5027, 118.5576, 24.7754, 118.8161], [52.7754, 119.9835, 53.5719, 126.1939], [32.2241, 78.3965, 32.6363, 78.5576], [35.7754, 120.5576, 38.7754, 121.5576], [40.7754, 76.5576, 41.7754, 79.5576], [42.7754, 115.5576, 49.7754, 131.5576], [44.8404, 131.5576, 48.4334, 134.8631], [47.9285, 115.4373, 48.2230, 115.5576], [45.7754, 82.3630, 46.2212, 82.5576], [45.7754, 82.5576, 47.7754, 91.5576], [41.7754, 128.5576, 42.7754, 131.5576], [49.7754, 119.5576, 52.7754, 127.5576], [35.4169, 77.1449, 35.7754, 78.5576], [27.2614, 88.7706, 27.7754, 89.2653], [28.2004, 96.2409, 28.7754, 97.5576], [39.7754, 120.5576, 40.7754, 126.5576] ] }, { "minLevel": 9, "maxLevel": 20, "label": "INEGI", "alt": "Fuente: INEGI (Instituto Nacional de Estadistica y Geografia)", "boxes": [ [18.0000, -95.0000, 20.0000, -87.0000], [17.4060, -91.0000, 18.0000, -88.7349], [28.0000, -101.0000, 29.4004, -99.9666], [32.0000, -117.1817, 32.7325, -113.1649], [15.5643, -97.9326, 16.0000, -95.2581], [24.0000, -113.0000, 26.0000, -97.0000], [16.0000, -91.0000, 16.9491, -90.3434], [18.0000, -115.0000, 20.0000, -109.0000], [28.0000, -119.0000, 32.0000, -103.0000], [14.4031, -94.2111, 16.0000, -91.0000], [26.0000, -117.0000, 28.0000, -99.0000], [20.0000, -90.6669, 22.0000, -86.6669], [26.0000, -99.0000, 26.4261, -97.5566], [16.0000, -103.0000, 18.0000, -91.0000], [22.0000, -111.0000, 24.0000, -97.0000], [18.0000, -107.0000, 22.0000, -95.0000] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Canada", "alt": "This data includes information taken with permission from Canadian authorities, including Her Majesty, Queens Printer for Ontario, Canada Post, GeoBase, Department of Natural Resources Canada. All rights reserved", "boxes": [ [78.0000, -115.0000, 80.0000, -101.0000], [70.0000, -77.0000, 74.0000, -67.0000], [80.0000, -69.0000, 82.0000, -61.0000], [62.0000, -141.0000, 70.0000, -63.0000], [41.9986, -83.0000, 44.0238, -77.4271], [56.0000, -81.0000, 62.0000, -63.0000], [50.0000, -57.0000, 54.0000, -55.0000], [48.0000, -129.0000, 56.0000, -57.0000], [56.0000, -63.0000, 68.0000, -61.0000], [70.0000, -125.9042, 78.0000, -77.0000], [56.0000, -135.0000, 58.0000, -87.0000], [46.0000, -87.5736, 48.0357, -57.0000], [52.0000, -135.0000, 56.0000, -129.0000], [82.0000, -91.0000, 84.0000, -61.0000],
Map Tile API Developer's Guide 373► API Reference
[46.3831, -57.0167, 49.9905, -50.9810], [58.0000, -141.0000, 62.0000, -91.0000], [44.0000, -85.0026, 46.0536, -59.0000] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [-21.4740, 55.1479, -20.7728, 55.9393] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [29.0724, 40.2408, 34.0557, 45.6538], [29.8076, 38.7937, 34.0739, 43.8802], [29.0724, 45.6538, 34.0557, 47.9928], [35.7168, 42.7138, 37.3779, 46.4809], [29.9029, 47.1930, 31.4399, 48.5938], [35.7168, 41.2402, 37.3779, 42.7138] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [44.8976, 13.8789, 46.5835, 18.1295], [42.1231, 14.4853, 44.8976, 18.6541], [42.5705, 15.6655, 43.3251, 17.0432], [44.8126, 16.5981, 45.7845, 19.5169], [44.9955, 16.1850, 45.1490, 16.4761], [45.4199, 18.1216, 45.9726, 19.1392] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Nepal", "alt": "Copyright Survey Department, Government of Nepal", "boxes": [ [30.1502, 81.3961, 30.4719, 82.2540], [27.4329, 81.6782, 27.9426, 82.8798], [28.2854, 79.7937, 30.6642, 82.2540], [26.4858, 83.0964, 29.4459, 85.7994], [26.2669, 85.5710, 28.4465, 88.2408] ] }, { "minLevel": 9, "maxLevel": 20, "label": "2014 THTC", "alt": "copyright 2014 Iran Maps provided by THTC", "boxes": [ [25.7411, 61.7923, 26.2083, 61.8881], [29.9265, 60.8423, 31.5665, 61.9599], [38.2632, 44.2983, 39.0496, 46.5449], [25.7433, 53.8979, 37.6020, 61.7923],
Map Tile API Developer's Guide 374► API Reference
[31.5665, 60.4947, 34.0374, 60.9660], [39.0244, 46.9254, 39.7910, 48.3969], [29.8177, 60.4678, 31.5665, 60.9671], [38.1617, 46.5449, 39.1950, 48.0120], [32.9515, 46.0457, 33.1362, 46.2203], [26.5239, 62.3114, 26.5998, 62.6364], [25.7433, 60.8544, 29.9265, 61.9791], [26.4634, 61.8391, 28.6155, 62.9147], [35.8416, 44.4164, 38.8818, 47.5346], [32.9552, 45.2424, 35.8416, 47.3873], [35.7409, 44.1806, 38.2632, 46.0286], [25.7783, 47.3792, 32.0891, 56.2187], [38.4003, 44.0023, 39.8596, 45.4530], [27.0181, 63.1942, 27.2641, 63.3436], [26.1964, 46.2203, 38.4489, 57.1922], [25.7411, 61.8081, 25.9431, 61.9006], [38.8953, 48.0120, 39.0229, 48.3415], [34.1048, 60.5115, 36.6543, 61.5751], [33.8976, 59.0624, 37.6020, 61.1473], [31.4968, 59.9152, 34.0374, 60.8423], [26.2013, 61.8221, 26.5448, 62.3152], [35.3974, 46.0286, 38.8972, 48.8454], [38.8972, 47.5269, 39.2823, 48.3741], [24.9003, 57.1430, 26.1964, 61.8081], [26.8134, 62.8691, 27.2641, 63.2960], [26.6245, 62.9016, 26.8405, 63.2208] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN Guatemala", "alt": "Aprobado por el INSTITUTO GEOGRAFICO NACIONAL Resolucion del IGN No 186-2011", "boxes": [ [13.7417, -91.8261, 14.1492, -89.8235], [16.4730, -90.6686, 16.5943, -90.6245], [14.0259, -89.8235, 14.1492, -89.6796], [14.1492, -90.6245, 16.5943, -89.0225], [16.5943, -91.4256, 17.8168, -89.0225], [14.1492, -92.2266, 16.1868, -90.6245] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [53.8757, 22.4807, 55.1024, 24.5276], [54.2630, 22.6378, 54.6908, 23.1253], [54.9394, 20.8924, 56.5027, 23.4230], [53.8579, 22.5790, 56.5027, 24.9113], [53.8579, 24.5937, 56.4848, 26.8994] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [35.1525, 33.5454, 35.7340, 34.6339], [34.8444, 33.6276, 35.2760, 34.1041] ] }, {
Map Tile API Developer's Guide 375► API Reference
"minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [49.1699, 19.3708, 52.6479, 23.8452], [50.3804, 23.7940, 50.6141, 24.1242], [51.6271, 18.2346, 55.0681, 24.1071], [50.3495, 23.3995, 51.0366, 24.1571], [51.0366, 23.1726, 52.2145, 23.7360], [52.7337, 14.0896, 53.0647, 14.3477], [49.5714, 22.2773, 51.4811, 23.7502], [50.8016, 23.3995, 51.5813, 24.1714], [48.9384, 21.8835, 49.9277, 22.9603] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [2.1134, -54.0010, 3.5684, -52.5112], [2.1062, -54.6066, 3.5684, -54.0010], [2.6665, -52.5112, 3.5742, -52.0258], [3.9930, -54.5201, 5.2588, -54.2990] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [15.6985, -61.9309, 16.5953, -61.0013] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [14.3135, -61.2546, 14.9680, -60.7258] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Jordan", "alt": "Royal Jordanian Geographic Centre", "boxes": [ [30.8890, 35.2899, 32.3179, 37.3047], [29.2293, 35.2899, 31.3679, 38.0203], [31.8515, 35.4964, 32.7823, 36.8242], [29.2293, 34.9258, 30.8890, 35.9751] ] }, { "minLevel": 9, "maxLevel": 20, "label": "BEV", "alt": "copyright Bundesamt fur Eich- und Vermessungswesen", "boxes": [
Map Tile API Developer's Guide 376► API Reference
[48.7534, 16.3752, 48.8317, 16.7250], [46.5375, 12.6822, 46.6390, 13.3457], [46.8181, 10.4415, 46.9033, 10.6752], [47.6962, 12.9642, 48.2248, 13.3457], [46.3748, 13.3457, 46.6390, 14.8717], [46.7953, 11.0567, 46.9033, 11.1249], [48.7534, 14.8717, 49.0177, 16.0162], [48.2248, 12.9642, 48.3571, 13.3457], [47.6962, 13.3457, 48.7534, 17.1607], [46.8219, 9.9561, 46.9033, 10.2682], [46.6390, 12.2012, 46.9033, 16.0162], [47.6962, 12.8955, 47.8109, 12.9642], [46.6390, 10.6752, 46.9033, 11.0567], [46.9033, 9.5307, 47.6962, 16.7792], [46.8266, 16.0162, 46.9033, 16.1893] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [58.0107, 27.4528, 58.7552, 27.6501], [57.8526, 24.2950, 57.9554, 24.7904], [58.7436, 27.4413, 59.4859, 28.2525], [57.8968, 21.7448, 59.3645, 23.4580], [57.9301, 23.4390, 59.7909, 27.4650], [57.7540, 23.1887, 57.8411, 23.2957] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [10.6629, -85.8099, 12.9543, -83.3936], [14.2095, -82.9224, 14.5307, -82.6012], [11.0412, -87.1376, 14.6525, -83.1509], [12.3118, -87.8420, 14.2011, -84.9162], [13.6161, -85.8103, 15.1814, -83.0464] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.4520, 13.7142, 46.8284, 16.3044], [45.4418, 13.5675, 45.5366, 13.6734], [45.4125, 13.6570, 45.6003, 13.9833], [45.4543, 14.0533, 45.7004, 14.6924], [45.5239, 14.6795, 45.5557, 14.7057], [45.5557, 14.5931, 46.1463, 15.7955], [46.8276, 15.9827, 46.8786, 16.2706], [45.5318, 13.5988, 45.5394, 13.6380], [45.5366, 13.3628, 46.5230, 13.9372], [45.3439, 14.6924, 45.7418, 15.4262] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics",
Map Tile API Developer's Guide 377► API Reference
"boxes": [ [47.4754, 38.4346, 50.1112, 40.3587], [47.7796, 23.7808, 52.3053, 30.3909], [45.8550, 30.3873, 51.8685, 37.3686], [47.9979, 23.0400, 48.0552, 23.1187], [50.7773, 34.6660, 51.2858, 35.5437], [47.7796, 23.6071, 50.6001, 25.5225], [44.0324, 29.5592, 46.3547, 37.3686], [44.9794, 29.0356, 47.9080, 30.3873], [50.5207, 23.4548, 51.7557, 24.4370], [51.6941, 34.3051, 51.9267, 34.4588], [51.7797, 30.5067, 52.4699, 34.3366], [46.3547, 34.8806, 50.8793, 38.6386], [47.9624, 23.1767, 48.1330, 23.5211], [48.3302, 22.1323, 49.0508, 22.5012], [47.9128, 22.4364, 50.5207, 23.9830], [47.9209, 22.1347, 48.5886, 23.2256], [47.7060, 24.7422, 47.8394, 25.2039] ] }, { "minLevel": 9, "maxLevel": 20, "label": "CNIG", "alt": "Informacion geografica propiedad del CNIG", "boxes": [ [37.3120, -6.8623, 39.3980, 0.2290], [38.2202, 3.0662, 40.2854, 5.1739], [36.8976, -7.5399, 41.6961, -6.5372], [39.3438, -7.6437, 39.7836, -7.2643], [35.2569, -2.9815, 35.3232, -2.9161], [35.6142, -7.0220, 37.9317, -1.2109], [27.4138, -18.2990, 29.4228, -13.2707], [35.8628, -5.3870, 35.9199, -5.2772], [38.4150, -6.7340, 43.7683, 3.4915], [27.4138, -18.2990, 29.4228, -13.2707] ] } ], "pedestrian": [ { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [-27.3403, 31.4364, -26.7719, 32.0286], [-27.0738, 30.7201, -26.2624, 31.5422], [-26.8455, 32.0275, -26.7719, 32.1475], [-26.8359, 30.8723, -25.6938, 32.1739] ] }, { "minLevel": 6, "maxLevel": 20, "label": "PSMA", "alt": "Copyright. Based on data provided under license from PSMA Australia Limited. Product incorporates data which is 2014 Telstra Corporation Limited, GM Holden Limited, Intelematics Australia Pty Ltd, HERE International LLC, Sentinel Content Pty Limited and Continental Pty Ltd", "boxes": [ [-32.0000, 113.0000, -20.0000, 151.0000], [-14.0000, 141.0000, -8.0000, 145.0000], [-30.0761, 167.0381, -28.0761, 169.0381], [-14.0000, 129.0000, -10.0000, 137.0000],
Map Tile API Developer's Guide 378► API Reference
[-38.0000, 135.0000, -32.0000, 151.0000], [-34.0000, 151.0000, -24.0000, 155.0000], [-34.0000, 127.0000, -32.0000, 135.0000], [-13.1672, 95.8626, -11.1672, 97.8626], [-20.0000, 123.0000, -14.0000, 147.0000], [-11.5539, 104.6728, -9.5539, 106.6728], [-44.0000, 141.0000, -38.0000, 149.0000], [-36.0000, 115.0000, -32.0000, 127.0000], [-20.0000, 121.0000, -16.0000, 123.0000] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IgeoE", "alt": "IgeoE - Portugal", "boxes": [ [39.3941, -7.5899, 39.6663, -6.9850], [40.9842, -7.3532, 41.2705, -6.5519], [36.5482, -32.0392, 40.4124, -23.6635], [32.2747, -17.3686, 33.1907, -15.9142], [41.7211, -7.2357, 42.0048, -6.5050], [39.6540, -7.5520, 40.2572, -6.7565], [36.9392, -9.0081, 38.4418, -7.2449], [39.4153, -8.4431, 41.9675, -7.2126], [37.9667, -7.2522, 38.3853, -6.8808], [38.4418, -8.9260, 39.5144, -6.7321], [30.1318, -15.8830, 30.1622, -15.8445], [39.4801, -9.1848, 42.1722, -7.8729], [38.1864, -9.5593, 39.5271, -8.8950], [40.1168, -7.4841, 40.9984, -6.7565], [41.2304, -7.3100, 41.7633, -6.5183] ] }, { "minLevel": 10, "maxLevel": 20, "label": "SOI", "alt": "Survey of Israel data source", "boxes": [ [29.3724, 34.2346, 31.5477, 35.4573], [32.6825, 35.0912, 33.1130, 35.7566], [32.7247, 35.3798, 33.1257, 35.9089], [30.9701, 34.4766, 33.1256, 35.6655] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGM", "alt": "INSTITUTO GEOGRAFICO MILITAR DEL ECUADOR AUTORIZACION No IGM-2011-01- PCO-01 DEL 25 DE ENERO DE 2011", "boxes": [ [0.4963, -78.4796, 0.8202, -77.2440], [-2.4189, -76.4202, -2.0950, -76.0083], [-2.7428, -80.9509, 1.1441, -80.5390], [-4.6863, -80.5390, 1.1441, -78.4796], [-3.0667, -78.0677, -2.7428, -77.2440], [-2.0950, -78.4796, 0.4963, -75.5964], [-1.4472, -75.5964, 0.1724, -75.1846], [-2.7428, -81.3628, -0.7994, -80.9509], [-3.7146, -78.4796, -2.0950, -78.0677], [-5.0102, -79.7153, -4.6863, -78.8915], [-2.7428, -78.0677, -2.0950, -76.4202], [1.1441, -79.3034, 1.4680, -78.4796] ] },
Map Tile API Developer's Guide 379► API Reference
{ "minLevel": 10, "maxLevel": 20, "label": "Geomatics", "alt": "Copyright Geomatics Ltd.", "boxes": [ [34.8037, 20.3974, 41.0512, 26.5331], [41.0512, 22.8393, 41.6370, 24.4931], [38.9765, 26.5331, 39.1817, 26.6201], [41.0512, 21.9014, 41.1740, 22.4426], [36.1209, 29.5552, 36.1723, 29.6034], [41.0512, 24.4883, 41.8654, 26.5489], [41.0512, 22.4426, 41.3788, 22.8625], [38.9687, 19.3748, 40.3571, 20.3974], [35.1058, 26.5331, 37.9255, 28.2956], [41.2829, 26.5380, 41.6486, 26.6501] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN France 2009 BD TOPO", "boxes": [ [48.7889, -2.0366, 51.1937, 2.7484], [44.8560, 6.2593, 45.8136, 7.2498], [44.5968, 6.6907, 45.0132, 7.1016], [42.2486, 0.3773, 46.1891, 6.8232], [45.7944, 6.8518, 46.1046, 7.1168], [46.5120, -5.2986, 48.9033, -2.1006], [47.3484, 7.1095, 48.6757, 7.8910], [45.8114, 5.9584, 46.5615, 6.9032], [41.3454, 8.4823, 43.1241, 9.6779], [42.5367, -2.1077, 46.5120, 2.1618], [46.5513, 6.1405, 47.3535, 7.0066], [45.8812, -2.1077, 48.9033, 6.7118], [47.2548, 6.3526, 48.6954, 7.5496], [48.6676, 2.4444, 51.1937, 8.2326], [42.8343, 4.3116, 45.2796, 7.6780] ] }, { "minLevel": 9, "maxLevel": 20, "label": "OGL", "alt": "Open Government Licence v.1.0.", "boxes": [ [51.5011, -5.3731, 52.6691, -5.1981], [53.8371, -8.1821, 59.6771, -1.2194], [50.3331, -5.1981, 53.8371, -1.2194], [50.3331, -1.2194, 55.0051, 1.7646], [49.1651, -7.9476, 50.3331, -1.9796] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Swisstopo", "alt": "Topografische Grundlage: copyright Bundesamt fur Landestopographie", "boxes": [ [45.8206, 6.8641, 47.4100, 7.3171], [47.4100, 6.9280, 47.5272, 7.3171], [47.2863, 9.5821, 47.5004, 9.6893], [46.0972, 8.5106, 46.2180, 8.6761], [46.0193, 8.6761, 46.2180, 9.1291], [45.7831, 8.7540, 46.0193, 9.1167],
Map Tile API Developer's Guide 380► API Reference
[46.2703, 9.4435, 46.4166, 9.8658], [46.4166, 6.4111, 47.0127, 6.8641], [46.2180, 8.2231, 46.4166, 9.1291], [46.5237, 10.2370, 46.6153, 10.4882], [46.2131, 10.0449, 46.2643, 10.1820], [46.1195, 5.9453, 46.2180, 6.3156], [47.0127, 9.5821, 47.0721, 9.9106], [46.6153, 9.5821, 47.0127, 10.4882], [47.6087, 8.6761, 47.8074, 9.4309], [46.4140, 10.0351, 46.6153, 10.1740], [46.4166, 9.5821, 46.6153, 10.0351], [46.1024, 6.7620, 46.4166, 6.8641], [46.4166, 7.3171, 47.6087, 9.5821], [46.3513, 9.8639, 46.4166, 10.0351], [46.6153, 6.1662, 46.7577, 6.4111], [47.0127, 6.6305, 47.1914, 6.8641], [46.3367, 10.0312, 46.4166, 10.1725], [47.6087, 8.2231, 47.8074, 8.6761], [46.1180, 9.1291, 46.4166, 9.3037], [46.0193, 7.3171, 46.4166, 8.2231], [45.8846, 7.3171, 46.0193, 8.0455], [46.2654, 9.9778, 46.3547, 10.0368], [46.2180, 5.9581, 46.6153, 6.4111] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Cenacarta", "alt": "Certain Data for Mozambique provided by Cenacarta 2014 by Cenacarta", "boxes": [ [-16.0985, 30.1219, -13.9704, 33.7148], [-22.9890, 31.1878, -18.8084, 36.5975], [-15.9653, 33.6194, -10.3973, 41.2432], [-18.8203, 31.8425, -15.6508, 36.5975], [-26.8763, 31.1878, -22.4084, 35.7659], [-24.9908, 34.2964, -23.3847, 35.6707], [-16.3417, 30.7148, -14.0950, 34.9419], [-17.1457, 38.6588, -15.8415, 40.2757] ] }, { "minLevel": 11, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.7302, 28.2568, 47.4471, 29.2353], [46.7892, 29.2282, 47.4471, 29.9684], [45.7302, 28.5878, 46.2901, 29.0637], [46.8530, 26.5110, 48.6163, 29.3448], [46.3002, 29.2029, 46.5592, 30.2333], [45.4102, 28.0701, 46.4249, 28.5878], [45.4154, 28.0081, 46.1325, 28.4224], [46.4187, 28.0753, 47.9267, 29.3100] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Statkart", "alt": "Copyright 2000; Norwegian Mapping Authority", "boxes": [ [68.8789, 27.8446, 71.4071, 32.1402], [68.4773, 24.6595, 71.3952, 26.3932], [61.0315, 6.1059, 70.9952, 18.0586],
Map Tile API Developer's Guide 381► API Reference
[66.1997, 15.2505, 67.3135, 16.3893], [63.9575, 13.0203, 65.6822, 14.7214], [69.6571, 25.9972, 71.4071, 28.8856], [59.2422, 9.9664, 63.2018, 13.0634], [56.4440, 2.9492, 63.9455, 12.0640] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [56.3085, 21.6724, 57.8204, 23.3336], [55.9347, 20.7407, 57.7144, 21.8250], [56.1948, 23.0950, 57.2653, 24.2779] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Deutschland", "alt": "Die Grundlagendaten wurden mit Genehmigung der zustandigen Behorden entnommen", "boxes": [ [51.9414, 6.7881, 53.8624, 7.7050], [47.2702, 7.7050, 55.0556, 13.2064], [48.0487, 13.2064, 49.6058, 13.9895], [50.3844, 13.2064, 54.2771, 15.0401], [48.8273, 5.8712, 51.9414, 7.7050] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Sri Lanka", "alt": "This product incorporates original source digital data obtained from the Survey Department of Sri Lanka. 2009 Survey Department of Sri Lanka The data has been used with the permission of the Survey Department of Sri Lanka", "boxes": [ [5.8461, 79.5067, 9.9652, 82.0121] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Lantmateriet", "alt": "Based upon electronic data National Land Survey Sweden.", "boxes": [ [58.0209, 17.3803, 62.5323, 19.7075], [56.8124, 17.7151, 58.4792, 19.8137], [55.2659, 13.7838, 58.0209, 17.4660], [58.0209, 11.5126, 64.3169, 17.4803], [62.5323, 15.7813, 69.3138, 25.2754], [55.1529, 12.3680, 56.6521, 13.7838], [60.9048, 13.0830, 68.0183, 18.3797] ] }, { "minLevel": 9, "maxLevel": 20, "label": "ITA", "alt": "La Banca Dati Italiana e stata prodotta usando quale riferimento anche cartografia numerica ed al tratto prodotta e fornita dalla Regione Toscana", "boxes": [
Map Tile API Developer's Guide 382► API Reference
[45.5627, 12.8285, 46.6783, 13.9860], [36.6566, 11.8869, 36.8801, 12.1816], [44.1083, 6.6130, 45.2558, 7.2468], [39.2141, 13.5406, 43.0524, 16.4857], [45.6248, 6.8008, 45.8575, 6.9794], [42.6396, 13.3581, 43.6743, 14.0461], [46.7941, 10.3931, 47.0561, 11.6257], [35.3758, 11.8034, 40.0397, 19.4309], [38.1821, 6.8824, 47.2069, 14.1446] ] }, { "minLevel": 6, "maxLevel": 20, "label": "2014 NavInfo", "alt": "copyright 2014 NavInfo Co Ltd. All Rights Reserved", "boxes": [ [20.7754, 106.5576, 22.7754, 113.5576], [28.6334, 93.5576, 28.7754, 94.0161], [42.7754, 111.5576, 45.7754, 115.5576], [32.7754, 120.5576, 33.5701, 120.8986], [21.7754, 113.5576, 22.7754, 116.5576], [42.7754, 79.5576, 45.7754, 94.5576], [23.7754, 117.5576, 24.7754, 118.5576], [42.7754, 94.5576, 44.7754, 96.5576], [21.7754, 98.5576, 22.7754, 104.5576], [28.7754, 82.5576, 29.7754, 98.5576], [24.7754, 117.5576, 25.7754, 119.5576], [38.7754, 120.5576, 39.7754, 124.5576], [29.7754, 120.5576, 32.7754, 122.5576], [41.7754, 79.2585, 41.8535, 79.5576], [29.7754, 122.5576, 31.7754, 123.5576], [27.6769, 91.7865, 27.7754, 92.1101], [27.7754, 117.5576, 29.7754, 122.5576], [18.7754, 108.5576, 20.7754, 111.5576], [29.7754, 79.5576, 42.7754, 120.5576], [36.7754, 121.5576, 37.7754, 123.5576], [48.7754, 86.6922, 49.2494, 88.1056], [40.7754, 120.5576, 42.7754, 128.5576], [25.7754, 117.5576, 26.7754, 120.5576], [47.7754, 85.4858, 48.7754, 90.1507], [49.7754, 127.5576, 50.7754, 128.5576], [30.7754, 78.5576, 36.7754, 79.5576], [23.7754, 97.5576, 28.7754, 98.5576], [26.7754, 117.5576, 27.7754, 121.5576], [22.7754, 98.5576, 29.7754, 117.5576], [20.7754, 99.5576, 21.7754, 102.5576], [42.7754, 110.3934, 44.7820, 111.5576], [36.7754, 73.5576, 40.7754, 79.5576], [49.7754, 118.4027, 50.9802, 119.5576], [25.1912, 119.5576, 25.7754, 119.9120], [27.7754, 84.5576, 28.7754, 93.5576], [17.7754, 108.5576, 18.7754, 110.5576], [24.5027, 118.5576, 24.7754, 118.8161], [52.7754, 119.9835, 53.5719, 126.1939], [32.2241, 78.3965, 32.6363, 78.5576], [35.7754, 120.5576, 38.7754, 121.5576], [40.7754, 76.5576, 41.7754, 79.5576], [42.7754, 115.5576, 49.7754, 131.5576], [44.8404, 131.5576, 48.4334, 134.8631], [47.9285, 115.4373, 48.2230, 115.5576], [45.7754, 82.3630, 46.2212, 82.5576], [45.7754, 82.5576, 47.7754, 91.5576], [41.7754, 128.5576, 42.7754, 131.5576], [49.7754, 119.5576, 52.7754, 127.5576], [35.4169, 77.1449, 35.7754, 78.5576], [27.2614, 88.7706, 27.7754, 89.2653], [28.2004, 96.2409, 28.7754, 97.5576], [39.7754, 120.5576, 40.7754, 126.5576]
Map Tile API Developer's Guide 383► API Reference
] }, { "minLevel": 9, "maxLevel": 20, "label": "INEGI", "alt": "Fuente: INEGI (Instituto Nacional de Estadistica y Geografia)", "boxes": [ [18.0000, -95.0000, 20.0000, -87.0000], [17.4060, -91.0000, 18.0000, -88.7349], [28.0000, -101.0000, 29.4004, -99.9666], [32.0000, -117.1817, 32.7325, -113.1649], [15.5643, -97.9326, 16.0000, -95.2581], [24.0000, -113.0000, 26.0000, -97.0000], [16.0000, -91.0000, 16.9491, -90.3434], [18.0000, -115.0000, 20.0000, -109.0000], [28.0000, -119.0000, 32.0000, -103.0000], [14.4031, -94.2111, 16.0000, -91.0000], [26.0000, -117.0000, 28.0000, -99.0000], [20.0000, -90.6669, 22.0000, -86.6669], [26.0000, -99.0000, 26.4261, -97.5566], [16.0000, -103.0000, 18.0000, -91.0000], [22.0000, -111.0000, 24.0000, -97.0000], [18.0000, -107.0000, 22.0000, -95.0000] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Canada", "alt": "This data includes information taken with permission from Canadian authorities, including Her Majesty, Queens Printer for Ontario, Canada Post, GeoBase, Department of Natural Resources Canada. All rights reserved", "boxes": [ [78.0000, -115.0000, 80.0000, -101.0000], [70.0000, -77.0000, 74.0000, -67.0000], [80.0000, -69.0000, 82.0000, -61.0000], [62.0000, -141.0000, 70.0000, -63.0000], [41.9986, -83.0000, 44.0238, -77.4271], [56.0000, -81.0000, 62.0000, -63.0000], [50.0000, -57.0000, 54.0000, -55.0000], [48.0000, -129.0000, 56.0000, -57.0000], [56.0000, -63.0000, 68.0000, -61.0000], [70.0000, -125.9042, 78.0000, -77.0000], [56.0000, -135.0000, 58.0000, -87.0000], [46.0000, -87.5736, 48.0357, -57.0000], [52.0000, -135.0000, 56.0000, -129.0000], [82.0000, -91.0000, 84.0000, -61.0000], [46.3831, -57.0167, 49.9905, -50.9810], [58.0000, -141.0000, 62.0000, -91.0000], [44.0000, -85.0026, 46.0536, -59.0000] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [-21.4740, 55.1479, -20.7728, 55.9393] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Navteq", "alt": "Navteq",
Map Tile API Developer's Guide 384► API Reference
"boxes": [ [29.0724, 40.2408, 34.0557, 45.6538], [29.8076, 38.7937, 34.0739, 43.8802], [29.0724, 45.6538, 34.0557, 47.9928], [35.7168, 42.7138, 37.3779, 46.4809], [29.9029, 47.1930, 31.4399, 48.5938], [35.7168, 41.2402, 37.3779, 42.7138] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [44.8976, 13.8789, 46.5835, 18.1295], [42.1231, 14.4853, 44.8976, 18.6541], [42.5705, 15.6655, 43.3251, 17.0432], [44.8126, 16.5981, 45.7845, 19.5169], [44.9955, 16.1850, 45.1490, 16.4761], [45.4199, 18.1216, 45.9726, 19.1392] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Nepal", "alt": "Copyright Survey Department, Government of Nepal", "boxes": [ [30.1502, 81.3961, 30.4719, 82.2540], [27.4329, 81.6782, 27.9426, 82.8798], [28.2854, 79.7937, 30.6642, 82.2540], [26.4858, 83.0964, 29.4459, 85.7994], [26.2669, 85.5710, 28.4465, 88.2408] ] }, { "minLevel": 9, "maxLevel": 20, "label": "2014 THTC", "alt": "copyright 2014 Iran Maps provided by THTC", "boxes": [ [25.7411, 61.7923, 26.2083, 61.8881], [29.9265, 60.8423, 31.5665, 61.9599], [38.2632, 44.2983, 39.0496, 46.5449], [25.7433, 53.8979, 37.6020, 61.7923], [31.5665, 60.4947, 34.0374, 60.9660], [39.0244, 46.9254, 39.7910, 48.3969], [29.8177, 60.4678, 31.5665, 60.9671], [38.1617, 46.5449, 39.1950, 48.0120], [32.9515, 46.0457, 33.1362, 46.2203], [26.5239, 62.3114, 26.5998, 62.6364], [25.7433, 60.8544, 29.9265, 61.9791], [26.4634, 61.8391, 28.6155, 62.9147], [35.8416, 44.4164, 38.8818, 47.5346], [32.9552, 45.2424, 35.8416, 47.3873], [35.7409, 44.1806, 38.2632, 46.0286], [25.7783, 47.3792, 32.0891, 56.2187], [38.4003, 44.0023, 39.8596, 45.4530], [27.0181, 63.1942, 27.2641, 63.3436], [26.1964, 46.2203, 38.4489, 57.1922], [25.7411, 61.8081, 25.9431, 61.9006], [38.8953, 48.0120, 39.0229, 48.3415], [34.1048, 60.5115, 36.6543, 61.5751], [33.8976, 59.0624, 37.6020, 61.1473], [31.4968, 59.9152, 34.0374, 60.8423],
Map Tile API Developer's Guide 385► API Reference
[26.2013, 61.8221, 26.5448, 62.3152], [35.3974, 46.0286, 38.8972, 48.8454], [38.8972, 47.5269, 39.2823, 48.3741], [24.9003, 57.1430, 26.1964, 61.8081], [26.8134, 62.8691, 27.2641, 63.2960], [26.6245, 62.9016, 26.8405, 63.2208] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN Guatemala", "alt": "Aprobado por el INSTITUTO GEOGRAFICO NACIONAL Resolucion del IGN No 186-2011", "boxes": [ [13.7417, -91.8261, 14.1492, -89.8235], [16.4730, -90.6686, 16.5943, -90.6245], [14.0259, -89.8235, 14.1492, -89.6796], [14.1492, -90.6245, 16.5943, -89.0225], [16.5943, -91.4256, 17.8168, -89.0225], [14.1492, -92.2266, 16.1868, -90.6245] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [53.8757, 22.4807, 55.1024, 24.5276], [54.2630, 22.6378, 54.6908, 23.1253], [54.9394, 20.8924, 56.5027, 23.4230], [53.8579, 22.5790, 56.5027, 24.9113], [53.8579, 24.5937, 56.4848, 26.8994] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [35.1525, 33.5454, 35.7340, 34.6339], [34.8444, 33.6276, 35.2760, 34.1041] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [49.1699, 19.3708, 52.6479, 23.8452], [50.3804, 23.7940, 50.6141, 24.1242], [51.6271, 18.2346, 55.0681, 24.1071], [50.3495, 23.3995, 51.0366, 24.1571], [51.0366, 23.1726, 52.2145, 23.7360], [52.7337, 14.0896, 53.0647, 14.3477], [49.5714, 22.2773, 51.4811, 23.7502], [50.8016, 23.3995, 51.5813, 24.1714], [48.9384, 21.8835, 49.9277, 22.9603] ] }, { "minLevel": 10, "maxLevel": 20,
Map Tile API Developer's Guide 386► API Reference
"label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [2.1134, -54.0010, 3.5684, -52.5112], [2.1062, -54.6066, 3.5684, -54.0010], [2.6665, -52.5112, 3.5742, -52.0258], [3.9930, -54.5201, 5.2588, -54.2990] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [15.6985, -61.9309, 16.5953, -61.0013] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [14.3135, -61.2546, 14.9680, -60.7258] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Jordan", "alt": "Royal Jordanian Geographic Centre", "boxes": [ [30.8890, 35.2899, 32.3179, 37.3047], [29.2293, 35.2899, 31.3679, 38.0203], [31.8515, 35.4964, 32.7823, 36.8242], [29.2293, 34.9258, 30.8890, 35.9751] ] }, { "minLevel": 9, "maxLevel": 20, "label": "BEV", "alt": "copyright Bundesamt fur Eich- und Vermessungswesen", "boxes": [ [48.7534, 16.3752, 48.8317, 16.7250], [46.5375, 12.6822, 46.6390, 13.3457], [46.8181, 10.4415, 46.9033, 10.6752], [47.6962, 12.9642, 48.2248, 13.3457], [46.3748, 13.3457, 46.6390, 14.8717], [46.7953, 11.0567, 46.9033, 11.1249], [48.7534, 14.8717, 49.0177, 16.0162], [48.2248, 12.9642, 48.3571, 13.3457], [47.6962, 13.3457, 48.7534, 17.1607], [46.8219, 9.9561, 46.9033, 10.2682], [46.6390, 12.2012, 46.9033, 16.0162], [47.6962, 12.8955, 47.8109, 12.9642], [46.6390, 10.6752, 46.9033, 11.0567], [46.9033, 9.5307, 47.6962, 16.7792], [46.8266, 16.0162, 46.9033, 16.1893] ] }, { "minLevel": 10, "maxLevel": 20,
Map Tile API Developer's Guide 387► API Reference
"label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [58.0107, 27.4528, 58.7552, 27.6501], [57.8526, 24.2950, 57.9554, 24.7904], [58.7436, 27.4413, 59.4859, 28.2525], [57.8968, 21.7448, 59.3645, 23.4580], [57.9301, 23.4390, 59.7909, 27.4650], [57.7540, 23.1887, 57.8411, 23.2957] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [10.6629, -85.8099, 12.9543, -83.3936], [14.2095, -82.9224, 14.5307, -82.6012], [11.0412, -87.1376, 14.6525, -83.1509], [12.3118, -87.8420, 14.2011, -84.9162], [13.6161, -85.8103, 15.1814, -83.0464] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.4520, 13.7142, 46.8284, 16.3044], [45.4418, 13.5675, 45.5366, 13.6734], [45.4125, 13.6570, 45.6003, 13.9833], [45.4543, 14.0533, 45.7004, 14.6924], [45.5239, 14.6795, 45.5557, 14.7057], [45.5557, 14.5931, 46.1463, 15.7955], [46.8276, 15.9827, 46.8786, 16.2706], [45.5318, 13.5988, 45.5394, 13.6380], [45.5366, 13.3628, 46.5230, 13.9372], [45.3439, 14.6924, 45.7418, 15.4262] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [47.4754, 38.4346, 50.1112, 40.3587], [47.7796, 23.7808, 52.3053, 30.3909], [45.8550, 30.3873, 51.8685, 37.3686], [47.9979, 23.0400, 48.0552, 23.1187], [50.7773, 34.6660, 51.2858, 35.5437], [47.7796, 23.6071, 50.6001, 25.5225], [44.0324, 29.5592, 46.3547, 37.3686], [44.9794, 29.0356, 47.9080, 30.3873], [50.5207, 23.4548, 51.7557, 24.4370], [51.6941, 34.3051, 51.9267, 34.4588], [51.7797, 30.5067, 52.4699, 34.3366], [46.3547, 34.8806, 50.8793, 38.6386], [47.9624, 23.1767, 48.1330, 23.5211], [48.3302, 22.1323, 49.0508, 22.5012], [47.9128, 22.4364, 50.5207, 23.9830], [47.9209, 22.1347, 48.5886, 23.2256], [47.7060, 24.7422, 47.8394, 25.2039] ]
Map Tile API Developer's Guide 388► API Reference
}, { "minLevel": 9, "maxLevel": 20, "label": "CNIG", "alt": "Informacion geografica propiedad del CNIG", "boxes": [ [37.3120, -6.8623, 39.3980, 0.2290], [38.2202, 3.0662, 40.2854, 5.1739], [36.8976, -7.5399, 41.6961, -6.5372], [39.3438, -7.6437, 39.7836, -7.2643], [35.2569, -2.9815, 35.3232, -2.9161], [35.6142, -7.0220, 37.9317, -1.2109], [27.4138, -18.2990, 29.4228, -13.2707], [35.8628, -5.3870, 35.9199, -5.2772], [38.4150, -6.7340, 43.7683, 3.4915], [27.4138, -18.2990, 29.4228, -13.2707] ] } ], "satellite": [ { "minLevel": 0, "maxLevel": 20, "label": "2014 DigitalGlobe", "alt": "copyright 2014 DigitalGlobe, Inc." }, { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [-27.3403, 31.4364, -26.7719, 32.0286], [-27.0738, 30.7201, -26.2624, 31.5422], [-26.8455, 32.0275, -26.7719, 32.1475], [-26.8359, 30.8723, -25.6938, 32.1739] ] }, { "minLevel": 6, "maxLevel": 20, "label": "PSMA", "alt": "Copyright. Based on data provided under license from PSMA Australia Limited. Product incorporates data which is 2014 Telstra Corporation Limited, GM Holden Limited, Intelematics Australia Pty Ltd, HERE International LLC, Sentinel Content Pty Limited and Continental Pty Ltd", "boxes": [ [-32.0000, 113.0000, -20.0000, 151.0000], [-14.0000, 141.0000, -8.0000, 145.0000], [-30.0761, 167.0381, -28.0761, 169.0381], [-14.0000, 129.0000, -10.0000, 137.0000], [-38.0000, 135.0000, -32.0000, 151.0000], [-34.0000, 151.0000, -24.0000, 155.0000], [-34.0000, 127.0000, -32.0000, 135.0000], [-13.1672, 95.8626, -11.1672, 97.8626], [-20.0000, 123.0000, -14.0000, 147.0000], [-11.5539, 104.6728, -9.5539, 106.6728], [-44.0000, 141.0000, -38.0000, 149.0000], [-36.0000, 115.0000, -32.0000, 127.0000], [-20.0000, 121.0000, -16.0000, 123.0000] ] }, { "minLevel": 9, "maxLevel": 20,
Map Tile API Developer's Guide 389► API Reference
"label": "IgeoE", "alt": "IgeoE - Portugal", "boxes": [ [39.3941, -7.5899, 39.6663, -6.9850], [40.9842, -7.3532, 41.2705, -6.5519], [36.5482, -32.0392, 40.4124, -23.6635], [32.2747, -17.3686, 33.1907, -15.9142], [41.7211, -7.2357, 42.0048, -6.5050], [39.6540, -7.5520, 40.2572, -6.7565], [36.9392, -9.0081, 38.4418, -7.2449], [39.4153, -8.4431, 41.9675, -7.2126], [37.9667, -7.2522, 38.3853, -6.8808], [38.4418, -8.9260, 39.5144, -6.7321], [30.1318, -15.8830, 30.1622, -15.8445], [39.4801, -9.1848, 42.1722, -7.8729], [38.1864, -9.5593, 39.5271, -8.8950], [40.1168, -7.4841, 40.9984, -6.7565], [41.2304, -7.3100, 41.7633, -6.5183] ] }, { "minLevel": 10, "maxLevel": 20, "label": "SOI", "alt": "Survey of Israel data source", "boxes": [ [29.3724, 34.2346, 31.5477, 35.4573], [32.6825, 35.0912, 33.1130, 35.7566], [32.7247, 35.3798, 33.1257, 35.9089], [30.9701, 34.4766, 33.1256, 35.6655] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGM", "alt": "INSTITUTO GEOGRAFICO MILITAR DEL ECUADOR AUTORIZACION No IGM-2011-01- PCO-01 DEL 25 DE ENERO DE 2011", "boxes": [ [0.4963, -78.4796, 0.8202, -77.2440], [-2.4189, -76.4202, -2.0950, -76.0083], [-2.7428, -80.9509, 1.1441, -80.5390], [-4.6863, -80.5390, 1.1441, -78.4796], [-3.0667, -78.0677, -2.7428, -77.2440], [-2.0950, -78.4796, 0.4963, -75.5964], [-1.4472, -75.5964, 0.1724, -75.1846], [-2.7428, -81.3628, -0.7994, -80.9509], [-3.7146, -78.4796, -2.0950, -78.0677], [-5.0102, -79.7153, -4.6863, -78.8915], [-2.7428, -78.0677, -2.0950, -76.4202], [1.1441, -79.3034, 1.4680, -78.4796] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Geomatics", "alt": "Copyright Geomatics Ltd.", "boxes": [ [34.8037, 20.3974, 41.0512, 26.5331], [41.0512, 22.8393, 41.6370, 24.4931], [38.9765, 26.5331, 39.1817, 26.6201], [41.0512, 21.9014, 41.1740, 22.4426], [36.1209, 29.5552, 36.1723, 29.6034], [41.0512, 24.4883, 41.8654, 26.5489], [41.0512, 22.4426, 41.3788, 22.8625],
Map Tile API Developer's Guide 390► API Reference
[38.9687, 19.3748, 40.3571, 20.3974], [35.1058, 26.5331, 37.9255, 28.2956], [41.2829, 26.5380, 41.6486, 26.6501] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN France 2009 BD TOPO", "boxes": [ [48.7889, -2.0366, 51.1937, 2.7484], [44.8560, 6.2593, 45.8136, 7.2498], [44.5968, 6.6907, 45.0132, 7.1016], [42.2486, 0.3773, 46.1891, 6.8232], [45.7944, 6.8518, 46.1046, 7.1168], [46.5120, -5.2986, 48.9033, -2.1006], [47.3484, 7.1095, 48.6757, 7.8910], [45.8114, 5.9584, 46.5615, 6.9032], [41.3454, 8.4823, 43.1241, 9.6779], [42.5367, -2.1077, 46.5120, 2.1618], [46.5513, 6.1405, 47.3535, 7.0066], [45.8812, -2.1077, 48.9033, 6.7118], [47.2548, 6.3526, 48.6954, 7.5496], [48.6676, 2.4444, 51.1937, 8.2326], [42.8343, 4.3116, 45.2796, 7.6780] ] }, { "minLevel": 9, "maxLevel": 20, "label": "OGL", "alt": "Open Government Licence v.1.0.", "boxes": [ [51.5011, -5.3731, 52.6691, -5.1981], [53.8371, -8.1821, 59.6771, -1.2194], [50.3331, -5.1981, 53.8371, -1.2194], [50.3331, -1.2194, 55.0051, 1.7646], [49.1651, -7.9476, 50.3331, -1.9796] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Swisstopo", "alt": "Topografische Grundlage: copyright Bundesamt fur Landestopographie", "boxes": [ [45.8206, 6.8641, 47.4100, 7.3171], [47.4100, 6.9280, 47.5272, 7.3171], [47.2863, 9.5821, 47.5004, 9.6893], [46.0972, 8.5106, 46.2180, 8.6761], [46.0193, 8.6761, 46.2180, 9.1291], [45.7831, 8.7540, 46.0193, 9.1167], [46.2703, 9.4435, 46.4166, 9.8658], [46.4166, 6.4111, 47.0127, 6.8641], [46.2180, 8.2231, 46.4166, 9.1291], [46.5237, 10.2370, 46.6153, 10.4882], [46.2131, 10.0449, 46.2643, 10.1820], [46.1195, 5.9453, 46.2180, 6.3156], [47.0127, 9.5821, 47.0721, 9.9106], [46.6153, 9.5821, 47.0127, 10.4882], [47.6087, 8.6761, 47.8074, 9.4309], [46.4140, 10.0351, 46.6153, 10.1740], [46.4166, 9.5821, 46.6153, 10.0351], [46.1024, 6.7620, 46.4166, 6.8641], [46.4166, 7.3171, 47.6087, 9.5821], [46.3513, 9.8639, 46.4166, 10.0351],
Map Tile API Developer's Guide 391► API Reference
[46.6153, 6.1662, 46.7577, 6.4111], [47.0127, 6.6305, 47.1914, 6.8641], [46.3367, 10.0312, 46.4166, 10.1725], [47.6087, 8.2231, 47.8074, 8.6761], [46.1180, 9.1291, 46.4166, 9.3037], [46.0193, 7.3171, 46.4166, 8.2231], [45.8846, 7.3171, 46.0193, 8.0455], [46.2654, 9.9778, 46.3547, 10.0368], [46.2180, 5.9581, 46.6153, 6.4111] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Cenacarta", "alt": "Certain Data for Mozambique provided by Cenacarta 2014 by Cenacarta", "boxes": [ [-16.0985, 30.1219, -13.9704, 33.7148], [-22.9890, 31.1878, -18.8084, 36.5975], [-15.9653, 33.6194, -10.3973, 41.2432], [-18.8203, 31.8425, -15.6508, 36.5975], [-26.8763, 31.1878, -22.4084, 35.7659], [-24.9908, 34.2964, -23.3847, 35.6707], [-16.3417, 30.7148, -14.0950, 34.9419], [-17.1457, 38.6588, -15.8415, 40.2757] ] }, { "minLevel": 11, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.7302, 28.2568, 47.4471, 29.2353], [46.7892, 29.2282, 47.4471, 29.9684], [45.7302, 28.5878, 46.2901, 29.0637], [46.8530, 26.5110, 48.6163, 29.3448], [46.3002, 29.2029, 46.5592, 30.2333], [45.4102, 28.0701, 46.4249, 28.5878], [45.4154, 28.0081, 46.1325, 28.4224], [46.4187, 28.0753, 47.9267, 29.3100] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Statkart", "alt": "Copyright 2000; Norwegian Mapping Authority", "boxes": [ [68.8789, 27.8446, 71.4071, 32.1402], [68.4773, 24.6595, 71.3952, 26.3932], [61.0315, 6.1059, 70.9952, 18.0586], [66.1997, 15.2505, 67.3135, 16.3893], [63.9575, 13.0203, 65.6822, 14.7214], [69.6571, 25.9972, 71.4071, 28.8856], [59.2422, 9.9664, 63.2018, 13.0634], [56.4440, 2.9492, 63.9455, 12.0640] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [
Map Tile API Developer's Guide 392► API Reference
[56.3085, 21.6724, 57.8204, 23.3336], [55.9347, 20.7407, 57.7144, 21.8250], [56.1948, 23.0950, 57.2653, 24.2779] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Deutschland", "alt": "Die Grundlagendaten wurden mit Genehmigung der zustandigen Behorden entnommen", "boxes": [ [51.9414, 6.7881, 53.8624, 7.7050], [47.2702, 7.7050, 55.0556, 13.2064], [48.0487, 13.2064, 49.6058, 13.9895], [50.3844, 13.2064, 54.2771, 15.0401], [48.8273, 5.8712, 51.9414, 7.7050] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Sri Lanka", "alt": "This product incorporates original source digital data obtained from the Survey Department of Sri Lanka. 2009 Survey Department of Sri Lanka The data has been used with the permission of the Survey Department of Sri Lanka", "boxes": [ [5.8461, 79.5067, 9.9652, 82.0121] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Lantmateriet", "alt": "Based upon electronic data National Land Survey Sweden.", "boxes": [ [58.0209, 17.3803, 62.5323, 19.7075], [56.8124, 17.7151, 58.4792, 19.8137], [55.2659, 13.7838, 58.0209, 17.4660], [58.0209, 11.5126, 64.3169, 17.4803], [62.5323, 15.7813, 69.3138, 25.2754], [55.1529, 12.3680, 56.6521, 13.7838], [60.9048, 13.0830, 68.0183, 18.3797] ] }, { "minLevel": 9, "maxLevel": 20, "label": "ITA", "alt": "La Banca Dati Italiana e stata prodotta usando quale riferimento anche cartografia numerica ed al tratto prodotta e fornita dalla Regione Toscana", "boxes": [ [45.5627, 12.8285, 46.6783, 13.9860], [36.6566, 11.8869, 36.8801, 12.1816], [44.1083, 6.6130, 45.2558, 7.2468], [39.2141, 13.5406, 43.0524, 16.4857], [45.6248, 6.8008, 45.8575, 6.9794], [42.6396, 13.3581, 43.6743, 14.0461], [46.7941, 10.3931, 47.0561, 11.6257], [35.3758, 11.8034, 40.0397, 19.4309], [38.1821, 6.8824, 47.2069, 14.1446] ] }, { "minLevel": 6, "maxLevel": 20,
Map Tile API Developer's Guide 393► API Reference
"label": "2014 NavInfo", "alt": "copyright 2014 NavInfo Co Ltd. All Rights Reserved", "boxes": [ [20.7754, 106.5576, 22.7754, 113.5576], [28.6334, 93.5576, 28.7754, 94.0161], [42.7754, 111.5576, 45.7754, 115.5576], [32.7754, 120.5576, 33.5701, 120.8986], [21.7754, 113.5576, 22.7754, 116.5576], [42.7754, 79.5576, 45.7754, 94.5576], [23.7754, 117.5576, 24.7754, 118.5576], [42.7754, 94.5576, 44.7754, 96.5576], [21.7754, 98.5576, 22.7754, 104.5576], [28.7754, 82.5576, 29.7754, 98.5576], [24.7754, 117.5576, 25.7754, 119.5576], [38.7754, 120.5576, 39.7754, 124.5576], [29.7754, 120.5576, 32.7754, 122.5576], [41.7754, 79.2585, 41.8535, 79.5576], [29.7754, 122.5576, 31.7754, 123.5576], [27.6769, 91.7865, 27.7754, 92.1101], [27.7754, 117.5576, 29.7754, 122.5576], [18.7754, 108.5576, 20.7754, 111.5576], [29.7754, 79.5576, 42.7754, 120.5576], [36.7754, 121.5576, 37.7754, 123.5576], [48.7754, 86.6922, 49.2494, 88.1056], [40.7754, 120.5576, 42.7754, 128.5576], [25.7754, 117.5576, 26.7754, 120.5576], [47.7754, 85.4858, 48.7754, 90.1507], [49.7754, 127.5576, 50.7754, 128.5576], [30.7754, 78.5576, 36.7754, 79.5576], [23.7754, 97.5576, 28.7754, 98.5576], [26.7754, 117.5576, 27.7754, 121.5576], [22.7754, 98.5576, 29.7754, 117.5576], [20.7754, 99.5576, 21.7754, 102.5576], [42.7754, 110.3934, 44.7820, 111.5576], [36.7754, 73.5576, 40.7754, 79.5576], [49.7754, 118.4027, 50.9802, 119.5576], [25.1912, 119.5576, 25.7754, 119.9120], [27.7754, 84.5576, 28.7754, 93.5576], [17.7754, 108.5576, 18.7754, 110.5576], [24.5027, 118.5576, 24.7754, 118.8161], [52.7754, 119.9835, 53.5719, 126.1939], [32.2241, 78.3965, 32.6363, 78.5576], [35.7754, 120.5576, 38.7754, 121.5576], [40.7754, 76.5576, 41.7754, 79.5576], [42.7754, 115.5576, 49.7754, 131.5576], [44.8404, 131.5576, 48.4334, 134.8631], [47.9285, 115.4373, 48.2230, 115.5576], [45.7754, 82.3630, 46.2212, 82.5576], [45.7754, 82.5576, 47.7754, 91.5576], [41.7754, 128.5576, 42.7754, 131.5576], [49.7754, 119.5576, 52.7754, 127.5576], [35.4169, 77.1449, 35.7754, 78.5576], [27.2614, 88.7706, 27.7754, 89.2653], [28.2004, 96.2409, 28.7754, 97.5576], [39.7754, 120.5576, 40.7754, 126.5576] ] }, { "minLevel": 9, "maxLevel": 20, "label": "INEGI", "alt": "Fuente: INEGI (Instituto Nacional de Estadistica y Geografia)", "boxes": [ [18.0000, -95.0000, 20.0000, -87.0000], [17.4060, -91.0000, 18.0000, -88.7349], [28.0000, -101.0000, 29.4004, -99.9666], [32.0000, -117.1817, 32.7325, -113.1649], [15.5643, -97.9326, 16.0000, -95.2581],
Map Tile API Developer's Guide 394► API Reference
[24.0000, -113.0000, 26.0000, -97.0000], [16.0000, -91.0000, 16.9491, -90.3434], [18.0000, -115.0000, 20.0000, -109.0000], [28.0000, -119.0000, 32.0000, -103.0000], [14.4031, -94.2111, 16.0000, -91.0000], [26.0000, -117.0000, 28.0000, -99.0000], [20.0000, -90.6669, 22.0000, -86.6669], [26.0000, -99.0000, 26.4261, -97.5566], [16.0000, -103.0000, 18.0000, -91.0000], [22.0000, -111.0000, 24.0000, -97.0000], [18.0000, -107.0000, 22.0000, -95.0000] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Canada", "alt": "This data includes information taken with permission from Canadian authorities, including Her Majesty, Queens Printer for Ontario, Canada Post, GeoBase, Department of Natural Resources Canada. All rights reserved", "boxes": [ [78.0000, -115.0000, 80.0000, -101.0000], [70.0000, -77.0000, 74.0000, -67.0000], [80.0000, -69.0000, 82.0000, -61.0000], [62.0000, -141.0000, 70.0000, -63.0000], [41.9986, -83.0000, 44.0238, -77.4271], [56.0000, -81.0000, 62.0000, -63.0000], [50.0000, -57.0000, 54.0000, -55.0000], [48.0000, -129.0000, 56.0000, -57.0000], [56.0000, -63.0000, 68.0000, -61.0000], [70.0000, -125.9042, 78.0000, -77.0000], [56.0000, -135.0000, 58.0000, -87.0000], [46.0000, -87.5736, 48.0357, -57.0000], [52.0000, -135.0000, 56.0000, -129.0000], [82.0000, -91.0000, 84.0000, -61.0000], [46.3831, -57.0167, 49.9905, -50.9810], [58.0000, -141.0000, 62.0000, -91.0000], [44.0000, -85.0026, 46.0536, -59.0000] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [-21.4740, 55.1479, -20.7728, 55.9393] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [29.0724, 40.2408, 34.0557, 45.6538], [29.8076, 38.7937, 34.0739, 43.8802], [29.0724, 45.6538, 34.0557, 47.9928], [35.7168, 42.7138, 37.3779, 46.4809], [29.9029, 47.1930, 31.4399, 48.5938], [35.7168, 41.2402, 37.3779, 42.7138] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics",
Map Tile API Developer's Guide 395► API Reference
"alt": "copyright EuroGeographics", "boxes": [ [44.8976, 13.8789, 46.5835, 18.1295], [42.1231, 14.4853, 44.8976, 18.6541], [42.5705, 15.6655, 43.3251, 17.0432], [44.8126, 16.5981, 45.7845, 19.5169], [44.9955, 16.1850, 45.1490, 16.4761], [45.4199, 18.1216, 45.9726, 19.1392] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Nepal", "alt": "Copyright Survey Department, Government of Nepal", "boxes": [ [30.1502, 81.3961, 30.4719, 82.2540], [27.4329, 81.6782, 27.9426, 82.8798], [28.2854, 79.7937, 30.6642, 82.2540], [26.4858, 83.0964, 29.4459, 85.7994], [26.2669, 85.5710, 28.4465, 88.2408] ] }, { "minLevel": 9, "maxLevel": 20, "label": "2014 THTC", "alt": "copyright 2014 Iran Maps provided by THTC", "boxes": [ [25.7411, 61.7923, 26.2083, 61.8881], [29.9265, 60.8423, 31.5665, 61.9599], [38.2632, 44.2983, 39.0496, 46.5449], [25.7433, 53.8979, 37.6020, 61.7923], [31.5665, 60.4947, 34.0374, 60.9660], [39.0244, 46.9254, 39.7910, 48.3969], [29.8177, 60.4678, 31.5665, 60.9671], [38.1617, 46.5449, 39.1950, 48.0120], [32.9515, 46.0457, 33.1362, 46.2203], [26.5239, 62.3114, 26.5998, 62.6364], [25.7433, 60.8544, 29.9265, 61.9791], [26.4634, 61.8391, 28.6155, 62.9147], [35.8416, 44.4164, 38.8818, 47.5346], [32.9552, 45.2424, 35.8416, 47.3873], [35.7409, 44.1806, 38.2632, 46.0286], [25.7783, 47.3792, 32.0891, 56.2187], [38.4003, 44.0023, 39.8596, 45.4530], [27.0181, 63.1942, 27.2641, 63.3436], [26.1964, 46.2203, 38.4489, 57.1922], [25.7411, 61.8081, 25.9431, 61.9006], [38.8953, 48.0120, 39.0229, 48.3415], [34.1048, 60.5115, 36.6543, 61.5751], [33.8976, 59.0624, 37.6020, 61.1473], [31.4968, 59.9152, 34.0374, 60.8423], [26.2013, 61.8221, 26.5448, 62.3152], [35.3974, 46.0286, 38.8972, 48.8454], [38.8972, 47.5269, 39.2823, 48.3741], [24.9003, 57.1430, 26.1964, 61.8081], [26.8134, 62.8691, 27.2641, 63.2960], [26.6245, 62.9016, 26.8405, 63.2208] ] }, { "minLevel": 0, "maxLevel": 20, "label": "2014 Microsoft Corp", "alt": "Copyright 2014 Microsoft Corp (Photographer)", "boxes":
Map Tile API Developer's Guide 396► API Reference
[ [43.0000, -9.0000, 43.8368, -1.4871], [47.6659, 17.0000, 48.1870, 17.1796], [49.0000, -3.0000, 53.0000, 7.0000], [25.0000, -83.0000, 43.0000, -80.0000], [54.9700, 15.0000, 55.4090, 15.2079], [58.8191, 16.9798, 60.0219, 19.3105], [49.0000, -95.1748, 49.4171, -94.7155], [24.4342, -81.8753, 25.0000, -80.0000], [53.0000, -3.0000, 61.0000, -1.0000], [51.0000, 13.0000, 57.0000, 15.0000], [59.8274, 23.9754, 61.0338, 26.0308], [43.0000, -77.0000, 45.1041, -71.4874], [45.9934, -70.7166, 47.5037, -67.7111], [51.1463, 15.0000, 51.1538, 15.0019], [28.0000, -86.0000, 49.0000, -83.0000], [37.0000, -125.0000, 49.0000, -86.0000], [41.7315, 3.0000, 43.0000, 3.3548], [45.5418, 13.0000, 47.0000, 13.9644], [53.0000, 4.6555, 53.7627, 7.0000], [38.8500, 8.3413, 39.0000, 9.0932], [34.0000, -80.0000, 43.0000, -74.0000], [43.0000, -1.0000, 49.0000, 7.0000], [29.2540, -105.6275, 31.0000, -104.0000], [49.0000, -11.0000, 59.0000, -3.0000], [50.4136, 13.0000, 51.0000, 14.4285], [36.9570, -8.0082, 37.0000, -7.8011], [38.8376, 17.0000, 39.5206, 17.2421], [47.0000, 13.0000, 49.0000, 17.0000], [43.0000, 13.0000, 43.8815, 13.8986], [39.6609, 17.0000, 41.1153, 18.6364], [43.0000, -79.1238, 43.5219, -76.7251], [46.2245, 13.3861, 47.0000, 16.5913], [38.4332, 1.1578, 40.4985, 4.6176], [53.0000, -1.0000, 54.7773, 0.5000], [42.9741, -9.3240, 43.3001, -8.9859], [38.2126, -9.5302, 39.9011, -9.0000], [48.3914, -5.1628, 48.5056, -5.0000], [35.9238, -6.6631, 37.0000, -1.8450], [51.1642, 15.0000, 51.3263, 15.0580], [25.6957, -100.1176, 28.0000, -96.8387], [40.0000, -74.0000, 43.0000, -68.0000], [32.5516, -80.0000, 34.0000, -77.7120], [50.8137, 14.5069, 51.0000, 14.9382], [37.0000, 13.0000, 43.0000, 17.0000], [43.0000, -83.0000, 44.1708, -82.3613], [60.2720, -1.0000, 60.8841, -0.7110], [36.9926, -8.9533, 37.0000, -8.9311], [47.0000, -5.0000, 49.0000, -1.0000], [37.4381, 12.0022, 38.2529, 13.0000], [37.0000, -9.0000, 43.0000, 1.0000], [41.0000, 1.0000, 43.0000, 3.0000], [31.0000, -122.0000, 37.0000, -86.0000], [39.0000, 7.0000, 61.0000, 13.0000], [49.0000, 13.0000, 49.3287, 13.4222], [35.4007, 11.8529, 37.0069, 14.7297], [44.3159, -68.0009, 45.9940, -66.8902], [43.0000, -1.5690, 46.2402, -1.0000], [42.4435, -9.3240, 43.0000, -9.0000], [46.2340, -2.6007, 47.0000, -1.0000], [43.0000, -71.5231, 46.0000, -68.0000], [28.0000, -104.0000, 31.0000, -86.0000], [36.6258, 14.3209, 37.0000, 15.2989] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN Guatemala",
Map Tile API Developer's Guide 397► API Reference
"alt": "Aprobado por el INSTITUTO GEOGRAFICO NACIONAL Resolucion del IGN No 186-2011", "boxes": [ [13.7417, -91.8261, 14.1492, -89.8235], [16.4730, -90.6686, 16.5943, -90.6245], [14.0259, -89.8235, 14.1492, -89.6796], [14.1492, -90.6245, 16.5943, -89.0225], [16.5943, -91.4256, 17.8168, -89.0225], [14.1492, -92.2266, 16.1868, -90.6245] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [53.8757, 22.4807, 55.1024, 24.5276], [54.2630, 22.6378, 54.6908, 23.1253], [54.9394, 20.8924, 56.5027, 23.4230], [53.8579, 22.5790, 56.5027, 24.9113], [53.8579, 24.5937, 56.4848, 26.8994] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [35.1525, 33.5454, 35.7340, 34.6339], [34.8444, 33.6276, 35.2760, 34.1041] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [49.1699, 19.3708, 52.6479, 23.8452], [50.3804, 23.7940, 50.6141, 24.1242], [51.6271, 18.2346, 55.0681, 24.1071], [50.3495, 23.3995, 51.0366, 24.1571], [51.0366, 23.1726, 52.2145, 23.7360], [52.7337, 14.0896, 53.0647, 14.3477], [49.5714, 22.2773, 51.4811, 23.7502], [50.8016, 23.3995, 51.5813, 24.1714], [48.9384, 21.8835, 49.9277, 22.9603] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [2.1134, -54.0010, 3.5684, -52.5112], [2.1062, -54.6066, 3.5684, -54.0010], [2.6665, -52.5112, 3.5742, -52.0258], [3.9930, -54.5201, 5.2588, -54.2990] ] }, { "minLevel": 11,
Map Tile API Developer's Guide 398► API Reference
"maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [15.6985, -61.9309, 16.5953, -61.0013] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [14.3135, -61.2546, 14.9680, -60.7258] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Jordan", "alt": "Royal Jordanian Geographic Centre", "boxes": [ [30.8890, 35.2899, 32.3179, 37.3047], [29.2293, 35.2899, 31.3679, 38.0203], [31.8515, 35.4964, 32.7823, 36.8242], [29.2293, 34.9258, 30.8890, 35.9751] ] }, { "minLevel": 9, "maxLevel": 20, "label": "BEV", "alt": "copyright Bundesamt fur Eich- und Vermessungswesen", "boxes": [ [48.7534, 16.3752, 48.8317, 16.7250], [46.5375, 12.6822, 46.6390, 13.3457], [46.8181, 10.4415, 46.9033, 10.6752], [47.6962, 12.9642, 48.2248, 13.3457], [46.3748, 13.3457, 46.6390, 14.8717], [46.7953, 11.0567, 46.9033, 11.1249], [48.7534, 14.8717, 49.0177, 16.0162], [48.2248, 12.9642, 48.3571, 13.3457], [47.6962, 13.3457, 48.7534, 17.1607], [46.8219, 9.9561, 46.9033, 10.2682], [46.6390, 12.2012, 46.9033, 16.0162], [47.6962, 12.8955, 47.8109, 12.9642], [46.6390, 10.6752, 46.9033, 11.0567], [46.9033, 9.5307, 47.6962, 16.7792], [46.8266, 16.0162, 46.9033, 16.1893] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [58.0107, 27.4528, 58.7552, 27.6501], [57.8526, 24.2950, 57.9554, 24.7904], [58.7436, 27.4413, 59.4859, 28.2525], [57.8968, 21.7448, 59.3645, 23.4580], [57.9301, 23.4390, 59.7909, 27.4650], [57.7540, 23.1887, 57.8411, 23.2957] ] },
Map Tile API Developer's Guide 399► API Reference
{ "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [10.6629, -85.8099, 12.9543, -83.3936], [14.2095, -82.9224, 14.5307, -82.6012], [11.0412, -87.1376, 14.6525, -83.1509], [12.3118, -87.8420, 14.2011, -84.9162], [13.6161, -85.8103, 15.1814, -83.0464] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.4520, 13.7142, 46.8284, 16.3044], [45.4418, 13.5675, 45.5366, 13.6734], [45.4125, 13.6570, 45.6003, 13.9833], [45.4543, 14.0533, 45.7004, 14.6924], [45.5239, 14.6795, 45.5557, 14.7057], [45.5557, 14.5931, 46.1463, 15.7955], [46.8276, 15.9827, 46.8786, 16.2706], [45.5318, 13.5988, 45.5394, 13.6380], [45.5366, 13.3628, 46.5230, 13.9372], [45.3439, 14.6924, 45.7418, 15.4262] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [47.4754, 38.4346, 50.1112, 40.3587], [47.7796, 23.7808, 52.3053, 30.3909], [45.8550, 30.3873, 51.8685, 37.3686], [47.9979, 23.0400, 48.0552, 23.1187], [50.7773, 34.6660, 51.2858, 35.5437], [47.7796, 23.6071, 50.6001, 25.5225], [44.0324, 29.5592, 46.3547, 37.3686], [44.9794, 29.0356, 47.9080, 30.3873], [50.5207, 23.4548, 51.7557, 24.4370], [51.6941, 34.3051, 51.9267, 34.4588], [51.7797, 30.5067, 52.4699, 34.3366], [46.3547, 34.8806, 50.8793, 38.6386], [47.9624, 23.1767, 48.1330, 23.5211], [48.3302, 22.1323, 49.0508, 22.5012], [47.9128, 22.4364, 50.5207, 23.9830], [47.9209, 22.1347, 48.5886, 23.2256], [47.7060, 24.7422, 47.8394, 25.2039] ] }, { "minLevel": 9, "maxLevel": 20, "label": "CNIG", "alt": "Informacion geografica propiedad del CNIG", "boxes": [ [37.3120, -6.8623, 39.3980, 0.2290], [38.2202, 3.0662, 40.2854, 5.1739], [36.8976, -7.5399, 41.6961, -6.5372], [39.3438, -7.6437, 39.7836, -7.2643],
Map Tile API Developer's Guide 400► API Reference
[35.2569, -2.9815, 35.3232, -2.9161], [35.6142, -7.0220, 37.9317, -1.2109], [27.4138, -18.2990, 29.4228, -13.2707], [35.8628, -5.3870, 35.9199, -5.2772], [38.4150, -6.7340, 43.7683, 3.4915], [27.4138, -18.2990, 29.4228, -13.2707] ] } ], "terrain": [ { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [-27.3403, 31.4364, -26.7719, 32.0286], [-27.0738, 30.7201, -26.2624, 31.5422], [-26.8455, 32.0275, -26.7719, 32.1475], [-26.8359, 30.8723, -25.6938, 32.1739] ] }, { "minLevel": 6, "maxLevel": 20, "label": "PSMA", "alt": "Copyright. Based on data provided under license from PSMA Australia Limited. Product incorporates data which is 2014 Telstra Corporation Limited, GM Holden Limited, Intelematics Australia Pty Ltd, HERE International LLC, Sentinel Content Pty Limited and Continental Pty Ltd", "boxes": [ [-32.0000, 113.0000, -20.0000, 151.0000], [-14.0000, 141.0000, -8.0000, 145.0000], [-30.0761, 167.0381, -28.0761, 169.0381], [-14.0000, 129.0000, -10.0000, 137.0000], [-38.0000, 135.0000, -32.0000, 151.0000], [-34.0000, 151.0000, -24.0000, 155.0000], [-34.0000, 127.0000, -32.0000, 135.0000], [-13.1672, 95.8626, -11.1672, 97.8626], [-20.0000, 123.0000, -14.0000, 147.0000], [-11.5539, 104.6728, -9.5539, 106.6728], [-44.0000, 141.0000, -38.0000, 149.0000], [-36.0000, 115.0000, -32.0000, 127.0000], [-20.0000, 121.0000, -16.0000, 123.0000] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IgeoE", "alt": "IgeoE - Portugal", "boxes": [ [39.3941, -7.5899, 39.6663, -6.9850], [40.9842, -7.3532, 41.2705, -6.5519], [36.5482, -32.0392, 40.4124, -23.6635], [32.2747, -17.3686, 33.1907, -15.9142], [41.7211, -7.2357, 42.0048, -6.5050], [39.6540, -7.5520, 40.2572, -6.7565], [36.9392, -9.0081, 38.4418, -7.2449], [39.4153, -8.4431, 41.9675, -7.2126], [37.9667, -7.2522, 38.3853, -6.8808], [38.4418, -8.9260, 39.5144, -6.7321], [30.1318, -15.8830, 30.1622, -15.8445], [39.4801, -9.1848, 42.1722, -7.8729], [38.1864, -9.5593, 39.5271, -8.8950], [40.1168, -7.4841, 40.9984, -6.7565],
Map Tile API Developer's Guide 401► API Reference
[41.2304, -7.3100, 41.7633, -6.5183] ] }, { "minLevel": 10, "maxLevel": 20, "label": "SOI", "alt": "Survey of Israel data source", "boxes": [ [29.3724, 34.2346, 31.5477, 35.4573], [32.6825, 35.0912, 33.1130, 35.7566], [32.7247, 35.3798, 33.1257, 35.9089], [30.9701, 34.4766, 33.1256, 35.6655] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGM", "alt": "INSTITUTO GEOGRAFICO MILITAR DEL ECUADOR AUTORIZACION No IGM-2011-01- PCO-01 DEL 25 DE ENERO DE 2011", "boxes": [ [0.4963, -78.4796, 0.8202, -77.2440], [-2.4189, -76.4202, -2.0950, -76.0083], [-2.7428, -80.9509, 1.1441, -80.5390], [-4.6863, -80.5390, 1.1441, -78.4796], [-3.0667, -78.0677, -2.7428, -77.2440], [-2.0950, -78.4796, 0.4963, -75.5964], [-1.4472, -75.5964, 0.1724, -75.1846], [-2.7428, -81.3628, -0.7994, -80.9509], [-3.7146, -78.4796, -2.0950, -78.0677], [-5.0102, -79.7153, -4.6863, -78.8915], [-2.7428, -78.0677, -2.0950, -76.4202], [1.1441, -79.3034, 1.4680, -78.4796] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Geomatics", "alt": "Copyright Geomatics Ltd.", "boxes": [ [34.8037, 20.3974, 41.0512, 26.5331], [41.0512, 22.8393, 41.6370, 24.4931], [38.9765, 26.5331, 39.1817, 26.6201], [41.0512, 21.9014, 41.1740, 22.4426], [36.1209, 29.5552, 36.1723, 29.6034], [41.0512, 24.4883, 41.8654, 26.5489], [41.0512, 22.4426, 41.3788, 22.8625], [38.9687, 19.3748, 40.3571, 20.3974], [35.1058, 26.5331, 37.9255, 28.2956], [41.2829, 26.5380, 41.6486, 26.6501] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN France 2009 BD TOPO", "boxes": [ [48.7889, -2.0366, 51.1937, 2.7484], [44.8560, 6.2593, 45.8136, 7.2498], [44.5968, 6.6907, 45.0132, 7.1016], [42.2486, 0.3773, 46.1891, 6.8232], [45.7944, 6.8518, 46.1046, 7.1168], [46.5120, -5.2986, 48.9033, -2.1006],
Map Tile API Developer's Guide 402► API Reference
[47.3484, 7.1095, 48.6757, 7.8910], [45.8114, 5.9584, 46.5615, 6.9032], [41.3454, 8.4823, 43.1241, 9.6779], [42.5367, -2.1077, 46.5120, 2.1618], [46.5513, 6.1405, 47.3535, 7.0066], [45.8812, -2.1077, 48.9033, 6.7118], [47.2548, 6.3526, 48.6954, 7.5496], [48.6676, 2.4444, 51.1937, 8.2326], [42.8343, 4.3116, 45.2796, 7.6780] ] }, { "minLevel": 9, "maxLevel": 20, "label": "OGL", "alt": "Open Government Licence v.1.0.", "boxes": [ [51.5011, -5.3731, 52.6691, -5.1981], [53.8371, -8.1821, 59.6771, -1.2194], [50.3331, -5.1981, 53.8371, -1.2194], [50.3331, -1.2194, 55.0051, 1.7646], [49.1651, -7.9476, 50.3331, -1.9796] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Swisstopo", "alt": "Topografische Grundlage: copyright Bundesamt fur Landestopographie", "boxes": [ [45.8206, 6.8641, 47.4100, 7.3171], [47.4100, 6.9280, 47.5272, 7.3171], [47.2863, 9.5821, 47.5004, 9.6893], [46.0972, 8.5106, 46.2180, 8.6761], [46.0193, 8.6761, 46.2180, 9.1291], [45.7831, 8.7540, 46.0193, 9.1167], [46.2703, 9.4435, 46.4166, 9.8658], [46.4166, 6.4111, 47.0127, 6.8641], [46.2180, 8.2231, 46.4166, 9.1291], [46.5237, 10.2370, 46.6153, 10.4882], [46.2131, 10.0449, 46.2643, 10.1820], [46.1195, 5.9453, 46.2180, 6.3156], [47.0127, 9.5821, 47.0721, 9.9106], [46.6153, 9.5821, 47.0127, 10.4882], [47.6087, 8.6761, 47.8074, 9.4309], [46.4140, 10.0351, 46.6153, 10.1740], [46.4166, 9.5821, 46.6153, 10.0351], [46.1024, 6.7620, 46.4166, 6.8641], [46.4166, 7.3171, 47.6087, 9.5821], [46.3513, 9.8639, 46.4166, 10.0351], [46.6153, 6.1662, 46.7577, 6.4111], [47.0127, 6.6305, 47.1914, 6.8641], [46.3367, 10.0312, 46.4166, 10.1725], [47.6087, 8.2231, 47.8074, 8.6761], [46.1180, 9.1291, 46.4166, 9.3037], [46.0193, 7.3171, 46.4166, 8.2231], [45.8846, 7.3171, 46.0193, 8.0455], [46.2654, 9.9778, 46.3547, 10.0368], [46.2180, 5.9581, 46.6153, 6.4111] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Cenacarta", "alt": "Certain Data for Mozambique provided by Cenacarta 2014 by Cenacarta", "boxes":
Map Tile API Developer's Guide 403► API Reference
[ [-16.0985, 30.1219, -13.9704, 33.7148], [-22.9890, 31.1878, -18.8084, 36.5975], [-15.9653, 33.6194, -10.3973, 41.2432], [-18.8203, 31.8425, -15.6508, 36.5975], [-26.8763, 31.1878, -22.4084, 35.7659], [-24.9908, 34.2964, -23.3847, 35.6707], [-16.3417, 30.7148, -14.0950, 34.9419], [-17.1457, 38.6588, -15.8415, 40.2757] ] }, { "minLevel": 11, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [45.7302, 28.2568, 47.4471, 29.2353], [46.7892, 29.2282, 47.4471, 29.9684], [45.7302, 28.5878, 46.2901, 29.0637], [46.8530, 26.5110, 48.6163, 29.3448], [46.3002, 29.2029, 46.5592, 30.2333], [45.4102, 28.0701, 46.4249, 28.5878], [45.4154, 28.0081, 46.1325, 28.4224], [46.4187, 28.0753, 47.9267, 29.3100] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Statkart", "alt": "Copyright 2000; Norwegian Mapping Authority", "boxes": [ [68.8789, 27.8446, 71.4071, 32.1402], [68.4773, 24.6595, 71.3952, 26.3932], [61.0315, 6.1059, 70.9952, 18.0586], [66.1997, 15.2505, 67.3135, 16.3893], [63.9575, 13.0203, 65.6822, 14.7214], [69.6571, 25.9972, 71.4071, 28.8856], [59.2422, 9.9664, 63.2018, 13.0634], [56.4440, 2.9492, 63.9455, 12.0640] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [56.3085, 21.6724, 57.8204, 23.3336], [55.9347, 20.7407, 57.7144, 21.8250], [56.1948, 23.0950, 57.2653, 24.2779] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Deutschland", "alt": "Die Grundlagendaten wurden mit Genehmigung der zustandigen Behorden entnommen", "boxes": [ [51.9414, 6.7881, 53.8624, 7.7050], [47.2702, 7.7050, 55.0556, 13.2064], [48.0487, 13.2064, 49.6058, 13.9895], [50.3844, 13.2064, 54.2771, 15.0401], [48.8273, 5.8712, 51.9414, 7.7050]
Map Tile API Developer's Guide 404► API Reference
] }, { "minLevel": 9, "maxLevel": 20, "label": "Sri Lanka", "alt": "This product incorporates original source digital data obtained from the Survey Department of Sri Lanka. 2009 Survey Department of Sri Lanka The data has been used with the permission of the Survey Department of Sri Lanka", "boxes": [ [5.8461, 79.5067, 9.9652, 82.0121] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Lantmateriet", "alt": "Based upon electronic data National Land Survey Sweden.", "boxes": [ [58.0209, 17.3803, 62.5323, 19.7075], [56.8124, 17.7151, 58.4792, 19.8137], [55.2659, 13.7838, 58.0209, 17.4660], [58.0209, 11.5126, 64.3169, 17.4803], [62.5323, 15.7813, 69.3138, 25.2754], [55.1529, 12.3680, 56.6521, 13.7838], [60.9048, 13.0830, 68.0183, 18.3797] ] }, { "minLevel": 9, "maxLevel": 20, "label": "ITA", "alt": "La Banca Dati Italiana e stata prodotta usando quale riferimento anche cartografia numerica ed al tratto prodotta e fornita dalla Regione Toscana", "boxes": [ [45.5627, 12.8285, 46.6783, 13.9860], [36.6566, 11.8869, 36.8801, 12.1816], [44.1083, 6.6130, 45.2558, 7.2468], [39.2141, 13.5406, 43.0524, 16.4857], [45.6248, 6.8008, 45.8575, 6.9794], [42.6396, 13.3581, 43.6743, 14.0461], [46.7941, 10.3931, 47.0561, 11.6257], [35.3758, 11.8034, 40.0397, 19.4309], [38.1821, 6.8824, 47.2069, 14.1446] ] }, { "minLevel": 6, "maxLevel": 20, "label": "2014 NavInfo", "alt": "copyright 2014 NavInfo Co Ltd. All Rights Reserved", "boxes": [ [20.7754, 106.5576, 22.7754, 113.5576], [28.6334, 93.5576, 28.7754, 94.0161], [42.7754, 111.5576, 45.7754, 115.5576], [32.7754, 120.5576, 33.5701, 120.8986], [21.7754, 113.5576, 22.7754, 116.5576], [42.7754, 79.5576, 45.7754, 94.5576], [23.7754, 117.5576, 24.7754, 118.5576], [42.7754, 94.5576, 44.7754, 96.5576], [21.7754, 98.5576, 22.7754, 104.5576], [28.7754, 82.5576, 29.7754, 98.5576], [24.7754, 117.5576, 25.7754, 119.5576], [38.7754, 120.5576, 39.7754, 124.5576], [29.7754, 120.5576, 32.7754, 122.5576], [41.7754, 79.2585, 41.8535, 79.5576],
Map Tile API Developer's Guide 405► API Reference
[29.7754, 122.5576, 31.7754, 123.5576], [27.6769, 91.7865, 27.7754, 92.1101], [27.7754, 117.5576, 29.7754, 122.5576], [18.7754, 108.5576, 20.7754, 111.5576], [29.7754, 79.5576, 42.7754, 120.5576], [36.7754, 121.5576, 37.7754, 123.5576], [48.7754, 86.6922, 49.2494, 88.1056], [40.7754, 120.5576, 42.7754, 128.5576], [25.7754, 117.5576, 26.7754, 120.5576], [47.7754, 85.4858, 48.7754, 90.1507], [49.7754, 127.5576, 50.7754, 128.5576], [30.7754, 78.5576, 36.7754, 79.5576], [23.7754, 97.5576, 28.7754, 98.5576], [26.7754, 117.5576, 27.7754, 121.5576], [22.7754, 98.5576, 29.7754, 117.5576], [20.7754, 99.5576, 21.7754, 102.5576], [42.7754, 110.3934, 44.7820, 111.5576], [36.7754, 73.5576, 40.7754, 79.5576], [49.7754, 118.4027, 50.9802, 119.5576], [25.1912, 119.5576, 25.7754, 119.9120], [27.7754, 84.5576, 28.7754, 93.5576], [17.7754, 108.5576, 18.7754, 110.5576], [24.5027, 118.5576, 24.7754, 118.8161], [52.7754, 119.9835, 53.5719, 126.1939], [32.2241, 78.3965, 32.6363, 78.5576], [35.7754, 120.5576, 38.7754, 121.5576], [40.7754, 76.5576, 41.7754, 79.5576], [42.7754, 115.5576, 49.7754, 131.5576], [44.8404, 131.5576, 48.4334, 134.8631], [47.9285, 115.4373, 48.2230, 115.5576], [45.7754, 82.3630, 46.2212, 82.5576], [45.7754, 82.5576, 47.7754, 91.5576], [41.7754, 128.5576, 42.7754, 131.5576], [49.7754, 119.5576, 52.7754, 127.5576], [35.4169, 77.1449, 35.7754, 78.5576], [27.2614, 88.7706, 27.7754, 89.2653], [28.2004, 96.2409, 28.7754, 97.5576], [39.7754, 120.5576, 40.7754, 126.5576] ] }, { "minLevel": 9, "maxLevel": 20, "label": "INEGI", "alt": "Fuente: INEGI (Instituto Nacional de Estadistica y Geografia)", "boxes": [ [18.0000, -95.0000, 20.0000, -87.0000], [17.4060, -91.0000, 18.0000, -88.7349], [28.0000, -101.0000, 29.4004, -99.9666], [32.0000, -117.1817, 32.7325, -113.1649], [15.5643, -97.9326, 16.0000, -95.2581], [24.0000, -113.0000, 26.0000, -97.0000], [16.0000, -91.0000, 16.9491, -90.3434], [18.0000, -115.0000, 20.0000, -109.0000], [28.0000, -119.0000, 32.0000, -103.0000], [14.4031, -94.2111, 16.0000, -91.0000], [26.0000, -117.0000, 28.0000, -99.0000], [20.0000, -90.6669, 22.0000, -86.6669], [26.0000, -99.0000, 26.4261, -97.5566], [16.0000, -103.0000, 18.0000, -91.0000], [22.0000, -111.0000, 24.0000, -97.0000], [18.0000, -107.0000, 22.0000, -95.0000] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Canada",
Map Tile API Developer's Guide 406► API Reference
"alt": "This data includes information taken with permission from Canadian authorities, including Her Majesty, Queens Printer for Ontario, Canada Post, GeoBase, Department of Natural Resources Canada. All rights reserved", "boxes": [ [78.0000, -115.0000, 80.0000, -101.0000], [70.0000, -77.0000, 74.0000, -67.0000], [80.0000, -69.0000, 82.0000, -61.0000], [62.0000, -141.0000, 70.0000, -63.0000], [41.9986, -83.0000, 44.0238, -77.4271], [56.0000, -81.0000, 62.0000, -63.0000], [50.0000, -57.0000, 54.0000, -55.0000], [48.0000, -129.0000, 56.0000, -57.0000], [56.0000, -63.0000, 68.0000, -61.0000], [70.0000, -125.9042, 78.0000, -77.0000], [56.0000, -135.0000, 58.0000, -87.0000], [46.0000, -87.5736, 48.0357, -57.0000], [52.0000, -135.0000, 56.0000, -129.0000], [82.0000, -91.0000, 84.0000, -61.0000], [46.3831, -57.0167, 49.9905, -50.9810], [58.0000, -141.0000, 62.0000, -91.0000], [44.0000, -85.0026, 46.0536, -59.0000] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [-21.4740, 55.1479, -20.7728, 55.9393] ] }, { "minLevel": 6, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [29.0724, 40.2408, 34.0557, 45.6538], [29.8076, 38.7937, 34.0739, 43.8802], [29.0724, 45.6538, 34.0557, 47.9928], [35.7168, 42.7138, 37.3779, 46.4809], [29.9029, 47.1930, 31.4399, 48.5938], [35.7168, 41.2402, 37.3779, 42.7138] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [44.8976, 13.8789, 46.5835, 18.1295], [42.1231, 14.4853, 44.8976, 18.6541], [42.5705, 15.6655, 43.3251, 17.0432], [44.8126, 16.5981, 45.7845, 19.5169], [44.9955, 16.1850, 45.1490, 16.4761], [45.4199, 18.1216, 45.9726, 19.1392] ] }, { "minLevel": 9, "maxLevel": 20, "label": "Nepal", "alt": "Copyright Survey Department, Government of Nepal", "boxes":
Map Tile API Developer's Guide 407► API Reference
[ [30.1502, 81.3961, 30.4719, 82.2540], [27.4329, 81.6782, 27.9426, 82.8798], [28.2854, 79.7937, 30.6642, 82.2540], [26.4858, 83.0964, 29.4459, 85.7994], [26.2669, 85.5710, 28.4465, 88.2408] ] }, { "minLevel": 9, "maxLevel": 20, "label": "2014 THTC", "alt": "copyright 2014 Iran Maps provided by THTC", "boxes": [ [25.7411, 61.7923, 26.2083, 61.8881], [29.9265, 60.8423, 31.5665, 61.9599], [38.2632, 44.2983, 39.0496, 46.5449], [25.7433, 53.8979, 37.6020, 61.7923], [31.5665, 60.4947, 34.0374, 60.9660], [39.0244, 46.9254, 39.7910, 48.3969], [29.8177, 60.4678, 31.5665, 60.9671], [38.1617, 46.5449, 39.1950, 48.0120], [32.9515, 46.0457, 33.1362, 46.2203], [26.5239, 62.3114, 26.5998, 62.6364], [25.7433, 60.8544, 29.9265, 61.9791], [26.4634, 61.8391, 28.6155, 62.9147], [35.8416, 44.4164, 38.8818, 47.5346], [32.9552, 45.2424, 35.8416, 47.3873], [35.7409, 44.1806, 38.2632, 46.0286], [25.7783, 47.3792, 32.0891, 56.2187], [38.4003, 44.0023, 39.8596, 45.4530], [27.0181, 63.1942, 27.2641, 63.3436], [26.1964, 46.2203, 38.4489, 57.1922], [25.7411, 61.8081, 25.9431, 61.9006], [38.8953, 48.0120, 39.0229, 48.3415], [34.1048, 60.5115, 36.6543, 61.5751], [33.8976, 59.0624, 37.6020, 61.1473], [31.4968, 59.9152, 34.0374, 60.8423], [26.2013, 61.8221, 26.5448, 62.3152], [35.3974, 46.0286, 38.8972, 48.8454], [38.8972, 47.5269, 39.2823, 48.3741], [24.9003, 57.1430, 26.1964, 61.8081], [26.8134, 62.8691, 27.2641, 63.2960], [26.6245, 62.9016, 26.8405, 63.2208] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN Guatemala", "alt": "Aprobado por el INSTITUTO GEOGRAFICO NACIONAL Resolucion del IGN No 186-2011", "boxes": [ [13.7417, -91.8261, 14.1492, -89.8235], [16.4730, -90.6686, 16.5943, -90.6245], [14.0259, -89.8235, 14.1492, -89.6796], [14.1492, -90.6245, 16.5943, -89.0225], [16.5943, -91.4256, 17.8168, -89.0225], [14.1492, -92.2266, 16.1868, -90.6245] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [
Map Tile API Developer's Guide 408► API Reference
[53.8757, 22.4807, 55.1024, 24.5276], [54.2630, 22.6378, 54.6908, 23.1253], [54.9394, 20.8924, 56.5027, 23.4230], [53.8579, 22.5790, 56.5027, 24.9113], [53.8579, 24.5937, 56.4848, 26.8994] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [35.1525, 33.5454, 35.7340, 34.6339], [34.8444, 33.6276, 35.2760, 34.1041] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [49.1699, 19.3708, 52.6479, 23.8452], [50.3804, 23.7940, 50.6141, 24.1242], [51.6271, 18.2346, 55.0681, 24.1071], [50.3495, 23.3995, 51.0366, 24.1571], [51.0366, 23.1726, 52.2145, 23.7360], [52.7337, 14.0896, 53.0647, 14.3477], [49.5714, 22.2773, 51.4811, 23.7502], [50.8016, 23.3995, 51.5813, 24.1714], [48.9384, 21.8835, 49.9277, 22.9603] ] }, { "minLevel": 10, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [2.1134, -54.0010, 3.5684, -52.5112], [2.1062, -54.6066, 3.5684, -54.0010], [2.6665, -52.5112, 3.5742, -52.0258], [3.9930, -54.5201, 5.2588, -54.2990] ] }, { "minLevel": 11, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [15.6985, -61.9309, 16.5953, -61.0013] ] }, { "minLevel": 9, "maxLevel": 20, "label": "IGN", "alt": "copyright IGN 2009 - BD TOPO", "boxes": [ [14.3135, -61.2546, 14.9680, -60.7258] ] }, {
Map Tile API Developer's Guide 409► API Reference
"minLevel": 10, "maxLevel": 20, "label": "Jordan", "alt": "Royal Jordanian Geographic Centre", "boxes": [ [30.8890, 35.2899, 32.3179, 37.3047], [29.2293, 35.2899, 31.3679, 38.0203], [31.8515, 35.4964, 32.7823, 36.8242], [29.2293, 34.9258, 30.8890, 35.9751] ] }, { "minLevel": 9, "maxLevel": 20, "label": "BEV", "alt": "copyright Bundesamt fur Eich- und Vermessungswesen", "boxes": [ [48.7534, 16.3752, 48.8317, 16.7250], [46.5375, 12.6822, 46.6390, 13.3457], [46.8181, 10.4415, 46.9033, 10.6752], [47.6962, 12.9642, 48.2248, 13.3457], [46.3748, 13.3457, 46.6390, 14.8717], [46.7953, 11.0567, 46.9033, 11.1249], [48.7534, 14.8717, 49.0177, 16.0162], [48.2248, 12.9642, 48.3571, 13.3457], [47.6962, 13.3457, 48.7534, 17.1607], [46.8219, 9.9561, 46.9033, 10.2682], [46.6390, 12.2012, 46.9033, 16.0162], [47.6962, 12.8955, 47.8109, 12.9642], [46.6390, 10.6752, 46.9033, 11.0567], [46.9033, 9.5307, 47.6962, 16.7792], [46.8266, 16.0162, 46.9033, 16.1893] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [58.0107, 27.4528, 58.7552, 27.6501], [57.8526, 24.2950, 57.9554, 24.7904], [58.7436, 27.4413, 59.4859, 28.2525], [57.8968, 21.7448, 59.3645, 23.4580], [57.9301, 23.4390, 59.7909, 27.4650], [57.7540, 23.1887, 57.8411, 23.2957] ] }, { "minLevel": 10, "maxLevel": 20, "label": "Navteq", "alt": "Navteq", "boxes": [ [10.6629, -85.8099, 12.9543, -83.3936], [14.2095, -82.9224, 14.5307, -82.6012], [11.0412, -87.1376, 14.6525, -83.1509], [12.3118, -87.8420, 14.2011, -84.9162], [13.6161, -85.8103, 15.1814, -83.0464] ] }, { "minLevel": 10, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics",
Map Tile API Developer's Guide 410► API Reference
"boxes": [ [45.4520, 13.7142, 46.8284, 16.3044], [45.4418, 13.5675, 45.5366, 13.6734], [45.4125, 13.6570, 45.6003, 13.9833], [45.4543, 14.0533, 45.7004, 14.6924], [45.5239, 14.6795, 45.5557, 14.7057], [45.5557, 14.5931, 46.1463, 15.7955], [46.8276, 15.9827, 46.8786, 16.2706], [45.5318, 13.5988, 45.5394, 13.6380], [45.5366, 13.3628, 46.5230, 13.9372], [45.3439, 14.6924, 45.7418, 15.4262] ] }, { "minLevel": 9, "maxLevel": 20, "label": "EuroGeographics", "alt": "copyright EuroGeographics", "boxes": [ [47.4754, 38.4346, 50.1112, 40.3587], [47.7796, 23.7808, 52.3053, 30.3909], [45.8550, 30.3873, 51.8685, 37.3686], [47.9979, 23.0400, 48.0552, 23.1187], [50.7773, 34.6660, 51.2858, 35.5437], [47.7796, 23.6071, 50.6001, 25.5225], [44.0324, 29.5592, 46.3547, 37.3686], [44.9794, 29.0356, 47.9080, 30.3873], [50.5207, 23.4548, 51.7557, 24.4370], [51.6941, 34.3051, 51.9267, 34.4588], [51.7797, 30.5067, 52.4699, 34.3366], [46.3547, 34.8806, 50.8793, 38.6386], [47.9624, 23.1767, 48.1330, 23.5211], [48.3302, 22.1323, 49.0508, 22.5012], [47.9128, 22.4364, 50.5207, 23.9830], [47.9209, 22.1347, 48.5886, 23.2256], [47.7060, 24.7422, 47.8394, 25.2039] ] }, { "minLevel": 9, "maxLevel": 20, "label": "CNIG", "alt": "Informacion geografica propiedad del CNIG", "boxes": [ [37.3120, -6.8623, 39.3980, 0.2290], [38.2202, 3.0662, 40.2854, 5.1739], [36.8976, -7.5399, 41.6961, -6.5372], [39.3438, -7.6437, 39.7836, -7.2643], [35.2569, -2.9815, 35.3232, -2.9161], [35.6142, -7.0220, 37.9317, -1.2109], [27.4138, -18.2990, 29.4228, -13.2707], [35.8628, -5.3870, 35.9199, -5.2772], [38.4150, -6.7340, 43.7683, 3.4915], [27.4138, -18.2990, 29.4228, -13.2707] ] } ]}
The copyright information is defined for each view scheme and contains the following elements:
Map Tile API Developer's Guide 411► API Reference
Table 111: Copyright information elements (response)
Element Description
minLevel Minimum zoom level for the specified copyright label.
maxLevel Maximum zoom level for the specified copyright label.
label Copyright text to display after the copyright symbol on the map.
alt Verbose copyright text of the label to display by mouse over label or info menu entry.
boxes The bounding boxes define areas where specific copyrights are valid. A bounding box is defined by
bottom (latitude), left (longitude) and top (latitude), right (longitude).
The default copyright has no boxes element and covers all other areas.
The bounding boxes may override or add to the copyright label depending on whether the map view
is contained completely within one of the bounding boxes or overlaps partially one or more of them.
VersionThis version resource handles requests for software version details.
The following URL shows the format of a version request and the table below explains each
parameter.
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/version?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&{param}={value}
Note: Metadata requests retrieve information specific to the base URLs they target. Thisinformation cannot be used in subsequent requests that use other base URLs. For example, toobtain a traffic map version, use metadata from the response to a request addressed to theTraffic Tiles base URL, but for a version of an aerial map, use metadata from the response to arequest addressed to the Aerial Tiles base URL.
Mandatory Query Parameters
The following table lists the mandatory parameters that need to be specified with every request. Not
specifying these parameters will make the system reject the request.
Table 112: Mandatory Query Parameters
Parameter Type Description
app_id String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Map Tile API Developer's Guide 412► API Reference
Parameter Type Description
app_code String A URL-safe encoded string obtained during the application registration.
See Acquiring Credentials on page 16 for information on getting
credentials.
Note: Usage of token is accepted although is deprecated
Example
The following example shows a request addressed to the version resource.
http://{1-4}.base.maps.cit.api.here.com/maptile/2.1/version?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg
The response contains information as shown in this example.
MRS: 2.1.36.0MOS: 2.0.1.2676023561Map: 8.30.53.109
Note that the first element is the version of the Map Tile API, while the second is the version of the
underlying map rendering system. The third element shows the version of the map currently loaded.
Please be aware that this is just an example and the version varies from release to release.
HTTP Status CodesMap Tile API supports the standard HTTP status codes detailed in the table below.
Table 113: HTTP status codes
Error code Description
200 OK Indicates success, but may also be returned when an invalid resource name and/or an invalid
parameter combination has been used in the request.
400 Bad request Indicates an invalid parameter value in the request, for example zoom out of range.
401 Unauthorized Indicates authentication failure.
403 Forbidden Indicates incorrect app_code or app_id in the request. See Acquiring Credentials on page
16 for more information.
404 Not found Indicates that the resource was not found.
500 Internal error Indicates a server configuration issue.
Map Tile API Developer's Guide 413► API Reference
Error code Description
503 Service Unavailable Indicates that the service is temporarily unavailable due to system overload or maintenance.