packet_mover

5 ms·

1.
by packet_mover 7mo ago
Context: I posted a Show HN a while back about an offline maps stack (vector tiles + routing + geocoding) for edge/on-prem/air-gapped deployments, and one common question was about hardware requirements. Original thread for backgr
2.
Hardware footprint benchmarks for an offline maps/routing/geocoding stack(corviont.com)
1 points by packet_mover 7mo ago|1 comments
3.
by packet_mover 9mo ago
It is built in a website builder ( https://unicornplatform.com/ ). I kept it intentionally simple while I validate demand - the real artifact is the demo + repo/docs, the site mostly just points people there and helps wi
4.
by packet_mover 9mo ago
Thanks both - appreciate the clarification and the Spain datapoint. Those numbers look pretty reasonable. I’ll keep Photon in mind and, as I get time to benchmark different approaches on a few representative regions/hardware, I’ll use
5.
by packet_mover 9mo ago
Thanks, appreciate the context. Bounding box input is a really interesting idea. For my product, the best use would probably be to automate the request/fulfillment flow if this ever picks up. Letting someone draw/paste a bbox make
6.
by packet_mover 9mo ago
Yeah, I also ran into that when ranking geocoding results - you want to show more "important"/notable places first. In your case, one pragmatic approach could be to keep only features with wikidata or wikipedia tags (and mayb
7.
by packet_mover 9mo ago
Thank you, that's very helpful.
8.
by packet_mover 9mo ago
No. When I looked at Photon and saw that it involves running Java plus an OpenSearch/Elasticsearch backend on the device, I assumed it would be heavier in terms of memory and moving parts than my setup (single SQLite file + small HTTP
9.
by packet_mover 9mo ago
Yes - I do plan to sell Corviont, and it is worth explaining the licensing bit. It is built on open-source components and OSM-derived data, so the obligations are mostly (a) keeping third-party software licensing/attribution intact, an
10.
by packet_mover 9mo ago
I do not have published benchmarks yet (I want to collect a few real region packs first and then write this up properly). One goal of Corviont is to avoid the on-device pain you hit with OSRM/Nominatim: the region pack is built once el
11.
by packet_mover 9mo ago
Yeah, house-number lookup is not there yet. The demo geocoder does place/street-level search + reverse, but house numbers need a richer address index - it's on the roadmap. Re: a bbox "builder" repo - it's an intere
12.
by packet_mover 9mo ago
Thanks for chiming in - super helpful context. I am trying to learn from real deployments as I design Corviont's updater for edge boxes (bandwidth caps, maintenance windows, unreliable WAN, atomic swap + rollback). When you say transit
13.
by packet_mover 9mo ago
Photon is solid - but it comes with a very different operational profile than what I am aiming for. Photon is built on Elasticsearch (Java) - so it tends to mean a heavier index + higher RAM/CPU expectations and more moving parts. That
14.
by packet_mover 9mo ago
Thank you! And yes, Corviont is intentionally a stack of separable services behind one gateway - so "geocoder-only" is exactly the kind of config I want to support (skip PMTiles + Valhalla and ship only the SQLite index + reverse
15.
by packet_mover 9mo ago
Good question. Corviont is region-focused (you package one region), not "host the whole planet". Hundreds of GB is usually the full planet at high zoom / lots of layers. Also it’s not one giant tile DB - there are 3 datasets:
16.
by packet_mover 9mo ago
Nice - thanks for the pointer. Headway is definitely a related "self-hosted maps stack" project. One place Corviont is trying to differentiate is the update story for edge/fleet deployments: the goal is a signed, resumable re
17.
by packet_mover 9mo ago
Good point - house-number search isn't there yet in Corviont. Right now the offline geocoder in the demo does place/street-level search + reverse, but street + house number ("Main St 12") isn't supported yet. It&#x2
18.
by packet_mover 9mo ago
That’s a really interesting framing - you’re basically describing hierarchical routing / "zoom-level" graphs: do the long leg on a coarse network (highways), then refine locally as you get closer to origin/destination. F
19.
Show HN: Offline tiles and routing and geocoding in one Docker Compose stack(corviont.com)
102 points by packet_mover 9mo ago|38 comments
20.
by packet_mover 9mo ago
More context on the angle: this is server-style offline maps for fleets/edge. You drop it on a box and multiple clients on the LAN share the same tiles + routing + geocoding over HTTP (no proprietary SDK in every app). A key goal is co
21.
Show HN: Offline tiles and routing and geocoding in one Docker Compose stack(github.com)
2 points by packet_mover 9mo ago|1 comments