Map of Abil in STAC format
A map built from OpenStreetMap data, ready to download
Customize the map
Open this place's area in the constructor and adjust everything to your needs
Open in constructor →Map passport
What this map contains by default
This is how the map is built as-is — every setting can be changed in the constructor.
About STAC
Map of Abil in STAC — an export of real OpenStreetMap data for the selected area.
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.
Which layers are in the file
This file for the selected area contains:
- Water
- Greenery
Coordinate systems
WGS 84 (EPSG:4326), selectable in the wizard
Units
Meters (projected in the chosen coordinate system)
| Category | GIS |
| File extension | .json |
| Tier | Open Beta |
How to use STAC for Abil
- pystac (Python) — read the document with the Item.from_file method, check the structure and add the card to your catalogue or collection.
- stac-validator — a quick check of conformance to the specification before publishing.
- STAC Browser — a static viewer: put the catalogue with the cards on static hosting and get a navigable catalogue without a single line of server code.
Programs that open STAC
FAQ: STAC for Abil
Is STAC a map data format?
No. STAC is a metadata description (JSON) that references the data itself but does not contain it. Our STAC Item describes the exported area and points to assets via links.
Does the exporter produce a catalog or an Item?
A single STAC Item v1.0. It is the atomic catalog element. You assemble the full Catalog/Collection hierarchy on your side by collecting such Items.
Are the asset links inside the Item embedded files?
No, they are href links (template paths to your export and preview). You export the data itself in a separate format (e.g. COG or GeoParquet) and tie it to the Item.
Why is STAC useful together with COG/GeoParquet?
STAC gives a uniform way to describe and discover your assets, while COG and GeoParquet are the cloud data themselves. Together they form a modern cloud-native stack.
Is this valid GeoJSON?
Yes, by the specification a STAC Item is a GeoJSON object: the file will open in QGIS or in a browser-based viewer and show the rectangle of the exported area. The useful payload, meanwhile, sits in the properties and in the assets block.
