Table of Contents

Community and Local Intelligence

Objective
Report types
Report payload example
Trust model
Expiry model
Moderation
OSM feedback loop

Mirrored from /mnt/DATA/git/pikebacker/docs/12_community_intel.md. Origin: repository. Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.

Community and Local Intelligence

Objective

Turn field reports into a structured, trust-scored, time-aware route quality layer.

Report types

water_available
water_unavailable
surface_wrong
rough_loaded_bike
hike_a_bike
locked_gate
private_access
closure
dangerous_dogs
mud_sand_washout
bridge_out
ferry_issue
sleep_option_good
sleep_option_bad
shop_closed_or_missing
repair_available
reroute_recommended

Report payload example

{
  "type": "water_unavailable",
  "location": { "lat": 47.1234, "lon": 11.5678 },
  "route_id": "route_123",
  "meters_from_start": 84231,
  "observed_at": "2026-06-30T14:30:00Z",
  "details": "Tap locked; no public access after 18:00.",
  "photo_optional": true
}

Trust model

Signals:

account age,
number of confirmed reports,
local status,
photo/GPS evidence,
agreement with other riders,
recency,
conflict count.

Expiry model

Reports should not live forever.

Default expiration:

water status: 60 days,
closures: 30 days,
mud/surface condition: 30 days,
locked gate: 90 days,
shop status: 90 days,
legal/access reports: manual review,
local hints: 180 days.

Moderation

Moderate:

illegal camping instructions,
private property entry hints,
sensitive locations,
abuse/harassment,
unsafe advice,
business defamation.

OSM feedback loop

Objective, verifiable corrections can be contributed back to OSM by trained editors following OSM community norms. Subjective suitability, safety, and camping hints should remain in the app layer unless they map to accepted OSM tags and are verifiable.