Skip to content

Commit 4098774

Browse files
Consistent Markdown
1 parent e747091 commit 4098774

File tree

6 files changed

+71
-217
lines changed

6 files changed

+71
-217
lines changed

docs/gers/changelog.mdx

+5-11
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ import changelog_buildings_churn from '!!raw-loader!@site/src/queries/duckdb/cha
66
import changelog_buildings_feature_by_change_type from '!!raw-loader!@site/src/queries/duckdb/changelog_buildings_feature_by_change_type.sql';
77
import changelog_buildings_join from '!!raw-loader!@site/src/queries/athena/changelog_buildings_join.sql';
88

9-
With each data release, Overture generates a [GERS](../) changelog to capture changes in the data tied to the unique ID for each feature. This information can be used to guide decisions about data matching, better understand data stability, and help detect data errors.
9+
With each data release, Overture generates a [GERS](../) changelog to capture changes in the data tied to the unique ID for each feature. This information can be used to guide decisions about data matching, better understand data stability, and help detect data errors.
1010

1111
The GERS changelog is available as Parquet files — partitioned by theme, type, and change type — at the following locations:
1212

@@ -15,7 +15,7 @@ The GERS changelog is available as Parquet files — partitioned by theme, t
1515
| Amazon S3 | `s3://overturemaps-us-west-2/changelog/` |
1616
| Microsoft Azure | `wasbs://[email protected]/` |
1717

18-
The latest path is:
18+
The latest path is:
1919
<QueryBuilder query="__OVERTURE_RELEASE/" language="text"></QueryBuilder>
2020

2121
## Types of changes
@@ -29,24 +29,18 @@ The types of changes in the changelog include:
2929

3030
## Querying the GERS changelog
3131

32-
We can query the changelog with DuckDB to get a quick look at changes in data from the last release to the current release. In this example, we're grabbing ID, feature type, and change type for buildings in several towns across the [Amhara Region](https://en.wikipedia.org/wiki/Amhara_Region) in Ethiopia.
32+
We can query the changelog with DuckDB to get a quick look at changes in data from the last release to the current release. In this example, we're grabbing ID, feature type, and change type for buildings in several towns across the [Amhara Region](https://en.wikipedia.org/wiki/Amhara_Region) in Ethiopia.
3333

3434
<QueryBuilder query={changelog_buildings_churn}></QueryBuilder>
3535

3636
We can also get a count of building features by change type for our area of interest.
3737

3838
<QueryBuilder query={changelog_buildings_feature_by_change_type}></QueryBuilder>
3939

40-
Taking this one step further, this time using Athena to run our query, we can join the changelog and data via Overture ID to connect the change type and feature geometries and properties.
40+
Taking this one step further, this time using Athena to run our query, we can join the changelog and data via Overture ID to connect the change type and feature geometries and properties.
4141

4242
<QueryBuilder query={changelog_buildings_join}></QueryBuilder>
4343

