Search
  1. Home
  2. United States Feeds
  3. realtimemobile-availtec
  4. Source Data Validation Report

realtimemobile-availtec — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-06-11T19:41:42Z,
for the dataset file:///shared/realtimemobile-availtec_02854156.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Feed Info

Publisher Name:
The Wave (Mobile)
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-03-19
Feed End Date:
2028-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. feed_info.txt
  6. frequencies.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 32
  • Routes: 12
  • Shapes: 34
  • Stops: 907
  • Trips: 601

Specification Compliance report

14 notices reported (0 errors, 14 warnings, 0 infos)

Notice Code Severity Total
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
route_long_name_contains_short_name WARNING 12

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:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"1" 2 "1" "1"
"4" 3 "4" "4"
"5" 4 "5" "5"
"7" 5 "7" "7"
"9" 6 "9" "9"
"10" 7 "10" "10"
"11" 8 "11" "11"
"12" 9 "12" "12"
"14" 10 "14" "14"
"15" 11 "15" "15"
"16" 12 "16" "16"
"18" 13 "18" "18"
stop_too_far_from_shape_using_user_distance WARNING 1

stop_too_far_from_shape_using_user_distance

Stop time too far from shape.

A stop time entry that is a large distance away from the location of the shape in shapes.txt as defined by shape_dist_traveled values.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
377 "556_shp" "t1F4-b4-sl2" 19 "1212" "Ala Career System Office off Springhill" [30.706039000000004,-88.124466] 114.33990531142129