december release notes and blog post

blog/2024-12-18-transportation-to-ga.mdx

@@ -0,0 +1,50 @@
+---
+title: Transportation theme navigates to GA
+---
+
+Over the past several releases, Overture has been laying the groundwork to transition our transportation theme from beta to general availability (GA). This post provides a brief roadmap of the work we’ve done to reach that goal, along with a request for our community to continue testing the data and providing valuable feedback.
+
+First, let’s talk about what GA means for the transportation theme. We have a few guiding principles:
+
+1. There are no "trust violations" in the schema and data. It needs to "just work" when a developer writes code based on our schema and documentation.
+2. The road geometry and attributes should be on par with the roads in OSM.
+3. Roads have stable GERS IDs and those IDs can be references for attaching additional data.
+4. The road features we capture should support our core use cases: rendering for display, GERS referencing, and basic routing capabilities.
+
+Most of our work over the past few months has been around #1 and #2. We've been resolving data-schema violations by fixing inconsistencies in our schema and issues with the data transformation steps in our pipeline. To satisfy #3, we’ve been monitoring changes in GERS IDs from release to release, and our metrics show us that the vast majority of roads are maintaining stable IDs.
+
+We've had to break a few things in our schema to make way for improvements:
+
+- To better support routing use cases, we added to the segment feature type a new property called `connectors`: an array of IDs with pre-computed linear reference values that explicitly link segments and connector features via coordinates. Each connector is a possible routing decision point, meaning it defines a place along the segment in which there is possibility to transition to other segments that share the same connector. This new property — a replacement for the old `connector_ids` property — will reduce complexity and improve accuracy as we calculate the intersections between segment and connector features. You can read more about this improvement [here](https://docs.overturemaps.org/blog/2024/08/15/preview-august-release/#transportation-schema-changes).
+
+- In the [November release](https://docs.overturemaps.org/release/2024-11-13.0/), we removed `lanes` from the schema to eliminate a significant trust violation. The `lanes` property has existed in the schema for months but we never populated it with data in our releases, which is a poor experience for our community. We intend to redesign `lanes` in the coming months.
+
+With these changes, we are confident we’ve met our requirements for general availability (GA). We'll continue refining our schema and improving our data throughout 2025. We encourage our community to keep the feedback coming, particularly around data quality and our core use cases of map display, routing, and matching data via GERS.
+
+Here are some specific ways you can help:
+
+1. Examine transportation data in your areas of interest and compare it to local sources of data. Here are some suggestions for downloading data using Overture's Python CLI.
+
+Philadelphia area
+```
+overturemaps download --bbox=-75.8264,39.7032,-74.5213,40.444 -f geoparquet --type=segment -o overture-segments-philadelphia.geoparquet
+```
+
+Riyadh Province, Saudia Arabia
+```
+overturemaps download --bbox=38.97,21.33,48.66,25.98 -f geoparquet --type=segment -o overture-segments-riyadh.geoparquet
+```
+
+Campobasso, Italy
+```
+overturemaps download --bbox=13.8152,40.8473,15.6336,42.0773 -f geoparquet --type=segment -o overture-segments-campobasso.geoparquet
+```
+
+2. Test our [transportation spitter tool](https://github.com/OvertureMaps/transportation-splitter). 
+
+3. Feed our data into a routing engine and let us know how it goes! Paul Ramsey from Crunchy Data shared [a vehicle routing example using PostGIS and Overture data](https://www.crunchydata.com/blog/vehicle-routing-with-postgis-and-overture-data0. We'd also like to see our users trying [Valhalla](https://valhalla.github.io/valhalla/) and [Grasshopper](https://github.com/graphhopper/graphhopper-maps). 
+
+4. Reach out to us at [email protected] if you have a specific use case and would like to discuss it. 
+
+
+

docusaurus.config.js

@@ -21,7 +21,7 @@ const config = {
   favicon: 'img/favicon.png',
 
   customFields: {
-    overtureRelease: '2024-11-13.0',
+    overtureRelease: '2024-12-18.0',
   },
 
 

release-blog/2024/2024-11-13.0.mdx

@@ -1,6 +1,6 @@
 ---
 title: 2024-11-13.0
-slug: latest
+slug: 2024-11-13.0
 ---
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';

release-blog/2024/2024-12-18.0.mdx

@@ -0,0 +1,100 @@
+---
+title: 2024-12-18.0
+slug: latest
+---
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+import QueryBuilder from '@site/src/components/queryBuilder';
+
+## Overview
+
+**The `2024-12-18.0` release of Overture data and `v1.4.0` of the Overture schema are now available.** This month [our transportation theme is going to GA](/blog), we're launching a bathymetry feature type in our base theme, and we're at 400 million address records and counting in our addresses theme. What a way to end the year!
+
+The datasets are available as GeoParquet files stored on both AWS and Azure. The release paths are:
+
+#### Microsoft Azure:
+```
+wasbs://[email protected]/2024-12-18.0
+```
+
+#### Amazon S3:
+```
+s3://overturemaps-us-west-2/release/2024-12-18.0
+```
+
+You can access the datasets by following the process outlined [here](https://docs.overturemaps.org/getting-data/). We encourage you to ask questions, report bugs, and provide feedback via our [data](https://github.com/OvertureMaps/data) and [schema](https://github.com/OvertureMaps/schema) repositories on GitHub. 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 **data AT overturemaps.org**. We’d love to hear from you.
+
+
+## Breaking changes
+
+None. 
+
+## Deprecations
+
+ None.
+
+## Theme-specific updates
+
+:::info
+The base, buildings, divisions, places, and transportation themes are in GA. The addresses theme is in alpha. 
+:::
+
+### Addresses
+- reached a milestone of 400 million address records
+- added new data for:
+    - Czechia
+    - Liechtenstein
+    - Uruguay
+    - various counties in California
+- replaced NAD data in Massachusetts with open data from MassGIS
+
+
+### Base
+- added `bathymetry` feature type with 60,000 new features
+- added new classes to `land`, `land_use`, and `water` feature types, including `fatbike`, `hike`, and `nordic`
+
+### Buildings
+- made incremental updates
+- hit an all-time high of 2.3 billion building features
+
+### Divisions
+- added a `class` property to explicitly call out the type of locality, e.g. hamlet, city
+- added new properties: `is_land`, `is_territorial`, and `prominence`
+- fixed issue with duplicate data in Tuvalu
+- added TIGER locality data for the United States
+
+### Places
+- no updates
+
+### Transportation
+- released the transportation theme in GA!
+- added new roads in the US, UK, and FR 
+- added non-OSM roads in:
+    - France: 172.87 kms
+    - United Kingdom: 20.21 kms 
+    - Italy: 1099.86 kms 
+    - Saudi Arabia: 29793.48 kms 
+    - United States: 215.51 kms
+- merged adjacent route values
+- fixed access restrictions that were not populating with data
+- fixed class value that was not populating with data for 3K segments
+
+## Global Entity Reference System (GERS) changelog
+
+The GERS changelog captures any changes in Overture features between this release and the previous release. The changelog is available as Parquet files — partitioned by theme, type, and change type — at the following locations on Azure and AWS:
+
+```
+wasbs://[email protected]/2024-12-18.0
+```
+```
+s3://overturemaps-us-west-2/changelog/2024-12-18.0
+```
+
+You can find more information about [the GERS Changelog in our documentation](https://docs.overturemaps.org/gers/changelog/).
+
+## Schema changelog
+The changelog for Overture schema `v1.4.0` is [here](https://github.com/OvertureMaps/schema/releases/tag/v1.4.0). 
+
+## Attribution
+
+You'll find information about attribution and licensing [here](/attribution).