Bounding box explorer
Look up a place's bounding box, drag its corners to adjust it, and copy it in the format your software expects.
Geocoding results come from OpenStreetMap data (© OpenStreetMap contributors, ODbL) via Nominatim, cached on our server. Map tiles © OpenStreetMap contributors.
Why the same box has different orderings
There is no single convention. GeoJSON (RFC 7946) and this site use west, south, east, north. Nominatim returns south, north, west, east. Leaflet and Google-style APIs take corner pairs in latitude, longitude order. Mixing them up is one of the most common geocoding bugs, so every format is shown here and labelled.
A box whose west edge is greater than its east edge crosses the 180° meridian, for example Fiji or the Chukotka peninsula. The explorer detects and draws these correctly. Read the full explanation in geographic bounding boxes explained.
A nod to the original OpenGeocoder
The 2012 OpenGeocoder stored nothing but strings and boxes: you searched, and if your place was missing you dragged a rectangle over it and saved it. Those boxes are still searchable in the 2012 archive.