citadina — Source Data Validation Report

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

Only the first 50 of 1944 affected records are displayed below.

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

You can see more about this notice here.

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

Only the first 50 of 172 affected records are displayed below.

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

Bad examples:

You can see more about this notice here.

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

trip_with_shape_dist_traveled_but_no_shape_distances

A trip has shape_dist_traveled values in stop_times.txt but the shape referenced by the trip's shape_id does not have shape_dist_traveled values on all of its points in shapes.txt.

When stop times define distance values but the shape does not carry matching distances on every point, consumers cannot use those distances to align stops to the shape geometry reliably. This inconsistency may cause incorrect routing or display behaviour.

Note: Only the first stop time carrying a shape_dist_traveled value is referenced in the notice; this is a representative row rather than an exhaustive list.

You can see more about this notice here.

Only the first 50 of 72 affected records are displayed below.

unknown_column

A column name is unknown.

You can see more about this notice here.