Page:
Repo-docs-06-offline-strategy
Pages
Codex-Project-Index
Repo-LICENSE-NOT-SELECTED
Repo-README
Repo-codex-BACKLOG
Repo-codex-CODEX-MASTER-PROMPT
Repo-codex-IMPLEMENTATION-TASKS
Repo-docs-00-executive-summary
Repo-docs-01-product-requirements
Repo-docs-02-mvp-scope
Repo-docs-03-system-architecture
Repo-docs-04-data-sources
Repo-docs-05-routing-and-scoring
Repo-docs-06-offline-strategy
Repo-docs-07-ux-flows
Repo-docs-08-data-model
Repo-docs-09-api-contract
Repo-docs-10-integrations
Repo-docs-11-local-rules-and-liability
Repo-docs-12-community-intel
Repo-docs-13-security-privacy
Repo-docs-14-testing-plan
Repo-docs-15-roadmap
Repo-docs-source-references
Repo-examples-sample-stage-plan
Clone
1
Repo-docs-06-offline-strategy
zemion edited this page 2026-07-06 14:42:16 +02:00
Mirrored from
/mnt/DATA/git/pikebacker/docs/06_offline_strategy.md. Origin:repository. Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.
Offline Strategy
Offline requirement
Offline use must cover riding-critical information, not only maps.
Offline pack contents
A trip offline pack should include:
- route geometry,
- route alternatives,
- daily stages,
- elevation profile,
- selected vector/raster map area,
- route-corridor POIs,
- emergency/bailout POIs,
- local rule cards,
- cached weather forecast at departure,
- saved bookings/deep links/addresses,
- user notes,
- GPX/TCX/FIT exports,
- report queue for later upload.
Pack scope
Use a corridor-based pack:
primary corridor: 5 km on either side of route
logistics corridor: 20 km around stage endpoints and bailout towns
map context: bounding box with simplification by zoom level
Offline modes
MVP offline mode
- Download planned route, POIs, stage plan, rules, and GPX.
- Allow map viewing if tile pack is present.
- Allow report capture and sync later.
- Allow basic distance-to-next-critical-thing calculation from cached data.
Production offline mode
- Offline rerouting using a compact regional routing graph.
- Offline POI search.
- Offline rule lookup.
- Offline elevation sampling.
- Offline exports.
Storage model
Mobile app storage:
- SQLite for structured trip data and POIs.
- File storage for tile packs and exports.
- Key-value storage for user preferences and sync state.
Pack versioning
Each offline pack should include:
{
"pack_id": "pack_123",
"trip_id": "trip_123",
"created_at": "2026-06-30T00:00:00Z",
"data_versions": {
"osm_extract": "geofabrik-europe-germany-2026-06-29",
"poi_index": "2026-06-29",
"rules": "2026-06-01",
"weather_cached_at": "2026-06-30T06:00:00Z"
},
"bbox": [6.0, 47.0, 15.0, 55.0],
"route_buffer_km": 5,
"expires_at": "2026-07-14T00:00:00Z"
}
User-facing warnings
Before departure, show:
- which items are available offline,
- which items are stale,
- which route sections lack cached POIs,
- whether offline rerouting is available,
- which exports are saved.