Home
United States Feeds
starmetro
Source Data Validation Report

starmetro — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T04:24:48Z,
for the dataset file:///shared/starmetro_37ce3d2b.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

StarMetro
- website: http://www.talgov.com/starmetro
- phone number: (850) 891-5200
- email: Not provided

Feed Info

Publisher Name:
StarMetro: Publisher URL:
http://www.talgov.com/starmetro: Feed Email:
N/A: Feed Language:
English: Feed Start Date:
2026-01-03: Feed End Date:
2026-05-01: Service Window:
2026-01-03 to 2026-05-01 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
transfers.txt
trips.txt

Counts

Agencies: 1
Blocks: 76
Routes: 39
Shapes: 140
Stops: 913
Trips: 1044

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Transfers Shapes Feed Information Fares V1 Route Colors Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed

Specification Compliance report

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

Notice Code Severity Total

feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	currentDate (?) Current date (YYYYMMDD format).	feedEndDate (?) Feed end date (YYYYMMDD format).	suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2	"20260424"	"20260501"	"20260501"

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

missing_recommended_field WARNING 2

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"fare_attributes.txt"	2	"agency_id"
"fare_attributes.txt"	3	"agency_id"

mixed_case_recommended_field WARNING 1972

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.

Good examples:
`Field Text`	`Dataset`
"Schwerin, Hauptbahnhof"	Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin"	NYC Ferry
"Campo Grande Norte"	Carris

Bad examples:
`Field Text`
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

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

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"routes.txt"	"route_long_name"	"BIG BEND"	3
"routes.txt"	"route_long_name"	"LIVE OAK"	10
"routes.txt"	"route_long_name"	"RED HILLS"	16
"routes.txt"	"route_long_name"	"SAN LUIS"	17
"routes.txt"	"route_long_name"	"SATURDAY AZALEA"	18
"routes.txt"	"route_long_name"	"SATURDAY BIG BEND"	19
"routes.txt"	"route_long_name"	"SATURDAY EVERGREEN"	20
"routes.txt"	"route_long_name"	"SATURDAY FOREST"	21
"routes.txt"	"route_long_name"	"SATURDAY GULF"	22
"routes.txt"	"route_long_name"	"SATURDAY LIVE OAK"	23
"routes.txt"	"route_long_name"	"SATURDAY MOSS"	24
"routes.txt"	"route_long_name"	"SATURDAY RED HILLS"	25
"routes.txt"	"route_long_name"	"SATURDAY TALL TIMBERS"	26
"routes.txt"	"route_long_name"	"TALL TIMBERS"	32
"routes.txt"	"route_long_name"	"HERITAGE GROVE"	35
"routes.txt"	"route_long_name"	"NITE NOLE"	37
"stops.txt"	"stop_name"	"W TENNESSEE ST AT MACOMB ST"	2
"stops.txt"	"stop_name"	"W TENNESSEE ST AT COPELAND ST WB"	3
"stops.txt"	"stop_name"	"W TENNESSEE ST AT RAVEN ST WB"	4
"stops.txt"	"stop_name"	"W TENNESSEE ST AT W BREVARD ST WB"	5
"stops.txt"	"stop_name"	"W TENNESSEE ST AT BASIN ST WB"	6
"stops.txt"	"stop_name"	"W TENNESSEE ST AT CALIARK ST WB"	7
"stops.txt"	"stop_name"	"N OCALA RD NORTH OF TENNESSEE N"	8
"stops.txt"	"stop_name"	"N OCALA RD AT CONTINENTAL AVE"	9
"stops.txt"	"stop_name"	"N OCALA RD AT MID BLOCK"	10
"stops.txt"	"stop_name"	"N OCALA RD AT GODBY HIGH"	11
"stops.txt"	"stop_name"	"W THARPE ST AT SAN LUIS EB"	12
"stops.txt"	"stop_name"	"W THARPE ST AT EAST OF MARYELLEN WB"	13
"stops.txt"	"stop_name"	"W THARPE ST AT TRIMBLE RD WB"	14
"stops.txt"	"stop_name"	"W THARPE ST AT W OF BURNS WB"	15
"stops.txt"	"stop_name"	"W THARPE ST AT NANI DR"	16
"stops.txt"	"stop_name"	"N MISSION RD AT PECAN RD NB"	17
"stops.txt"	"stop_name"	"N MISSION RD AT HARTSFIELD RD NB"	18
"stops.txt"	"stop_name"	"N MISSION RD AT MOON LN NB"	19
"stops.txt"	"stop_name"	"N MISSION RD AT HUNTINGTON WOODS NB"	20
"stops.txt"	"stop_name"	"N MISSION RD AT MCCORD BLVD NB"	21
"stops.txt"	"stop_name"	"N MISSION RD AT GAFFNEY LOOP NB"	22
"stops.txt"	"stop_name"	"N MISSION RD AT FRED GEORGE RD NB"	23
"stops.txt"	"stop_name"	"FRED GEORGE RD AT SCHOOL CROSSWALK SB"	24
"stops.txt"	"stop_name"	"FRED GEORGE RD AT OLD BAINBRIDGE RD NB"	25
"stops.txt"	"stop_name"	"FRED GEORGE AT ST LOUIS CHURCH SB"	26
"stops.txt"	"stop_name"	"N MISSION RD AT FRED GEORGE RD SB"	27
"stops.txt"	"stop_name"	"N MISSION RD AT MISSION TRACE BLVD SB"	28
"stops.txt"	"stop_name"	"N MISSION RD AT CAYUGA ST SB"	29
"stops.txt"	"stop_name"	"N MISSION RD AT MOON LN SB"	30
"stops.txt"	"stop_name"	"N MISSION RD AT HARTSFIELD RD IB"	31
"stops.txt"	"stop_name"	"W THARPE ST AT BURNS ST EB"	32
"stops.txt"	"stop_name"	"W THARPE ST AT TRIMBLE RD EB"	33
"stops.txt"	"stop_name"	"W THARPE ST AT FALCON CREST EB"	34
"stops.txt"	"stop_name"	"W TENNESSEE AT MISSION SAN LUIS WB"	35

