You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[GTFS-Fares v2] Add fare_leg_join_rules.txt (#439)
* Add Effective Fare Leg to term definition
* Add fare_leg_join_rules.txt
* Modify fare_leg_rules for effective fare leg
* Add from/to_stop_id
* Update file desc for from/to_stop_id
* Editorial updates
from_network_id and to_network_id should exist in networks.txt
foreign_key_violation
If the checks for missing_required_column and missing_required_field above are complete and do not generate a notice, then:
If the value for from_network_id does not exist in networks.network_id or routes.network_id) or the value for to_network_id does not exist in (networks.txt or routes.txt):
Trigger Notice
childFieldName,
childFilename,
csvRowNumber,
fieldValue,
parentFieldName,
parentFilename
ERROR
Wrong foreign key.
A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.
from_stop_id and to_stop_id should exist in stops.txt
foreign_key_violation
If the checks for missing_required_field above are complete and do not generate a notice, then:
If from_stop_id value does not exist in stops.txt or to_stop_id value does not exist in stops.txt:
Trigger Notice
childFieldName,
childFilename,
csvRowNumber,
fieldValue,
parentFieldName,
parentFilename
ERROR
Wrong foreign key.
A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.
Sample GTFS datasets
Severity
ERROR
Additional context
The text was updated successfully, but these errors were encountered:
Commit Nº 1
AUTHOR × DATE
MESSAGE
FILES CHANGED
NEW RULE DETAILS
Describe the new validation rules
Do not trigger a notice and ignore subsequent checks
If from_network_id column does not exist or to_network id column does not exist:
Trigger Notice and do not check for missing_required_field
FieldName,
Filename
If from_network_id is empty and to_network_id is empty:
Trigger Notice and do not check for foreign_key_violation
csvRowNumber,
FieldName,
Filename
The given field has no value in some input row, even though values are required.
If the value for from_network_id does not exist in networks.network_id or routes.network_id) or the value for to_network_id does not exist in (networks.txt or routes.txt):
Trigger Notice
childFieldName,
childFilename,
csvRowNumber,
fieldValue,
parentFieldName,
parentFilename
A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.
Trigger Notice and do not check for foreign_key_violation
csvRowNumber,
FieldName,
Filename
The given field has no value in some input row, even though values are required.
If from_stop_id value does not exist in stops.txt or to_stop_id value does not exist in stops.txt:
Trigger Notice
childFieldName,
childFilename,
csvRowNumber,
fieldValue,
parentFieldName,
parentFilename
A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.
Sample GTFS datasets
Severity
ERROR
Additional context
The text was updated successfully, but these errors were encountered: