Reitti v5.3.1 Brings Custom Maps, Multi-Segment Trips, and H3 Spatial Coverage: Worth Updating?

Reitti just pushed v5.3.1, and it’s one of those updates that hits every type of user differently. Custom map styles are here, multi-segment trips should please power users, and they’ve added H3 spatial indexing support if you know what that is (or even why you’d care). Opinions are flying fast on r/selfhosted, so let’s break this down.

Custom Map Styles: A Niche Win or Total Rabbit Hole? #

This was the most hyped feature in the changelog, and for good reason. The idea is you can now throw in your own Mapbox or CartoCSS styles, making the maps look exactly how you want them. Do you need this? Probably not unless you’re running something very aesthetics-focused like a travel app or a logistics dashboard. One user, u/mr_potato_sass, pointed out that it’s a “nice-to-have that quickly turns into overkill.” They did a basic light mode → dark mode map switch in under 30 minutes but admitted tweaking custom layers was “a productivity black hole.” Fair point. If you care about visual consistency (or have design-driven friends nagging you), this will make you happy. Otherwise, stock styles were already pretty good. You can also download and self-host styles directly, which keeps costs low if you’re farming free tier APIs too hard. Small detail, big deal. MangoMap and QGIS still beat it in specialized setups, but for lightweight self-hosted map tools, Reitti’s looking more pro by the update.

Multi-Segment Trips: Finally #

Let’s talk routing. Reitti 5.3.1 now officially supports multi-segment trips, meaning you’re no longer limited to A→B. It’s A→B→C→Z for routing junkies. This should help any use case involving delivery routes, tourist planning, or worst-case… pub crawls. (u/okbutwhy joked: “Can’t believe I waited years to plot a bar-hopping journey this advanced.”) Testing this feels smooth as long as you’ve got decently up-to-date data sources. u/selfhostingDude87 mentioned slight hiccups with outdated OSM files. So yeah, if you’re running this to the ground with 2019’s map data, expect some weird paths. Otherwise, this looks bulletproof. Multi-stop routing alone puts it ahead of lightweight options like OwnTracks, though it still can’t match SaaS tooling like Google Maps for algorithm finesse. Also worth noting: Reitti still runs a relatively lean stack. On a VPS with 2GB RAM and minimal swap, multi-segment routing clocked in fine. Try run that on a Pi though, and your experience might hinge on patience and coffee.

H3 Spatial Coverage: Do You Even Hex, Bro? #

Okay, so H3 spatial indexing. Some people just skipped this in the changelog entirely because H3 doesn’t sound flashy, but I promise you: this is nerd-crack if you know why it matters. H3 adds another layer of precision for things like coverage maps, grid-based visualizations, or spatial clustering. If you’re eyeballing data-heavy use cases (think fleet tracking, utilities), this opens new doors. u/neomatric shared a slick example: heatmaps of EV charging stations using H3 + Reitti’s new spatial APIs. Full nerd mode activated. Is this overkill for basic trip planning or directions? For sure. But this is why we self-host in the first place—tools that overdeliver even if 95% of us will never bother. Oh, and here’s a nice quirk: because Reitti 5.x introduced proper API tokens, you can now hook H3 spatial queries into a ton of analytics setups. Want to funnel trip stats into Grafana or plot heat zones in Tableau? Done. Just keep in mind, actual battery impact and compute loads scale hard once you go full-map-madness.

Should You Update? #

If you’re already running Reitti, yeah, update. It’s not often a point release feels like a feature drop, but v5.3.1 has enough here to justify a go. Even if you ignore the H3 stuff entirely (I won’t judge), multi-segment trips and map customization might make your setup feel less vanilla. Running old hardware or scared of breaking your install? The community reported no major regressions so far. A few ARM folks (u/armneverdies) shared that Pi builds are sluggish with multi-stop routing, though, so consider offloading medium/large projects to a beefier VPS if you value performance. New install? Reitti’s time-to-setup isn’t bad, hovering at 10-15 minutes unless you detest fiddling with Docker Compose. Dependencies aren’t nightmarish either—just remember recent Python versions are non-negotiable because 5.2+ depends on some modern packages.

Final Thoughts #

Reitti v5.3.1 is solid. While most self-hosted users won’t need H3 or multi-segment routing daily, these updates turn it into a more competitive, flexible mapping platform even if you’re doing niche setups. Just don’t spend too much time perfecting map styles unless you have infinite hours to burn.

FAQ #

What is H3 Spatial Indexing? #

H3 is an open indexing system by Uber that divides space into hexagonal grids instead of squares. It’s used for mapping data like population density, fleet coverage, etc. Better precision, but overkill for basic directions.

Does Reitti work on a Raspberry Pi? #

Yes, but performance varies. Multi-segment trips, in particular, might slow things to a crawl without adequate resources. For best results, consider a 4GB+ Pi or using a cloud VPS option like Hetzner/DO.

How does Reitti compare to OwnTracks or OtServer? #

Reitti is better for routing and visualization-heavy use cases. OwnTracks stays lightweight and excels at location reporting, while OtServer doesn’t get close on map/routing complexity. Pick based on what you most need.