Calculating bbox...
Enter a center coordinate and radius to calculate the latitude/longitude bounding box.
What Is a Bounding Box from Center Point and Radius?
A bounding box from center point and radius is the smallest practical latitude/longitude rectangle that fully contains a circular search area around one coordinate. Developers use it to turn a slow "find everything within 25 miles" query into a fast first-pass filter. GIS analysts use the same idea to build map extents, request tiles, crop datasets, or limit API calls before running a more precise distance calculation.
The output uses the common web map and geospatial API order: minLon, minLat, maxLon, maxLat. That order is easy to mix up because humans often say latitude first, but formats such as GeoJSON and many map APIs use longitude first. This calculator labels each value and also provides SQL and GeoJSON output so the result can move directly into an application or GIS workflow.
How the Radius to Bounding Box Calculation Works
The calculator treats Earth as a sphere using a WGS84 mean radius of 6,371.0088 km. It converts the requested radius into an angular distance, then expands the center latitude north and south by that amount. Longitude is wider at high latitudes because meridians converge toward the poles, so the longitude delta is adjusted by the cosine of the center latitude.
This spherical method is accurate enough for search prefilters, map extents, and service-area lookups. It is not a substitute for the final exact-distance filter. After a database returns candidates inside the bounding box, run a haversine, Vincenty, PostGIS distance, or platform-specific geospatial distance function to remove points that are inside the rectangle but outside the circle.
Using a Bounding Box for Location Search SQL
A bounding box is useful because ordinary numeric indexes on latitude and longitude can reject most rows before expensive distance math runs. In the normal case, the SQL shape is simple: latitude sits between min and max latitude, and longitude sits between min and max longitude.
When the box crosses the antimeridian, longitude cannot use one BETWEEN condition. The valid longitudes are split on both sides of ±180°, so the calculator returns an OR clause. That detail prevents the classic production bug where searches near Fiji, Kiribati, or eastern Russia silently return no results.
Common Radius Search Bounding Box Use Cases
| Use case | Typical radius | Why a bbox helps |
|---|---|---|
| Store locator | 5-50 km | Fast first-pass database filter before exact distance sorting. |
| Food delivery | 2-15 miles | Limits candidate restaurants, couriers, or addresses before service checks. |
| Real estate search | 1-25 miles | Finds listings near a school, city, transit stop, or user-selected point. |
| Weather alerts | 10-100 km | Builds an approximate extent for map overlays, warnings, and API requests. |
| Fleet tracking | 500 m-20 km | Narrows nearby vehicles, depots, or incidents in real-time dashboards. |
Handling Antimeridian and Pole Edge Cases
Most bounding-box calculators work in the middle of a continent and fail near the International Date Line. This one explicitly detects wrapped longitude ranges. If min longitude is greater than max longitude, the box crosses the antimeridian and the GeoJSON output becomes a MultiPolygon split across the map edge.
Near the North Pole or South Pole, a radius can include every longitude. When that happens, longitude bounds are set to -180° and 180°. That behavior is clearer and safer than returning a misleading narrow longitude interval from unstable tangent math near the pole.
Bounding Box vs Exact Distance Search
A bounding box is a rectangle around a circle. It includes the whole search radius, but it also includes the rectangle corners, which are farther away than the requested radius. That is intentional: the box is a fast prefilter, not the final answer.
The production pattern is two-stage. First, query the bounding box to reduce the candidate set. Second, calculate exact distance from the center point and keep only rows within the radius. This pattern gives good performance without losing correct matches at the circle edge.
Bounding Box Calculator FAQ
How do I calculate a bounding box from latitude, longitude, and radius?
Convert the radius to an angular distance on Earth, expand latitude north and south, then calculate a longitude delta adjusted by the cosine of the center latitude. This tool performs those steps and returns copy-ready bbox, SQL, and GeoJSON output.
Why is a bounding box only an approximation for radius search?
The search radius is circular, but a bounding box is rectangular. The rectangle contains the full circle plus extra area in the corners, so you should apply an exact distance formula after the bounding-box filter.
How do I query a bounding box that crosses the antimeridian?
Use latitude BETWEEN min and max latitude, then split longitude with an OR condition: longitude greater than minLon or longitude less than maxLon. The calculator generates this wrapped SQL automatically.
Should I use bounding box filtering before a haversine distance query?
Yes. The bounding box reduces the number of rows that need trigonometric distance calculations. This is a common approach for store locators, nearby search, and map APIs.
What order should bounding box coordinates use in APIs?
Most geospatial APIs use minLon, minLat, maxLon, maxLat. GeoJSON coordinates also use longitude, latitude order. This calculator labels the order clearly to prevent lat/lon swaps.
Does this bounding box calculator work near the poles?
Yes. If the radius reaches a pole, the calculator returns the full longitude range from -180° to 180° and marks the result as pole coverage.
Related Calculators
Haversine Distance Calculator
Calculate exact great-circle distance between two coordinates
Destination Point Calculator
Find a coordinate from bearing and distance
Distance & Bearing Calculator
Get distance and initial bearing between coordinates
Coordinate Converter
Convert between latitude and longitude coordinate formats
UTM Zone Finder
Find the UTM zone and EPSG code for a coordinate