Georizon documentation
Georizon ingests geospatial data — panoramas, point clouds, aerial and oblique imagery, orthophotos — processes it, and serves it back through viewers and APIs.
Getting data in is the part that needs a contract. Every delivery is read by an ingest template: a piece of code that walks your bucket, finds the files, reads the pose data and indexes it. Each template expects a specific folder layout and a specific metadata format. Deliver something it doesn't recognise and processing fails, usually with a message about a file it couldn't find.
These pages are that contract.
Where to start#
If you are preparing a delivery, read Concepts first — it covers the conventions every template shares (coordinate systems, rotation angles, filename matching, how strict each template is). Then read the page for your specific template.
If you don't know which template your dataset uses, ask your Georizon contact, or look at the dataset's ingest profile in the web app.
An assistant can drive the same delivery loop through the MCP server.
- Getting startedHow a Georizon dataset delivery works, from bucket credentials to processed output.
- ConceptsConventions shared across ingest templates: coordinate systems, rotation angles, filename matching and sets.
- MCPConnect an assistant to Georizon over MCP: datasets, delivery, processing runs and snapshots, with the same permissions as the web app.
- Ingest templatesOne page per ingest template: the folder layout, metadata format and parameters each one expects.
- Data exportPackaging data Georizon holds into a downloadable archive, and what the formats give you.