Ecological Infrastructure
The operating system for ecology.
Rangifer is the operating system for ecology: a map-first data and interface layer for diagnosing environmental problems, prioritizing interventions, and producing citable reports for sustainability work. It is built for people who need to see the territory, inspect the records, and understand how the metrics were made.
Entry Points
Four public surfaces around one ecological system.
The site is organized around the map, the interfaces, the data, and the method. Each page points back to the same sustainability stack: evidence, reports, interfaces, and transparent methods for improving ecological conditions.
Live ecological map
Species-level urban forest exploration, layer controls, biodiversity context, and downloadable public data.
Assessments and citable outputs
Polygon-specific reports for consultants, planners, and ESG teams, with API and MCP access available behind the scenes.
Public ecological datasets
Current ecology catalog, layer coverage, delivery modes, access paths, and legacy tree audit documentation.
Transparent pipeline
Ingestion, normalization, enrichment, QA, and publication logic documented end to end.
Why This Form
The map is not a feature. It is the front door.
Ecology is spatial, uneven, and contested. The UI should expose geography first, then let the user drill into records, metrics, and methods. That is why Rangifer reads more like a public ecological operating system than a software landing page.
Spatial surface
The map is the primary interface. It exposes the actual geography, not a dashboard abstraction.
Report surface
The same ecological system becomes a citable assessment when you move from a polygon to a report.
Method surface
Every published metric is accompanied by enough documentation to audit, reproduce, and challenge it.
Public Access
Start with the live map, inspect the dataset, then connect via REST or MCP. The pages are designed to explain the stack instead of selling around it.