-
Notifications
You must be signed in to change notification settings - Fork 101
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
Trigger warning for duplicated stop_code #471
Comments
Hi Aaron, Alas, such thing varies a lot among data producers. I agree that this warning could be useful for many producers. But for another large set of data producers, stop codes are not unique, and it will be just generate a long list of warning that people will start ignoring. I would therefore advocate to not apply such validation by default, and to not generate such warning. If there is a large need in a specific part of the industry, we invite this part of the industry to contribute in kind as an op-in validation rule. Thanks! |
What is the framework for parameterizing what rules are called? |
By default it's only spec. |
What about https://gtfs.org/best-practices/ ? |
Hello, Two pieces of information to add here:
|
stops
.stop_code
is a free text field for passenger-facing IDs. In most cases,stop_code
needs to be unique in a dataset. (There may be some exceptions, for example, if stops within a station all share the same ID?)Requested solution:
Warnings on non-unique
stop_code
values.Related: "[REQUEST] Implement unique Stop ID verification (GTFS Rule)" #230
The text was updated successfully, but these errors were encountered: