How far can you get in 40 minutes from each subway station in NYC?

Original Article ↗ Hacker News Discussion ↗

Model & Accuracy Concerns

  • Map is an isochrone visualization; assumes instant transfers, no wait time, and uniform service, especially around midday on weekdays.
  • Walking speed is fixed (1.2 m/s) after the subway trip; unclear if station access time or traffic signals are included.
  • Several users report that real-world trips (esp. with transfers or off-peak) are 20–30% slower, especially in Queens and for cross-borough routes.
  • Edge inconsistencies and “local vs express” nuances sometimes aren’t reflected (e.g., similar reach for express-interchange stations vs locals; odd symmetric/asymmetric reach between endpoints).
  • Some users treat it as visually compelling but not suitable for precise trip planning without “ground truth” validation.

Transit Frequency, Maintenance, and Funding

  • Criticism that the model ignores headways; actual subway waits and transfer times can dominate door-to-door time.
  • Discussion of poor maintenance track record, recurring weekend outages (e.g., 7 train), and deferred maintenance driven by long-term underfunding.
  • Political decisions, budget cuts, and last‑minute project changes are blamed for operational/maintenance problems and slower trains.

Cars vs. Transit & User Experience

  • One view: if transit isn’t at ~5-minute headways, many riders will choose cars; outside dense cores, transit is seen as tedious.
  • Counterpoints: in dense cities (e.g., Budapest) high-frequency transit beats car ownership on cost, convenience, and stress.
  • In NYC specifically, car travel faces congestion and parking delays; subways allow productive time vs. “passive” driving.

Density, Land Use, and Where Subways Make Sense

  • Debate over “every 500k city should have a subway” vs. “only high-density cities justify the cost.”
  • Arguments that subways should be built early to induce density, paired with zoning and transit-oriented development.
  • Discussion of land value capture (Henry George ideas, Tax Increment Financing, “rail plus property” models in Tokyo/Hong Kong/Switzerland).

Alternative Modes & Other Systems

  • Many suggest that well-designed trams/BRT with dedicated lanes or busways (e.g., Mexico City BRT, Adelaide O‑Bahn, Lincoln Tunnel XBL) provide strong cost–benefit.
  • Others emphasize that subways vastly outperform trams in capacity and speed, especially at rush hour.

New Jersey, Airports, and Regional Connectivity

  • Critique that the visualization omits PATH, LIRR, Metro-North, NJ Transit, making reach look worse than full regional rail would.
  • Complaints about weak NJ coverage versus Queens/Brooklyn, though some note that multiple NJ services exist, just under different agencies.
  • JFK and Newark are perceived as poorly integrated compared to European “airport express” models; workarounds (LIRR to Jamaica, etc.) are mentioned.

Tools, Prior Art, and Use Cases

  • Links to the project’s open-source code, Mapbox’s isochrone API, an older TripTropNYC tool, and an open-source router from a previous urban-tech project.
  • Some relate the map to travel-time-based housing search (“Zillow by commute time”) and to games (e.g., Jet Lag: The Game, transit “speedruns”).

Bugs, Oddities, and Miscellaneous

  • Reports of specific UI bugs (e.g., Howard Beach/Broad Channel not updating).
  • Observations that much of Queens is 40+ minutes from most of Brooklyn, reinforcing calls for new cross‑borough projects like the Interborough Express.
  • Mixed reactions: many find the visualization “mesmerizing” and enlightening about subway reach; others focus on its optimistic assumptions and missing modes.