mapbench

Transparency

Corrections & Change Log

When MapBench finds a factual, calculation, data-source or implementation error that materially changes what a page tells the user, we correct it and record the change here. Routine design polish and minor wording edits are not listed as corrections.

DatePageWhat was wrongWhat changed
14 Oct 2026Moonrise & MoonsetThe page loaded a moon-phase interface instead of a location-based moonrise and moonset workflow.The tool now calculates moonrise, moonset and upper transit for the selected location and date, with local-time context and moon-phase information.
14 Oct 2026Magnetic DeclinationThe page reused a true-bearing workflow and did not calculate magnetic declination from a geomagnetic model.The tool now uses the British Geological Survey World Magnetic Model 2025 service and clearly separates true and magnetic bearings.
14 Oct 2026Population Within RadiusUS results were based on a curated major-city dataset and could not represent suburban or rural population well.US mode now uses Census ZCTA population and housing data with ACS demographic context, while clearly describing the centroid-based approximation.
14 Oct 2026Cities Within RadiusUS coverage was limited to the curated world-city list.US mode now uses Census incorporated places and census-designated places; the global curated-city fallback remains for worldwide use.
14 Oct 2026ZIP Codes Within RadiusThe lookup depended mainly on OpenStreetMap postcode search and could return a limited result set.US mode now uses Census ZIP Code Tabulation Areas with 2020 population and housing context, and explains that ZCTAs are not USPS delivery polygons.
14 Oct 2026Indexing and locale routesUntranslated locale tool URLs could be discovered even when the underlying content fell back to English, and filtered tool-directory URLs were crawlable.Retired locale routes now consolidate to canonical English destinations, translated alternates were removed from the sitemap, and filtered tool-directory variants are noindex with clean category hubs used for internal linking.

How MapBench handles corrections

Material errors are logged

We record changes that alter a result, data source, calculation method or important factual statement. Small style edits are not presented as substantive corrections.

Methods are rechecked

A reported issue is tested against the implemented calculation and the documented source before the result or explanatory text is changed.

Affected pages stay linked

Each entry points back to the relevant tool or policy page so readers can review the corrected version, method and current limitations.

Report an error

Send the affected URL, the input or statement you believe is wrong, the expected result, and a source when one is available. We review reproducible reports against the implemented method and documented source data.

Contact MapBench →·Editorial policy →·Methodology →·Data sources →