Corrections & transparency

A clearer record,
even when facts change.

Sources are revised. Definitions change. A useful correction starts with the exact place, metric, reference period and authoritative evidence.

i

Reports go to a review queue. Submission does not approve a change or promise a response time. The current source-backed technical profiles remain under editorial review.

Report a data issue in Oregon

Choose another state. This form covers source-backed state, county and city or town observations with an approved snapshot in this build.

Use public source evidence. Do not include personal information, credentials or private records. Your report and evidence link are stored for review; this form does not collect contact details.

Provide an HTTPS link to the public source supporting your report.

Include the affected period, the current claim and the source-supported correction. Use 20–4,000 characters.

Review the source releases represented in this build before deciding whether a different period or source explains the discrepancy.

How a correction is handled

  1. Identify the claim. Trace it to the observation, source release and transformation.
  2. Check the evidence. Distinguish an upstream revision, a geographic mismatch, a definition change and an implementation error.
  3. Find affected surfaces. A corrected observation can affect profiles, comparisons, rankings, exports and API values.
  4. Publish consistently. Verify the corrected release and its dependent representations before considering the issue resolved.
  5. Keep the reason visible. Preserve the correction date, explanation and appropriate source links.

Public correction history

Only audited resolutions with completed propagation checks for the current approved publication appear here. Submitted report text and review identities stay private.

Loading public resolutions…

    Read the methodology or explore the technical profiles.