Skip to content

History / vehicles for agency

Revisions

  • docs: record trip-less vehicle inclusion (Extension 5a) as not implemented Maglev drops trip-less vehicles from vehicles-for-agency entirely rather than including them with tripId/tripStatus absent. An attempted fix (#1129) surfaced unresolved problems with ingestion-time filtering, multi-agency feed attribution, and query-time feed access, so the gap was closed as won't-fix (#1128). Records the decision and outlines the ingestion-time approach that would be needed if revisited.

    @burma-shave burma-shave committed Jul 10, 2026
    6cbefce

  • docs: record lastUpdateTime/lastLocationUpdateTime emit 0 in Maglev The legacy Java implementation omitted these fields from TripStatus responses when no real-time update had been received. Maglev emits 0 instead, using the shared TripStatus struct across all endpoints to avoid per-endpoint omission complexity. Add Implementation Decisions entries to trip-details, trip-for-vehicle, and vehicles-for-agency documenting the deviation. Cross-reference from each field description that specifies legacy absent behaviour. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

    @burma-shave burma-shave committed Jul 2, 2026
    4b4f3be

  • docs: record outOfRange=true (Extension 4a) implementation decision for vehicles-for-agency Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

    @burma-shave burma-shave committed Jul 2, 2026
    536eff0

  • docs: record ageInSeconds=0 implementation decision for vehicles-for-agency Closed by PR OneBusAway/maglev#1108. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

    @burma-shave burma-shave committed Jul 1, 2026
    05730c4

  • Remove implementation opinions from API specs Specs describe legacy OBA behaviour only. Any opinion on what Maglev should do belongs exclusively in the Implementation Decisions section. Prescriptive sentences ("The Go implementation should...", "A clean Go reimplementation should...") have been removed or rephrased as tentative statements about what the original developer probably intended ("The intended behaviour was probably..."), so the defect context is preserved without preempting implementation decisions. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

    @burma-shave burma-shave committed May 28, 2026
    3be3a92

  • Update OBA API specs (2026-05-11T23:13:08Z)

    @burma-shave burma-shave committed May 11, 2026
    fe19578