NYC Live now reaches farther across the Hudson, with a New Jersey departure explorer and a clearer view of the transit already on the map.

Web — 0.2.0

  • New Jersey explorer: choose Hudson–Bergen Light Rail or NY Waterway, select a boarding stop or landing, and see the next published departures. Later service days show their date.
  • NY Waterway: see reported ferry positions alongside routes and landings around the Hudson waterfront. Selected boats show their next landing when that information is available.
  • More geographic context: streets and land coverage extend through Jersey City, Hoboken, Weehawken and nearby areas, including PATH coverage toward Newark and Harrison.
  • Clearer trains: PATH, LIRR and Metro-North use rounded, route-colored corridors. Coincident variants share a line, neighboring colors run in parallel, and train markers show their service name.
  • Clearer buses: MTA buses use blue capsule markers with white route numbers. Thin route lines follow street geometry more closely, stops have visible outlines, and small route names sit alongside the line.
  • Less clutter: the Citi Bike count disappears when its layer is off. A deliberate saved bike preference is preserved.

HBLR departures are scheduled times, without live delay information. NJ Transit bus and commuter-rail modes remain hidden while provider access is awaiting approval. PATH and MTA transit continue using their independent sources. Train positions are estimates; bus and ferry positions are reported by their providers.

Open the live map to explore.

API — v1

  • Added a separate NY Waterway feed at /api/v1/feeds/waterway, with provider-scoped vessel identifiers and independent freshness information for next-landing predictions.
  • Added published regional departures at /api/v1/nj/departures, including service calendars, exceptions, departures after midnight and explicit timetable validity.
  • Strengthened ferry freshness checks so unavailable or stale predictions do not replace valid reported vessel positions.
  • Prepared NJ Transit live endpoints behind a disabled release gate. They return an explicit unavailable response while access is pending; they do not collect live data or expose retained positions.

The API remains on /api/v1; this release adds resources without changing the existing feed-envelope version.