BlueCarbon

Evidence for blue carbon, from the parcel up.

Digital monitoring, reporting and verification for mangrove restoration. Land, boundaries and the record of who asserted what — held so that a verification body can check it rather than take our word for it.

Boundaries measured on the serverGeodesic and planar area, the UTM frame they were computed in, and the disagreement between them — recorded, not rounded away.
The file you uploaded, kept as you uploaded itPreserved byte for byte with its SHA-256. A new boundary supersedes the old one; nothing is overwritten.
Verra Geolocation v5.0 checked at ingestConformance issues are raised when the boundary is saved, not discovered during validation.
KML, KMZ, GeoJSON, shapefile, GeoPackageOr draw the parcel on the map. Whatever the surveyor sent, the same pipeline reads it.
An audit trail your verifier can read themselvesEvery change hash-chained to the one before it, written in the same transaction as the change it records.

The audit chain is tamper-evident, not tamper-proof: a selective edit is detected, a wholesale rewrite would need an external witness. Said here for the same reason it is said in the API — a verifier will test a system that claims otherwise.

BlueCarbonDigital monitoring, reporting and verification for mangrove restoration.

Sign in

Use the address your organisation created your account with.

Organisations are created through the API; this dashboard signs in to one that already exists. Your session is held in a cookie the browser cannot read, so no script on this page can take it.