Home
Malaysia Feeds
rapid-rail-kl
Source Data Validation Report

rapid-rail-kl — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T19:26:19Z,
for the dataset file:///shared/rapid-rail-kl_5d3d5ddb.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

rapidrail
- website: http://www.myrapid.com.my
- phone number: 60378852585
- email: Not provided

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2019-01-01 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
frequencies.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 7
Shapes: 14
Stops: 167
Trips: 42

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

ShapesFrequenciesRoute ColorsHeadsigns

Specification Compliance report

135 notices reported (0 errors, 125 warnings, 10 infos)

Notice Code Severity Total

missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"

mixed_case_recommended_field WARNING 120

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 120 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.
"agency.txt"	"agency_name"	"rapidrail"	2
"stops.txt"	"stop_name"	"PANDAN INDAH"	5
"stops.txt"	"stop_name"	"PANDAN JAYA"	6
"stops.txt"	"stop_name"	"CHAN SOW LIN"	9
"stops.txt"	"stop_name"	"HANG TUAH"	11
"stops.txt"	"stop_name"	"PLAZA RAKYAT"	12
"stops.txt"	"stop_name"	"MASJID JAMEK"	13
"stops.txt"	"stop_name"	"BANDARAYA - UOB"	14
"stops.txt"	"stop_name"	"SULTAN ISMAIL"	15
"stops.txt"	"stop_name"	"SENTUL TIMUR"	19
"stops.txt"	"stop_name"	"PUTRA HEIGHTS"	20
"stops.txt"	"stop_name"	"SUBANG ALAM"	21
"stops.txt"	"stop_name"	"ALAM MEGAH"	22
"stops.txt"	"stop_name"	"SUBANG JAYA"	29
"stops.txt"	"stop_name"	"CGC GLENMARIE"	30
"stops.txt"	"stop_name"	"ARA DAMANSARA"	31
"stops.txt"	"stop_name"	"LEMBAH SUBANG"	32
"stops.txt"	"stop_name"	"KELANA JAYA"	33
"stops.txt"	"stop_name"	"TAMAN BAHAGIA"	34
"stops.txt"	"stop_name"	"TAMAN PARAMOUNT"	35
"stops.txt"	"stop_name"	"ASIA JAYA"	36
"stops.txt"	"stop_name"	"TAMAN JAYA"	37
"stops.txt"	"stop_name"	"ABDULLAH HUKUM"	40
"stops.txt"	"stop_name"	"BANK RAKYAT BANGSAR"	41
"stops.txt"	"stop_name"	"KL SENTRAL - REDONE"	42
"stops.txt"	"stop_name"	"PASAR SENI"	43
"stops.txt"	"stop_name"	"MASJID JAMEK"	44
"stops.txt"	"stop_name"	"DANG WANGI"	45
"stops.txt"	"stop_name"	"KAMPUNG BARU - CBP COOPBANK PERTAMA"	46
"stops.txt"	"stop_name"	"AMPANG PARK"	48
"stops.txt"	"stop_name"	"DATO' KERAMAT"	50
"stops.txt"	"stop_name"	"SRI RAMPAI"	53
"stops.txt"	"stop_name"	"WANGSA MAJU"	54
"stops.txt"	"stop_name"	"TAMAN MELATI"	55
"stops.txt"	"stop_name"	"PUTRA HEIGHTS"	57
"stops.txt"	"stop_name"	"PUCHONG PRIMA"	58
"stops.txt"	"stop_name"	"PUCHONG PERDANA"	59
"stops.txt"	"stop_name"	"BANDAR PUTERI"	60
"stops.txt"	"stop_name"	"TAMAN PERINDUSTRIAN PUCHONG"	61
"stops.txt"	"stop_name"	"PUSAT BANDAR PUCHONG"	62
"stops.txt"	"stop_name"	"IOI PUCHONG JAYA"	63
"stops.txt"	"stop_name"	"ALAM SUTERA"	65
"stops.txt"	"stop_name"	"AWAN BESAR"	67
"stops.txt"	"stop_name"	"SRI PETALING"	68
"stops.txt"	"stop_name"	"BUKIT JALIL"	69
"stops.txt"	"stop_name"	"SUNGAI BESI"	70
"stops.txt"	"stop_name"	"BANDAR TASIK SELATAN"	71
"stops.txt"	"stop_name"	"BANDAR TUN RAZAK"	72
"stops.txt"	"stop_name"	"SALAK SELATAN"	73
"stops.txt"	"stop_name"	"CHAN SOW LIN"	75

route_color_contrast WARNING 1

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeColor (?) The faulty record's HTML route color.	routeTextColor (?) The faulty record's HTML route text color.
"PYL"	6	"#FFCD00"	"#FFFFFF"

route_long_name_contains_short_name WARNING 1

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`.
"BRT"	8	"BRT"	"BRT Sunway Line"

stop_too_far_from_shape WARNING 2

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.
11	"shp_KJ_1"	"KJL_MonFri_1"	399	"KJ37"	"PUTRA HEIGHTS"	[2.99665404,101.5746142]	105.43992618329838
8	"shp_KJ_0"	"KJL_MonFri_0"	326	"KJ37"	"PUTRA HEIGHTS"	[2.99665404,101.5746142]	105.43992618329838

unknown_column INFO 10

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.
"routes.txt"	"category"	9
"routes.txt"	"status"	10
"stop_times.txt"	"route_id"	1
"stop_times.txt"	"direction_id"	2
"stops.txt"	"category"	5
"stops.txt"	"route_id"	6
"stops.txt"	"geometry"	7
"stops.txt"	"isOKU"	8
"stops.txt"	"status"	9
"stops.txt"	"search"	10