You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the May 21 methodology sync decision and reaffirmed at the May 28 SEPTA check-in, we're setting up an in-team SEPTA OTP test environment so TransitOPS / Jarvus can validate pathways data the way Noah does before changes reach his QA pipeline. This unblocks parallel validation on lat/lon refinement and potentially supports the companion app development workstream over the next three weeks.
Use scope (from Noah): "These are for use only for purposes related to the current GTFS-Pathways task order. They are not to be shared outside Jarvus / TransitOps."
Use cases
Lat/lon refinement validation (near-term)
Replicate Noah's color-coded-by-level lat/lon visualization (per the May 21 walkthrough) so we can validate the 3-point minimum alignment approach before delivering refined coordinates for Olney and the other published stations in the next GTFS publication window. SEPTA's next GTFS publication is June 28 (no changes during FIFA per Noah at the May 28 check-in), so there's runway to refine before that.
Companion app integration (in scoping)
Per the May 28 SEPTA check-in, Noah accepted a budget-neutral calendar extension on Task Order 1 through Friday June 19 for companion app iteration + in-station user testing. There's potential to incorporate OTP validation into the companion app workflow during this stretch — worth scoping early to know whether it fits the three-week timeline.
Hours allocation
Per Christopher's framing at the May 28 check-in: this falls under Ryan's remaining hours on the task order. Coordinate with Christopher on prioritization between the lat/lon refinement validation and any companion-app-integration scoping.
References
May 21 SEPTA check-in: meetings/20260521_weekly_checkin.md
May 28 SEPTA check-in: meetings/20260528_weekly_checkin.md
Background
Per the May 21 methodology sync decision and reaffirmed at the May 28 SEPTA check-in, we're setting up an in-team SEPTA OTP test environment so TransitOPS / Jarvus can validate pathways data the way Noah does before changes reach his QA pipeline. This unblocks parallel validation on lat/lon refinement and potentially supports the companion app development workstream over the next three weeks.
OTP configs from Noah (sent May 28)
Use scope (from Noah): "These are for use only for purposes related to the current GTFS-Pathways task order. They are not to be shared outside Jarvus / TransitOps."
Use cases
Lat/lon refinement validation (near-term)
Replicate Noah's color-coded-by-level lat/lon visualization (per the May 21 walkthrough) so we can validate the 3-point minimum alignment approach before delivering refined coordinates for Olney and the other published stations in the next GTFS publication window. SEPTA's next GTFS publication is June 28 (no changes during FIFA per Noah at the May 28 check-in), so there's runway to refine before that.
Companion app integration (in scoping)
Per the May 28 SEPTA check-in, Noah accepted a budget-neutral calendar extension on Task Order 1 through Friday June 19 for companion app iteration + in-station user testing. There's potential to incorporate OTP validation into the companion app workflow during this stretch — worth scoping early to know whether it fits the three-week timeline.
Hours allocation
Per Christopher's framing at the May 28 check-in: this falls under Ryan's remaining hours on the task order. Coordinate with Christopher on prioritization between the lat/lon refinement validation and any companion-app-integration scoping.
References
meetings/20260521_weekly_checkin.mdmeetings/20260528_weekly_checkin.md