44-
Finally we can use the results of our query to visualize building features by change type and inspect the properties for each feature. The example below, created using [kepler.gl](https://kepler.gl/), shows buildings in [Finote Selam](https://en.wikipedia.org/wiki/Finote_Selam), a city in the Amhara Region of Ethiopia. The data is from Overture's `2024-06-13-beta.0` release, to which we added 100 million new buildings, many of them derived from satellite imagery by Microsoft.
45-
44+
Finally we can use the results of our query to visualize building features by change type and inspect the properties for each feature. The example below, created using [kepler.gl](https://kepler.gl/), shows buildings in [Finote Selam](https://en.wikipedia.org/wiki/Finote_Selam), a city in the Amhara Region of Ethiopia. The data is from Overture's `2024-06-13-beta.0` release, to which we added 100 million new buildings, many of them derived from satellite imagery by Microsoft.
4645

4746
![Buildings By Change Type](/img/gers/buildings-change-type-amhara-region.png)
48-
49-
50-
51-
52-

docs/getting-data/data-mirrors/bigquery.mdx

+25-72
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
title: BigQuery (Google)
33
---
44

5+
6+
57
Overture data is accessible in Google BigQuery as part of the [Google Cloud Public Dataset Program](https://cloud.google.com/bigquery/public-data), with the data being listed and maintained by [CARTO](https://www.carto.com).
68

79
![Overture data in Google Cloud](/img/getting-data/BigQuery-1.png)
@@ -13,104 +15,55 @@ Below is a step-by-step guide on how to access and use Overture data in BigQuery
1315
To get started using Overture data in BigQuery, you must create or select a Google Cloud project with billing [enabled](https://cloud.google.com/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project). BigQuery is automatically enabled in new projects, but in order to activate it in a preexisting project, you should enable the [BigQuery API](https://console.cloud.google.com/apis/enableflow?apiid=bigquery&inv=1&invt=Abns8w).
1416

1517
## Getting Overture data in Google BigQuery
18+
1619
1. Log in to your [Google Cloud Console](https://console.cloud.google.com/).
1720
2. Navigate to the **BigQuery** section by selecting `BigQuery` from the side menu or searching for it in the search bar.
1821

19-
![Overture data in Google Cloud](/img/getting-data/bigquery-2.png)
20-
21-
1. In the BigQuery console, click **Add Data**. Then, click on **Public Datasets**.
22-
23-
![Overture data in Google Cloud](/img/getting-data/bigquery-4.png)
22+
![Overture data in Google Cloud](/img/getting-data/bigquery-2.png)
2423

25-
1. The Google Cloud data marketplace will open. In the search box look for **Overture Maps**.
24+
3. In the BigQuery console, click **Add Data**. Then, click on **Public Datasets**.
2625

26+
![Overture data in Google Cloud](/img/getting-data/bigquery-4.png)
2727

28-
<img
29-
src="/img/getting-data/bigquery-5.png"
30-
alt="Overture data in Google Cloud"
31-
width="900"
32-
height="auto"
33-
/>
28+
4. The Google Cloud data marketplace will open. In the search box look for **Overture Maps**.
3429

30+
![Overture data in Google Cloud](/img/getting-data/bigquery-5.png)
3531

3632
5. Select the **Overture Maps Data** listing. Then, click on **View dataset**.
3733

38-
39-
<img
40-
src="/img/getting-data/bigquery-6.png"
41-
alt="Overture data in Google Cloud"
42-
width="900"
43-
height="auto"
44-
/>
45-
34+
![Overture data in Google Cloud](/img/getting-data/bigquery-6.png)
4635

4736
6. Back again in the BigQuery console you will see the `bigquery-public-data` project and the `overture_maps`dataset selected.
4837

49-
50-
<img
51-
src="/img/getting-data/bigquery-7.png"
52-
alt="Overture data in Google Cloud"
53-
width="900"
54-
height="auto"
55-
/>
56-
38+
![Overture data in Google Cloud](/img/getting-data/bigquery-7.png)
5739

5840
7. Our recommendation is that you add the `overture_maps` dataset or entirely the `bigquery-public-data` project in your starred selection in order to have access to the Overture data always at hand.
5941

60-
61-
<img
62-
src="/img/getting-data/bigquery-8.png"
63-
alt="Overture data in Google Cloud"
64-
width="900"
65-
height="auto"
66-
/>
67-
42+
![Overture data in Google Cloud](/img/getting-data/bigquery-8.png)
6843

6944
## Working with Overture data in BigQuery
7045

71-
8. Now that Overture Maps data is available in your BigQuery console, you can start using it. Note that in the `overture_maps` dataset you have access to all tables from all the different Overture Maps themes: Addresses, Base, Buildings, Divisions, Places and Transporatation.
72-
73-
74-
<img
75-
src="/img/getting-data/bigquery-9.png"
76-
alt="Overture data in Google Cloud"
77-
width="900"
78-
height="auto"
79-
/>
80-
46+
1. Now that Overture Maps data is available in your BigQuery console, you can start using it. Note that in the `overture_maps` dataset you have access to all tables from all the different Overture Maps themes: Addresses, Base, Buildings, Divisions, Places and Transportation.
8147

82-
9. The release version is detailed as a `label` in each of the tables. You can check it out in the **Details** section of each table.
48+
![Overture data in Google Cloud](/img/getting-data/bigquery-9.png)
8349

50+
2. The release version is detailed as a `label` in each of the tables. You can check it out in the **Details** section of each table.
8451

85-
<img
86-
src="/img/getting-data/bigquery-10.png"
87-
alt="Overture data in Google Cloud"
88-
width="900"
89-
height="auto"
90-
/>
52+
![Overture data in Google Cloud](/img/getting-data/bigquery-10.png)
9153

54+
3. You can now query any of the tables directly from your SQL Editor in BigQuery. Here's one example for the Places data in Overture Maps.
9255

93-
10. You can now query any of the tables directly from your SQL Editor in BigQuery. Here's one example for the Places data in Overture Maps.
56+
![Overture data in Google Cloud](/img/getting-data/bigquery-11.png)
9457

95-
96-
<img
97-
src="/img/getting-data/bigquery-11.png"
98-
alt="Overture data in Google Cloud"
99-
width="900"
100-
height="auto"
101-
/>
102-
103-
104-
```sql
105-
// Identify places within the "Restaurant" category
106-
SELECT id, phones.list[0].element AS phone, names.primary AS name
107-
FROM `bigquery-public-data.overture_maps.place`
108-
WHERE categories.primary = "restaurant"
109-
LIMIT 100;
110-
```
58+
```sql
59+
-- Identify places within the "Restaurant" category
60+
SELECT id, phones.list[0].element AS phone, names.primary AS name
61+
FROM `bigquery-public-data.overture_maps.place`
62+
WHERE categories.primary = "restaurant"
63+
LIMIT 100;
64+
```
11165

11266
## Additional notes
11367

11468
- **Updates**: CARTO regularly updates the Overture datasets in BigQuery and keeps the dataset synced with the last release. You can check the release version of the data as a metadata label in each table.
115-
- **Support**: If you encounter issues accessing the data, contact CARTO support via [email protected].
116-
69+
- **Support**: If you encounter issues accessing the data, contact CARTO support via [[email protected]](mailto:[email protected]).

docs/getting-data/data-mirrors/databricks.mdx

+14-76
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ title: Databricks
55
Overture data is accessible through the [Databricks Marketplace](https://marketplace.databricks.com/?searchKey=CARTO&sortBy=date) via public listings published and maintained by [CARTO](https://www.carto.com). Below is a step-by-step guide on how to access and use the data:
66

77
## Before you begin
8+
89
Before accessing the Overture Maps data in Databricks, ensure you have:
910

1011
- **Databricks Account**: An active Databricks account with access to the Databricks Marketplace.
@@ -16,108 +17,45 @@ Before accessing the Overture Maps data in Databricks, ensure you have:
1617
1. Log in to your Databricks workspace.
1718
2. From the Databricks workspace home page, navigate to the **Databricks Marketplace** by selecting the **Marketplace** tab from the sidebar.
1819

19-
20-
<img
21-
src="/img/getting-data/databricks-1.png"
22-
alt="Databricks Marketplace"
23-
width="900"
24-
height="auto"
25-
/>
26-
20+
![Databricks Marketplace](/img/getting-data/databricks-1.png)
2721

2822
3. Use the search bar in the Databricks Marketplace to search for `CARTO` or `Overture Maps`.
2923

30-
31-
<img
32-
src="/img/getting-data/databricks-2.png"
33-
alt="Databricks Marketplace"
34-
width="900"
35-
height="auto"
36-
/>
37-
24+
![Databricks Marketplace](/img/getting-data/databricks-2.png)
3825

3926
4. The listings have been organized by Overture theme; therefore, you will find the following listings available: Addresses, Base, Buildings, Divisions, Places and Transportation. Select one to access the listing details.
4027

41-
42-
<img
43-
src="/img/getting-data/databricks-3.png"
44-
alt="Databricks Marketplace"
45-
width="900"
46-
height="auto"
47-
/>
48-
28+
![Databricks Marketplace](/img/getting-data/databricks-3.png)
4929

5030
5. Review the dataset description, terms of use, and any documentation provided by CARTO.
5131
6. Click **Get instant access** to request access to the dataset.
5232

53-
54-
<img
55-
src="/img/getting-data/databricks-4.png"
56-
alt="Databricks Marketplace"
57-
width="900"
58-
height="auto"
59-
/>
60-
33+
![Databricks Marketplace](/img/getting-data/databricks-4.png)
6134

6235
7. Before you get access you can specify where are you planning to use the data and also provide a custom name to the Databricks Catalog in which the data will be made available. After accepting the terms, click on **Get instant access**.
6336

64-
65-
<img
66-
src="/img/getting-data/databricks-5.png"
67-
alt="Databricks Marketplace"
68-
width="900"
69-
height="auto"
70-
/>
71-
37+
![Databricks Marketplace](/img/getting-data/databricks-5.png)
7238

7339
8. Now, in the same listing page you have the option to click on **Open**.
7440

75-
76-
<img
77-
src="/img/getting-data/databricks-6.png"
78-
alt="Databricks Marketplace"
79-
width="900"
80-
height="auto"
81-
/>
82-
41+
![Databricks Marketplace](/img/getting-data/databricks-6.png)
8342

8443
9. After clicking on **Open** you will be taken to your Catalogs with the newly created Catalog `carto_overtue_maps_places`open.
8544

86-
87-
<img
88-
src="/img/getting-data/databricks-7.png"
89-
alt="Databricks Marketplace"
90-
width="900"
91-
height="auto"
92-
/>
93-
45+
![Databricks Marketplace](/img/getting-data/databricks-7.png)
9446

9547
## Working with Overture data in Databricks
9648

97-
10. Once you have the Overture Maps data that you need in your Catalogs you can start working with it. Following our example, in the Place table you can click on **Create** and then **Query**.
98-
99-
100-
<img
101-
src="/img/getting-data/databricks-8.png"
102-
alt="Databricks Marketplace"
103-
width="900"
104-
height="auto"
105-
/>
106-
107-
108-
11. That will open the SQL Editor ready to query the `place` table.
49+
1. Once you have the Overture Maps data that you need in your Catalogs you can start working with it. Following our example, in the Place table you can click on **Create** and then **Query**.
10950

51+
![Databricks Marketplace](/img/getting-data/databricks-8.png)
11052

111-
<img
112-
src="/img/getting-data/databricks-9.png"
113-
alt="Databricks Marketplace"
114-
width="900"
115-
height="auto"
116-
/>
53+
2. That will open the SQL Editor ready to query the `place` table.
11754

55+
![Databricks Marketplace](/img/getting-data/databricks-9.png)
11856

119-
## Additional notes
57+
## Additional notes
12058

12159
- **Updates**: CARTO regularly updates the Overture datasets in Databricks and keeps the listings synced with the last release. You can check the release version of the data from the share description in each listing.
122-
- **Support**: If you encounter issues accessing the data, contact CARTO support via [email protected].
60+
- **Support**: If you encounter issues accessing the data, contact CARTO support via [[email protected]](mailto:[email protected]).
12361
- **Databricks**: For more information on Databricks Marketplace, refer to the official [Databricks documentation](https://docs.databricks.com/en/marketplace/index.html).

0 commit comments

Comments
 (0)