ETA
--:--
Service status
Velo is under maintenance
The service is temporarily unavailable while the database platform is being upgraded.
The service is temporarily unavailable while the database platform is being upgraded.
Scenic park access: green = rideable, amber = push/separate facility, red = bicycle blocked. It requires a Scenic graph built with v284 or later.
Selected route objectives are shown together on the map. At least one must remain enabled.
Suggestions appear automatically within the effective radius when a current position is available. Press Enter to run the typed search without the distance limit.
Use your current position to load the forecast.
Not loaded · Weather via Velo
The browser talks only to Velo. Upstream providers, caches and regional policy are server-owned.
Velo advertises capabilities through GET /api/v1/capabilities and product regions through GET /api/v1/regions. Routing, search, elevation, weather, sights and regional overlays stay behind Velo-owned /api/v1/ endpoints.
Regional elevation provenance is returned by Velo. Velo prefers an active self-hosted normalized regional DEM; the previous server-side regional provider remains a temporary fallback until a verified local generation is active.
No regional offline package is stored on this device.
| Region | Status | Routing | Search | Weather | Sights | Elevation | Official routes | Junctions / closures | Transport |
|---|
This table is generated from GET /api/v1/regions and the Velo capability catalogue. Only product regions advertised by the server are shown; browser-side provider fallbacks and country allow-lists are not used.
Check whether a newer Velo deployment is available.
Installing an application update or clearing the application cache does not delete locally stored bikes, destinations, routes, rides, or settings.
If Safari or an installed Home Screen app still shows an older build, clear the application cache here. Velo removes only cached application files and map tiles, then reloads from the server.
Search or tap the map to choose a destination. With a destination set, each further tap extends the route: the previous finish becomes a stop and the tapped point becomes the new finish. Choosing a search result or saved destination replaces the finish instead. Double-click the blue route to add a waypoint mid-route, or press and drag the route and release where the waypoint should go. Tap a waypoint to remove it. Tap the finish pin to remove it; the last stop becomes the finish again.
Library, Plan, and Ride share the same header, with the compass at the top right. Settings is always above the compact zoom controls, followed by the map-focus control, in a vertically centred left rail. In Ride, the compact 2D/3D, speaker, and follow controls use a matching centred rail on the right. The location control cycles between a free map, position follow, and heading-up follow. Follow mode keeps the rider fixed low in the usable map viewport while the map moves beneath it. Heading-up uses physical device orientation in Library, Plan and Ride; GPS course remains a separate motion signal. Dragging the Ride map disengages position follow. The same route-context header is used in Library, Plan and Ride. Its elevation trace shows route-distance progress and ETA-aware weather icons; Ride switches that trace to a moving rider-anchored window while Library and Plan show the route preview. Library, Plan, and Ride also keep a compact lower mode header above the mode dock; Library and Plan use it as the workspace handle, while Ride keeps it as a compact route-status header. Pressing the already-active Plan tab toggles the Plan workspace open or closed. The map-focus control hides the lower workspace/header and mode dock without losing the selected view or Library subtab.
Saved rides, recent rides, bikes and destinations live under Library and are stored locally in this browser. Clearing site data removes them unless you export important rides or routes first.
Import and export planned routes under Library → Saved rides. Export or finish the active ride under Library → Recent rides, and use the per-item export controls in either ride list.
Official route, closure, transport and cycling-POI layers are selected from the active Velo product region and loaded through Velo. Under Navigation, the sights layer can be filtered by category and distance from the route.
The public client does not contact map or data providers directly. Velo owns provider selection, caching, regional capability policy and normalized API responses.
The application shell works offline after installation. Previously viewed or explicitly cached Velo map tiles remain available. A regional offline package can retain route overlays, closures, cycling POIs and transport stops for the current Velo region. Routing and live server updates still require a connection unless a dedicated offline-routing package is installed by a native client.