yamtam cli

CLI to access real-time NYC metro-area transit data from yamtam.nyc.

Reads the cadence-separated data files yamtam.nyc publishes (realtime trips and static stops per system, plus the shared route-color map) and prints arrivals for the stations you care about.

usage: yamtam.py [-h] [--rt RT] [--stop STOP] [--system SYSTEM]

options:
  -h, --help       show this help message and exit
  --rt RT          Repeated optional routes (e.g. E, F, 7, LIRR1, MNR1)
  --stop STOP      Repeated optional stops (station name or GTFS id)
  --system SYSTEM  Repeated optional systems (subway, lirr, mnr, ferry, bus)

Examples

Show next arrivals at Court Sq-23 St on the subway:

yamtam --stop "Court Sq" --system subway

Show only the E and F at a station:

yamtam --stop "Court Sq-23 St" --rt E --rt F

Behavior

• Systems: subway, lirr, mnr, ferry, bus. Defaults to all.
• Express merge: express trains (FX, 7X, 6X) are folded into their local route (F, 7, 6) so one destination shows one combined row.
• Direction ordering: southbound groups are listed first, then northbound.
• Headings: subway arrivals are grouped by destination borough (e.g. Southbound (Brooklyn-bound)); LIRR westbound notes whether the train terminates at Penn Station or Grand Central.
• Route badges: subway symbols are centered in a 5-char color bar (e.g. E ), while LIRR/MNR/bus codes start at the 2nd character. LIRR and Metro-North badges show the branch abbreviation (e.g. MON for Montauk, HUD for Hudson) pulled from static/routes.json, instead of the opaque numeric id (LIRR5 -> MON, MNR1 -> HUD).
• Colors: routes are tinted with their official hex color when the terminal supports 24-bit ANSI color.
• Caching: feeds are cached under /tmp/yamtam/ and refreshed only when stale (realtime every ~2 min, static stops/colors/routes daily).

Development

python3 -m pytest cli/yamtam/tests/
ruff format cli/yamtam/
ruff check cli/yamtam/