From article to assessment: a connected pilot

How one synthetic territory moves through the blog, geostory, catalogue, and SEA workspace.

Short finding

A useful geospatial publication should let readers move from interpretation to the exact source data—and let practitioners reuse a recorded source version in a structured assessment. This pilot demonstrates that connection with artificial data.

Warning

The three demonstration zones are synthetic. They are not measurements, administrative boundaries, or evidence for a real environmental decision.

Explore the territory

Open the geostory in a separate local view

Method

1. Three non-overlapping polygons were written as GeoJSON in EPSG:4326.
2. Existing GDAL tools on the nettop validate the source.
3. The build creates GeoPackage and CSV/WKT distributions.
4. SHA-256 checksums identify the exact downloadable files.
5. Django registers version 1.0.0 as an immutable catalogue record.
6. A SEA project can reference that exact version and retain the relationship.

Data and reproducibility

• Resource page
• GeoJSON
• GeoPackage
• CSV with WKT
• Checksums
• Dynamic catalogue record

Limitations

The current geostory is a lightweight, dependency-free local export so the interface works before Docker is installed. When GeoLibre becomes available, the same versioned data and narrative should be recreated there and exported back into this site.

The pilot does not claim legal completeness, regulatory compliance, or fitness for a real SEA.