Search
Clear search
Close search
Google apps
Main menu
true

Validation Warnings

CategoryWarningDescription
FaresMultiple fares without rules / fares with and without rulesFares defined without rules are valid for all itineraries that meet their transfer limitations. Review the corresponding fares to make sure that correct fare information is shown to users.

Learn more about guidelines for fares.

FrequenciesFrequency headway longer than intervalAn entry in the frequencies.txt file was found where the headway_secs value is much greater than the difference between end_time and start_time. Do not set headway_secs greater than the frequency interval.

We recommend you fix entries that cause this warning.
FrequenciesOverlapping frequency-based tripsThis warning indicates that two trips with overlapping frequency intervals and the same sequence of stops and times were found operating on the same day. This may indicate duplicate trips in the feed or misconfigured calendar entries that cause trips to activate on the wrong day. Verify that you correctly defined the service periods and exceptions; for example, weekend service enabled on a weekday (because it is a holiday) but without disabling the weekday service may create duplicate trips.
RoutesRoute name reused This warning indicates that routes are unnecessarily subdivided. Review each warning instance. This warning is not necessarily a problem, usually it shows routes named by type or operator and can be ignored in that case.

Learn more about feed guidelines for routes.

Routesroute_short_name contained in route_long_name Fields route_long_name and route_short_name should exclude each other, that is, neither should contain the other name.

Learn more about feed guidelines for routes.

Routesroute_short_name equals route_long_name Fields route_short_name and route_long_name must not be the same. If they are, specify the data in only one of the two fields.

Learn more about feed guidelines for routes.

Routesroute_short_name is too long The route_short_name should be a short identifier. This warning reports any route_short_name field longer than 6 characters, however this is not a hard limit. If the route_short_name contains a proper name, and there is also a route_long_name, then you can ignore these warnings.

Learn more about feed guidelines for routes.

Service dates and timesTrip duplicatesThis warning indicates that two trips were found operating on the same day that have the same sequence of stops and arrival or departure times. This may indicate duplicate trips in the feed or misconfigured calendar entries that cause trips to activate on the wrong day. Verify correct definition of service periods and exceptions; for example, weekend service enabled on a weekday (because it is a holiday) but without disabling the weekday service may create duplicate trips.

Learn more about guidelines for Trips.

ShapesStop does not match shape_dist_traveled value This warning is caused by an incorrect shape_dist_traveled value that does not match the location of the stop along the shape. In some cases, the system can ignore the shape_dist_traveled value and match the stop to the shape; review the problem instances nevertheless. It may be a good idea to completely remove the shape_dist_traveled values.

Learn more about guidelines for Shapes.

ShapesStop too far from shapeThis warning can be caused by wrong shapes or wrong stop locations. The problem instances should be reviewed to verify that the shape matches the course of the corresponding trip.
A stop was found in the stop_times.txt file that was more than 150 meters away from the trip path of travel as defined by the shape entry in the shapes.txt file. This warning can be caused by wrong shape definition or wrong stop locations.
Review problem instances to verify that the shape matches the course of the corresponding trip and that all stop locations are correct.

Learn more about guidelines for Shapes.

