Contact

Reporting a wrong result

This is the most useful mail I get, and the one I act on fastest. A report I can reproduce is worth a great deal more than one I cannot, so where possible include:

• Which tool, and the page address.
• What you clicked or typed — coordinates or place names are ideal, since they let me reproduce the exact case.
• What the tool reported, and what you expected instead.
• Where your expected figure comes from, if you have a source. Some disagreements turn out to be two datasets rather than a bug, and knowing which one you are comparing against settles it quickly.

Before writing in, it is worth checking the tool’s own page — each one documents where its numbers stop being reliable, and a good share of surprising results are the documented limits rather than faults.

Suggesting a tool

Requests are welcome. The ones that get built tend to be narrow: single-purpose, answerable from open data, and genuinely awkward to do elsewhere. Telling me what you were actually trying to accomplish helps more than describing an interface — the underlying problem is often solvable with a tool that already exists here.

Privacy and data requests

Same address. If you are asking about what is stored, what analytics or advertising cookies are set, or want to change your consent choices, the Privacy Policy covers most of it, and the cookie preferences link in the footer reopens the consent options at any time.

Corrections to the written content

The tool pages make factual claims — about grid resolutions, map projections, datasets and their limits. If one of them is wrong, I would genuinely like to know, and I will correct it. Errors in the explanation are as much a bug as errors in the arithmetic.