Wemap Routing API
First, if it is not done yet, please contact our sales team (contact@getwemap.com) to use our service.
🔗 Swagger
POST https://multi-routers.getwemap.com/v2/compute-itineraries
{
origin: { lat: 43.5951782, lng: 3.9216961 },
destination: { lat: 43.6091792, lng: 3.9123375 },
travelMode: 'WALK'
}
or indoor:
POST https://multi-routers.getwemap.com/v2/compute-itineraries
{
origin: { "lat": 48.84453132, "lng": 2.37323723, "level": 0 },
destination: { "lat": 48.8442561, "lng": 2.3762027, "level": -1 },
travelMode: 'WALK'
}
Coverage
Overall
Our service uses two kind of navigation graphs:
- using OSM based data from public database
- private custom graphs drawn over private custom maps by the Wemap team. This graphs can be multi-levels!
Connection between these graphs are seamless
OSM based data coverage
| profile | coverage |
|---|---|
| walk | France |
| car | Europe |
| bike safest | Haute-Garonne, Herault, Île-de-France, Isère |
| bike fastest | Haute-Garonne, Herault, Île-de-France, Isère |
| bike tourism | same as bike safest |
| pmr | France |
Custom navigation graph coverage
Please contact our sales team (contact@getwemap.com)
Services implementation
| World map | Custom map | Custom map + world | |
|---|---|---|---|
| Simple itinerary | Yes | Yes | Yes |
| Waypoints | Yes | Not implemented | Not implemented |
| TravelMode | walk, bike, car, transit (on demand) | walk | walk |
| TravelModePreference | bike (safest, fastest, tourism) | Not implemented | Not implemented |
| Itinerary alternatives | Yes | Not implemented | Not implemented |
| Optimize waypoints | Not implemented | Not implemented | Not implemented |
| Itinerary modifiers (avoid stairs, escalators, elevator) | avoid stairs => pmr | Yes | Yes |
| Output distanceAndDurationOnly | Not implemented | Not implemented | Not implemented |
| multiple destinations | Not implemented | Yes | Not implemented |
Mobile SDKs
You can also use our services directly from our Mobile SDK implementations