Criteria for choosing a web map provider
In my previous article I defined the basics of a web map service provider. In this article I will discuss the criteria for choosing the right web map provider.
There are many good articles about comparing the technical features of the web map providers. I am specially interested in what I should know about an application before I start using the map, or even before I start reading comparitive articles of the web map providers. I did not find an article discussing purely the characteristics of the application where the map will be used, because there is no single answer. So I decided to summarize the criterias I use, when choosing a map service.
There are two terms which I use throughout the post, “web map provider” and “web map api”. To clarify the difference, here a short description of both:
Web map provider
Web map providers offers a service, from where a map or layers can be loaded. It does not necessary contain a user interface, it can also be a rest service. Examples of providers are Google, Bing, ArcGIS Server and non-commercial Open Street Map.
Web map api
Before analyzing the map providers, I usually analyze the data I want to use.
Quality and Type
When I choose the external data to use, I consider type and quality of the data:
- I choose if I want to use tiled data for a background or vector data for performing queries.
- I check who is producer of the data and how often it will be updated. For example, data in OpenStreetMap is updated often by user contributions; commercial web map providers get their data from GIS data Providers.
As soon as I know which data I want to use, I need to know:
- In which format it is and to where it should be stored.
- Which is the amount of the data to use and how often it will be used.
Usage of data
Ideal is, if you define early the maximum data to show, because web map providers limit the amount and increase the costs, if the limits are exceeded. The amount of data affects naturally also the performance of the application. An example of a limit is a selection. Usually when selecting hundreds of elements, every web map provider is at its limits. A solution could be revisiting the business case of simultaneous selection or implementing alternative, a more informative and more performant way of showing the selection.
Usage of application
In addition to the aspect of the data volume, the usage of the application is as important. It is good to analyze frequency of the usage, environment of the usage and the need for “out of the box” services and integration.
I recommend to know the amount of expected users and frequency of the usage. This helps to analyze the transaction and performance requirements. This amount is needed if you are evaluating a commercial web map provider. Also the domain of the application, may it be free, public, private or intranet, will affect to the cost of using commercial web map provider. OpenStreetMap is an exception; it can be used without costs.
If you want to use the application or the data offline, some providers are more recommended than others:
- ArcGIS and Bing offer offline usage only via native interfaces.
- Google offers limited usage via premium license.
- Open Street Map is an exception as well; it is even possible to download the map data and host it on own premises.
- Layers from commercial providers can be shown in OpenLayers web api, but then the license of the commercial web map provider is still valid.
Services and integration
Different web map providers have a different focus. Open Streep map is concentrating on being a traditional map data provider. Additional services like routing and geocoding are provided by third parties. Commercial providers are providing different kind of services, for example traditional Gis data analysis from Esri or Street map from google. When choosing a data provider it is good to recognize if services like routing or elevation will be used now or in the near future, or if there is a need for integration like for example office or 3D.
If the decision of the web map provider is not clear after evaluating the requirements for the data and usage, there are also useful criteria for web map api. I find the criteria from Papa John for a third party library also applicable for web map service provider.
I find ideal, when the focus of the web map provider matches to the requirements. In that case I can be sure that my favorite service wont obsolete soon. Please notice that some of the most innovative and new services are considered as experimental and that they still can change or become obsolete. The stability of the api is important, in this area the commercial apis score is better than OpenLayer. A good documentation and activity of the community are also helpful for the developer. Google maps is in this area my favorite.
If you ask me which web map provider and web map api I would use, I would give you the typical consultant answer: “It depends”. But I hope that I gave you a few inputs in this article, so you know on what it depends. I like to hear your comments about what you find important when choosing an external framework, no matter if this is a web map provider or something else.