Viridis Conservation · Open ecosystem
Land Package, version 1.0
One file format for evidence about a piece of land, so a result from one tool can be read by another without losing where it came from.
A Land Package is a JSON file. It holds map layers, the source of each layer, statements about the land marked as measured, modelled or estimated, a list of data that could not be retrieved, and a declaration of what is private.
The format, the validators in Python and JavaScript, and their tests are open source under Apache-2.0.
Which tools use it today
| Tool | State | What that means |
|---|---|---|
| Viridis land design reports | Writes it | Each report includes a land_package.json file. The report is not delivered if the file is invalid or disagrees with the design. |
| The checker on this site | Reads it | Checks a Land Package file in your browser and shows its layers, claims, missing data and privacy declaration. The file is not uploaded. |
| Dendritic Forest Management | Converts | A Dendritic Forest landscape package converts to a Land Package and back unchanged, tested on three of the project's example landscapes. Dendritic Forest itself does not read or write Land Packages. |
| VergeCommon | Writes it | A woodland project can download a draft or a checked plan as a Land Package. The file is made in the browser and is marked as personal data when it holds woodlot parcels. Other co-op records are not exported this way. |
| Contour Alley Designer | Writes it | Each design run that passes its checks writes a Land Package with the field area, tree-row area, plant count and an indicative cost-share figure, each labelled as derived, modelled or estimated. It holds no coordinates and no map layers. |
| Global Soil Intelligence Project | Not yet | Its public data releases are not open. |
| Viridis Ecological OS | Reads it | The decision workspace accepts a Land Package as starting evidence. You choose which of its USD figures to use, and each keeps its kind and the file's hash as its source. The file is not uploaded. |
What a package holds
land_package- The format version.
name, created, generator- What the package describes, its date, and the tool that wrote it.
crs, units- Always EPSG:4326, metres and square metres.
subject- The kind of land (property, field, woodlot or landscape) and its area.
privacy- Whether the location is exact, whether the file holds personal data, and the consent it rests on.
sources- Every dataset or method used: title, address, date, licence and notes.
layers- Named map layers. Each lists its sources and its GeoJSON features.
claims- Statements about the land. Each has a kind and names a source or a method.
not_retrieved- Data the tool tried to get and could not, and what that means for the reader. Present even when empty.
receipt- Optional. Fingerprints that let a result be reproduced.
extensions- Optional. Tool-specific content. A reader keeps what it does not understand.
integrity- A SHA-256 hash of everything else in the file, taken over canonical JSON (RFC 8785) so any language can check it.
Claim kinds: measured, modelled, estimated, derived, stated. A measured claim must name the source of the measurement.
The rules a valid package meets
LP1 · Geometry
GeoJSON in EPSG:4326, longitude then latitude. Out-of-range coordinates and open rings are errors.
LP2 · Provenance
A layer with features names at least one source. A claim names a source or a method.
LP3 · Honesty
The list of data not retrieved is always present. Claim kinds are a fixed list, so a modelled figure cannot travel as a measurement.
LP4 · Privacy
The file declares location precision, personal data and consent. Whether it may be shared is worked out by the reader and is never written into the file.
LP5 · Integrity
A file whose hash does not match its content is invalid.
LP6 · Lossless
A Dendritic Forest landscape package converted in and back out is identical.
LP7 · Nothing dropped silently
Unknown layers and extensions are kept. An unsupported geometry type is an error.
LP8 · Deterministic
The same content gives the same bytes and the same hash.
Limits
- Version 1 has no raster layers and no time series.
- A land design report's package holds a street address and exact boundaries. It is marked as personal data held for its owner, and a reader must treat it as not shareable.
- Zones, plant positions and water features in a land design report are model output. Water features are marked as proposed, not engineered.
- A package made from a file that recorded no sources is valid, and carries a warning on every layer.
- The schema checks structure. Source cross-references, ring closure, coordinate range and the hash are checked by the open reference validators, in Python and JavaScript.
- The hash shows that a file has not changed since it was written. It does not show who wrote it.
Schema file SHA-256: 141771af2ebb6c03cbff8d505d4b915506a9d1d28ea236d6bdca0feaba7ed61a