Data release endpoint or feed?

[tijptjik]

Is there an authoritative (consistently structured) source with data releases which also note the associated schema version, and (ideally) link out to the various storage endpoints.

The closest I could find is the table of historic versions on the release calendar blog, but this lags behind the actual release of new data and could easily change its formatting.

Ideally we'd have an API endpoint, or simply a JSON file under version control, or publishing the release in the repo as you're doing for the schema.

[krizleebear]

I think this meets your requirements:
https://github.com/OvertureMaps/data/blob/main/overture_releases.yaml

[tijptjik]

Thanks for the stop-gap measure! The STAC catalog mentioned below is the ultimate ✨

[jenningsanderson]

@tijptjik — Yes! We've been working on a STAC catalog at https://stac.overturemaps.org/catalog.json

Open to any feedback you might have about this!

[tijptjik]

ohhh yes! This is very exciting :) And ideally it would only go live after the uploads to both storage options have been completed. This would avoid edge cases where consumers pick up the STAC release and start ingesting the data before it's actually fully been made available.

Although with the full theme <> featureType mapping specified in the catalog, at least the consumers can check for consistency with what's available in storage.

Either way, big improvement! Much appreciated :)