Fix wrong_parent_location_type in GTFS

Diagnosis

What this notice means

The parent_station ID exists, but the parent's location type is not allowed for the child.

Operational effect

Apps cannot interpret the station hierarchy correctly.

Scope

Report field	Type	Meaning
`csvRowNumber`	integer	The row number of the faulty record.
`expectedLocationType`	string	The expected location type of the faulty record.
`locationType`	string	The faulty record's `stops.location_type`.
`parentCsvRowNumber`	integer	The row number of the faulty record's parent.
`parentLocationType`	string	The location type of the faulty record's parent.
`parentStation`	object	The id of the faulty record's parent station.
`parentStopName`	string	The stop name of the faulty record's parent.
`stopId`	string	The id of the faulty record.
`stopName`	string	The faulty record's `stops.stop_name`.

Repair

1
Compare the child and parent rows named by the report.
2
Use a station (1) as parent for a platform, entrance, or generic node, and a platform (0) as parent for a boarding area. A station must have no parent. Correct the reference or a misclassified type to match the real location.
3
Check the result
After a repair, rebuild the archive and validate it again. Confirm that the affected records are correct and that no new related notices appeared. A reviewed warning or informational notice may remain when it describes intentional, supported data.

Re-check your feed in the browserFree, no upload for a file you pick.

Worked example

Assume P1 and P2 are platforms of the existing station ST1. P1 must reference that station, not P2.

stop_id,location_type,parent_station
ST1,1,
P1,0,P2
P2,0,ST1

stop_id,location_type,parent_station
ST1,1,
P1,0,ST1
P2,0,ST1

Illustrative excerpt, not a complete GTFS feed. Keep all other required records and fields.

Sources