Skip to main content

Wemap Routing API

First, if it is not done yet, please contact our sales team (contact@getwemap.com) to use our service.

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:

  1. using OSM based data from public database
  2. 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

profilecoverage
walkFrance
carEurope
bike safestHaute-Garonne, Herault, Île-de-France, Isère
bike fastestHaute-Garonne, Herault, Île-de-France, Isère
bike tourismsame as bike safest
pmrFrance

Custom navigation graph coverage

Please contact our sales team (contact@getwemap.com)

Services implementation

World mapCustom mapCustom map + world
Simple itineraryYesYesYes
WaypointsYesNot implementedNot implemented
TravelModewalk, bike, car, transit (on demand)walkwalk
TravelModePreferencebike (safest, fastest, tourism)Not implementedNot implemented
Itinerary alternativesYesNot implementedNot implemented
Optimize waypointsNot implementedNot implementedNot implemented
Itinerary modifiers (avoid stairs, escalators, elevator)avoid stairs => pmrYesYes
Output distanceAndDurationOnlyNot implementedNot implementedNot implemented
multiple destinationsNot implementedYesNot implemented

Mobile SDKs

You can also use our services directly from our Mobile SDK implementations