## How it works
-The reveser geocoding API does not exactly compute the address for the
+The reverse geocoding API does not exactly compute the address for the
coordinate it receives. It works by finding the closest suitable OSM object
and returning its address information. This may occasionally lead to
unexpected results.
https://nominatim.openstreetmap.org/reverse?lat=<value>&lon=<value>&<params>
```
-where `lat` and `lon` are latitude and longitutde of a coordinare in WGS84
+where `lat` and `lon` are latitude and longitude of a coordinate in WGS84
projection. The API returns exactly one result or an error when the coordinate
is in an area with no OSM data coverage.
-Additional paramters are accepted as listed below.
+Additional parameters are accepted as listed below.
!!! warning "Deprecation warning"
The reverse API used to allow address lookup for a single OSM object by
- its OSM id. This use is now deprecated. Use the [Address Lookup API](../Lookup)
+ its OSM id. This use is now deprecated. Use the [Address Lookup API](Lookup.md)
instead.
### Output format
* `email=<valid email address>`
-If you are making large numbers of request please include an appropriate email
+If you are making a large number of requests, please include an appropriate email
address to identify your requests. See Nominatim's [Usage Policy](https://operations.osmfoundation.org/policies/nominatim/) for more details.
"licence":"Data © OpenStreetMap contributors, ODbL 1.0. https:\/\/www.openstreetmap.org\/copyright",
"osm_type":"way",
"osm_id":"280940520",
-"lat":"-34.4391708",
+ "lat":"-34.4391708",
"lon":"-58.7064573",
"place_rank":"26",
"category":"highway",