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
Reviewing boundary_area entities under the region subtype in the most recent release, I see there are a handful of duplicates. It looks like data from both geoBoundaries and OpenStreetMap are being used to populate the region subtype in Tuvalu, which is the only country affected by this issue.
Running the following query
SELECT id, names.primary as name, sources[1].dataset as source
FROM read_parquet('s3://overturemaps-us-west-2/release/2024-07-22.0/theme=divisions/type=division_area/*', filename=true, hive_partitioning=1)
WHERE country = 'TV'
AND subtype = 'region';
SELECT id, names.primary as name, sources[1].dataset as source
FROM read_parquet('s3://overturemaps-us-west-2/release/2024-07-22.0/theme=divisions/type=division/*', filename=true, hive_partitioning=1)
WHERE country = 'TV'
AND subtype = 'region';
Reviewing boundary_area entities under the region subtype in the most recent release, I see there are a handful of duplicates. It looks like data from both geoBoundaries and OpenStreetMap are being used to populate the region subtype in Tuvalu, which is the only country affected by this issue.
Running the following query
results in this list of entities
Geometries of the geoBoundaries-sourced entities are clipped to land, OpenStreetMap geometries are not. Example of Nanumea:
geoBoundaries
OpenStreetMap
The text was updated successfully, but these errors were encountered: