You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: content/blog/overture-maps/index.md
+8-6
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Why We Stopped using OpenStreetMap and switched to Overture Maps"
3
-
description: "Faster Queries, Seamless Integration, and Real-Time Mapping with Overturen Maps"
4
-
lead: "Faster Queries, Seamless Integration, and Real-Time Mapping with Overturen Maps"
3
+
description: "Efficient way to access and work with spatial data in the cloud."
4
+
lead: "Efficient way to access and work with spatial data in the cloud."
5
5
date: 2024-06-28T06:59:51Z
6
6
lastmod: 2024-06-28T06:59:51Z
7
7
draft: false
@@ -12,11 +12,13 @@ contributors: ["Vladi"]
12
12
13
13
{{< img src="1716710901364.jpeg" caption="Switching from OSM to Overture Maps" class="wide" >}}
14
14
15
-
We didn’t want to talk about Overture Maps until we tested it ourselves. Now we have, and here's why it became the clear choice for our geospatial data needs, especially in mobility projects.
15
+
*Disclaimer: This article is about OpenStreetMap BigQuery Public Dataset and Overture Maps on BigQuery. Unintentionally this article raised concerns in OSM community. Clarifying edits where added to the article.*
16
16
17
-
### The Problem with OpenStreetMap (OSM)
17
+
*Note: Overture Maps dataset is based on OpenStreetMap data plus other sources. It is not a replacement for OpenStreetMap, but rather a more efficient way to access and work with spatial data in the cloud.*
18
18
19
-
For years, **OpenStreetMap (OSM)** was the go-to for spatial data in tools like **BigQuery**. It was reliable enough—until it wasn’t. The **OSM dataset hasn’t been updated in two years**, forcing companies to maintain their own exports and creating unnecessary overhead.
19
+
### The Problem with OpenStreetMap (edit: BigQuery Public dataset)
20
+
21
+
For years, **OpenStreetMap (edit: BigQuery Public dataset)** was the go-to for spatial data in **BigQuery**. It was reliable enough—until it wasn’t. The **OSM (edit: BigQuery Public) dataset hasn’t been updated in two years**, forcing companies to maintain their own exports and creating unnecessary overhead.
20
22
21
23
If you’ve used OSM, you know how cumbersome it can be to load massive map files, only to end up with stale data. That was the turning point for us. We needed something faster and more reliable.
22
24
@@ -80,7 +82,7 @@ We’ve put together a [collection of SQL queries and interactive maps](https://
80
82
81
83
### Key Takeaways
82
84
83
-
**Why did we stop using OpenStreetMap and switch to Overture Maps?**
85
+
**Why did we switch to Overture Maps?**
84
86
85
87
1.**Speed**: Querying maps directly in BigQuery and Snowflake is far faster than loading static files.
86
88
2.**Flexibility**: You can join your internal data with Overture’s high-quality map data using SQL, without the need for data exports or transformations.
0 commit comments