route_long_name_contains_short_name WARNING 4

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`.
"Night 1"	12	"Night 1"	"Night 1"
"Night 2"	13	"Night 2"	"Night 2"
"Night 3"	14	"Night 3"	"Night 3"
"Night 5"	15	"Night 5"	"Night 5"

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.
424	"19087"	"209311"	14108	"1001HIGH"	"1001 HIGH RD"	[30.45156100000001,-84.31346]	199.29668628852124

stop_without_stop_time WARNING 11

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
427	"S BR952"	"S BRONOUGH ST AT PENSACOLA ST SB"
439	"S MA1008"	"S MLK JR BLVD AT PALMER ST SB"
441	"445R&T"	"445 R&T PERKINS WY AT MIDBLOCK EB"
443	"R&TWAHNB"	"R&T PERKINS WY AT ALTHEA GIBSON WAY"
470	"GATE 14"	"C.K. STEELE PLAZA GATE 14"
471	"DUVHAR"	"S DUVAL ST AT HARRISON ST NB"
610	"POTTSRDB"	"POTTSDAMER ST AT RED BARBER NB"
793	"DVLGAINS"	"DUVAL AT GAINES ST NB"
794	"LKBMCKLL"	"LAKE BRADFORD RD AT MCCASKILL AVE SB"
798	"R&TCLEV"	"R&T PERKINS WY AT DISSTON ST EB"
799	"PALMADA"	"PALMER ST AT ADAMS ST EB"

stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

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.	stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`.	stopId1 (?) The id of the first stop that is referred to.	stopName1 (?) The name of the first stop that is referred to.	match1 (?) Latitude and longitude pair of the first matching location.	stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`.	stopId2 (?) The id of the second stop that is referred to.	stopName2 (?) The name of the second stop that is referred to.	match2 (?) Latitude and longitude pair of the second matching location.
424	"19087"	"209311"	14108	"1001HIGH"	"1001 HIGH RD"	[30.453352689012483,-84.3134741164798]	14107	"TENCALRK"	"W TENNESSEE ST AT CALIARK ST WB"	[30.449126480000984,-84.31094113318193]