Forward & Reverse Geocoding

FREEMIUM
Verified
By Geocoding | Updated 2 days ago | Mapping
Popularity

9.8 / 10

Latency

209ms

Service Level

100%

Forward & Reverse Geocoding Overview

Followers: 4
Resources:
Product Website Terms of use
API Creator:
avatar
Geocoding
GeocodeSupport
Rate API:
Log In to Rate API

README

Easy to use forward and reverse geocoding search based on OpenStreetMap data. Just add your X-RapidAPI-Key header with your apikey and use the free-form forward geocoding search or the structured forward geocoding search (e.g. for address completion, postalcode retrieval or showing your address on a map) or the reverse geocoding search for asset tracking and more.

You can use this geocoding service with any map you like, e.g. the MapTiles API here at RapidAPI.

Attribution Requirement
You have to attribute OpenStreetMap contributors (see https://www.openstreetmap.org/copyright ) as this geocoder is based on OpenStreetMap data.

For a complete documentation of all available query parameters and options, visit https://docs.geocodingapi.net

Rate Limiting
Please note that the Forward & Reverse Geocoding API is bound by rate-limiting. For continuous frequent requests, requests per second are limited to 3 (Basic plan), 6 (Pro plan), 24 (Ultra plan) or 48 (Mega plan). There is a burst rate allowed of up to 4 (Basic plan), 9 (Pro plan), 36 (Ultra plan) or 72 (Mega plan) requests per second for one second max but using this burst rate will dimish your further available requests in the next second, so that you can only send a max amount of 6 (Basic plan), 12 (Pro plan), 48 (Ultra plan) or 96 (Mega plan) requests in total in two seconds. Further requests will get blocked (indicated by a 429 http error - “too many requests”). The blocking may uphold for several seconds before you are allowed to send requests again. Please note that the bulk rate requests limits are an approximation and are dependent on the round trip time latency of your requests.

Rating: 5 - Votes: 4