Diagnosis
What this notice means
The reported point lies near zero latitude and zero longitude.
Operational effect
Why it matters
This often indicates missing coordinates exported as zeros and can place a location far from the service area.
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 row. |
entityId | string | The id of the faulty entity. |
featureIndex | integer | The index of the feature in the feature collection. |
filename | string | The name of the affected GTFS file. |
latFieldName | number | The name of the field that uses latitude value. |
latFieldValue | number | The latitude of the faulty row. |
lonFieldName | number | The name of the field that uses longitude value. |
lonFieldValue | number | The longitude of the faulty row |
Repair
How to fix it
- 1
Use the reported file, entity, and coordinate fields to compare the point with the real location.
- 2
Restore accurate coordinates or repair the export default. Do not shift the point by an arbitrary amount merely to avoid the check.
- 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