MIT
Source code
All GSIP software source is public: apps, backend, workers, library, modelling tools, API and tests. Use, modify, self-host or extend it under MIT. Dependencies retain their own licences.
Open data, honest boundaries
Explore the soil library tools, planned public releases, licences and privacy boundaries.
The release job fails closed if a contribution lacks its immutable grant, contains a precise location field, or carries embedded image metadata. New releases contain structured data only until photo screening is deployed and its calibration approved.
Individual spectra remain private pending a fingerprinting and privacy review, even without coordinates. An H3 cell alone does not make a spectrum safe to publish.
Inspect the export sourceMIT
All GSIP software source is public: apps, backend, workers, library, modelling tools, API and tests. Use, modify, self-host or extend it under MIT. Dependencies retain their own licences.
ODbL 1.0
Public database records use an open share-alike data license with source attribution.
CC BY-SA 4.0
Contributors retain ownership and grant publication under a separate photo license with recorded attribution.
Public release boundary
Citation and takedown
The generated dataset card carries source citations, schema, license boundaries, photo attribution, and export-date provenance. A public privacy contact will be published before real contributions are released. Copies already released may persist; withdrawal removes eligibility from future GSIP releases and requires affected artifacts to be rebuilt. Do not post private contributor details in public issues.
Build on the library
The private local store accepts typed camera RGB and instrument reflectance records linked by sample identity. Local declarations are not verified GSIP acceptance. Hosted uploads, node exchange and public spectral releases remain gated.
Library developer guide ↗Agents and developers
The read-only API and MCP server are designed for the capture protocol, eligible public cells and release metadata, with licences and citations. Configured endpoints appear below. They expose no precise locations or private library records, and offer no capture or node-registration tool.
Agent guide · OpenAPI description · MCP endpoint https://toxldjgwkxtneoqsazym.supabase.co/functions/v1/gsip-public/mcp