"How to" for web integrators

Integration with Leaflet

The easiest way to integrate the skobbler maps into your own website is by using our skobbler plugin. Here are 4 easy steps to use it:

  1. The skobbler plugin is built on top of Leaflet, the open-source JavaScript library for mobile-friendly interactive maps, so the library must be firstly included into your HTML markup:
    <link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.css" />
    <script src="http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.js"></script>
  2. Our map-tile styles and the skobbler specific map-controls layout, are accessible in Leaflet via our plugin. Simply include skobbler.js plugin just below the leaflet library inclusion, like this:
    <link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.css" />
    <script src="http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.js"></script>
    
    <script src="PATH_TO_SKOBBLER.js"></script>
  3. You can select our map position into your website, by simply choosing a unique ID for any HTML DIV-tag you want. A height for your DIV element is mandatory, since a 0 height DIV will not be able to display the map:
    <link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.css" />
    <script src="http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.js"></script>
    
    <script src="PATH_TO_SKOBBLER.js"></script>
    
    <style>
        #map {
            height: 500px;
        }
    </style>
    
    <div id="map"></div>
  4. You can initialize the map by specifying only the ID you chose earlier, and your API key (the credentials needed to use our API, yours being found here):
    <link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.css" />
    <script src="http://cdn.leafletjs.com/leaflet-0.7.2/leaflet.js"></script>
    
    <script src="PATH_TO_SKOBBLER.js"></script>
    
    <style>
        #map {
            height: 500px;
        }
    </style>
    
    <div id="map"></div>
    
    <script>
        var map = L.skobbler.map('map', {
            apiKey: 'YOUR_API_KEY'
        });
    </script>
    In this case, the map will have the default set of options we thought to be appropriate for most of our users. However, a specific set of options can be defined like this:
    <script>
        var map = L.skobbler.map('map', {
            apiKey: 'YOUR_API_KEY',
    
            mapStyle: 'day',
            bicycleLanes: true,
            onewayArrows: true,
            pois: 'all',
            primaryLanguage: 'en',
            fallbackLanguage: 'en',
            mapLabels: 'localNaming',
            retinaDisplay: 'auto',
    
            zoomControl: true,
            zoomControlPosition: 'top-left',
    
            center: [52.52112, 13.40554],
            zoom: 12
        });
    </script>
After integrating our plugin, any one of the Leaflet specific actions, layers, markers etc can be added and played with on the newly created map object:
var marker = L.marker([52.52112, 13.40554]).addTo(map);
marker.bindPopup("Hello world!<br>I am a popup.", { offset: new L.Point(-1, -41) }).openPopup();
For the verbose and well documented list of possible customization, see the Leaflet site and documentation. Next, we provide you with all our possible map options, nicely explained:

Option Type Default Description
apiKey string null Find your web api key on the Api key page
mapStyle string 'day' Tile styling can be chosen from the following options: day, night, lite, bike or outdoor
bicycleLanes boolean true Show or hide the bicycle lanes
onewayArrows boolean true Show or hide the one way arrows for the one way streets
pois string 'all' You can choose to populate the map with Point of Interest (POIs). Pick from: all, important or none
primaryLanguage string 'en' Chose one of the supported languages by using the following country codes: en, de, fr, it, es, ru
fallbackLanguage string 'en' Choose the backup language, for those places which have no naming available in the primary language. The codes are: en, de, fr, it, es, ru
mapLabels string 'localNaming' You can pick one of the following map labeling methods: localNaming, transliterationOnly, noTransliteration, nativeLocalized, transliterationNative
retinaDisplay string 'auto' By specifying the retina setting, you can set the map behavior when viewed from a retina-capable device: auto, on, off
zoomControl boolean true Show or hide the zoom controls
zoomControlPosition string 'top-left' The location of the zoom controls, if visible: top-left, top-right, bottom-left or bottom-right
center string null Specify the initial map center, as desired
zoom number null Specify the initial zoom level from a range of 0 to 18

Routing server

The routing server supports only GET requests with the following URL structure:

https://YOUR_API_KEY.tor.skobbler.net/tor/RSngx/command/json/version/locale/YOUR_API_KEY?parameters

All parameters are mandatory, except the request parameters which are command-specific.

Name Description
command The command to be called. The routing server supports:
calcroute – for routes calculation
version The version of the routing server. In general it is formed by two numbers: majorRevisionNumber_minorRevisionNumber.
Example 8_3, 9_0, 10_2
locale Defines the language in which the api and http messages will be sent.
Possible values: de(German), en(English)
Default: en
YOUR_API_KEY Your API key.
parameters This is the list of parameters required by the selected comamnd.
It is a list of name=value arguments separated by „ & ”. The entire arguments list has to be URL-encoded.

Example:

http://YOUR_API_KEY.tor.skobbler.net/tor/RSngx/calcroute/json/18_0/en/YOUR_API_KEY?start=46.5472,24.5615&dest=46.5447,24.5607&profile=carFastest&advice=yes

Requesting a route - the calcroute command

The command's parameters can be:

  • mandatory (marked with YES)
  • not mandatory (marked with NO), in which case they will have a default value.

National conventions

  • POINT – Pair of two float values.(ex: 12.12345,43.123456)
  • BOOL – „yes”/”1” and „no”/”0” values
  • INT – an integer value

Parameters defining the route's calculation

Name Value Description Mandatory
start POINT GPS position of the start of the route.
Format: Latitude,Longitude
YES, when no startMercator
dest POINT GPS position of the destination.
Format: Latitude,Longitude
YES, when no destMercator
startMercator POINT Same as start, but in mercators.
Format: Longitude, Latitude (aka X,Y), which is reversed when compared with start!
When both present, the mercator coordinates have priority.
YES, when no start
destMercator POINT Same as dest, but in mercators.
Format: Longitude, Latitude (aka X,Y), which is reversed when compared with dest!
When both present, the mercator coordinates have priority.
YES, when no dest
profile TEXT This defines the routing profile:
For car: carShortest, carFastest, carEfficient – where carEfficient is a carFastest that makes use of OSM+ driving speeds (i.e. collected from real drivers)
For pedestrian: pedestrian,
For bicycle: bicycle.
YES
toll BOOL Yes: Toll roads are used without restrictions in route calculation.
No: The routing algorithm will tend to avoid toll roads.
Default: yes.
NO
highways BOOL Yes: Highways are used without restrictions in route calculation.
No: The routing algorithm will tend to avoid highways.
By highway we refer to segments being defined in OSM as motorway or motorway_link.
Default: yes.
NO
ferrylines BOOL Yes: Ferry-lines are used without restrictions in route calculation.
No: The routing algorithm will tend to avoid ferry-lines.
Default: yes.
NO

Parameters defining the route's calculation

Name Value Description Mandatory
advice BOOL Yes: Send the route's advice (i.e. step by step instructions).
Default: no
NO
points BOOL Yes: Send the route's geometry as a list of GPS coordinates.
Default: no
NO
countries BOOL Yes: Send the list of countries traversed by the route. Each country is identified by its code: http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2
Default: no
NO
viaType TEXT The type of via points. All the via points will have the same type.
Possible values:
exact (default) – the via point's exact coordinate is used (i.e. the point is mapped on the street network, and the route will go through the position where the via points is mapped)
NO
v# POINT GPS positions of via points: v0, v1, ..., v10.
They are are read and used in the order of their number.
The numbers do not have to be contiguous. For example there can be only v3 and v7, meaning that v3 is the first via point and v7 the second.
Format: Latitude,Longitude.
NO
vM# POINT Mercator positions of via points: vM0, vM1, ..., vM10.
Same rules as for GPS via points.
The combination of the two styles (GPS – mercator) is supported. However, if a via point number appears in both versions, the mercator version have priority.
Format: Longitude, Latitude (aka X,Y), which is reversed when compared with v#!
NO
alternates BOOL Yes: Compute up to two alternates.
Default: no
NO

Example:

http://YOUR_API_KEY.tor.skobbler.net/tor/RSngx/calcroute/json/18_0/en/YOUR_API_KEY?start=53.197963,14.028484&dest=52.7338,12.748245&profile=carFastest&points=yes

Response

Always Returned

Name Description
routelength The total route's length in meters
duration Estimated duration of the route, in seconds. It depends on the routing profile and the type of roads that are used
hasFerries Use it as a BOOL value. Its possible values are:
  • 0 – meaning that the route contains no ferry lines
  • 1 – meaning that the route contains ferry lines

Suggestion: use as: 0 – no ferry lines, different than 0 – ferry lines present
hasHighWays same as hasFerries, but for highways. By highway we mean segments having as OSM type motorway or motorway_link
hasTolls same as hasFerries but for toll roads. NOTE that by toll we refer strictly to the roads or ferry-lines that are marked explicitly in OSM as having a toll.
mercBBox the route's bounding box in mercator coordinates: [minX,minY,maxX,maxY]

Advice and Summary: advice=yes

The route advice is returned in the form of (advice type, coordinate, distance, optional param, instruction).

Name Description
adviceType The adviceType is an integer value that specifies the general type of advice, as follows:
  • DestinationPoint (0) - when the next advice is for exact point location, not street;
  • DestinationStreet (1) - destination is a street;
  • LastRouteItem (2) - we are on the last route item, but it is not the destination;
  • DestinationRoundabout (3) - destination is in a roundabout;
  • U_Turn (4) - need to make a u-turn;
  • Ignore (5) - if no advice should be said;
  • EnterHighway (6) - will enter on highway;
  • ExitHighway (7) - need to exit from highway;
  • HighwayLink (8) - getting from one hway to other;
  • CrossingHighway (9) - intersection between highways;
  • Roundabout (10) - roundabout instruction;
  • T Street (11) - T-street instruction;
  • StraightAhead (12) - route is straight ahead, when are multiple streets in crossing;
  • StreetCrossing (13) - an intersection between other streets than highways;
  • CarryStraightOn (14) - when no advice can be generated because lack of route items, or the distance to the advice is very big;
  • ContinueDistStr (15) - informal advice to continue on a street for a certain distance (only US);
  • ContinueDist (16) - informal advice to continue for a certain distance (only US);
  • CountinueStraight (17) - informal advice to continue straight on (only US);
  • RouteGuidance (18) - informal advice for starting the route (only US);
  • RouteGuidanceStr (19) - informal advice for starting the route from a certain street (only US);
distance distance is the distance in meters to the advice
optional param The optional param is dependent on the advceType parameter, as follows:
  • If the adviceType is RoundAbout or ExitHighway, there will be an exitNumber parameter that will indicate the roundabout/highway exit number (this is a string, since highway exit numbers can contain letters)
  • If the adviceType is StreetCrossing, T Street, CrossingHighway, EnterHighway, there will be a turnDirection parameter indicating the type of turn:
    • Straight Ahead (0)
    • Slight Right (1)
    • Slight Left (2)
    • Left (3)
    • Right (4)
    • Hard Right (5)
    • Hard Left (6)
    • U Turn (7)
    • T Street (8)
  • If the adviceType is HighwayLink or DestinationPoint, there will be a side parameter indicating the side you must keep on : Left = 0, Right = 1
instruction the advice as text

Example:

[…]?
start=52.504461,13.390038&dest=52.505382,13.390768&profile=carFastest&advice=yes

 "route" : {
      "advisor" : [
         {
            "adviceType" : 11,
            "coordinates" : {
               "x" : 13.390875,
               "y" : 52.504520
            },
            "distance" : 58,
            "instruction" : "In 50 meters , turn left at the T junction onto Friedrichstraße ",
            "turnDirection" : 3
         },
         {
            "adviceType" : 1,
            "coordinates" : {
               "x" : 13.390703,
               "y" : 52.505388
            },
            "distance" : 96,
            "instruction" : "In 90 meters you will reach your designated road"
         }
      ],
      "duration" : 37.0,
      "hasFerries" : 0,
      "hasHighWays" : 0,
      "hasTolls" : 0,
      "mercBBox" : [ 18025257, 11006587, 18025326, 11006729 ],
      "routelength" : 155.699493,
      "summary" : [ "Puttkamerstraße", "Friedrichstraße" ]
   },

	 [...status..]

Points: points=yes

The route's geometry will be returned as an array of GPS positions. The points have the same order as in the route.

The Bounding box is sent also in GPS coordinates: gpsBBox [minLong, minLat, maxLong, maxLat]

Example:

[...]?start=52.339528,8.980182&=52.876193,8.952722&profile=carFastest&points=yes
Json format:
{
	route: 
{
	duration: 3978,
	gpsBBox: [8.798697,52.338753, 9.00734, 52.879147],
	hasFerries: 0,
	hasHighWays: 0,
	hasTolls: 0,
	mercBBox: [17597314,10949109,17616761,11032055],
	routePoints:
    
    [ {x: 8.98025, y: 52.339253},
     {x: 8.98231, y: 52.339456},
    [...]
     {x: 8.950982,y: 52.877011}
    ],
	routelength: 78605.5
},
	status:[...]
}

Via Points

The server will send information about the via points:

  • the exact location where they are mapped, in mercator-coordinates: xm, ym. This coordinate belongs to a road. (Note that the input via points's coordinates coming from the user might be some distance away from any road)
  • The id of a via-point is taken from the request, i.e. v#, where # will be the id of a via points in the answer.
  • The distance (in meters) and duration (in seconds) from the start of the route to the point of the route where the via point is mapped on the route: dta2via for distance and eta2via for duration.

Example:

:[...]?start=53.197963,14.02848&dest=52.7338,12.748245&viaType=exact&v0=53.379639,14.058484&v1=54.779639,14.058484&profile=carFastest
	route: {
	duration: 55583,
	hasFerries: 1,
	hasHighWays: 1,
	hasTolls: 1,
	mercBBox: [17965438,10648906,18087561,10971519],
	routelength: 992082.8125,
	viaInfo: [
	{
	dta2via: 28665,
	eta2via: 1296,
	id: 0,
	xm: 18087561,
	ym: 10871360
},
	{
	dta2via: 603710,
	eta2via: 32268,
	id: 1,
	xm: 18087561,
	ym: 10648906
}]},
	status: { […]}}

Alternative Routes

The alternates parameter controls whether the alternative routes calculation is triggered or not.

Name Value Description Mandatory
alternates BOOL Specify whether alternative routes should be computed or not.
Possible values:
no / 0 – use as default. No alternative route will be calculated;
yes / 1 – alternative route will be calculated in a way chosen on the server side, based on the profile's value in the request;
NO

Note that:

  • For the short profiles no alternatives are calculated: carShortest.
  • A maximum of two alternates are computed for the other profiles. This means it can happen that only one alternate is calculated or even none.
  • All the input (e.g. highways, toll) and output (e.g. advice) options are applied to all alternates.

Examples:

[…]?start=52.5177,13.3618&dest=52.5099,13.3579&profile=carFastest&alternates=yes

JSON response: there are more routes in the same response: route is the classic one – the main route, and alternate# are the alternates, where # starts from 1.

Each route will contain the same type of response.

{
   "alternate1" : {
     ...
   },
   "alternate2" : {
     ...
   },
   "route" : {
    .....
   },
  .....
}

Countries: countries=yes

Returns the list of countries traversed by the route:

  • each country is identified by its code (2 letters. United States appear as one country, US);
  • each country appears only once in the list;
  • the country codes are ordered alphabetically.

Example:

[...]?start=46.5687,23.4193&dest=52.5246,13.4796&profile=carFastest&countries=yes

Response:

[...]
routeCountries: 
[
	"CZ",
	"DE",
	"HU",
	"RO",
	"SK"
],
[...]

Status codes

HTTP Status Code Routing Status/
TOR API Code
Message Details
200 600 Route calculated. Everthing worked as expected, the route was calculated.
404 621 Command not supported
405 631 The HTTP method used is not allowed
200 680 The start and destination points are the same. The start and destination points are the same. No route is calculated.
200 681 Invalid starting point. The start point is out of the road network or not covered by our maps.
200 682 Invalid destination point. The destination point is out of the road network or not covered by our maps.
200 683 Route cannot be calculated. General route calculation error.
200 684 Invalid via point. The via point is out of the road network or not covered by our maps.
Not used. 681 or 682 will be returned instead in this situation.
200 690 Unknown server error. This should never happend.
400 610 Missing argument At least one mandatory parameter is missing from the client request
400 611 Invalid argument At least one of the parameters received from the client has an invalid value. For example: it is of a wrong type (e.g. a text instead of a number), has an invalid format (e.g. GPS coordinates formed by less or more than 2 numbers) or an invalid value (e.g. invalid GPS coordinate).

RealReach™

RealReach™ provides features like the maximum possible walking / driving / biking coverage, given a chosen time frame, by nicely drawing a blueish area above our maps.

This is the RealReach™ URL:

http://YOUR_API_KEY.tor.skobbler.net/tor/RSngx/RealReach/json/18_0/en/YOUR_API_KEY
                        
And this is an example of a request:

http://YOUR_API_KEY.tor.skobbler.net/tor/RSngx/RealReach/json/18_0/en/YOUR_API_KEY?start=44.4325,26.1039&transport=pedestrian&range=180&units=sec&toll=1&highways=1&nonReachable=0&response_type=gps
                        
Here is another request example:

http://YOUR_API_KEY.tor.skobbler.net/tor/RSngx/RealReach/json/18_0/en/YOUR_API_KEY?startMercator=18024748,11004862&transport=pedestrian&range=180&units=sec&toll=1&highways=1&nonReachable=0&response_type=mercator
                        
Here are the list of options that you can use, along with explanations:
Option Type Default Description
YOUR_API_KEY string null Find your web api key on the Api key page
start string Center of RealReach™ in GPS coordinates: Latitude, Longitude
startMercator string Center of RealReach™ in mercator coordinates: X,Y (Where X corresponds to Longitude and Y to Latitude). Has priority over start, when both are present
transport string You can pick one of the transport options: pedestrian, bike, car
range int The range for which we calculate RealReach™
units string You can choose between sec and meter. 'Sec' is for time and 'Meter' is for distance
nonReachable boolean Specifies whether to calculate or not the interior contours (non reachable areas) inside the RealReach™
toll boolean You can specify whether to avoid or not the use of toll roads in route calculation
highways boolean Specifies whether to avoid or not the use of highways in route calculation
response_type string You can choose how you want to get the results, in 'gps' or 'mercator' points
You can see RealReach™ in action just below:

Tile server & Static map

Overview

The server provides raster map images according to the provided configuration parameters.

  Main services
  • map tiles service according to the XYZ schema
  • static map (single image)
  Main features
  • more map styles to choose from
  • high-level map customization
  • label internationalization (i18n)
  • retina support

Tile server

Form:

http://SUBDOMAIN-YOUR_API_KEY.skobblermaps.com/TileService/OP_MODE/VERSION/SETTING_FLAGS/STYLE_ID/Z/X/Y.EXT@2x
                        
Examples:

http://tiles2-YOUR_API_KEY.skobblermaps.com/TileService/tiles/2.0/010011101/0/10/550/335.png
                        


http://tiles3-YOUR_API_KEY.skobblermaps.com/TileService/tiles/2.0/110011101/10/6/34/20.png@2x
                        

Static map

Form:

http://SUBDOMAIN-YOUR_API_KEY.skobblermaps.com/TileService/OP_MODE/VERSION/SETTING_FLAGS/STYLE_ID/LAT,LON,ZOOM/WIDTHxHEIGHT.EXT@2X
                        
Examples:

http://tiles1-YOUR_API_KEY.skobblermaps.com/TileService/static/2.0/00001210100/5/52.50326,13.39387,12/450x320.png
                        

Parameters

Name Description Mandatory
SUBDOMAIN Subdomain aliases
Useful to circumvent browser limitations on parallel resource loading from the same domain; improves download performance on client side
Possible values: tiles1, tiles2, tiles3, tiles4
YES
OP_MODE Operation mode:
tiles - for standard XYZ tiles
static - for static map (single image)
YES
YOUR_API_KEY The client's API key, alphanumeric string
To obtain an API key subscribe at http://developer.skobbler.com/
YES
VERSION Possible values:
2.0
YES
SETTING_FLAGS Map setting flags as alphanumeric string, each character representing a setting.
Please check the possible settings and flag values below.
YES
STYLE_ID Style-ID (numeric)
At the moment the following default styles are supported:
0 - day
2 - night
5 - outdoor
7 - light
10 - bicycle
For client-specific custom styles please contact us.
YES
EXT Image format (extension)
Currently supported formats:
  png<MAXIMUM_COLORS>
   MAXIMUM_COLORS = [3-256] (default: server dependant), e.g. png64
  jpg<IMAGE_QUALITY>, jpeg<IMAGE_QUALITY>
   IMAGE_QUALITY = [1,100] (default: 80), e.g. jpg60
YES
@2x Retina image modifier, for non-retina it should be omitted
If used, the returned image will have double of the initial size. The content of the image will be identical (or very similar) to the non-retina version.
NO

  Tile server specific parameters

X X tile number according to the standard XYZ schema YES
Y Y tile number according to the standard XYZ schema YES
Z Zoom level, supported values [0,18] YES

  Static map specific parameters

LAT Latitude coordinate of the map center (ex. 52.33952) YES
LON Longitude coordinate of the map center (ex. 8.98018) YES
ZOOM Zoom level [0-18] YES
WIDTH Image width in pixels, supported values [16,1024] YES
HEIGHT Image width in pixels, supported values [16,1024] YES

Setting flags

The settings flags allow high-level map customization. Each option is represented by one flag. The choice for using flags instead of individual parameters was made to shorten the URL and facilitate caching (ex. CloudFront)
The SETTINGS_FLAGS is an alphanumeric string, each character represents a flag. At the moment only numeric values are used, but if more than ten values will be needed in the future the alpha chars will also be used. There is no rule whether the flags start with value 0 or 1, this varies to better match their meaning.

Structure:

BICYCLE_LANES | ONEWAY ARROWS | HEIGHTMAP | POIS | PRIMARY_LANG | FALLBACK_LANG | FIRST_LABEL | SECOND_LABEL | SHOW_AND/OR_LABELS | TRANSLIT_BACKUP | RESERVED_I18N | CLUSTERING

Name Description Mandatory Default
BICYCLE_LANES Render bicycle lanes:
0 - no
1 - yes
YES 0
ONEWAY ARROWS Render oneway arrows
0 - no
1 - yes
NO 0
HEIGHTMAP Render heightmap (relief shading)
0 - no
NO 0
POIS Render POIs
0 - no
1 - only important POIs (STYLE_ID-dependant)
2 - all
NO 0
PRIMARY_LANG Primary language choice for the labels
1 - EN
2 - DE
3 - FR
4 - IT
5 - ES
6 - RU
NO 1
FALLBACK_LANG Fallback language (this language will be used if there is no label corresponding to the primary language)
1 - EN
2 - DE
3 - FR
4 - IT
5 - ES
6 - RU
NO 1
FIRST_LABEL What names to show for the first part of the label
1 - local
  e.g. In Germany , you'll see e.g. 'München', in Russia 'Москва', in Japan '東京'
2 - transliterated - to Latin or Cyrillic, depending on the alphabet of the primary language
  e.g. 'Moskva' in Russia or 'Dong Jing' in Japan
3 - international - names will be displayed based on the primary/fallback language
  e.g. If the language is set to English, names will read e.g. 'Moscow', 'Munich', 'Tokyo'.
NO 3
SECOND_LABEL What name to show for the second part of the label
0 - none
1 - local
  e.g. In Germany , you'll see e.g. 'München', in Russia 'Москва', in Japan '東京')
2 - transliterated - to Latin or Cyrillic, depending on the alphabet of the primary language
  e.g. 'Moskva' in Russia or 'Dong Jing' in Japan
3 - international - names will be displayed based on the primary/fallback language
  e.g. If the language is set to English, names will read e.g. 'Moscow', 'Munich', 'Tokyo'.
NO 1
SHOW_AND/OR_LABELS To show one of two names for each label
1 - OR, show only one label
  if the first exists that one, else the second
2 - AND, show both labels, the second in parentheses
  e.g. 'München (Munich)' Note: the second label will be shown only if it is not identical to the first
NO 1
TRANSLIT_BACKUP Transliteration backup: use transliteration as backup if international name is missing
0 - no
1 - yes
NO 1
RESERVED_I18N Reserved flag for future Internationalization options NO 0
CLUSTERING Flag for clustering elements on the map
0 - no
1 - yes
NO 0

Example: 010212132101

Status codes

Requests for images (tile or static) return HTTP status codes according to the HTTP standards. The response's content is either the image or empty (on error).

HTTP Status Code HTTP Status Message Details
200 OK Success, the image is returned
304 Not modified Indicates that the image has not been modified since the last request
403 Forbidden Indicates that the used API key is invalid
404 File not found Indicates that there is no image matching the provided URL parts or parameters
5xx Server specific errors