Stops and stationsPoint location too close to origin (0,0)A stop with a coordinate pair “0,0” or close to it is definitely incorrectly located or missing coordinates completely, this must be fixed.
Stops and stationsStops too close / Stations too close Ideally, a real-world stop should be represented by only one stop in the GTFS feed. However, in some schedule and routing systems, the same real-world stop is handled with different internal codes and defined in the feed multiple times.
Review these warnings to make sure they are not caused by bad stop locations or bad stop or station modeling. Stops with different names that are too close together can also indicate a problem.
Stops and stationsStops too close together The system returns this message when it finds two stops in file stops.txt that are very close to each other. This warning often implies that the stops are duplicates.
When two stops are very close, there is a good chance they actually represent the same stop. Stops with different names that are too close to one another can also indicate a problem. Stops which are close but on different levels may also trigger this warning.
Although this warning is common, it does not necessarily block the launch. The trip planner uses stop location in determining where to place a stop icon marker on the map. The marker represents the physical location where a passenger boards. Schedule and routing systems sometimes use different internal codes (defined multiple times in the GTFS feed) for the same stop.
We recommend that you consolidate internal codes into a single stop location code for each unique geolocation to allow placement of a single map marker on that point. However, ideally a real-world stop should be represented by only one stop inside the GTFS feed. 
Review these warnings to make sure they are not caused by bad stop locations or incorrect stop modeling.
Stops and stationsStop too close to station Validation found a stop in the stops.txt file that is more than 100 meters but less than 1000 meters from its parent station, as linked through the parent_station column. The stop may not actually be part of the parent station complex. Subway entrances can be far away from the center of the corresponding station. In this case, you can ignore the warning. Review these warnings to make sure they are not caused by bad stop locations or by bad stop or station modeling.
Stops and stationsStops match shape in wrong orderThis warning can be caused by an incorrect shape, wrong stop sequences, or wrong stop location.
Review the problem instances to verify that all stop locations are correct and that the shape matches the course of the corresponding trip.
Stops and stationsStops with same name and descriptionIf a stop_desc value is provided, it should add information and not just duplicate the stop_name.
Stops and stationsStop unused / station unusedStops that are not used by any trip in the feed won’t be processed further. We recommend that you check that unused stop or station entities are intended and not caused by a problem in the feed.
A validation warning about unused stops or stations in a GTFS feed indicates that there are entries in the stops.txt file that are not used by any entries in the stop_times.txt file. That means that no transit vehicles are scheduled to use that stop or station. While there is no restriction about including in your GTFS feed stops or stations that are not served by any transit vehicles, GTFS providers are encouraged to leave these entities out of their feeds since such entries might confuse riders if, for example, they are shown on a map or included in search results.
Here are some things to check when resolving "Unused stop" or "Unused station" validation warnings:
* If transit vehicles should be scheduled to use that stop or station, it may indicate a problem with entries in the stop_times.txt file, such as the stop being incorrectly excluded from the trip or stop pattern of a route.
* If the stop or station is no longer in service, it may be best to remove it from the feed.
* If using stop-station hierarchy in a GTFS feed, then station entries (stops with a location_type of 1) typically do not have corresponding entries in the stop_times.txt file. If a station entry is not correctly annotated with the proper location_type value, the feed validator considers it a regular stop and warns that it is unused.
Stops and stationsUn-merged stop warnings Un-merged stop warnings occur when stops should have been merged. Duplicate stops on Google Maps are confusing for users. The easiest way to fix this is:
  1.  Review the warning output to identify which stops need to be merged ("problem stop").
  2. Find the geocodes of all problem stops in the new feed.
  3. Update the geocodes of problem stops in the old feed to match the new feed.
Assuming there are few stops with this problem, you can manually perform these updates.
TransfersMin_transfer_time is missingThis warning indicates that a transfer was defined as timed transfer but no min_transfer_time was defined. Either the wrong transfer_type was defined or the min_transfer_time was not set.

You must fix this situation.

Learn more about guidelines for Transfers.

TransfersTransfer distance is very largeThis warning indicates that a transfer was defined between two stops that are very far away from each other at a distance that passengers wouldn’t normally walk (> 2km), this must be fixed.

Learn more about guidelines for Transfers.

TransfersTransfer walking speed is too fastThis warning indicates that a transfer was defined between two stops with a min_transfer_time that requires very fast walking (> 2m/s), this must be fixed.

Learn more about guidelines for Transfers.

TripsBlock trips with inconsistent route typesA block trip implies that passengers can remain on a vehicle to transfer from one route to the next. If the route_type changes, either the block or the route_type is incorrectly defined, this must be fixed.

Learn more about guidelines for Trips.

TripsStop headsign duplicates stop nameThe stop_headsign describes the direction for trips departing from the specified stop. This prevents routing results directing you to take a route towards Central Terminal if you are departing from Central Terminal.

Learn more about guidelines for Trips.

TripsTrip headsign contains route_long_nameSince the trip_headsign may be displayed together with the route_long_name information should not be duplicated.

Learn more about guidelines for Trips.

TripsTrip headsign contains route_short_nameSince the system displays trip_headsign with the route_short_name field, this information should not be duplicated. This prevents routing results like “1 towards 1 Central Terminal”.

Learn more about guidelines for Trips.

TimeTime warningsSee agency_timezone for information on time warnings.