A path graph
The app routes on a real network of walking paths, not on a drawing. That's what makes real-time positioning and junction-by-junction guidance to the ride possible.
How it works
What runs behind the scenes of a park
Guiding someone around a park isn't just dropping a dot on an image. Behind every park there's real data work — and that's why we add them one at a time, not "every park in the world at once".
The pipeline
Four building blocks to make a park "work"
Each one needs clean data and a bit of hands-on work. Here's the gist, in plain terms.
OpenStreetMap data
The paths and the base map come from OpenStreetMap (vector, open) — no more proprietary illustrated plan. The same open foundation for every park.
Hand-editing
OpenStreetMap is sometimes incomplete or rough inside a park. So we clean the graph by hand: closing off exits out of the park, merging duplicate paths, handling temporary closures.
Multilingual matching
Wait times often arrive under the ride's local name, in the park's language. We reconcile them with the displayed name so everything lines up, with no duplicates or gaps.
The tools
Adding a park is open
All this data work is done with two open web tools. Anyone can explore them; submissions are by invitation.
Park onboarding wizard
Add or correct a park end to end: identity, bounding box, attractions. The wizard prepares the contribution to submit.
Free to explore — submission by invitation
Open the wizardGraph editor
Refine a park's walking-path graph on a satellite view: draw, fix and connect the paths, then submit your changes.
Free to explore — submission by invitation
Open the editorWhy one at a time
One park at a time, but a park that really works
Since each park needs this hand-verified data work, we can't ship them all at once. We add parks step by step, and quality comes before quantity. Multi-park mode is here — the next parks follow, one by one.
← Back to home