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, with 30 metre data.
Change one hostname
| Original host |
|
|---|---|
| Use instead | openelevation.mygeocode.com |
| Key parameter | None on the original. Add key=... to use your account, or whitelist your server IPs. Or send nothing and use the free 2,500 a day. |
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.
Try it before you sign up for anything. Requests to openelevation.mygeocode.com count toward the same 2,500 a day you get on our own endpoints, with no key and no account. Above that, credits at $0.001 per request or €50 a month unlimited. Signing up takes an email address and nothing else.
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": 8752 },
{ "latitude": 46.5763, "longitude": 7.6613, "elevation": 3459 }
]
}Details and differences
- Elevation is returned as an integer number of metres, as Open-Elevation does. Use our own /v1/elevation endpoint if you want decimals and the dataset resolution.
- 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.