TL;DR
A demo showing offline map tiles, routing and geocoding packaged in a single Docker Compose stack is live as a first step. The team plans features including a local map updater, custom GeoJSON overlays, richer address results, and expanded edge deployment examples.
What happened
The project published a Monaco demo that demonstrates a single Docker Compose-based stack combining offline map tiles, routing and geocoding. The maintainers say this demo reflects the architecture they intend to scale to larger regions and production fleets. Upcoming work includes a background 'local map updater' service designed to fetch new map bundles, verify them, and swap datasets without downtime; support for loading custom overlays (POIs, geofences or other operational GeoJSON layers) rendered in the UI; improvements to geocoding that aim to return house numbers and optional geometries for streets and areas in forward and reverse search; and broader edge deployment targets. The roadmap also lists first-class integrations for Portainer and Mender plus deployment examples for K3s/Kubernetes and edge runtimes on AWS and Azure. The team is soliciting user input via a feedback form to help prioritize these items.
Why it matters
- Combines offline tiles, routing and geocoding into a single, locally deployable stack, reducing reliance on external APIs for offline/edge use cases.
- Planned map updater aims to let operators refresh datasets without interrupting running services, important for live fleets and continuous operations.
- Custom overlay support would let organizations render their own POIs and geofences on top of base maps for operational workflows.
- Richer geocoding with house numbers and geometry could improve address accuracy and spatial queries in both forward and reverse lookups.
- Expanded edge deployment targets and integrations (Portainer, Mender, K3s/Kubernetes, AWS/Azure examples) aim to simplify rollouts across diverse infrastructures.
Key facts
- A Monaco demo has been released as the first step toward broader usage.
- The demo uses a Docker Compose stack that packages offline tiles, routing, and geocoding together.
- Planned 'local map updater' will pull new map bundles, verify them, and switch active datasets without downtime.
- Custom overlays will accept GeoJSON for POIs, geofences, and operational layers rendered in the UI.
- Geocoding improvements will target house-number results and optional geometry for streets and areas in forward and reverse searches.
- Planned platform integrations include Portainer and Mender.
- Deployment examples are planned for K3s/Kubernetes and edge runtimes on AWS and Azure.
- The project requests user feedback via a form to help set feature priorities.
- Original source published at corviont.com on 2026-01-03T15:55:16+00:00.
What to watch next
- Release of the local map updater service that enables dataset refresh without downtime.
- Availability of custom overlay support (GeoJSON POIs, geofences) rendered in the UI.
- Rollout of richer geocoding output including house numbers and optional geometries for streets and areas.
- Timeline for Portainer, Mender integrations and K3s/Kubernetes, AWS and Azure deployment examples — not confirmed in the source.
Quick glossary
- Docker Compose: A tool for defining and running multi-container Docker applications using a YAML file to configure application services.
- Geocoding: The process of converting between textual addresses and geographic coordinates (forward geocoding) and the reverse.
- GeoJSON: A common JSON-based format for encoding geographic data structures such as points, lines and polygons.
- Point of Interest (POI): A specific location on a map that someone may find useful or interesting, such as a business or landmark.
- Edge runtime: A computing environment that runs workloads close to where data is generated or consumed, often on local or remote devices rather than centralized cloud servers.
Reader FAQ
Where can I try the Monaco demo?
not confirmed in the source
Will geocoding return house numbers and street geometries?
The roadmap states planned improvements to return house numbers and optional geometries for streets and areas in forward and reverse search.
Which edge platforms are targeted?
The team lists Portainer and Mender integrations and deployment examples for K3s/Kubernetes and edge runtimes on AWS and Azure.
How can users influence feature priorities?
The project requests input through a feedback form; users are invited to indicate which features matter most.
What we’re building next The Monaco demo is the first step. It’s the same architecture we’ll use for larger regions and real fleets – here’s what’s on the way: 🧩…
Sources
- Show HN: Offline tiles and routing and geocoding in one Docker Compose stack
- Offline tiles and routing and geocoding in one Docker …
- monaco-demo/README.md at main – Corviont Maps
- Corviont – Documentation
Related posts
- When Ctrl-C Outperforms a Profiler: Practical Sampling with a Debugger
- Blog adds X-Clacks-Overhead HTTP header on Cloudflare Pages to honor Pratchett
- ParadeDB (YC S23) Seeks Database Engineers for Postgres-native Search Platform