Maps inside your backend.
Your editors draw routes and areas in the same screen where they write the content. The tour on your website then shows the route, its length, the walking time and the elevation profile.
Try the route editor.
The route editor for your backend, live. A walk through the old town of Graz is already in it.
Drag a point and the route takes another way
Switch between walking, cycling and driving
Upload a GPX or KML file
Try the polygon editor.
Areas for regions, municipalities or protected areas, live. The municipality of Gosau is already loaded.
Move the corners or draw a new area
Add a municipality or a protected area from a Maptoolkit Connector
Click two areas, then merge them or cut one out of the other
Try the search.
Type a place or an address and pick it from the results, the way your editors set the location of an entry.
Search for any place or address
Click a result to see it on the map
Click the map for the address there
Part of your backend.
The editors are JavaScript components that you place in a page of your backend. They run on the same Maptoolkit maps and APIs as your website.
Two components
The route editor (MTK.EditorInterface) with a POI select (MTK.ItemSelect), and the polygon editor (MTK.PolygonEditor).
Routing for the magnet tool
Routes between two points come from the Routing API, for walking, cycling or driving.
File formats
Routes from GPX or KML files, areas from KML or GeoJSON files.
Route facts
The Data Enhancement Tools add length, ascent and descent, the elevation profile, surface and way types, travel times and turn-by-turn directions.
Places and addresses
The Geocoding API finds places and addresses worldwide, forward and reverse.
Print maps
A GPX or KML file can be the source of a Printmaps map, set with one URL parameter.
Where the edited tour appears.
A route made in the backend is ready for every channel that uses your content:
Tourism portals
Every tour on your website with its route, facts and elevation profile.
Apps
The same tours in your app, on vector maps for iOS and Android.
Print-ready maps for brochures and tour sheets from the route of a tour.
Route from the Routing API, heights from the Elevation API.
Questions about tour data.
Short answers on GPX downloads, travel times, preview maps and turn-by-turn directions.
Can I offer a tour as a GPX download?
Yes. The Routing API returns a calculated route as JSON, GPX or KML, chosen with one parameter, so a tour can be offered as a GPX download for GPS devices and outdoor apps. Routes are available for walking, cycling and driving. The GPX file holds the track points of the route but no heights; for those, use the Elevation API or the Route Enhancement API.
How are walking and cycling times for a tour calculated?
The Route Enhancement API estimates travel times from the length of a route and its elevation, so the climbs and descents of a tour count, not just its distance. One request returns estimates for walking and for cycling. Driving times come from the Routing API, which calculates routes for walking, cycling and driving.
Can I show a small preview map of each tour in a list?
Yes. The Static Maps API returns a map as a JPEG, PNG or WebP image with your route drawn on it, from a list of points, a GeoJSON line or a KML file. You choose the size, the map style, the line color and width, and you can add direction arrows. This gives every tour in a list a small preview image without loading an interactive map.
Can I add turn-by-turn directions to a tour drawn on a map?
Yes. The Route Enhancement API matches a GPX or KML track, or a GeoJSON line, to the road and path network and returns turn-by-turn instructions in the language you choose. Each instruction has its distance, the street name and the surface. This turns a route drawn on a map or recorded with a GPS device into step-by-step directions.
See your use case on a Maptoolkit map.
In the demo, one of our engineers walks you through the platform, your data and the move from your current provider.