Maptoolkit (MTK) is a framework of APIs and technologies for the development of compelling geodata applications, created and hosted by Toursprung.
MTK enables you to build scalable and cutting-edge map applications both on the web and within mobile apps with a minimum of effort. MTK goes beyond usual mapping APIs as it also covers geodata hosting with an automatic server-side generation of geodata clustering, export formats and meta data such as elevation.
It is used by market leading brands in publishing and tourism throughout Europe (see also our Showcases):
The Maptoolkit components
- Geo-Data Hosting
- 3D Maps
- MTK in Mobile Apps
- Routing API
- Statis Maps API
- UI Components
- Geocoding API
- Elevation API
Which of the two APIs is used depends on your specific requirements. Version 8 makes projects possible that are not dependent on Google Maps, thus avoiding fees imposed by Google. This is especially attractive for large projects. Version 8 also gives you access to the vast functions of the open source technology Leaflet JS. See LeafletJS.com. It is however possible to load Google Maps into v8 where needed, for example to display Google satellite imagery.
They offer a wide range of additional features to display geodata such as POIs or routes/tracks from Maptoolkit Geodata Hosting,
such as server-side clustering with heatmap functionality,
location hashes for permalinks,
a set of infowindow templates,
map controls such as fullscreen or location search or
mouse-over spread of overlapping POI markers.
Define bounding box instead of center and zoom to fit the map to the maximum available space on the current device instead of a predefined zoom level.
Dynamically fit zoom level and map position to geodata: a route, a set of POIs or a polygon.
Besides the cartography provided by Toursprung and the map layers accessible via the Google Maps API, also Bing, OpenStreetMap, OpenCycleMap or any other compatible tile server can be used with Maptoolkit.
Maptoolkit enables you to take advantage of server-side clustering and geodata caching using a powerful and fast server-cluster that currently serves more than three million map requests per day. Maptoolkit is built to scale.
To achieve that level of scalability we mirror our customers’ geodata – either by nightly sync processes (all we need is a structured interface on your side) or by supplying you a solid Push API that you can use to create, update or delete geodata on our servers.
It is based on data from OpenStreetMap – whose data density and quality is almost unrivaled – and is being updated regularly. The additional elevation data (hill shading and contour lines) has a resolution of 30m (alps) and 90m (rest of the world). The map is available up to zoom level 18 (building level, about 1:2,000). In comparison: The Google Terrain Map is only available up to zoom level 15 (about 1:18,000).
Maptoolkit geodata such as routes or POIs can be displayed onto these 3D models, making it the perfect application especially for displaying outdoor activities in mountainous regions.
The integration between 2D and 3D maps doesn’t just cover the display of geodata, also map sections and zoom levels are perfectly calculated between the two, even after the user has moved around in 3D.
Furthermore we have developed an algorithm that calculates the perfect camera position for each route, showing the start point and as much of the route as the terrain permits. The transition from 2D to 3D can be made in a way that the camera “flies” to a route’s ideal start position. We can provide a backend tool to manually fine-tune camera positions for routes.
The above example can be seen at Bergwelten.com, implemented for Red Bull.
Toursprung operates a Routing API for
bicycle routing and
The routing API currently covers Western Europe. The base network for the Routing API is the OpenStreetMap network of roads and ways. The bicycle routing is based on three layers of data: 1) road network, 2) digital elevation model, giving preference for routes with less vertical climb, 3) a route popularity heatmap of Europe, based on 3 million user provided bike routes, giving preference to more popular alternatives and thus covering “soft” factors such as surface quality, traffic or scenicness.
The API is modeled after the Google Maps API but goes beyond its feature set: With the Maptoolkit Static Maps API you can also overlay geodata from Maptoolkit Geodata Hosting. This includes POIs (custom marker images are possible) and routes (lines). Furthermore geodata formats such as KML or GPX can be used.
Static maps are especially suited for applications that need fast loading times, for example mobile web or SEO landing pages, for the creation of PDFs or print views, or for the automatic creation of content images for geocontent, for example for list views.
They include a route Editor, a route planner, interactive elevation profiles, picture strips and a map wizard.
You can integrate your own POIs from Maptoolkit Geodata Hosting. So you can provide your users a search box that doesn’t just return places and addresses but also your own geocontent.
Results can be grouped (places, addresses, points of interest)
Our geocoder understands hundreds of touristic regions and national parks in Germany, Austria and Switzerland
Results can be limited to a certain country, a certain country can be given preference or displayed differently: If you have mainly German users you can display results as “Berlin” (without country) but “Vienna, Austria”.
Nevertheless third party geocoders can be used and integrated in a MTK application as well, whatever suits the the specific use case best.
The Elevation API operates with open government data from various sources, wrong data, however rare, can not be ruled out entirely. Furthermore the coverage area of the Elevation API is limited to latitudes up to 60°N in Europe, USA, Australia and Taiwan. (60°N roughly corresponds to Bergen, Norway.)
See the chapter UI Components for a deploy-ready interactive elevation profile that operates with the Elevation API.
Toursprung supports Maptoolkit implementations by providing a working prototype according to your specific needs plus a developer briefing at project start, and will provide accompany your implementation project closely with support and troubleshooting. In addition to the working prototype and the UI Components, software libraries for the connection to the Geodata Push API can be provided in PHP, Ruby, Python and Perl. All APIS are well-documented.