Open-Elevation drop-in replacement
Open-Elevation's public server is a volunteer project with no uptime promise. openelevation.mygeocode.com answers the same lookup endpoint, by GET or POST, from a global 15 arc-second grid (about 460 m) that covers land and the sea floor.
Change one hostname
| Original host |
|
|---|---|
| Use instead | openelevation.mygeocode.com |
| Key parameter | None on the original, and none needed here either: any address gets 2,500 requests a day without one. For credit, packages and a usage history add key=... to the query or send the X-API-Key header. |
curl "https://api.open-elevation.com/api/v1/lookup?locations=27.9881,86.9250|46.5763,7.6613"curl "https://openelevation.mygeocode.com/api/v1/lookup?locations=27.9881,86.9250|46.5763,7.6613"Why people move
No key needed, same URL structure, and a server that is monitored and paid for.
Same free allowance, key or not. Requests to openelevation.mygeocode.com count toward the same 2,500 free requests a day your address, or your key, gets on our own endpoints. Above that, prepaid credit at €0.0001 per request, or €50 a month for an Unlimited key. Signing up takes a name and an email address, and no card.
Endpoints
| Path on openelevation.mygeocode.com | What it does | Backed by |
|---|---|---|
/api/v1/lookup?locations=lat,lon|lat,lon | Lookup by GET | Elevation lookup |
/api/v1/lookup (POST, JSON body) | Lookup by POST | Elevation lookup |
Example response
This is what the request above returns. Field names, nesting and types follow Open-Elevation. Only the data behind them is ours.
{
"results": [
{
"latitude": 27.9881,
"longitude": 86.925,
"elevation": 8627
},
{
"latitude": 46.5763,
"longitude": 7.6613,
"elevation": 843
}
]
}Details and differences
Open-Elevation has no key, and none is needed here either for the first 2,500 requests a day. For credit, packages and a usage history, add key=... to the query or send the X-API-Key header.
- Both the GET form with
locations=lat,lon|lat,lonand the POST body with alocationslist are served. - Heights come from a global terrain model at about 460 m resolution, land and sea floor, and are returned as whole metres, as Open-Elevation does.
- Up to 1,024 points per request; each point counts as one request.
If your client depends on a field or behaviour that is not listed here, tell us. Compatibility gaps get fixed quickly because they are usually small.
Other drop-in hosts
- Google Maps
- Bing Maps
- HERE
- Mapbox
- Geocode.Farm
- Nominatim (OSM)
- OpenCage
- LocationIQ
- Geoapify
- TomTom
- MapQuest
- Geocodio
- PositionStack
- ip-api
- ipinfo
- ipstack
How the drop-ins work, the overview, and the JavaScript library drop-ins.