Christopher Yamas

This PR refactors the Virginia committees scraper to bypass the frequent source errors that were occurring due to a confluence of how the page was structured and how spatula seeks...

📄🚀 – OTP/Delays Analysis Use Case Profile Development

6

## Overview The **On-Time Performance (OTP) and Delays Analysis** use case was identified as the _highest priority_ profile during the [April 2025 Contributors Group meeting](https://docs.google.com/document/d/1CxJhfJyaLrF9UbuuEgX6BWJtO5uwSIG3YrBXt4s_5mQ/edit?tab=t.0#heading=h.mrzjki33no6y), receiving 9 votes. This profile...

🚀💻 – Passenger Counts at Fare Gates Without Fare Transactions

3

WMATA operates in situations where fare gates are opened in "free mode" without requiring fare taps, resulting in passenger count records that are not linked to fare transactions. While the...

📄🚀 – Modify passenger_events table to accommodate fare gate and station-based events

1

## Issue Summary This proposal addresses a gap in the TIDES specification with regard to handling fare gate events and other station-based passenger movements that are not directly associated with...

📄🚀 – Add device_status table for tracking device maintenance and availability

2

## Issue Summary This proposal suggests creating a new `device_status` table to track device maintenance activities, offline periods, and operational status changes. This emerged as [one of the related recommendations](https://docs.google.com/document/d/1O_rrVLWta3zX_rVd3dCDt9dxmrseyx57H-5LGE8Yd2w/edit?tab=t.0#bookmark=id.3cjogc912sba)...

🐛📄 – Rename 'duration' fields in stop_visits for clarity

1

## Problem Description In the TIDES `stop_visits` table, several fields representing durations use the suffix `_time` instead of a more appropriate suffix like `_duration` or `_seconds`. This inconsistent naming creates...

🐛📄 – Clarify event_count usage in passenger_events

2

## Problem Description The TIDES spec does not formally document whether `event_count` in the `passenger_events` table is only expected for certain event types (e.g., "Passenger boarded" or "Passenger alighted"). This...

🐛📄 – Improve event_type naming convention in passenger_events

1

## Problem Description The current TIDES spec uses event types as strings with spaces (e.g., "Passenger boarded") in the `passenger_events` table. This naming convention creates practical challenges when working with...

🐛📄 – Resolving Conflict between Multiple Operators + Primary Key in trips_performed

2

## The Problem: Conflict between TCRP recommendation and TIDES spec There is a contradiction between the TCRP paper guidance and the TIDES specification regarding how to handle multiple operators for...