geo.bounding-box
Latitude/longitude bounding box that contains every point within a distance of a centre point.
2.0.0 · published 2026-10-03 by charlie · Anterra
Pinned by 15 tests, run in TypeScript, Python and Rust.
What it does
The smallest latitude/longitude box that contains every point within a given distance of a centre. It is the cheap first filter for "find everything within 10 km": query the box with an index, then check the real distance (`geo.distance`) on what comes back.
## Method
For example
bounding_box(51.507, -0.128, 10,000)→ min lat 51.417, min lng -0.272, max lat 51.597, max lng 0.017 10 km around central Londonbounding_box(0, 0, 100,000)→ min lat -0.899, min lng -0.899, max lat 0.899, max lng 0.899 100 km around the origin is square in degrees on the equatorbounding_box(60, 10, 100,000)→ min lat 59.101, min lng 8.201, max lat 60.899, max lng 11.799 at 60 degrees north the longitude span is about twice the latitude span
The function
The same function in TypeScript, Python and Rust, pinned by the same tests. Pick your language; the choice follows you around the registry.
pub fn bounding_box(lat: f64, lng: f64, distance_metres: f64) -> BoundingBox
| lat | float | centre latitude in degrees, -90 to 90 |
| lng | float | centre longitude in degrees, -180 to 180 |
| distance_metres | float | search radius in metres, 0 or more |
| returns | BoundingBox | minLng > maxLng means the box crosses the antimeridian |
The type it declares, generated into your project
/// Degrees, rounded outward to 7 decimals so the box always contains the circle.
#[derive(Debug, Clone, Copy, PartialEq)]
pub struct BoundingBox {
pub min_lat: f64,
pub min_lng: f64,
pub max_lat: f64,
pub max_lng: f64,
}
Your code names it in one line, in the file that uses it
fune!(geo.bounding-box@^2); // then call bounding_box(…)
Imports name this capability’s declared dependencies, which fune builds next to it in your project; each one links to its page.
use super::funejson::Value; ← the fune runtime: the JSON value the test vectors use; fune build keeps it only where a signature takes one
use super::math_atan::atan; ← from math.atan ^1.0.0 · built alongside by fune
use super::math_sin_cos::sin_cos; ← from math.sin-cos ^1.0.0 · built alongside by fune
// The latitude/longitude box that contains every point within a distance of a
// centre, by the method of J. P. Matuschek, "Finding Points Within a Distance
// of a Latitude/Longitude Using Bounding Coordinates"
// (http://janmatuschek.de/LatitudeLongitudeBoundingCoordinates).
//
// Sine, cosine and arctangent come from math.sin-cos and math.atan instead of
// f64::sin and friends, because the platform maths library may differ in the
// last bit between Rust, JavaScript and Python. The shared helpers use only
// + - * /, and the rest here only + - * / sqrt floor ceil, all correctly
// rounded, in the same order in all three.
/// IUGG mean radius R1 of the GRS 80 ellipsoid (Moritz, Journal of Geodesy 74 (2000)).
const EARTH_RADIUS_METRES: f64 = 6371008.8;
/// Ten millionths of a degree, about a centimetre.
const SCALE: f64 = 10000000.0;
/// Within a millionth of a grid step of a 7-decimal value counts as that value,
/// so a centre of 51.5074 stays 51.5074 rather than becoming 51.5073999.
const SNAP: f64 = 0.000001;
const PI: f64 = 3.141592653589793;
const HALF_PI: f64 = PI / 2.0;
const DEGREES: f64 = PI / 180.0;
/// asin for 0 <= x, on math.atan: asin x = atan(x / sqrt(1 - x^2)), with
/// (1 - x)(1 + x) to keep precision near 1. There is no shared asin; x >= 1
/// (reachable only by rounding, just short of a pole) is a quarter turn.
fn asin_positive(x: f64) -> f64 {
if x >= 1.0 {
return HALF_PI;
}
atan(x / ((1.0 - x) * (1.0 + x)).sqrt())
}
/// Outward rounding: a lower bound goes down and an upper bound goes up, so
/// rounding can only grow the box, never cut the circle.
fn round_down(x: f64) -> f64 {
(x * SCALE + SNAP).floor() / SCALE + 0.0
}
fn round_up(x: f64) -> f64 {
(x * SCALE - SNAP).ceil() / SCALE + 0.0
}
fn check_number(value: f64, what: &str) {
if !value.is_finite() {
panic!("{} must be a finite number", what);
}
}
/// The box containing every point within `distance_metres` of (`lat`, `lng`).
///
/// # Panics
/// Panics if a coordinate is out of range or the distance is negative or not finite.
pub fn bounding_box(lat: f64, lng: f64, distance_metres: f64) -> BoundingBox {
check_number(lat, "latitude");
check_number(lng, "longitude");
check_number(distance_metres, "distance");
if lat < -90.0 || lat > 90.0 {
panic!("latitude must be between -90 and 90 degrees");
}
if lng < -180.0 || lng > 180.0 {
panic!("longitude must be between -180 and 180 degrees");
}
if distance_metres < 0.0 {
panic!("distance must be 0 or more metres");
}
let r = distance_metres / EARTH_RADIUS_METRES;
let r_degrees = r / DEGREES;
let mut min_lat = lat - r_degrees;
let mut max_lat = lat + r_degrees;
let mut min_lng;
let mut max_lng;
if min_lat > -90.0 && max_lat < 90.0 {
let sin_r = sin_cos(r).sin;
let cos_lat = sin_cos(lat * DEGREES).cos;
let d_lng = asin_positive(sin_r / cos_lat) / DEGREES;
min_lng = lng - d_lng;
max_lng = lng + d_lng;
// Past the antimeridian the bound comes round the other side, leaving
// min_lng > max_lng: the box is the two strips either side of 180.
if min_lng < -180.0 {
min_lng += 360.0;
}
if max_lng > 180.0 {
max_lng -= 360.0;
}
} else {
// The circle reaches a pole, so it covers every longitude.
if min_lat < -90.0 {
min_lat = -90.0;
}
if max_lat > 90.0 {
max_lat = 90.0;
}
min_lng = -180.0;
max_lng = 180.0;
}
BoundingBox {
min_lat: round_down(min_lat),
min_lng: round_down(min_lng),
max_lat: round_up(max_lat),
max_lng: round_up(max_lng),
}
}
pub fn bounding_box_to_value(b: &BoundingBox) -> Value {
Value::obj(vec![
("minLat", Value::Float(b.min_lat)),
("minLng", Value::Float(b.min_lng)),
("maxLat", Value::Float(b.max_lat)),
("maxLng", Value::Float(b.max_lng)),
])
}
pub fn fune_vector(args: &[Value]) -> Value {
// Refuse what the typed signature cannot hold, with the wording TypeScript
// and Python use, rather than let the conversion below quietly change it.
if !matches!(args[0], Value::Int(_) | Value::Float(_)) {
panic!("latitude must be a finite number");
}
if !matches!(args[1], Value::Int(_) | Value::Float(_)) {
panic!("longitude must be a finite number");
}
if !matches!(args[2], Value::Int(_) | Value::Float(_)) {
panic!("distance must be a finite number");
}
bounding_box_to_value(&bounding_box(
args[0].as_f64(),
args[1].as_f64(),
args[2].as_f64(),
))
}Install
fune build
With that line in your source, in a Rust project (language rust in fune.project), fune build resolves it and its 2 dependencies, pins them in fune.lock, downloads only the Rust package of each, and builds the code above into your project’s .fune/build, one readable file per capability with a header linking back here. A crate’s build.rs runs it before every compile. Or pin a range in fune.project and build in one step:
fune add geo.bounding-box
The manifest, vectors and README with only the Rust implementation. Install it without the registry with fune add ./geo.bounding-box-2.0.0-rust.fune, or fetch it from a terminal with fune pull geo.bounding-box@2.0.0:rust.
The whole function, every language, is one file too: geo.bounding-box-2.0.0.fune, 22,478 bytes, sha256 7e79132161c5e6092da15d9f79b040dfba351e8cb429691518d00652677f0457. It installs into a project of any language.
Customise it in your app
The seams this capability offers. Put a marker directly above a function of your own and fune build wires it into the built code; the package on the registry is not changed, the built file’s header lists it under CUSTOMISED, and fune hooks lists every hook in the project. How hooks work.
before — your function gets the arguments and returns them, changed or not, or throws to refuse the call.
// fune: before geo.bounding-box
after — your function gets the result and the arguments, and returns the final result.
// fune: after geo.bounding-box
replace — inside this capability’s code only, calls to a dependency go to your function, with the same signature. Other capabilities that use it are unaffected; write in * to replace it everywhere.
// fune: replace math.atan in geo.bounding-box
// fune: replace math.sin-cos in geo.bounding-box
step — your function runs at a numbered point inside the function’s body, receives the in-scope values it names as parameters, and may return replacements. List the points with fune show geo.bounding-box --steps.
// fune: step geo.bounding-box after <n|label>
Tests
A version published now needs at least 8 tests for every function, and one that expects the error for each function that throws; the registry refuses it otherwise. fune verify --all runs each case in TypeScript, Python and Rust, and a project runs them again with fune verify. This page lists the cases; it does not run them. The exact JSON is vectors.json.
| Case | Arguments | Expected | |
|---|---|---|---|
| 10 km around central London | 51.507, -0.128, 10,000 | → | min lat 51.417, min lng -0.272, max lat 51.597, max lng 0.017 |
| 100 km around the origin is square in degrees on the equator | 0, 0, 100,000 | → | min lat -0.899, min lng -0.899, max lat 0.899, max lng 0.899 |
| at 60 degrees north the longitude span is about twice the latitude span | 60, 10, 100,000 | → | min lat 59.101, min lng 8.201, max lat 60.899, max lng 11.799 |
| southern and eastern hemispheres | -33.869, 151.209, 5,000 | → | min lat -33.914, min lng 151.155, max lat -33.824, max lng 151.263 |
| zero distance is the point itself, not nudged a grid step outward by its binary value | 51.507, -0.128, 0 | → | min lat 51.507, min lng -0.128, max lat 51.507, max lng -0.128 |
| crossing the antimeridian wraps maxLng round, so minLng > maxLng | 0, 179.9, 50,000 | → | min lat -0.45, min lng 179.45, max lat 0.45, max lng -179.65 |
| a centre on the antimeridian wraps minLng round | 45, -180, 1,000 | → | min lat 44.991, min lng 179.987, max lat 45.009, max lng -179.987 |
| a circle over the north pole covers every longitude (the asin formula alone gives NaN here) | 89.9, 0, 20,000 | → | min lat 89.72, min lng -180, max lat 90, max lng 180 |
| a circle over the south pole covers every longitude | -89.95, 45, 10,000 | → | min lat -90, min lng -180, max lat -89.86, max lng 180 |
| just short of the pole the longitude span is very wide but not global | 80, 0, 1,100,000 | → | min lat 70.107, min lng -81.634, max lat 89.893, max lng 81.634 |
Show the other 5 tests
| Case | Arguments | Expected | |
|---|---|---|---|
| a radius larger than the Earth is the whole globe | 0, 0, 30,000,000 | → | min lat -90, min lng -180, max lat 90, max lng 180 |
| negative distance is an error | 51.5, 0, -1 | → | error: distance must be 0 or more metres |
| latitude out of range is an error | 95, 0, 1,000 | → | error: latitude must be between -90 and 90 degrees |
| longitude out of range is an error | 0, -181, 1,000 | → | error: longitude must be between -180 and 180 degrees |
| a distance that is not a number is an error | 0, 0, 10km | → | error: distance must be a finite number |
More from the author
J. P. Matuschek, "Finding Points Within a Distance of a Latitude/Longitude Using Bounding Coordinates", http://janmatuschek.de/LatitudeLongitudeBoundingCoordinates. The Earth is a sphere of radius 6,371,008.8 m (IUGG mean radius, as in `geo.distance`). The angular radius is r = d / R; latitudes are centre ± r; the longitude half-width is asin(sin r / cos lat), which is wider than r away from the equator (about twice as wide at 60°).
## Edge cases
- **Poles.** If the circle reaches or crosses a pole, it covers every longitude: the box is clamped to ±90 and runs from -180 to 180. Without this check the asin formula is asked for asin of more than 1 and returns NaN. - **The antimeridian.** A bound that passes ±180 comes round the other side, so minLng > maxLng. That is the signal that the box is two strips, minLng..180 and -180..maxLng; a query must OR them rather than use BETWEEN. - **Zero distance** is the point itself. **Negative distance** is an error. - A radius larger than the Earth gives the whole globe.
## Rounding outward
Bounds are rounded to 7 decimal places (about 1 cm), outward: the minimums down and the maximums up, so rounding can only grow the box and never cut off part of the circle. A value within a millionth of a step of a 7-decimal value (about 1e-13 degrees) is taken to be that value, so a centre of 51.5074 with distance 0 stays 51.5074 rather than becoming 51.5073999 because its binary value sits a hair below.
`math.round-float` is not used: it rounds to the nearest, and a box has to round each bound in its own direction, with the snap above. Those two one-line functions (floor or ceil of x × 10^7 ± 10^-6) stay here.
## What changed in 2.0.0
- **Sine, cosine and arctangent come from `math.sin-cos` and `math.atan`** instead of private copies. The registry has no asin, so a two-line asin for 0 ≤ x stays here, built on `math.atan`: asin x = atan(x / √((1 − x)(1 + x))), and π/2 when rounding pushes x to 1 or more just short of a pole. - **The unrounded bounds can differ from 1.x in the last bits** (for about one input in twelve), because the shared helpers reduce angles and evaluate atan differently. A difference that small changes a 7-decimal bound only when the bound lies within about 1e-13 degrees of a grid step, so no sampled box changed (none of 10,500), but it is not impossible, which is why this is a new major version. - **Vectors.** Every 1.x vector keeps its expected answer; each was re-derived from an independent 60-digit reference (own series for π, sin, cos and atan, asin through atan, decimal square root) with the outward rounding and snap applied to the true bounds, and matches. There is no rounding-change vector: the outward rounding is unchanged, and a trig-only change that crosses a grid step would need a bound within about 1e-13 degrees of it, roughly one chance in ten million per bound, too rare to construct from realistic coordinates. The vectors now compare exactly (`floats exact`): the three languages return the same doubles.
## Accuracy
Against the 60-digit reference, with the inputs taken as the exact doubles given, on 4,500 random centres within 80° of the equator and radii from 1 m to 20,000 km, the unrounded bounds are within 1.1e-13 degrees of the true bounds and the longitude half-width within 8 units in the last place. Within a fraction of a degree of a pole the problem is ill-conditioned (asin of nearly 1, the cosine of a latitude near 90°), and the error grows to about 3e-12 degrees, still some 30,000 times smaller than a grid step. 1.x had the same bounds. Every one of the 10,500 sampled boxes, rounded outward, equalled the true box rounded outward.
## Why the answers are identical in every language
The trigonometry comes from `math.sin-cos` and `math.atan`, which use only correctly rounded IEEE 754 operations (+ − × ÷) in the same order in all three languages, instead of the platform's Math.sin, which may differ in the last bit and could tip a value across a rounding step. The rest (sqrt, floor, ceil) is correctly rounded too, so TypeScript, Python and Rust compute the same doubles before and after rounding.
Files
| Path | Bytes |
|---|---|
| README.md | 4,494 |
| impl/python.py | 3,762 |
| impl/rust.rs | 4,843 |
| impl/typescript.ts | 3,722 |
| vectors.json | 2,743 |