This release is a pre-release and may not be stable for production use.
scse-spatial
A registry that indexes and queries spatial data resources on other services.
Overview
scse-spatial is the spatial data extension to a scenario services web application stack. It turns geodata files into fast, web-optimized resources and serves them to any map app.
A workflow loads data. A web app reads it. This repository provides both sides: the ingest path and the HTTP API.
Feeding it
Workflows push data in with the CLI or a few lines of Python. The Spatial
object connects to a PostGIS database and to object storage. It exposes
services for rasters, features, and a STAC catalog.
with Spatial("<platform>", settings=Settings()) as spatial:
spatial.rasters.sync_hierarchy(
"emissions",
[path],
parameters_class=EmissionParameters,
metadata_class=EmissionMetadata,
extract_meta=extract_em_meta,
)
spatial.stac.export_catalog()
The platform converts each source file into optimized formats, uploads them, and indexes them. A re-run skips files whose content did not change.
Workflows live in their own repositories. See WORKFLOWS.md for more information.
Connecting to a platform
In multi-tenant deployments the connection details come from the manager API. Staff log in with their user account once; the credentials are cached locally and used in place of the shared service secret.
spatial login # prompts for username and password, caches them
spatial whoami # show the identity the CLI would use
spatial platforms # list the platforms you can access
The manager DSN's secret material stays in the local environment through
{env:...} placeholders. Imports are attributed to the logged-in user.
HTTP API
Web apps can read data over HTTP. A Litestar server lists hierarchies and layers, renders map tiles through TiTiler, and streams vector tiles and GeoJSON from object storage.
curl -X PATCH http://<scse-spatial>/v1/{platform}/rasters/ \
-H "Content-Type: application/json" \
-d '{"hierarchy_id": 3, "parameters__contains": {"sector": "power"}}'
Point an scse-app at the /v1 or /titiler endpoints, or open /docs and
/titiler/docs for interactive API docs. See HTTP_API.md for more information.
Development Setup
# Install Poetry, minimum version >=1.2 required
pipx install poetry
# You may have to reinitialize your shell at this point.
source ~/.bashrc
# Activate in-project virtualenvs
poetry config virtualenvs.in-project true
# Add dynamic versioning plugin
poetry self add "poetry-dynamic-versioning[plugin]"
# Install dependencies
# (using "--with dev" if dev dependencies should be installed as well)
poetry install --with dev
# Activate virtual environment
poetry shell
# Copy the template environment configuration
cp template.env .env
Metadata
Release files for scse-spatial 1.0.0rc1
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 | Actions |
|---|---|---|---|---|
| scse_spatial-1.0.0rc1.tar.gz | 85.1 kB | With provenance | Details for scse_spatial-1.0.0rc1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scse_spatial-1.0.0rc1-py3-none-any.whl | Python 3 | none | any | Details for scse_spatial-1.0.0rc1-py3-none-any.whl |
Total release size: 195.5 kB
Release files / scse_spatial-1.0.0rc1.tar.gz
| Download URL | scse_spatial-1.0.0rc1.tar.gz |
|---|---|
| Size | 85.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf20bb3b42d6e2e9d79c8a0c9f5438eada080298c3c562bc8b6947b6257b8c3f
|
|
BLAKE2b-256 checksum How to use checksums |
1750c81cad1a8ea22d94261632706cc92c50d9bb97199a8382bc4ec3687d66fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 22, 2026.
Transparency logRelease files / scse_spatial-1.0.0rc1-py3-none-any.whl
| Download URL | scse_spatial-1.0.0rc1-py3-none-any.whl |
|---|---|
| Size | 110.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2b686ebe734b942067a5df7d468141c5c5f068a81a87a77d82ff55027d808ab
|
|
BLAKE2b-256 checksum How to use checksums |
945047278573ff35b781d27b6009a27883e5138f1c06285f446221070cd4d88c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 22, 2026.
Transparency logSecurity for scse-spatial 1.0.0rc1
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
Both files in this release have been uploaded with provenance metadata.
Attestation for scse_spatial-1.0.0rc1.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 22, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.