Skip to content

Metadata for all other Overture Maps tables#1611

Open
xavipereztr wants to merge 6 commits intogoogle:mainfrom
xavipereztr:xavipereztr-alltables
Open

Metadata for all other Overture Maps tables#1611
xavipereztr wants to merge 6 commits intogoogle:mainfrom
xavipereztr:xavipereztr-alltables

Conversation

@xavipereztr
Copy link
Contributor

No description provided.

@@ -0,0 +1,10 @@
var dataset = ee.FeatureCollection(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please use loadBigQueryTable()

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please provide me a bit more clarity on what's needed here? It's only for this example for the Addresses data or in all other examples too? Can you point me to some other example that uses loadBigQueryTable() as expected here? thanks!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean, just like you use loadBigQueryTable() in https://github.com/google/earthengine-catalog/blob/main/examples/overture-maps/overture-maps_places_place.js#L2

If that doesn't work for some of the datasets, let's discuss why

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have updated the PR to fix:

  • Regular examples: ee.FeatureCollection() → ee.FeatureCollection.loadBigQueryTable()
  • Preview files: Changed to SQL query pattern with ee.FeatureCollection.runBigQuery()

@@ -0,0 +1,10 @@
var dataset = ee.FeatureCollection(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sadly, this table is too large to load like this (EE has certain limitations). ee.FeatureCollection.runBigQuery() can be used to work around them, but this call will incur charges, unlike use of BQ through EE. I'd avoid this and any other very larget table for now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this comment only applicable for the example? Can we have a dataset (Overture Buildings) listed without the example? I think we should keep listing all Overture's tables, otherwise the product is incomplete.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, this is a great example that I was waiting for to discuss internally how to handle such large tables. I'll start an internal discussion, but it might take a while.

- Regular examples: ee.FeatureCollection() → ee.FeatureCollection.loadBigQueryTable()
- Preview files: Changed to SQL query pattern with ee.FeatureCollection.runBigQuery()
@xavipereztr xavipereztr requested a review from simonff January 14, 2026 09:11
@@ -0,0 +1,10 @@
var dataset = ee.FeatureCollection(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The syntax is ee.FeatureCollection.loadBigQueryTable()

(yes, it's non-intuitive)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@simonff I changed this files on today's PR. They don't include this anymore but:

// Query water in New York City area for preview.
var query = "SELECT geometry FROM bigquery-public-data.overture_maps.water " +
"WHERE ST_INTERSECTS(geometry, ST_GEOGFROMTEXT('POLYGON((" +
"-74.3 40.4, -73.7 40.4, -73.7 40.95, -74.3 40.95, -74.3 40.4))'))";

// Load collection.
var water = ee.FeatureCollection.runBigQuery(query);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants