Skip to content

Commit 19bfbf4

Browse files
authored
March release notes (#312)
Signed-off-by: Dana Bauer <dana.bauer@gmail.com>
1 parent 2e1bd64 commit 19bfbf4

2 files changed

Lines changed: 132 additions & 1 deletion

File tree

blog/2026-03-18-release-notes.mdx

Lines changed: 131 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,131 @@
1+
---
2+
title: 2026-03-18 release notes
3+
tags:
4+
- releases
5+
---
6+
import Tabs from '@theme/Tabs';
7+
import TabItem from '@theme/TabItem';
8+
import QueryBuilder from '@site/src/components/queryBuilder';
9+
10+
## Overview
11+
12+
**The `2026-03-18.0` release of Overture data and `v1.16.0` of the Overture schema are now available.** You can access the datasets, changelog, GERS registry, bridge files, and PMTiles on AWS and Azure at the paths listed below.
13+
14+
## What's new?
15+
The [data changelog](https://docs.overturemaps.org/gers/changelog/) now includes `columns_changed`, capturing which properties changed, per feature. Also in this release, we've made several improvements to the pipeline architecture of the transportation theme, including adding several data quality improvements and fresher source data. This architectural change also lays the groundwork for integrating additional road network sources into Overture in the near future.
16+
17+
18+
## Deprecations
19+
The `categories` property in the places schema is now deprecated and will be removed in the June 2026 release, replaced by the new `basic_category` and `taxonomy` properties. All three properties will be available until then to ease the transition for our users. The taxonomy documentation is [here](https://docs.overturemaps.org/guides/places/taxonomy/).
20+
21+
22+
## Getting the data and release artifacts
23+
24+
You can access this month's data and release artifacts by following the process outlined [here](/getting-data). The paths to the data and release artifacts are listed below. We encourage you to ask questions and provide feedback on the Overture Maps [Discussion forum on GitHub](https://github.com/orgs/OvertureMaps/discussions). You can also file issues and report bugs in our [data](https://github.com/OvertureMaps/data/issues) and [schema](https://github.com/OvertureMaps/schema/issues) repositories. If you have a suggestion for a new dataset or if you have data you'd like to contribute to Overture, you can email us at community@overturemaps.org. We’d love to hear from you.
25+
26+
27+
28+
### Release data
29+
30+
**Microsoft Azure:**
31+
```
32+
az://overturemapswestus2.blob.core.windows.net/release/2026-03-18.0/
33+
```
34+
35+
**Amazon S3:**
36+
```
37+
s3://overturemaps-us-west-2/release/2026-03-18.0/
38+
```
39+
### Data changelog
40+
41+
**Microsoft Azure:**
42+
```
43+
az://overturemapswestus2.blob.core.windows.net/changelog/2026-03-18.0/
44+
```
45+
46+
**Amazon S3:**
47+
```
48+
s3://overturemaps-us-west-2/changelog/2026-03-18.0/
49+
```
50+
51+
52+
### Bridge files
53+
54+
**Microsoft Azure:**
55+
```
56+
az://overturemapswestus2.blob.core.windows.net/bridgefiles/2026-03-18.0/
57+
```
58+
59+
**Amazon S3:**
60+
```
61+
s3://overturemaps-us-west-2/bridgefiles/2026-03-18.0/
62+
```
63+
64+
### GERS registry
65+
66+
67+
**Microsoft Azure:**
68+
```
69+
az://overturemapswestus2.blob.core.windows.net/registry/
70+
```
71+
72+
**Amazon S3:**
73+
```
74+
s3://overturemaps-us-west-2/registry/
75+
```
76+
77+
### PMTiles
78+
79+
**Amazon S3:**
80+
```
81+
s3://overturemaps-extras-us-west-2/tiles/2026-03-18.0/
82+
```
83+
84+
<!-- truncate -->
85+
86+
87+
## Theme-specific updates
88+
89+
:::info
90+
The base, buildings, divisions, places, and transportation themes are in GA. The addresses theme is in alpha.
91+
:::
92+
93+
### Addresses
94+
95+
- improved city, street, or number column in Slovakia, Belgium, Austria, and in Quebec, CA
96+
- added units to Portugal, Iceland, and Baden-Württemberg DE
97+
- added data in Lower Saxony and Mecklenburg-Vorpommern, DE
98+
99+
100+
### Base
101+
- made minor, incremental updates to the data
102+
103+
104+
### Buildings
105+
- made minor, incremental updates to the data
106+
107+
108+
### Divisions
109+
- made minor, incremental changes to the data
110+
111+
112+
### Places
113+
- made improvements to the `taxonomy` and `basic_category` fields
114+
115+
116+
### Transportation
117+
118+
- fixed source linear references: the `sources` array for segment features previously dropped positional information (`between`) on the last source entry; now the `sources` array has correct linear references, and adjacent ranges with identical values are merged into cleaner, more compact output
119+
120+
- cleaned up routes: `routes` with no identifying properties and duplicate entries covering adjacent sub-ranges have been removed
121+
122+
- added more accurate timestamps: `update_time` in the `sources` array now reflects the most recent timestamp across both the feature and its components, a change that accounts for ~90M source-level differences (~28% of segments) but does not affect source identity or count.
123+
124+
125+
## Schema changelog
126+
127+
The changelog for Overture schema `v1.16.0` is [here](https://github.com/OvertureMaps/schema/releases/tag/v1.16.0).
128+
129+
## Attribution
130+
131+
You'll find information about attribution and licensing [here](/attribution).

docusaurus.config.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ function getFromEnvironment(variableName, defaultValue) {
2121
}
2222

2323
function getLatestOvertureRelease() {
24-
const fallback = '2026-01-21.0';
24+
const fallback = '2026-03-18.0';
2525
try {
2626
const { execSync } = require('child_process');
2727
const response = execSync('curl -s https://stac.overturemaps.org/catalog.json', {

0 commit comments

Comments
 (0)