Geocoding API
| Geocoding | Description | Google price | mymappi price |
|---|---|---|---|
| Direct Geocoding | Postal address translation to geographic coordinates | Around $5 / 1000 requests | Around €1.00 / 1000 requests according to the plan |
| Reverse Geocoding | Reverse translation of geographic coordinates to postal address |
Roads API
| Roads | Description | Google price | mymappi price |
|---|---|---|---|
| Snap to road | Given random coordinates, it returns the coordinates equivalent to the point of the nearest road (drawing the line perpendicular to the longitudinal axis of the road) | Around $5 / 1000 requests | Around €1 / 1000 requests according to the plan |
| Distance to road | Given random coordinates, it returns the distance in meters to the nearest road (drawing the line perpendicular to the longitudinal axis of the road) | ||
| Nearest road information | Given random coordinates, it returns information about the nearest road such as the name, maximum speed, number of lanes, type of road, etc. | ||
| Highway type | Given coordinates close to a road, it returns the type of road in question | ||
| Speed limit | Given coordinates close to a road, it returns the maximum speed at which you can drive on it | Around $20 / 1000 requests |
Directions API
| Directions | Description | Google price | mymappi price |
|---|---|---|---|
| Routing | Returns navigation instructions from point A to point B, potentially passing through various intermediate points, by car, pedestrian or bike | Between $5 and $10 / 1000 requests depending on whether they are requested with traffic data and / or with intermediate points on the route | Around €1 / 1000 requests according to the plan |
| Public transport (coming soon) | Returns navigation instructions from point A to point B, potentially passing through various intermediate points on public transport | ||
| Distance matrix | Given a number of origins and destinations, it calculates in matrix form the time it takes for the fastest route among all combinations of origins and destinations. (Limits of 10k elements according to the plan, expandable in personalized plan up to 200k) | Between $5 and $10 / 1000 requests depending on whether they are requested with traffic data and / or intermediate points on the route. (Up to 40k elements in the basic and 20k elements in the advanced) | Around €1 / 1000 requests according to the plan |
| Traveling salesman | Solve the traveler's problem. Given a number of coordinates, calculates the optimal route to go through all points as quickly as possible | Limited | Around €1 / 1000 requests according to the plan |
| Isochrone | Returns a polygon or line in GeoJSON format representing the reachable areas from a location, in any transport mode (car, pedestrian, bike, public transport) within a certain amount of time. | Not Available |
Places API
| Places | Description | Google price | mymappi price |
|---|---|---|---|
| Nearby | Returns the points of interest at a certain distance from a geographic coordinates, being able to choose the number of results, filter by various types, etc. | Between $17 and $38 / 1000 requests depending on the desired information | Around €4 / 1000 requests according to the plan |
| Place information | Given an identifier of a point of interest, it returns all the information about it | ||
| Autocomplete | Translates on-the-fly a postal address or place name into geographic coordinates, returning all possible matches. | Between $5 and $10 / 1000 requests depending on whether they are requested with traffic data and / or intermediate points on the route. (Up to 40k elements in the basic and 20k elements in the advanced) |
Plans
| Plans | Max. transactions / day | Max. transactions / month | Max. requests / second | Android / iOS SDK | Monthly price | Annual price | Support | Dedicated team for integration |
|---|---|---|---|---|---|---|---|---|
| Starter | 5k | 150k | 3 | NO | FREE | FREE | NO | |
| Developer | 5k | 150k | 9 | YES | €49.00 | €490.00 | NO | |
| Startup | 10k | 300k | 15 | YES | €149.00 | €1,490.00 | NO | |
| Enterprise | Custom | Custom | Custom | YES | Custom | Custom | Premium (Videocall, Phone, Email) | YES |
Transactions / Requests scheme
| API | Request type | # Transactions / Request | Notes |
|---|---|---|---|
| Geocoding | Direct geocoding | 2 | |
| Reverse geocoding | 1 | ||
| Roads | Snap to road | 2 | |
| Distance to road | 2 | ||
| Nearest road information | 4 | ||
| Highway type | 2 | ||
| Speed limit | 4 | ||
| Directions | Route calculation | 2 | Up to 10 intermediate waypoints. For more than 10 waypoints, each request costs 4 transactions |
| Distance matrix | 2 | Two transactions per element. Elements are equivalent to the number of computed routes. For example, for 4 origin coordinates and 5 destination coordinates, the total amount of elements is (4 x 5 = 20 elements) | |
| Traveling salesman | 5/15* | Five transactions per waypoint (*we also offer Premium optimization API for 15 transactions per waypoint) | |
| Isochrone | 2 | ||
| Places | Nearby | 4 | Four transactions per each 10 results (each page returns up to 20 results) |
| Place information | 2 | Two transactions per each 10 results (each page returns up to 20 results) | |
| Autocomplete | 2 |
EN 
ES