STAC 🗂

SpatioTemporal Asset Catalog

Open Beta
.json · application/json

STAC (SpatioTemporal Asset Catalog) is not a data format but an open JSON schema for describing geo assets: satellite imagery, rasters, vector layers. The Catalog -> Collection -> Item -> Asset hierarchy plus the STAC API REST spec made STAC the de-facto standard for cloud catalogs (AWS, Microsoft Planetary Computer, ESA Copernicus). Our exporter generates a SINGLE STAC Item v1.0 — a JSON document describing the exported area: bbox, GeoJSON frame geometry, export datetime, per-layer statistics, and asset links. It is a "brick" you drop into your own catalog. To be clear: the Item's asset links are template hrefs to your export, not embedded data, and this is an Item rather than a full Catalog/Collection hierarchy.

Export STAC now ✨ Open Beta — free, no limits

Key Features

STAC Item v1.0, valid as a GeoJSON Feature (type=Feature, geometry, bbox)
Export-frame geometry in WGS84; datetime/created/updated set at export time
Per-layer stats (name, feature count, geometry type) under `osm2cdr:*` properties
An assets block with data/thumbnail roles and root/self catalog links
Plain JSON — opens in any STAC tool or a regular text editor

About STAC Format

The easiest way to picture STAC is a card in a library catalogue. There is no data in it, but there is everything needed to find the data: which territory, when the export was made, what is inside and at which link the file sits. That is exactly how the cloud catalogues of large providers are arranged — a single JSON schema on top of different storages.

The export is for those who run their own geodata storage. You exported an area, put a card next to it, and a month later you find what you need by searching on territory and date rather than by going through file names. When there are dozens of exports, such cards add up into your own searchable catalogue.

What is in the file: one STAC Item of version 1.0 — and at the same time a valid GeoJSON object. Inside are the extent and the geometry of the frame, the date and time of the export, properties with a summary of the layers (which layers made it in and how many objects they contain), service links and an assets block. The asset links are templates: you export the data itself in a separate format and substitute your own storage address.

What Program Opens STAC Files

The following programs and applications can open, edit, and work with SpatioTemporal Asset Catalog (.json) files exported from OSM2CDR:

💻pystac / pystac-client 💻stac-fastapi 💻Radiant Earth STAC Browser 🌎QGIS (STAC plugin) 💻rasterio / stackstac

Format specifications

Who Uses STAC Maps

🏗
Cataloging your exports: place a STAC Item next to a raster/vector in your own catalog
A description card next to the export: a month later you find it by territory and date, not by file name.
💻
Publishing a mini-STAC: one Collection plus many Items on static storage or GitHub Pages
Your own mini catalogue on static hosting: one collection plus a set of cards, with no server code.
📊
Asset search and discovery via a STAC API (stac-fastapi / pystac-client) in your stack
Search and selection by territory and time in your stack through the standard STAC API.
🎨
Integration with the cloud-native STAC + COG + GeoParquet triad for analytical pipelines
Metadata paired with cloud-native data — COG for rasters, GeoParquet for vectors.

How to Export STAC

1
Select area
Draw a rectangle or polygon on the interactive map at osm2cdr
2
Choose STAC
Select SpatioTemporal Asset Catalog from the list of 127 available export formats
3
Export
Click Export and receive your .json file in 1-5 minutes
4
Download
Download the ready STAC file and open it in pystac / pystac-client

How to Open After Export

Popular maps in STAC

Free

Get SpatioTemporal Asset Catalog map exports

Download professional STAC maps from OpenStreetMap. Instant generation, any area.

Free / export
Export STAC now →

Frequently Asked Questions

Is STAC a map data format?
Does the exporter produce a catalog or an Item?
Are the asset links inside the Item embedded files?
Why is STAC useful together with COG/GeoParquet?
Is this valid GeoJSON?
What is written in the properties of the card?

Related Formats

Frequently Exported Together

Related Articles