Repository navigation
docs: draft release notes for 2026-11-18.0 - #620
Conversation
Signed-off-by: overture-pull-requester[bot] <280063256+overture-pull-requester[bot]@users.noreply.github.com>
🗺️ Overture Docs preview is live!
Note ♻️ This preview updates automatically with each push to this PR. |
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
Adam Lastowka (Rachmanin0xFF)
left a comment
There was a problem hiding this comment.
These are a significant departure from the previous release notes. They are missing a lot of the markdown formatting / conventions of the previous release notes.
I don't think we should publish these as-is so I'm putting a block on this for now. We can probably just patch this (I may open a PR targeting this branch), but we should fix the prompt introduced in https://github.com/OvertureMaps/tf-data-platform/pull/6133
|
Update: okay nvm he is pushing the commit to my PR. so I will merge that |
|
#623 regarding the formatting failures... |
|
accessibility workflows should resolve once PR is updated with manual edits |
<!-- markdownlint-disable --> ## Pull Request Relates to #620. The automated draft in that PR doesn't follow the format of earlier release notes. This PR rewrites the notes to match `blog/2026-10-21-release-notes.mdx`. The longer-term fix is to update the prompt! Changes: - Uses the standard overview lead, with the release and schema version in bold. - Restores the data and artifact paths, the `{/* truncate */}` marker, the theme status info box, and the schema changelog and attribution sections. - Rewrites each theme as short bullets in past tense. Adds OSM cut-off dates for Base, Buildings, Divisions, and Transportation. - Uses the usual table shapes: Type, Count, and Change for Base and Divisions. Buildings get a per-source table. Transportation gets the dataset and count-change tables. - Takes all numbers from the draft. Per-source building counts and per-dataset transportation counts are October's counts plus the deltas in the draft. The building source counts add up to the new total exactly. Not included, because the draft has no data for them: - Transportation lengths (km), and the length-change table. - The places top-level taxonomy table. - GERS churn for Divisions. Validation: none run. This is a content-only change. --------- Signed-off-by: Adam Lastowka <adamlastowka@gmail.com> Signed-off-by: Stephen Epps <stephen@overturemaps.org> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: Stephen Epps <stephen@overturemaps.org>
There was a problem hiding this comment.
🟡 Changes recommended
The release notes describe address_levels_2 as a core field even though it is absent from schema v2.0.0, leaving the measured array element or derived coverage metric unclear.
1 open issue
What changed in this PR
Adds draft release notes for Overture’s 2026-11-18.0 data release and schema v2.0.0, generated from release-candidate artifacts for human review.
Changes:
- Lists dataset and release-artifact locations on AWS and Azure.
- Summarizes updates across all six themes, including feature counts, source refreshes, normalization, and GERS churn.
- Links to the schema changelog and attribution guidance.
| File | Description |
|---|---|
blog/2026-11-18-release-notes.mdx |
Adds November release notes with artifact paths and theme-specific updates. |
Review effort: Balanced
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>


Draft generated from release-candidate artifacts. Human review is required.