Skip to content

docs(prd): plan route check for pre-defined routes (M2-F36) - #123

Merged
RSid merged 1 commit into
mainfrom
docs/m2-f36-route-check
Oct 8, 2026
Merged

RSid merged 1 commit into
mainfrom
docs/m2-f36-route-check

Conversation

@RSid

@RSid RSid commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Summary

Plans a route check feature: a separate /check page where organizers (e.g. walking-tour leads) tap out a route they've already chosen and see the obstacles and aids along it, then share a read-only annotated link with participants. Docs only; no code changes.

  • PRD: new Flow E (§5.5) and tickets M2-F36 – M2-F40, plus permissible extensions (forking shared routes, GPX import, freehand tracing) with no IDs yet.
  • Decisions log: DEC-029 (approved by owner) — separate page, tap-to-place points snapped with a walking profile, resolved geometry carried in share URLs, and the openrouteservice TOS review.
  • Opens OQ-14 (share-URL length) and OQ-15 (validate tap-to-place with 2–3 organizers).

Tickets closed

  • None closed. Adds M2-F36, M2-F37, M2-F38, M2-F39, M2-F40; opens OQ-14, OQ-15.

Decisions touched

  • DEC-029 (new). References DEC-003, DEC-010, DEC-020; none reversed.

Third-party TOS review

Read the HeiGIT / openrouteservice terms of service and API restrictions on 2026-10-07. Full notes are in DEC-029. Key points:

  • Interactive use is allowed; overburdening is not. Repeatedly exceeding quotas can get the account blocked or removed without notice. Standard plan: 2,000 directions/day, 40/minute (taken from the account site's published plan config, which is JS-rendered — confirm in the dashboard before launch).
  • All Scout users share one ORS account, and today's limit on /api/route is per-IP (30/min). Two or three organizers tapping at once could exceed 40/min. M2-F37 (process-wide ORS budget) is a prerequisite for M2-F38.
  • Max 50 waypoints per request → /check caps routes at 50 points.
  • Results are CC-BY-SA 4.0 with required attribution; the shared view (M2-F40) shows "© openrouteservice by HeiGIT | Data from OpenStreetMap" next to the route.
  • No personal data may be sent to the API; route checks send only coordinates and a profile.
  • Terms change on posting; DEC-029 calls for a re-read before M2-F38 ships.

Tests added or changed

  • None (docs only). Pre-commit hooks pass.

Mocks introduced

  • None.

Screenshots

  • N/A (docs only).

Out of scope

  • Implementing any of M2-F36 – M2-F40.
  • The planner's map attribution, which credits ORS only on /about. The terms allow attribution "elsewhere"; not changed here.
  • The existing ID overlap between M2-F24/M2-F25 and M3-F24/M3-F25; new tickets start at F36 to avoid it.

Author checklist

  • PR title uses Conventional Commits and cites the ticket id.
  • Unit tested and manually tested, including for accessibility — N/A, docs only.
  • New dependency? None.
  • Data-schema change? None.
  • Closed an OQ-NN? None closed; OQ-14 and OQ-15 opened.

🤖 Generated with Claude Code

Add Flow E and tickets M2-F36..M2-F40 for a separate /check page that
reports on organizer-chosen routes (walking tours), plus DEC-029 with
the openrouteservice TOS review. Open OQ-14 and OQ-15.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RSid
RSid marked this pull request as ready for review October 8, 2026 17:12
@RSid
RSid merged commit 3c8ca8c into main Oct 8, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant