Diagnosis
What this notice means
The reported customer-facing text does not follow the recommended mixed-case style.
Operational effect
Why it matters
All-uppercase names or unnecessary abbreviations can be harder to read and pronounce.
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 |
|---|---|---|
csvRowNumber | integer | The row number of the faulty record. |
fieldName | string | Name of the faulty field. |
fieldValue | string | Faulty value. |
filename | string | Name of the faulty file. |
Repair
How to fix it
- 1
Compare the text with the name used on signs and in public timetables.
- 2
Use natural capitalization and readable wording. Preserve established acronyms and languages without upper/lower case; do not mechanically title-case every name.
- 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