overturemaps / schema Goto Github PK

https://docs.overturemaps.org/gers/ web page has a problem. I don't know where to report it so I'll report it here. The problem is it goes on and on and on about the gers, without ever providing one single example so users could get an idea of what one of these identifiers looks like. Thank you.

charity_organization references community_organization, but it doesn't exist.

charity_organization;[charity_organization,community_organization]

https://github.com/OvertureMaps/schema/blob/main/task-force-docs/places/overture_categories.csv#L1536C44-L1536C66

It should probably be:

-charity_organization;[charity_organization,community_organization]
+charity_organization;[public_service_and_government,organization,social_service_organizations,charity_organization]

It seems like there is a typo in one of the columns of the Overture Admin Boundaries. For example, consider this DuckDB query:

DESCRIBE SELECT * FROM read_parquet('s3://overturemaps-us-west-2/release/2023-07-26-alpha.0/theme=admins/type=*/*', filename=true, hive_partitioning=1)

The query yields the following result:

┌──────────────────────┐
│     column_name      │
│       varchar        │
├──────────────────────┤
│ id                   │
│ updatetime           │
│ version              │
│ names                │
│ adminlevel           │
│ maritime             │
│ subtype              │
│ localitytype         │
│ context              │
│ isocountrycodealpha2 │
│ isosubcountrycode    │
│ defaultlanugage      │
│ drivingside          │
│ sources              │
│ bbox                 │
│ geometry             │
│ filename             │
│ theme                │
│ type                 │
├──────────────────────┤
│ 19 rows              │
└──────────────────────┘

I would expect the default language column to be called defaultlanguage, not defaultlanugage.

Political perspectives included in admin schema.

Test issue for now

Hi,

My goal is to find the connectors where are tagged with highway=traffic_signal (in OSM).

Unfortunately, I couldn't find that tag in the sourcetag.

Please advise.

I don't see bbox referenced in the schema files, but I do see bbox columns in the 2023-10-19-alpha.0 released Parquet files (e.g. s3://overturemaps-us-west-2/release/2023-10-19-alpha.0/theme=buildings/type=building/part-00765-87dd7d19-acc8-4d4f-a5ba-20b407a79638.c000.zstd.parquet).

In Parquet, the bbox looks like this:

{
   ... other fields
  required group bbox {
    optional double minx;
    optional double maxx;
    optional double miny;
    optional double maxy;
  }
}

So the bbox is required, but the nested minx, maxx, miny, and maxy fields are optional (or nullable). I was curious if this was leveraged anywhere in the data (should clients be prepared to handle null minx etc?) or if it should be changed in the schema to make those fields required.

Let me know if this is a better issue for the data repo or for a discussion instead.

Variable names speak for themselves in most cases, but it would still be useful.

A proposal for a simple, usable format : categories.json.txt

Testing push from GitHub to Slack

Testing push to Slack channel