One geospatial platform for the whole county.
Honua serves your data, publishes your open data hub, builds your public apps and dashboards, runs administration, and gives staff an AI agent that cites every answer. It replaces the GIS stack end to end, and the tools you already run keep working on day one.
Demo answer: illustrative request triage over synthetic records; school points are exercise anchors.
Work order proposed, waiting for one approval
Four county journeys, one platform
These snapshot previews share verified Maui layers and clearly labelled demo records. Open a journey to see the full screen.
Property and planning
- Search by TMK across 2,538 real parcels
- Zoning, FEMA flood and tsunami overlays with source details
- State land use, SMA and growth boundaries; community plan source pending; permits by TMK in MAPPS, the County permit system
311 operations
- 469 requests on real streets, by district, type and SLA
- Location facts on intake: district, nearest asset, crew, hazard zone
- Preview feed and proposed hand-off to a CRM or work order
Emergency preparedness exercise
- Tsunami zones, school exercise anchors and simulated road status
- Public view and EOC-only layers, public GeoJSON and OGC feeds
- Self-hostable; this preview uses snapshot data
Public works assets
- Storm drains, culverts, signals and real NBI bridge ratings
- Inspections, work order board and crew dispatch
- Field updates from existing field apps, offline with conflict handling
The platform
These are platform integration examples; the pages above use verified static snapshots. Honua's own apps and the tools you already own read the same endpoints.
Your data
Honua Server
Every layer is published once and served through each protocol below. Writes through OGC API Features and GeoServices REST go to the same records.
Who reads it
Switch without breaking your tools
Existing clients point at Honua's endpoints and keep working while you move apps across. Validate each integration in your pilot.
| Tool you run today | Reads Honua through | Example endpoint | Day one |
|---|---|---|---|
| Desktop GISexisting licences and projects | GeoServices REST, WMS | …/rest/services/Parcels/FeatureServer | Pilot check |
| Existing web maps and dashboardsvalidate saved maps in your pilot | GeoServices REST | …/rest/services/Hazards/MapServer | Pilot check |
| Permitting systemparcel, zoning and overlay lookups | FeatureServer query | …/Zoning/FeatureServer/0/query | Pilot check |
| EOC boardzones and shelters as map layers | GeoServices REST, WMS | …/Preparedness/FeatureServer | Pilot check |
| Field appsinspections, offline sync | FeatureServer edits, OGC API Features | …/StormDrains/FeatureServer/0 | Pilot check |
| QGISanalysts and partner agencies | OGC API Features and Tiles, WFS | …/ogc/collections | Pilot check |
A layer URL changes in each tool once. Validate data, symbology and saved maps before migration. New apps are built in Studio, and the old ones are retired when nobody opens them.
Migration pathWhat the county gets
Estimates from the demo records. Method notes under each figure.
About 36 requests a week (469 over 90 days); duplicate checks, routing and status replies drafted by the agent save about 13 minutes per request. Demo estimate.
The agent drafts the sitrep from snapshot layers; the planning chief reviews and approves. Typical manual compilation runs about 2 hours. Demo estimate.
Server, portal and hub, app builder, admin and AI assistant in one subscription. Fewer licences, contracts and renewals.
Every agent change is a proposal with citations. One named person approves it in Console, and the audit log records both.