Submit a correction
Email [email protected] with the full page URL, the exact phrase or calculation in question, the input values used and a primary source when possible. Include screenshots only when helpful, and omit private data unrelated to the issue.
How reports are assessed
We attempt to reproduce numerical bugs, verify mathematical constants against primary standards and review changes in source data or product capabilities. Some map discrepancies come from coordinates, chosen methods, reference years or routing-provider datasets rather than a simple arithmetic mistake.
How updates are handled
A corrected formula or interface behavior should be re-tested across tools that share the same calculation functions. When a substantive public claim changes, its cited source and methodological limitations should be updated. We do not claim that every user-submitted suggestion is verified or published.
Accessibility feedback
Reports about keyboard navigation, contrast, screen-reader labels, touch sizing, map interaction and small-screen layout are welcome. Alternative text-based inputs are especially important because some map interactions rely on sight or precision touch.
Private information
If a report contains information that should not be public, identify that concern explicitly in the email. Users should not send passwords, security credentials, sensitive GPS histories or identity documents.
What a useful correction report contains
Send the full page URL, a screenshot only if safe to share, the numeric inputs, units, location if relevant, displayed output and the expected output with a clear reference or calculation. If the issue appears only on mobile, include the browser and approximate screen width. Do not submit passwords, private access tokens or other people's sensitive locations.
What happens after a report
We review whether the problem is a formula mistake, map coordinate error, incomplete provider response, wording problem or a change in third-party data. When appropriate, we patch code or revise content and retest the affected task. We cannot promise a particular turnaround, and a submitted report is not a guarantee that any disputed geographic interpretation is accepted.
Where to reach the editor
Email [email protected] or consult the contact page. Methodological disputes benefit from linking original source documentation and explaining what should change.
What makes a report actionable
When reporting a problem, include the exact page address, input values and selected units. For maps, include a reproducible center coordinate and radius or route points when sharing them is safe. State what the page showed and what result you expected, with a primary reference if one is available. For privacy, do not send sensitive home or employment location details unless necessary and appropriate.
The editor should distinguish a verified mathematical bug from a provider outage, a difference in dataset vintage or a misunderstanding of straight-line versus travel-time distance. Material factual changes belong in the relevant tool explanation, and recurring errors should lead to regression tests. The corrections page offers a contact path but does not promise a response time that has not been established.