If a figure, source, geography label, or explanation looks wrong, report it through the contact form so it can be checked against the source and build rules.
Use the contact form and choose "Corrections". Include the page URL, the specific figure or wording, what you believe is wrong, and the source that supports the change. Screenshots help with display problems, but a page URL is still needed.
If the dispute concerns an upstream authority's published value rather than this site's transcription or processing, say so. Cities of Europe can correct its own work, but it cannot revise an official source dataset.
The operator checks the report against the source file, geography grain, field recipe, and rendered page. Issues are classified as blocker, major, or minor. A blocker can attach data to the wrong entity or geography, publish materially corrupted data, expose protected data, or breach a publication licence. The affected fact or page is withdrawn immediately, and a page-level blocker remains out of the index until fixed.
A major error materially changes a value, calculation, comparison, citation, or interpretation. The fix preserves the superseded artifact and adds a public correction entry. Minor typographical or cosmetic errors use the normal release process. An ordinary upstream source revision is not described as a project error unless Cities of Europe represented it incorrectly.
COR-2026-001 · Status: Fixed
A project audit found that machine-readable metadata described greater-city profiles as City. The visible pages kept their greater-city labels, and displayed figures were not changed by this defect.
The machine record identifies 172 affected routes and links its complete field or page appendix.
The corrected deployment and its validation evidence are recorded in the correction ledger.
COR-2026-002 · Status: Fixed
A project review found that EEA city codes had been attached to GISCO profiles without an accepted crosswalk, including confirmed wrong-entity links. The affected air-quality facts are being withdrawn. The retained EEA inputs may be reconsidered only after reviewed identity decisions.
The machine record identifies 340 affected routes and links its complete field or page appendix.
The corrected deployment and its validation evidence are recorded in the correction ledger.
COR-2026-003 · Status: Fixed
A project review found that public profiles included facts, relationships, maps, and routes before the exact source use had passed a commercial-reuse review. The affected material was withdrawn. Provider-coordinate and map features remain unavailable; PAGE-004 scopes the only seven eligible linked-authority-record panels under exact-surface clearances and the current unchanged OPS-016 gate. Associated points remain distinct from provider coordinates.
The machine record identifies 6 affected routes and links its complete field or page appendix.
The corrected deployment and its validation evidence are recorded in the correction ledger.
COR-2026-004 · Status: Fixed
A project citation named a City Statistics codelist version that the retained evidence did not establish. The affected pages are being changed to cite the exact accepted Eurostat datacode response and captured nomenclature article without claiming a codelist version.
The machine record identifies 696 affected routes and links its complete field or page appendix.
The corrected deployment and its validation evidence are recorded in the correction ledger.
COR-2026-006 · Status: Fixed
A project review found that the accepted release did not establish a defensible unit and concept basis for the rent metric or a defensible unit basis for the German bicycle-network values. The project withheld all 323 affected facts across 196 profiles, preserved the source observations, inferred no conversion, and validated the deployed remedy.
The machine record identifies 196 affected routes and links its complete field or page appendix.
The corrected deployment and its validation evidence are recorded in the correction ledger.
COR-2026-007 · Status: Confirmed, correction pending
A project review found that the retained publishable evidence does not establish whether provider record MT001C is a city or greater city. The candidate correction labels its type unresolved, suppresses type-dependent claims and comparisons, infers no replacement type, and keeps the route noindex.
The machine record identifies 1 affected routes and links its complete field or page appendix.
The correction is not marked fixed until deployment and post-deployment evidence are recorded. Current site-wide noindex containment is tracked independently.
COR-2026-010 · Status: Fixed
A project review found that 234 German profile figures showed a 2022 value although the accepted newer Eurostat release already held an eligible 2023 value for the same city and metric. The selection step picked each series' newest number before checking whether its source-status flag allowed display, then fell back to the older release. The project corrected the selection rule and rebuilt the affected figures from the accepted source data. No other value, page, or source decision changed, the superseded selection evidence is preserved, and the corrected figures were validated on the deployed version.
The machine record identifies 109 affected routes and links its complete field or page appendix.
The corrected deployment and its validation evidence are recorded in the correction ledger.