Files
pikebacker/docs/10_integrations.md
2026-07-02 21:04:05 +02:00

1.5 KiB

Integrations

Routing integrations

Use provider adapters.

Prototype

  • openrouteservice API adapter.
  • Mock adapter for tests.

Production

  • GraphHopper or Valhalla self-hosted adapter.
  • Custom bikepacking profile layer on top of base routing.
  • Offline routing adapter later.

Map integrations

  • MapLibre-compatible rendering.
  • Vector tiles from OpenMapTiles, Protomaps/PMTiles, MapTiler, or self-hosted pipeline.
  • OSM attribution must be visible.

Accommodation integrations

MVP should use:

  • OSM campsites/shelters/huts/hostels/hotels,
  • deep links to search platforms,
  • manual entries/imports for partner datasets.

Later:

  • Booking.com Demand API if accepted as partner,
  • direct campsite/hut reservation systems,
  • Warmshowers-style partner/deep links if official access exists.

Weather integrations

MVP:

  • forecast at stage endpoints and exposed segments.
  • warnings for heat, rain, wind, storms, freezing nights.

Later:

  • route-time weather simulation,
  • weather-aware rerouting,
  • mud risk after rainfall.

Device integrations

MVP:

  • GPX export.

Next:

  • TCX export with course points.
  • FIT export.

Later:

  • Garmin Courses API subject to approval.
  • Wahoo Cloud API subject to approval and use-case fit.
  • Hammerhead/Karoo sync if public/partner APIs allow.

Authentication and partnerships

Do not assume public access to commercial APIs. Use deep links first and provider interfaces so partner integrations can be added without changing the domain model.