Wiki: refresh stop-agency notes after #2128

Open Beginner friendly
#2,140 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
87/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Update stops-for-location.md, Multi-Agency-Static-Feeds-Stop-Consolidation.md §10, and search-stop.md to reflect the behavior after #2128 and the status of #1791. Start by checking the current statements against the issue details and the relevant change in #2128. Done means all three wiki statements accurately describe the index ordering and the closed, unmerged issue.

Written by the indexing model from the issue text.

Description

After #2128, GetAgenciesForStops reads the precomputed stop_agencies table. A few wiki statements are now stale:

  • stops-for-location.md says a stop's agency comes from stop_times → trips → routes → agencies via GetAgenciesForStops. The behavior is the same, but it now reads the index.
  • Multi-Agency-Static-Feeds-Stop-Consolidation.md §10 calls the first GetAgenciesForStops row "unordered". It is ordered by stop_id, then agency_id.
  • search-stop.md still calls #1791 "not yet merged". It was closed without merging.
Dominant language
Go
Stars
57
Forks
113
Avg merge
5d 10h
Merged PRs (30d)
151

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OneBusAway/maglev

All issues in OneBusAway/maglev

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.