We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue by barbeau May 1, 2020 Originally opened as CUTR-at-USF#379
Summary:
Invalid locations of (0,0) for a vehicle position are relatively common, so we should check for these in E026.
Also consider additional measures for validating location as discussed for GTFS stops in MobilityData/gtfs-validator#148.
Steps to reproduce:
Throw an error
Expected behavior:
What did you expect the application to do?
Observed behavior:
No errors are thrown
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue by barbeau
May 1, 2020
Originally opened as CUTR-at-USF#379
Summary:
Invalid locations of (0,0) for a vehicle position are relatively common, so we should check for these in E026.
Also consider additional measures for validating location as discussed for GTFS stops in MobilityData/gtfs-validator#148.
Steps to reproduce:
Throw an error
Expected behavior:
What did you expect the application to do?
Observed behavior:
No errors are thrown
The text was updated successfully, but these errors were encountered: