×
Namespaces

Variants
Actions
(Difference between revisions)

Ovi Maps API - Information about map types

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Automated change of category from Ovi Maps to Nokia Maps)
jasfox (Talk | contribs)
(Jasfox - Archive)
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Web]][[Category:Browser]][[Category:Nokia Maps]]
+
[[Category:Nokia Maps]][[Category:JavaScript]]
 +
 
 +
{{Archived|timestamp=20130201151019|user=[[User:Jasfox|Jasfox]]| The Ovi Maps API has been superceded by the Nokia Maps API.
 +
The Nokia Maps API v2 is the successor of the Ovi Maps API. The latest version of the API can be found  [http://developer.here.net/javascript_api here].}}
 +
 
 +
{{ArticleMetaData
 +
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 +
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 +
|devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') -->
 +
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Nokia Qt SDK 1.1]) -->
 +
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 +
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 +
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 +
|signing=<!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 +
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 +
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 +
|id= <!-- Article Id (Knowledge base articles only) -->
 +
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 +
|translated-by= <!-- [[User:XXXX]] -->
 +
|translated-from-title= <!-- Title only -->
 +
|translated-from-id= <!-- Id of translated revision -->
 +
|review-by=<!-- After re-review: [[User:username]] -->
 +
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate=20110627
 +
|author=[[User:Maveric]]
 +
}}
 +
 
 +
 
 
{{Abstract|This article provides more information on the map types in Ovi Maps API}}  
 
{{Abstract|This article provides more information on the map types in Ovi Maps API}}  
  
Line 81: Line 110:
 
</code>
 
</code>
  
==Summary==
+
==For more on Ovi Maps API==
 +
 
 +
For reference the old Ovi Maps API documentation is archived here:
 +
* [http://api.maps.ovi.com Ovi Maps]
 +
 
 +
For the latest Nokia Maps API full documentation and API reference here:
 +
* [http://developer.here.net/javascript_api Nokia Maps API]
  
This was an overview on the map types and overlays, and will be subject to change and update.
+
You may also access the interactive API explorer
 +
* [http://developer.here.net/javascript_api_explorer API explorer]

Revision as of 16:01, 3 January 2013


Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

The Ovi Maps API has been superceded by the Nokia Maps API. The Nokia Maps API v2 is the successor of the Ovi Maps API. The latest version of the API can be found here.

Article Metadata
Article
Created: Maveric (27 Jun 2011)
Last edited: jasfox (03 Jan 2013)


This article provides more information on the map types in Ovi Maps API

Contents

Introduction

The following map types and overlays are described in the Ovi Maps API Reference:

Map types and map overlays

ovi.mapsapi.map.Provider NIGHT
This type provides a night mode overlay. (Not available on all platforms)
ovi.mapsapi.map.Provider NORMAL
This type provides a normal street map.
ovi.mapsapi.map.Provider PUBLIC_TRANSPORT
This type provides a public transport overlay. (Not available on all platforms)
ovi.mapsapi.map.Provider SATELLITE
This type provides a satellite map.
ovi.mapsapi.map.Provider SMARTMAP
This type provides a smart map.
ovi.mapsapi.map.Provider SMART_PT
This type provides a trafic overlay. (Not available on all platforms)
ovi.mapsapi.map.Provider TERRAIN
This type provides a map with geographical attributes like level curves and growth. (Not available on all platforms)
ovi.mapsapi.map.Provider TRAFFIC
This type provides a traffic info overlay. (Not available on all platforms)
ovi.mapsapi.map.Provider TRAFFIC_INCIDENTS
This type provides a traffic incidents overlay. (Not available on all platforms)


When the documentation states "Not available on all platforms" it basically means that to be sure, you should programmatically check the availability of the mentioned map type or overlay.

The main case is that you can have a map type combined with multiple overlays, that is, if they are supported. Also, if the overlay is supported for the specific map type, has a direct implication will it be showed at all.

One supported combination is SMARTMAP map type, which accompanied with SMART_PT will add the Public Transporation overlay. Remember to zoom enough to see the layer in action.

The map types NORMAL, SATELLITE and TERRAIN have their direct counterparts in the map UI buttons "Map View", "Satellite" and "Terrain" respectively.

When the map type is changed, it basically means that in the backend different types of tiles will be served to the client.

So, whenever you change the map type, the only thing that changes are the tiles.

Provider

A provider specifies all the basic information about some tileset, like how big are the tiles, how far you can zoom in/out, where do the tiles come from and so on.

A provider is basically the ovi.mapsapi.map.Provider class, but it's also extended by a few other classes - for instance, ovi.mapsapi.map.js.ImgTileProvider. So you, as a developer, can extend that class (ovi.mapsapi.map.js.ImgTileProvider) and provide your own paths to some tiles, the max zoom level, min zoom level, and some other small things.

Important

This article will be updated of the legal aspects on using private tile providing system. Please carefully read the Terms and Conditions before attempting anything related operations. It is better to send direct e-mail to me, in case you have thought about taking this private tile providing in use.

Please send your questions and description on your implementation to:

marko.lumivuori@nokia.com

I will see that your question will be dispatched further and get answered.

About supported platforms

This depends on the map type you're using, the renderer for the map, the product and even more things. For example, you can have one thing in product X on IE, but that won't be available in Ovi on IE - or it'll be available in the normal map display used on cellphones and desktops, but if you'll run the Plugin display, for 3D maps, it won't be available.

For the support is pretty versatile subject, you should first request a list of supported types on the client before attempting to use a type or layer that would not be available anyways. This to avoid any errors by not being able to receive tiles, and to cause the map display to go into a state where only a refresh would return the original tiles.

How to query the map types and overlays

 
ovi.mapsapi.util.OList availableBaseMapTypes
 
A list of all available ovi.mapsapi.map.Provider for base map types.
 
ovi.mapsapi.util.OList availableOverlays
 
A list of all available ovi.mapsapi.map.Provider for map overlays.

For more on Ovi Maps API

For reference the old Ovi Maps API documentation is archived here:

For the latest Nokia Maps API full documentation and API reference here:

You may also access the interactive API explorer

175 page views in the last 30 days.
×