busmaps.com

Search

Home
United States Feeds
fmcta
Source Data Validation Report

fmcta — Source Data Validation Report

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

Use this report alongside our documentation.

Summary

Agencies included

Fairmont-Marion County Transit Authority
- website: http://www.fmcta.com/
- phone number: 304-366-8177
- email: Not provided

Feed Info

Publisher Name:
Mountaineer Technology Consultants: Publisher URL:
https://mountaineertech.com/: Feed Email:
N/A: Feed Language:
English: Feed Start Date:
2019-07-21: Feed End Date:
2026-12-31: Service Window:
2019-09-10 to 2026-12-31 (?) 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
feed_info.txt
frequencies.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 16
Shapes: 32
Stops: 85
Trips: 143

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

Shapes Frequencies Feed Information Route Colors Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Location Types

Specification Compliance report

23954 notices reported (0 errors, 23953 warnings, 1 infos)

Notice Code Severity Total

leading_or_trailing_whitespaces WARNING 23934

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

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

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) Faulty record's field name.	fieldValue (?) Faulty value.
"shapes.txt"	2	"shape_id"	" 168772"
"shapes.txt"	3	"shape_id"	" 168772"
"shapes.txt"	4	"shape_id"	" 168772"
"shapes.txt"	5	"shape_id"	" 168772"
"shapes.txt"	6	"shape_id"	" 168772"
"shapes.txt"	7	"shape_id"	" 168772"
"shapes.txt"	8	"shape_id"	" 168772"
"shapes.txt"	9	"shape_id"	" 168772"
"shapes.txt"	10	"shape_id"	" 168772"
"shapes.txt"	11	"shape_id"	" 168772"
"shapes.txt"	12	"shape_id"	" 168772"
"shapes.txt"	13	"shape_id"	" 168772"
"shapes.txt"	14	"shape_id"	" 168772"
"shapes.txt"	15	"shape_id"	" 168772"
"shapes.txt"	16	"shape_id"	" 168772"
"shapes.txt"	17	"shape_id"	" 168772"
"shapes.txt"	18	"shape_id"	" 168772"
"shapes.txt"	19	"shape_id"	" 168772"
"shapes.txt"	20	"shape_id"	" 168772"
"shapes.txt"	21	"shape_id"	" 168772"
"shapes.txt"	22	"shape_id"	" 168772"
"shapes.txt"	23	"shape_id"	" 168772"
"shapes.txt"	24	"shape_id"	" 168772"
"shapes.txt"	25	"shape_id"	" 168772"
"shapes.txt"	26	"shape_id"	" 168772"
"shapes.txt"	27	"shape_id"	" 168772"
"shapes.txt"	28	"shape_id"	" 168772"
"shapes.txt"	29	"shape_id"	" 168772"
"shapes.txt"	30	"shape_id"	" 168772"
"shapes.txt"	31	"shape_id"	" 168772"
"shapes.txt"	32	"shape_id"	" 168772"
"shapes.txt"	33	"shape_id"	" 168772"
"shapes.txt"	34	"shape_id"	" 168772"
"shapes.txt"	35	"shape_id"	" 168772"
"shapes.txt"	36	"shape_id"	" 168772"
"shapes.txt"	37	"shape_id"	" 168772"
"shapes.txt"	38	"shape_id"	" 168772"
"shapes.txt"	39	"shape_id"	" 168772"
"shapes.txt"	40	"shape_id"	" 168772"
"shapes.txt"	41	"shape_id"	" 168772"
"shapes.txt"	42	"shape_id"	" 168772"
"shapes.txt"	43	"shape_id"	" 168772"
"shapes.txt"	44	"shape_id"	" 168772"
"shapes.txt"	45	"shape_id"	" 168772"
"shapes.txt"	46	"shape_id"	" 168772"
"shapes.txt"	47	"shape_id"	" 168772"
"shapes.txt"	48	"shape_id"	" 168772"
"shapes.txt"	49	"shape_id"	" 168772"
"shapes.txt"	50	"shape_id"	" 168772"
"shapes.txt"	51	"shape_id"	" 168772"

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 16

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.
"routes.txt"	2	"agency_id"
"routes.txt"	3	"agency_id"
"routes.txt"	4	"agency_id"
"routes.txt"	5	"agency_id"
"routes.txt"	6	"agency_id"
"routes.txt"	7	"agency_id"
"routes.txt"	8	"agency_id"
"routes.txt"	9	"agency_id"
"routes.txt"	10	"agency_id"
"routes.txt"	11	"agency_id"
"routes.txt"	12	"agency_id"
"routes.txt"	13	"agency_id"
"routes.txt"	14	"agency_id"
"routes.txt"	15	"agency_id"
"routes.txt"	16	"agency_id"
"routes.txt"	17	"agency_id"

stop_too_far_from_shape WARNING 1

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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.
52	"173160"	"5505970"	498	"1920511"	"Farmington"	[39.511444143543265,-80.24794464120858]	212.56006104134332

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.
69	"174225"	"5521012"	626	"1883729"	"Courthouse"	[39.48536349400596,-80.1430271837029]	625	"1875707"	"Transfer Station"	[39.4852787368255,-80.14475378960846]

unknown_column INFO 1

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file.	fieldName (?) The name of the unknown column.	index (?) The index of the faulty column.
"trips.txt"	"block_name"	11