Diagnosis
What this notice means
The reported rows have an identical ID or identical combination of key fields.
Operational effect
Why it matters
An app may reject the records or choose a row unpredictably.
Scope
Files to check and report fields
Use the file or input resource identified in the report. Check the message and available context fields; runtime failures may not identify a GTFS row.
| Report field | Type | Meaning |
|---|---|---|
fieldName1 | string | Composite key's first field name. |
fieldName2 | string | Composite key's second field name. |
fieldValue1 | string | Composite key's first value. |
fieldValue2 | string | Composite key's second value. |
filename | string | The name of the faulty file |
newCsvRowNumber | integer | The row of the other occurrence. |
oldCsvRowNumber | integer | The row of the first occurrence. |
Repair
How to fix it
- 1
Compare
oldCsvRowNumberandnewCsvRowNumberinfilename, using the reported key fields. - 2
Remove a true duplicate. For different entities, correct the key and update affected references. For a compound key, such as
trip_idplusstop_sequence, check the whole combination. - 3Check 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.
Sources