Skip to content
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

sta GTFS feed parent station IDs not conform to IFOPT spec #186

Open
hbruch opened this issue Mar 27, 2024 · 3 comments
Open

sta GTFS feed parent station IDs not conform to IFOPT spec #186

hbruch opened this issue Mar 27, 2024 · 3 comments
Assignees

Comments

@hbruch
Copy link
Contributor

hbruch commented Mar 27, 2024

According to the IFOPT standard (EN 28701:2012, see also https://wiki.openstreetmap.org/wiki/Key:ref:IFOPT), the IFOPT ID should start with first two letters Country Code.

Currently The sta GTFS declares parent stations with stop_ids like Parentit:...:

"it:22021:1060:1:2790","Velturno, Castello","46.6703839725599","11.6009552752191","","Parentit:22021:1060"

IMHO, the parent station should have an ID of it:22021:1060, and if there are Trips which refer to this as stops in the stop_times, a new (unspecific) dummy quay should be introduced like e.g. it:22021:1060:na:na

@rcavaliere
Copy link
Member

@hbruch can you please provide me an example of file in which such IDs are present? We typically only have compliant IDs in South Tyrol!

@hbruch
Copy link
Contributor Author

hbruch commented Mar 27, 2024

Technically, it is "compliant" in a sense that the feed's structure is ok (parent stations have correct location code and are not referenced as stop_times). Nevertheless https://gtfs.api.opendatahub.com/v1/dataset/sta-time-tables/raw uses Parentit:... stop_ids in stops.txt.

This is IMO a custom way to assign IDs to parent stations which will I expect not to be done by other operators and hence will result in issues when merging feeds with other Italian or European feeds.

@rcavaliere
Copy link
Member

@hbruch ah you are right! It's the file stops.txt. That's clearly a bug. I will manage the issue with the Data Provider (STA). Thanks for highlighting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants