New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add NYC's MTA transit network. #90
Comments
Thanks. I have a question regarding the GTFS data
In addition there are the also the following
Thanks |
Another Question regarding the search area
|
Which 'network' values are valid?
aren't used at all. What I see also as 'network' https://ptna.openstreetmap.de/results/US/NY/US-NY-MTA-Analysis.html#networkdetails
They are not considered as relevant at the moment, I can add them though |
It looks like they are also city bus routes. Looking at wikipedia article for one of the lines there https://en.wikipedia.org/wiki/Q72_(New_York_City_bus) it says:
I guess it's quirk of when MTA acquired/merged with some of the other smaller local bus operators.
For customers all these are just regular city buses with the usual branding, look and fare system.
transit.land site shows no routes associated with this, but when I downloaded http://web.mta.info/developers/files/google_transit_supplemented.zip that's linked there, I do see
They are operated by MTA.
NYC DOT, not MTA, operates the Staten Island Ferry, providing free service between Staten Island and Lower Manhattan every day of the week, year-round.
SI Ferry is not really part of "MTA" network. |
My original request was specifically for NYC proper. But if you want to expand MTA's coverage, I'm not against it 😉
NYC ;)
MTA operates LIRR (Long Island Rail Road) which runs to the very eastern tip of LI, which consist of Suffolk and Nassau counties
Depends what they consider "southerneastern". 😄
MTA also operates Metro-North Railroad which has lines to/from Connecticut's Fairfield and New Haven counties. This map shows all their commuter railroad lines https://new.mta.info/map/22461 MTA also works closely with Port Authority of NY/NJ (which operates PATH subway/lightrail lines |
I suggest keeping the search area to NYC and see what might be missing after having sorted all the stuff. I see 'network' = 'LIRR' in the analysis report, so the current search might find many of the extra lines I will extend the list of accepted 'network' values by
and we'll see the outcome. |
I'd say maybe
Hopefully we'll be fixing it all soon enough 😅
I think all/most of these are coming from NSI.
https://nsi.guide/index.html?t=transit&k=route&v=subway&tt=nyc#nycsubway-8c396c
I believe this comes from https://nsi.guide/index.html?t=transit&k=highway&v=bus_stop&tt=mta#nyctransit-b4d0c3
This probably comes from https://nsi.guide/index.html?t=transit&k=route&v=ferry&tt=staten#statenislandferry-732c9d
https://nsi.guide/index.html?t=transit&k=route&v=subway&tt=staten#statenislandrailway-8c396c Hopefully we'll get around to normalizing it all.😵 |
Started sorting the lines in the OSM-Wiki Analysis runs a 3rd time now |
Is it OK for GTFS to start with
|
why wouldn't it be? |
I wasn't clear on how to name them.
Should that be reflected in the name of the feed? BTW: f-dr5r-nyctsubway and f-dr5r-mtanewyorkcitytransit are identical, so we're fine with the 7 GTFS feeds above (I hope) |
To the riders it all looks like the same company and service, so I don't think we should bother trying to document their internal corporate structure in OSM tags. A common system-wide name is fine. Regarding subway feeds, |
Released |
Yep, except if this makes a difference in 'operator' values
Oops, I did check routes.txt and trips.txt and they are identical. I did not check shape.txt though. Would be beneficial to present the shapes also. |
I've been thinking about the value of Similarly, for the buses shouldn't it be different from the value of I'm not quiet clear on all the semantics and implications if these tags change... And I'm thinking that a similar change needs to happen to https://github.com/osmlab/name-suggestion-index/blob/main/data/transit/route/bus.json#L10440 and https://github.com/osmlab/name-suggestion-index/blob/main/data/transit/route/subway.json#L332, |
Yeah, right! There is no clear understanding OSM-world-wide either. I see 'network' as the authority which organizes the PT in the area, is partly funded/subsidized by government (on lower level: county) to have reasonable fares, defines tariff zones, (transfer) rules, ... and - now coming to the 'operator' section - publishes "public invitation to bid" for operating a specific bus/subway/... route for the next 3-5 years with a requested SLA. 'operator' can participate in this bid and hope to get the contract, then buy buses/..., hire drivers, ... hoping to operator the route with a financial revenue. That's simply spoken; how it works here in Munich, DE and will definitely not apply world-wide. So, f.m.p.o.v. it's a task for the local mappers to define the semantics. A possible mapping is "agency" of GTFS to 'operator' in OSM. |
I noticed an issue with some of the subway lines. They are the same thing. The trains have "diamond" symbol on their displays and MTA calls them "express" lines. I'm guessing in GTFS feed MTA uses 6X, 7X, FX because <> characters are not allowed or somehow else cause problems. |
I've changed that in the CSV input data for PTNA. Neither GTFS nor OSM have a way expressing the diamond symbol, nor do they have a way expressing complex colour schemes like the (quite simple) one for the subway U8 here |
Please add New York City's MTA transit network of busses, subways, and ferry if possible.
The official website is https://new.mta.info/
GTFS feeds are available at from https://www.transit.land/operators/o-dr5r-nyct and https://www.transit.land/operators/o-dr5r7-nycdot
The text was updated successfully, but these errors were encountered: