Polygon bounding box calculator

This calculator scans your polygon coordinates and returns the southwest-style minimum corner and northeast-style maximum corner without calling a map service. It is useful for map viewport setup, spatial filtering, indexing, validation, and quick geographic summaries. The calculation is deterministic, accepts ordinary decimal-degree coordinates, and uses the same logic in the browser and through the API.

Prepare the polygon vertices

Provide at least three vertices, with each vertex represented by a lat and lon number in decimal degrees. Latitude must fall between -90 and 90, while longitude must fall between -180 and 180. The points may describe a convex polygon, a concave polygon, or even a ring whose first point is repeated at the end. Unlike an area or centroid calculation, bounding-box calculation does not depend on winding direction and does not need the vertices to arrive clockwise or counterclockwise. Every supplied point contributes independently to the extrema. The capability still requires three points because its input represents a polygon rather than an arbitrary point collection. Use numbers rather than formatted coordinate strings, degree symbols, cardinal-direction suffixes, or comma-separated text. Invalid records, missing coordinates, non-finite values, and out-of-range geographic coordinates are rejected clearly instead of being coerced. A request can contain up to 10,000 vertices, which keeps execution predictable while covering detailed boundaries used in typical application workflows.

Understand the returned corners

The result contains min_corner and max_corner. The minimum corner combines the smallest latitude found anywhere in the list with the smallest longitude; the maximum corner combines the largest latitude with the largest longitude. These corners describe an axis-aligned rectangle in the latitude-longitude coordinate plane. They are not necessarily vertices of the original polygon, because the lowest latitude and lowest longitude may occur at different points. No padding, projection, rounding, or geodesic expansion is applied, so values in the response preserve the numeric extrema supplied by the caller. Longitude is treated literally within the conventional -180 to 180 range. Consequently, a polygon that crosses the antimeridian can produce a numerically wide box, such as one extending from -179 to 179 degrees. That behavior is intentional and explicit: it reports ordinary minimum and maximum longitude rather than choosing a wrapped map viewport. If your application uses wrapped longitudes, it can compare alternative antimeridian-aware spans after receiving these direct bounds.

Use the bounds in mapping and data pipelines

Bounding boxes are compact summaries, so they fit naturally at the start of many spatial workflows. A map interface can use the two corners to choose an initial viewport. A database import can store the four extrema beside a polygon and use them for a fast first-pass overlap test before running a more expensive point-in-polygon or geometry intersection operation. Validation code can compare expected service regions with submitted shapes, while analytics jobs can group boundaries by broad geographic extent. Remember that the box contains the polygon but does not reproduce its shape: points inside the rectangle may still lie outside a concave polygon, and overlapping boxes do not prove that two polygons intersect. The calculation also works directly in latitude and longitude rather than a projected coordinate reference system. That makes it ideal for coordinate envelopes and map navigation, but widths expressed in degrees are not constant physical distances across latitudes. Run it free in the browser for individual checks, or automate repeatable requests through the API for $0.002 per item.