division area data not found for id 23e81262-d6ed-45a3-a1a0-4bc6a2a887d8 in Sep 2025 release of overture data

[shakeelkadam]

division area data not found for id 23e81262-d6ed-45a3-a1a0-4bc6a2a887d8 in Sep 2025 release of overture data

INSTALL spatial;
LOAD spatial;
INSTALL httpfs;
LOAD httpfs;

SET s3_region='us-west-2';

SELECT
*
FROM
read_parquet('s3://overturemaps-us-west-2/release/2025-09-24.0/theme=divisions/type=division_area/*', filename=true, hive_partitioning=1 )
WHERE
id = '23e81262-d6ed-45a3-a1a0-4bc6a2a887d8';

SELECT
*
FROM
read_parquet('s3://overturemaps-us-west-2/release/2025-09-24.0/theme=divisions/type=division/*', filename=true, hive_partitioning=1 )
WHERE
id = '23e81262-d6ed-45a3-a1a0-4bc6a2a887d8';

[sasastanojkov]

@shakeelkadam did it ever exist? From what I see, division with id "23e81262-d6ed-45a3-a1a0-4bc6a2a887d8" is present in divisions. And same as the last time it was created by this OSM node Amundsen–Scott South Pole Station. That entity doesn't have polygon so it makes sense not to have it in division_area.
Additionally, if you want to search for polygon of the division use filter WHERE division_id = '{gers_id}'. division and division_area entities do not share ids. Each has its unique one.