Skip to content

feat(schedule): retain static GTFS journey timing - #90

Merged
adot-7 merged 2 commits into
mainfrom
ao/metroshell-59/issue-76
Aug 13, 2026
Merged

feat(schedule): retain static GTFS journey timing#90
adot-7 merged 2 commits into
mainfrom
ao/metroshell-59/issue-76

Conversation

@adot-7

@adot-7 adot-7 commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Closes #76

Summary

  • retain validated GTFS stop times, service IDs, calendar rules, and optional exceptions
  • add deterministic Delhi-local scheduled journey timing on the existing BFS route, including explicit transfer compatibility/unavailable states
  • add compact SCHEDULED / NEXT SERVICE sidebar summary and expandable stop detail
  • document/test expired 2025-12-31 weekly calendar carry-forward as estimated scheduled demo data

Tests

  • gofmt -w ...
  • go test ./...
  • go vet ./...
  • go build ./...
  • git diff --check

No realtime or vehicle-position claims are made.

@adot-7
adot-7 merged commit 0984cbf into main Aug 13, 2026
1 check 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.

Phase 6: retain schedules and add journey timing

1 participant