Why Our Mile-Point App Feels Instant-Response (Even Offline)
Why Our Mile-Point App Feels Instant-Response (Even Offline)
We bundle the roads as one lightweight file. The first time you install the app it downloads a single MBTiles package (think of it like an offline map). It’s about the size of a podcast episode, so it works fine on spotty rural Wi-Fi.
Tiles are pre-cut at zoom-14. Each 4096 × 4096 pixel “tile” already matches the road network at roughly 1:16 k scale—perfect for field work.
A tiny Go web-server lives inside the app. Instead of calling an internet API, the app spins up a micro-server (written in Go) on your phone. That server answers all “Where am I on the route?” questions.
On-demand smart indexing. When you pan into a brand-new tile, the server reads that tile once, slices the road bits into super-small 15-foot squares, and remembers the result. It never does that work again for the same area.
4-millisecond look-ups. Taps, GPS pings, or asset locations hit the local server, which snaps the point to the nearest road segment and returns its mile-point in about 0.004 seconds—fast enough that users never feel a delay.
Works where cell service doesn’t. Because everything lives on the device—map, index, and engine—crews keep working in tunnels, mountains, or post-storm zones.
Bottom line: We moved the heavy GIS math out of the cloud and into your pocket, and you still get battery-friendly, sub-second results everywhere you drive.
