overture_core
Shared, framework-agnostic business logic — portable job classes built on overture-serverless.
overture-stac (and its pyarrow>=16 floor via stac-geoparquet) is an optional extra. Install overture-core[stac] (quote it in shells like zsh that glob brackets: pip install 'overture-core[stac]') if you need stac.job.PublishStac or stac.catalog.build_release_catalog. stac.latest_release_job.LatestRelease only reads the STAC root catalog over HTTPS via pystac, so it works without the extra. Plain overture-core covers the cloud/iceberg/versioning/uuids/uuids_sql modules too. cloud.azure needs overture-core[azure], and cloud.aws.object.read_parquet_prefix needs a pyarrow of your choosing on the path.
maproulette/geojson/shapely are likewise behind an optional overture-core[maproulette] extra, needed only for apis.maproulette.MapRouletteClient.
Modules
Framework-agnostic helpers, each importable on its own without pulling in the job classes below.
| Module | Scope |
|---|---|
uuids |
Pure Python, Spark-free UUID generation for any UUID version, current or future RFC. |
uuids_sql |
SQL-string equivalents of uuids, for computing UUID columns server-side in Spark or Trino instead of round-tripping through a Python UDF. |
versioning |
Deriving a consistent dated version string for sources that don't publish explicit version metadata. |
iceberg |
Shared Iceberg + Sedona catalog configuration, reusable across platforms/engines. |
cloud |
Cloud helpers: provider-agnostic code plus one subpackage per vendor (aws, azure, databricks). |
pypi |
Provider-agnostic PyPI package download/publish helpers, usable against any index. |
apis |
Clients for third-party HTTP APIs, one module per vendor (apis.tomtom for TomTom's Map Content API, apis.maproulette for MapRoulette's project/challenge API — the latter needs overture-core[maproulette]). Anything that's not a cloud platform but still an external service belongs here. |
urls |
Generic URL string utilities not tied to any specific service or cloud provider. |
bbox |
Validating and safely rendering an optional bounding-box string param ("min_lon,min_lat,max_lon,max_lat", '' = full planet), shared by any entry point that accepts one. |
stac |
STAC catalog reads/writes and the jobs that publish them (see Jobs). |
data |
Describing a data location and its sync configuration, independent of the mechanism used to move it. |
docs |
Automating docs-repo updates for a release, via a GitHub App. |
artifacts |
Release artifact types (metadata, license, attribution) and the tree-search/S3 I/O to read and write them. |
dataset |
Parsing, validating and rendering provider/resource dataset configs and the license policy, plus the overture-datasets CLI. |
Jobs
stac.job.PublishStac: publishes the Overture STAC catalog. Two modes selected by the presence of thereleaseparam:- single-release (
release+source_path+scratch_bucket): publish just that release, mirror scoped tostac/{release}/. Schema comes from the RC bundle'smetadata.json. - walk (no
release, requiresscratch_bucket): rebuild the catalog for every release currently in the public bucket, mirror the wholestac/prefix with delete-orphans. Schema per release comes from the existing STAC (schema:versionin eachcatalog.json); on cache miss the job self-heals by reading schema from the released RC bundle inscratch_bucketand raises if it can't recover.
- single-release (
stac.latest_release_job.LatestRelease: reads the STAC root catalog (root_href, defaults to the prod root) and resolves the newest release ID. Read-only, HTTPS-only, no AWS credentials or S3 access needed. Stashes the result onself.latest_releasefor a caller that instantiates the job directly instead of going throughrun().
Future work
- Bundle-owned schema accessor — when
ReleaseCandidateBundlebecomes publishable, moveread_schema_version_from_rc_bundleonto it asresolved_schema_version(); single-release mode's schema read shrinks to one line. - Upstream
build_release_catalog— file a PR against OvertureMaps/stac exposing this as a public API (their CLI already does the exact call sequence). When it lands, our wrapper collapses.
Metadata
Release files for overture-core 1.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| overture_core-1.2.3.tar.gz | 279.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| overture_core-1.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 362.1 kB
Release files / overture_core-1.2.3.tar.gz
| Download URL | overture_core-1.2.3.tar.gz |
|---|---|
| Size | 279.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d47a0a07d5a63f7adea45173bc57dcf15f64d313939c9785a54d6e868d051cfe
|
|
BLAKE2b-256 checksum How to use checksums |
9c32deb2b53473afaec22545a8090e555735629e1eceeef2726e66320cd006dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logRelease files / overture_core-1.2.3-py3-none-any.whl
| Download URL | overture_core-1.2.3-py3-none-any.whl |
|---|---|
| Size | 83.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9763fc2f4e181c45a97aecbd65d86ed7a675b5e8df96c40b9d231e892a03d664
|
|
BLAKE2b-256 checksum How to use checksums |
33a66b4e3e2e830b26c020cb7c9db1441ff5799888f56bc0ceab2341fb90485c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logSecurity for overture-core 1.2.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for overture_core-1.2.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
