GMAP Location Intelligence vs LocationAPI
GMAP Location Intelligence
gmap.comLocationAPI
locationapi.orgSide by side
| Figure | GMAP Location Intelligence | LocationAPI |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| Android | — | Yes |
| API | — | Yes |
| Plans published | 2 | 2 |
| Spec score · Location Intelligence Software | 7.3 (#21) | 7.8 (#12) |
| Headquarters | Leeds, United Kingdom | The contact page lists an address in Jubilee Hills, Hyderabad, Telangana, India. |
| Support | Every MVPLUS licence includes full training and ongoing support from GMAP experts. | The FAQ says the company aims to reply to every query within one business day and offers dedicated support plans for enterprise customers. |
Plans
GMAP Location Intelligence
- IMPACTPriced on request
- MVPLUSPriced on request
In their own words
GMAP Location Intelligence
GMAP Location Intelligence has no write-up on Specifiction yet; its figures are above.
LocationAPI
LocationAPI is a geolocation API that estimates connected-device locations from visible cellular towers and WiFi networks without GPS. Its calculations use cellular and WiFi data, datasets, and algorithms, and it describes coverage for IoT, M2M, and other connected devices worldwide. Requests use JSON POST to a regional endpoint. The documentation includes cURL, PHP, Python, and JavaScript examples, plus an interactive sandbox. Each request can include up to 7 cells and 15 WiFi objects. WiFi positioning is enabled only for eligible deployments based on region and intended use. Accuracy varies by source and location: the FAQ gives cell-based estimates around 450 metres in urban areas and 1500 metres in rural areas, and WiFi estimates around 25–50 metres in urban areas and 50–150 metres in rural areas. The Developer plan is free, has daily and monthly request limits, and is marked for no commercial use. Business offers flexible usage, with pricing priced on request and as low as $0.10 per device. The documentation recommends scoped access tokens, kept server-side and rotated regularly.