Ovi Maps API - Information about map types
This article provides more information on the map types in Ovi Maps API
The following map types and overlays are described in the Ovi Maps API Reference:
Map types and map overlays
This type provides a night mode overlay. (Not available on all platforms)
This type provides a normal street map.
This type provides a public transport overlay. (Not available on all platforms)
This type provides a satellite map.
This type provides a smart map.
This type provides a trafic overlay. (Not available on all platforms)
This type provides a map with geographical attributes like level curves and growth. (Not available on all platforms)
This type provides a traffic info overlay. (Not available on all platforms)
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.
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.
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:
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
This was an overview on the map types and overlays, and will be subject to change and update.