Diagnosis
What this notice means
The amount's format does not match the decimal precision expected for the associated currency.
Operational effect
Why it matters
Fare processing may reject the amount or interpret its precision incorrectly.
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 of the faulty record. |
currencyCode | object | Faulty record's currency code. |
fieldName | string | Faulty record's field name. |
fieldValue | string | Faulty currency field amount value. |
filename | string | The name of the faulty file. |
Repair
How to fix it
- 1
Check the reported
currencyCode, amount field, and original fare. - 2
Format the amount with the currency's required decimal precision and a decimal point. Confirm rounding with the fare source rather than changing the price arbitrarily.
- 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