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.MONfor Montauk,HUDfor Hudson) pulled fromstatic/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/
Metadata
Release files for yamtam 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| yamtam-0.3.2.tar.gz | 10.7 kB | Without provenance | Details for yamtam-0.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| yamtam-0.3.2-py3-none-any.whl | Python 3 | none | any | Details for yamtam-0.3.2-py3-none-any.whl |
Total release size: 20.8 kB
Release files / yamtam-0.3.2.tar.gz
| Download URL | yamtam-0.3.2.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f31112aa6915bde0902dc7b2f50033814f41ed99d616579da098de28ffd3d0e
|
|
BLAKE2b-256 checksum How to use checksums |
555f9de99e8d4933743d7350a3b03c060b16dd3fb9177c1a2093ac98d819b318
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.13
|
Release files / yamtam-0.3.2-py3-none-any.whl
| Download URL | yamtam-0.3.2-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc8eeb027888186e528e958b4012f51ec51c7f030c6d3387d192e2e304cda8ba
|
|
BLAKE2b-256 checksum How to use checksums |
8174174de2bd3253052ad64b41ed800038a9b9602017b16f7382e5a3ff7ea24a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.13
|
Security for yamtam 0.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.