Data accuracy, freshness and errors

Accuracy

Trust and checking.

Status labels: Live (checked directly, dated) Built in code; not independently verified In progress Planned, not shipped Open decision or unverified Not offered / no claim made

C0352 How accurate is the data?

We cannot give a number. No independent audit exists. Names come from official lists, and layers from official public vectors, but both can be outdated or wrong in places.

Open decision or unverified Permalink

C0353 Who checks the data?

Build rules check for things like invented names, prices and contacts, which are forced to zero. That is discipline, not verification of truth. No independent party checks it.

Built in code; not independently verified Permalink

C0354 What does “inventedNames = 0” cover?

That every graph name comes from an ingested source. It does not cover whether the source is right, current or unambiguous.

Built in code; not independently verified Permalink

C0355 What does “inventedPrices = 0” mean?

That no price was made up. It is why price fields are empty or clearly labelled estimates. It does not mean any shown figure is a market price.

Built in code; not independently verified Permalink

C0356 What does “inventedContacts = 0” mean?

That no email or phone in the compilation was made up. Every contact comes from a published source. It says nothing about consent or currency.

Built in code; not independently verified Permalink

C0357 What does “inventedGPS = 0” mean?

That no coordinates were fabricated. Places use polygon centroids from boundary data, and they are not facility locations.

Built in code; not independently verified Permalink

C0358 Are centroids accurate locations?

They are the middle of an administrative area. They locate places approximately and never a mill, mine, port or address.

Built in code; not independently verified Permalink

C0359 Can I use ET for legal boundaries?

No. The project records legal_survey as false, and we make no claim that boundaries are authoritative or agree with disputed-area conventions.

Built in code; not independently verified Permalink

C0360 How do I report a mistake?

Write through data rights with the name, the screen and what the source says. We cannot promise to fix a source's own error.

Open decision or unverified Permalink

C0361 Is there an error log or change history for the data?

Not for the data itself. Only release-level entries are recorded, in the changelog, and no per-node edit history is kept for readers.

Open decision or unverified Permalink

C0362 Have users found errors?

We have no documented user base, so we have no user error reports to cite. Internal polish lists exist.

Open decision or unverified Permalink

C0363 Why do some internal documents quote different numbers?

Older documents carry stale counts from smaller graphs. Figures on this site replace them, and we label the date for each.

Built in code; not independently verified Permalink

C0364 Which numbers on this site are current?

The graph and place counts were read on 2026-09-30. Overlay and picture counts are from late August or from build notes, and are marked as not re-measured.

Built in code; not independently verified Permalink
No public download yet. Ask to be told when access opens.Request access