simplemaplab

Methodology

By Marko Visic · Updated Nov 21, 2026

SimpleMapLab's distance, radius, routing, area, location, elevation and time-zone tools, its blank maps and its studies rest on a short list of formulas and datasets. Below: each method as the site's code runs it, the data behind it with its license and date, and the known limits.

Checking our numbers. Each study's full results download as JSON and CSV under CC BY 4.0, the inputs are listed in the sources table, and every method is written out on this page. If a figure on the site doesn't match the source it names, that's a bug: please tell us. Every fix is listed in the corrections log.

1. Distance and great-circle math

Straight-line distances on the site, in the Distance Between Two Places tool, the radius tools and the "nearest" searches in the studies, use the haversine formula: the great-circle distance on a sphere. The distance and halfway tools, Turf.js's own distance and circle functions and both ZIP-code studies use Turf's mean Earth radius, R = 3,958.76 mi (6,371.0088 km). The ZIP, city and population radius lookups on our server use 3,958.8 mi (6,371 km) and some map helpers 3,959 mi; those radii differ by less than 0.01%.

The haversine formula is:

a = sin²(Δlat/2) + cos(lat₁)·cos(lat₂)·sin²(Δlng/2)
d = 2·R·arcsin(√a)

The Earth is slightly flattened, so a sphere is an approximation. Against the distance measured on the WGS84 ellipsoid (Vincenty's formulae), the sphere is within about 0.6%, checked over 140,000 random pairs in November 2026. The largest gaps are on short north–south lines: about 0.56% too long near the equator and 0.45% too short near the poles. On long lines the gap is smaller, −0.26% to +0.38% at 6,214 mi (10,000 km). The site uses the spherical formula everywhere, so the tools and the studies measure distance the same way.

2. Halfway point: the great-circle midpoint

The Halfway Point tool returns the geographic midpoint of two places: the point on the shortest path over the Earth's surface (the great circle) that is the same straight-line distance from both. It is not the average of the two latitude/longitude pairs, which is correct only for points on the same meridian and drifts on east–west or long pairs.

It is computed as the standard spherical midpoint: both points are converted to unit vectors, the two vectors are summed, the sum is normalized back to unit length, and that direction is converted back to latitude and longitude (longitude wrapped to −180…180). The midpoint does not depend on the Earth's radius. The tool measures the total with the haversine distance on the 3,958.76 mi sphere, and each side is half of it.

Antipodal case: when the two places are almost opposite each other on the globe (more than 12,400 mi apart, or the summed vector collapses to zero), every point on the connecting great circle is equally "halfway," so there is no single midpoint and the tool says so instead of drawing one.

This is a straight-line midpoint, not a driving midpoint. The point that splits the drive evenly can sit tens of miles away, because highways bend around terrain, water and city grids. Each side's drive time is an estimate at 55 mph over the straight-line distance until you press “Show real driving distance & time”, which asks the router (section 3) for each side.

3. Road distance and drive time

Road distances and drive times come from Valhalla, an open-source route planner that FOSSGIS e.V. runs as a public server on OpenStreetMap roads. Your browser doesn't call it. Distance Between Two Places, Crow Flies Distance, Multi-Stop Route Distance, the Distance Matrix Calculator and the halfway tool's driving option ask our server (/api/route), and our server asks Valhalla for a car route. The answer is the route's length and its time on clear roads. Valhalla takes speeds from OpenStreetMap's speed limits where they are mapped and from defaults for the road type where they aren't, and the server has no live traffic data.

FOSSGIS's terms allow at most one request a second, so each page sends its router requests one at a time, a little over a second apart, and the tools with many legs send them in few requests. Multi-Stop Route Distance asks for one route through its stops, up to 10 stops and 932 mi (1,500 km) of straight line from stop to stop in a request, and reads each leg from it; when one leg has no road the router refuses the whole route, and the tool then asks those legs one by one. The Distance Matrix Calculator sends one matrix request when every point is within 93 mi (150 km) of every other, and otherwise routes through several points at once, each step one pair. Our server sends the router the site's name and address with each request, as the terms also ask.

The halfway tool's driving option asks for three routes: from each place to the straight-line midpoint, and between the two places. On that last route, the maneuver times place the halfway point by drive time, where half the route's time is behind you. For the towns near that point, our server (/api/drive-times) times the drive from both places on the same Valhalla server. When every town is within 93 mi (150 km) of both places in a straight line, one matrix request does it, and a town the matrix leaves without a time gets its own route. Past that the server refuses a matrix (its answer on November 15, 2026), so ours asks one route per town, from the first place through the town to the second, with requests starting a second apart, as FOSSGIS's usage terms ask. On those routes the time from the town on to the second place stands in for the drive the other way. The tool lists the fairest town first: the one whose longer drive is shortest.

The public server routes only between places up to 932 mi (1,500 km) apart in a straight line, so the tools ask it only then. Past that distance, or where no road joins the two places, they show the straight-line distance alone. On the distance tool, the walking and cycling times are the road distance at 3 mph and 12 mph, and the flying time is the straight line at 500 mph.

4. Drive-time areas (Valhalla isochrones)

The Drive Time Map asks our server (/api/isochrone), which asks the same FOSSGIS server for the area reachable from the start point within each chosen time, by car, bike or on foot (Valhalla's auto, bicycle and pedestrian modes). The times are 10, 15, 20, 30, 45 or 60 minutes, or a custom time from 5 to 60; the public server fails on larger areas, so 60 minutes is the limit. It takes at most four times per request, so the tool splits longer lists. Valhalla returns each area as polygons, simplified with a 492 ft (150 m) Douglas–Peucker tolerance and with pieces under 30% of the largest piece's area dropped.

The speeds are Valhalla's, as in section 3, and live traffic is not modeled: the areas show free-flowing roads, so in congested traffic you reach less ground in the same time. The area figure the tool prints is an approximation: the shoelace formula on longitude and latitude, scaled at 69.172 mi per degree and by the cosine of the polygon's mean latitude.

5. Radius circles

The Map Radius Tool, Find ZIP Codes in Radius, Find Cities in Radius and Population Within Radius draw their circles with Turf.js's circle(): 80 points, each at the set radius from the center along a great circle on the 3,958.76 mi sphere. On the WGS84 ellipsoid the edge is within about 0.6% of the set radius (section 1).

On the site's web map (Web Mercator) a circle is drawn larger the farther it is from the equator, and a wide circle looks egg-shaped, its poleward side stretched more than the other. Its points are still the set distance from the center. The rings on the study maps, such as the empty zones in the Most Remote Places study, are drawn with d3-geo's geoCircle(), with a vertex every 2° around the ring.

6. Area and radius population

The Map Area Calculator uses Turf.js's area(): the polygon's area on a sphere of radius 3,958.76 mi (6,371.0088 km), the same sphere as the distances. Its perimeter is the sum of the haversine lengths of the sides.

The Map Radius Tool prints a circle's area and circumference with the flat-circle formulas π·r² and 2π·r. On the sphere the area inside a circle is 2πR²(1 − cos(r/R)), slightly less: π·r² is larger by 0.005% at a 100 mi radius, 0.13% at 500 mi and 0.53% at 1,000 mi.

The Population Within Radius tool sends the center and radius to our server, which measures the haversine distance (R = 3,958.8 mi) from the center to every ZIP code's point, the latitude and longitude in the SimpleMaps file, and sums the population of the ZIPs whose point is inside the circle. The sum covers ZIPs with a Census ZIP Code Tabulation Area; PO-box, single-business and military ZIPs inside the circle are counted separately, without population. The density figure divides the total by the circle's area, π·r².

7. Location lookups

The location tools start from a point: your device's position (GPS or network) when you press the location button, a searched address, or a tap on the map. Most of them ask OpenStreetMap's Nominatim about that point instead of testing it against boundaries themselves:

Two tools do run a point-in-polygon test in your browser: Address to County Lookup, against the 2017 county boundaries, and What Country Am I In?, against Natural Earth's 1:50m country shapes (it asks Nominatim when no shape contains the point, at a small island for example). The test casts a ray from the point and counts how often it crosses the shape's edges; an odd count means inside. Before you press the location button, the where-am-I pages show an approximate location from your IP address, which our host, Vercel, provides; it isn't stored.

8. Place search and reverse geocoding

Your browser sends text searches straight to Photon and reverse lookups straight to Nominatim; we don't proxy or store them. Driving routes, drive-time areas, time zones, ZIP lookups and population counts go through our server, as the Privacy Policy explains. The site sends no API key to Photon or Nominatim.

9. Elevation

The tools that show one point's elevation (What Is My Elevation?, the Elevation Finder, Coordinates to Address and the Random Location Generator), the elevation profile and the Horizon Distance Calculator read the public AWS Terrain Tiles (Mapzen "Terrarium" PNG tiles). Per Mapzen's data-sources documentation, they combine USGS 3DEP elevation at about 33 ft (10 m) resolution in the US outside Alaska, SRTM at 98 ft (30 m) on most other land, ArcticDEM north of 60°, several national models and NOAA's ETOPO1 for ocean depth. Each pixel encodes elevation as meters = R·256 + G + B/256 − 32768.

A point readout uses zoom 14, where a pixel spans about 31 ft (9.6 m) at the equator and 22 ft (6.8 m) at 45° latitude, and is bilinearly interpolated between the four surrounding pixels. Values below zero (land below sea level, or the sea floor) are reported, not set to zero.

Over most open ocean the tiles above zoom 10 hold 0, while the zoom-10 tiles still carry the ocean depth from NOAA's ETOPO1. So where a point on water reads 0 at zoom 14, or a zoom-14 value far off the zoom-10 one, the tools that show one point's elevation give the zoom-10 depth and name ETOPO1 (NOAA) as its source; the elevation profile and the horizon calculator don't. The elevation profile samples 24 to 160 points along the great circle between your waypoints, at zoom 14 for routes under about 5 mi (8 km), zoom 13 under about 25 mi (40 km) and zoom 12 beyond, and counts climb and descent only once the terrain has moved more than 13 ft (4 m) from the last counted point.

Attribution for the terrain data:

Air pressure follows the U.S. Standard Atmosphere, 1976, for the lowest layer of the atmosphere:

P = P₀ · (1 − L·h / T₀)^(g₀·M₀ / (R*·L))

with P₀ = 101,325 Pa, T₀ = 288.15 K, L = 0.0065 K/m (lapse rate), g₀ = 9.80665 m/s², M₀ = 0.0289644 kg/mol and R* = 8.31432 J/(mol·K), an exponent of about 5.2559. What Is My Elevation? uses the geopotential height for h; the Elevation Finder uses the elevation itself with the exponent rounded to 5.255.

10. Time zones

The Time Zone Finder sends the point to our server, which finds its IANA time-zone identifier with the geo-tz library (version 8.1.11) in polygons from timezone-boundary-builder (release 2026f, its full set, so each zone keeps its own name). Daylight saving time counts as in effect when the zone's next clock change, searched for over the coming 400 days, sets the clocks back; a zone with no change ahead keeps one time all year. Offsets and changes are read through the JavaScript Intl.DateTimeFormat API from your browser's copy of the IANA tz database.

11. Blank map rendering

The SVG files in the blank-maps library are generated ahead of time from TopoJSON with d3-geo projections:

PNG downloads are drawn in your browser from the SVG on an HTML canvas, at the width you pick (1,200, 2,400, 4,800 or 7,200 px). The PDF places a 2,400 px PNG on the paper size you pick, with jsPDF. The files are made in your browser; nothing is uploaded to a server.

12. Study methodology: Most Remote Places

The Loneliest Towns in America study groups the free SimpleMaps US ZIP Codes file (v1.95.1, CC BY 4.0; population from the American Community Survey 2020–2024 5-year estimates) by postal city and state: 33,634 ZIP rows in the 50 states and DC. A place's population is the sum of its ZIPs, and its point is the population-weighted mean of their points. Places with at least 10,000 people are "anchor cities" (5,488); places with 50 to 9,999 people are the candidate towns (21,376).

For every candidate, the haversine distance (R = 3,958.76 mi) to every anchor is computed, about 117 million distances, and the five nearest anchors are kept. Towns are ranked by the distance to the nearest anchor, rounded to 0.1 mi. Two national rankings are published: the lower 48 (without Alaska and Hawaii) and all 50 states with DC, where the top 100 places are all in Alaska. Each state's list ranks its own candidates. The distances are straight lines, not driving distances, and the 50-person floor leaves out postal cities whose ZIPs hold fewer people.

13. Study methodology: State Capital Radius

The 100-Mile Radius Around Every US State Capital study centers each circle on the state capitol building as mapped in OpenStreetMap (ODbL), looked up through Nominatim on November 11, 2026. Delaware's point is the Legislative Hall grounds and Ohio's is Capitol Square, the Statehouse grounds. For every ZIP row of the free SimpleMaps file in the state, it measures the haversine distance from that point (R = 3,958.76 mi); ZIPs whose point is within 100 mi count toward the population inside.

A state's share is that population divided by the population of all the state's ZIP rows in the same file, so the numerator and the denominator come from one dataset (ACS 2020–2024 5-year estimates). Summed over the 50 states, 173,161,206 of 334,152,804 people (51.82%) live within 100 mi of their state's capitol. DC has no state capital and is left out.

The "largest place outside the radius" is the postal city (the place name on ZIP codes) with the most people in ZIPs outside the circle, so it is a mail name, not a municipality: the New York row names Brooklyn, and the Florida row's Miami is every ZIP with that postal name. Its distance is measured to one of its ZIP points. The study also reports each state's population-weighted center (the mean ZIP latitude and longitude, weighted by population) and that center's distance from the capitol.

14. Study methodology: State Coastlines

The State Coastlines study computes no lengths of its own. It ranks the 50 states by NOAA's published general coastline, tidal shoreline and Great Lakes shoreline figures; the study page gives the definitions and the source.

15. What we don't do

16. Data sources, licenses and updates

ZIP code data: SimpleMaps US Zip Codes Database v1.95.1 (July 8, 2026). The public ZIP lists and both ZIP studies use the free version (CC BY 4.0); single-ZIP lookups, radius totals and demographics use the licensed Comprehensive version on our server. Population: American Community Survey 2020–2024 5-year estimates.

DataSourceLicenseUpdates
Map tilesOpenFreeMap (OpenMapTiles schema) on OpenStreetMap dataODbL (map data)Rebuilt by OpenFreeMap from OpenStreetMap; it publishes weekly planet builds
Place search and reverse geocodingPhoton (Komoot) and Nominatim (OpenStreetMap Foundation), both on OpenStreetMap dataODbL (data)Live services, queried at the moment you search
Road routes and drive-time areasValhalla on OpenStreetMap roads, public server run by FOSSGIS e.V.ODbL (data), MIT (Valhalla)FOSSGIS rebuilds the road graph from OpenStreetMap; on November 11, 2026 its status endpoint reported tiles built that day
US state and county boundariesCensus Bureau cartographic boundary files: the 2025 edition on the 51 county pages and in the county tools (What County Am I In?, the interactive county map, Map with Counties, County Map with Cities); the 2017 edition (us-atlas 3.0.1) for state outlines, Address to County Lookup, Map with ZIP Codes and the blank mapsPublic domain (US government work)County pages: 2025 edition since November 12, 2026, the county tools since November 17, 2026; the rest not refreshed since the 2017 edition
ZIP code boundariesCensus Bureau TIGER/Line 2010 ZIP Code Tabulation Areas (OpenDataDE’s State-zip-code-GeoJSON, simplified)Public domain (US government work)Not refreshed: 2010 shapes
ZIP points and populationSimpleMaps US Zip Codes Database v1.95.1 (July 8, 2026); population from American Community Survey 2020–2024 5-year estimatesFree file: CC BY 4.0 (public ZIP lists, both ZIP studies). Comprehensive file: paid license, kept on our server (single-ZIP lookups, radius totals, demographics)Rebuilt when we adopt a newer SimpleMaps release
State and county population, land areaCensus Bureau Vintage 2025 population estimates (July 1, 2025) and 2026 Gazetteer filesPublic domain (US government work)Rebuilt when we adopt a newer Census release
World country boundariesNatural Earth 1:50m and 1:110m, version 4.1.0 (world-atlas 2.0.2)Public domainNot refreshed: version 4.1.0
World townsGeoNames cities1000 extract, built October 7, 2026CC BY 4.0Rebuilt when we refresh the extract
ElevationAWS Terrain Tiles (Mapzen Terrarium): USGS 3DEP, SRTM, national models, NOAA ETOPO1Open data; required credits in section 9Static: version 1.1, released late 2017, no regular updates planned
Time-zone polygonstimezone-boundary-builder release 2026f (November 1, 2026), as bundled with geo-tz 8.1.11 (published November 2, 2026), its full setODbLUpdated when we update geo-tz
State capitol locations (capital study)OpenStreetMap, looked up through Nominatim on November 11, 2026ODbLOne-time lookup
National ParksNational Park Service list of the 64 national parks; each park’s location is the center of its NPS boundary and its area comes from the NPS acreage listingPublic domain (US government work)Edited by hand when a park is added

Where the versions come from: the site's US boundary files are byte-identical to us-atlas 3.0.1, built from the Census Bureau's 2017 cartographic boundary files (the county pages use the same recipe on the 2025 files, which have Connecticut's nine planning regions and Alaska's Chugach and Copper River census areas), and its world files to world-atlas 2.0.2, built from Natural Earth 4.1.0. The ZIP shapes are the Census Bureau's 2010 TIGER/Line ZCTA files as converted to GeoJSON by OpenDataDE, simplified for the web. The terrain tiles' version and update note are in Mapzen's data-sources documentation (section 9). Reference pages (county lists, blank maps, size comparisons, blog posts) name their own sources on the page.

17. Study and map licensing

SimpleMapLab's study datasets (the JSON and CSV files on each study page) are published under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. You may reproduce, remix, adapt and build upon them for any purpose, including commercial, as long as you give appropriate credit. The two ZIP studies are built on SimpleMaps' free file, also CC BY 4.0, so keep its credit too; each file carries it in its source field. Standard attribution:

SimpleMapLab (2026). [Study Title]. Retrieved from [Study URL].

In the blank-maps library, the blank, labeled and colored maps are public domain (CC0): free for any use, no credit required. The US "with cities" maps use SimpleMaps' city data and need the credit “City data: SimpleMaps (CC BY 4.0)”.

18. Accuracy bounds and known limitations

Where each calculation is accurate and where it isn't:

19. Checking our results

Each study page links its full results as data.json and data.csv, with the source credit in each file. With the free SimpleMaps file (version 1.95.1) and the methods above, the two ZIP studies can be recomputed independently.

If you reproduce a study and get different numbers, please let us know: either we have a bug to fix or the method needs a clearer explanation.

20. Corrections

When we find an error, or you report one, we fix the underlying data, formula or text, rebuild the affected pages, and add an entry to the corrections log with the date, what the page said and what it says now. A page's “Updated” date moves only when its content changes, not for wording or design edits.

To report a possible error: email hello@simplemaplab.com with "Correction:" in the subject line, the page URL, the value you believe is wrong, and your source if you have one. We respond within 1–3 business days and publish fixes within 48 hours of confirmation.

Questions

Anything that should be on this page but isn't, such as a calculation you can't reproduce, a source you think we should disclose or a limitation we haven't mentioned: tell us.