You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the total # of errors, warnings, info, etc seems to be a sum of the number of occurrences of notices with that severity.
Instead, it should be the # of unique notices. For example, in the dataset below, the error count should be 2, not 39399.
Why?
Validator users have consistently given feedback that the number of occurrences is overwhelming, and sometimes a deterrent for producers to actually fix issues, since it isn't clear that they can often fix thousands of occurrences with 1-2 changes. We want to highlight the unique number of validation notices triggered instead to reduce overwhelm and indicate the diversity of problems within a dataset.
Occurrences can be added in the future, and should be included per notice, e.g block_trips_with_overlapping_stop_timestotal_occurrences is 4.
Add total_unique_error, total_unique_warning, total_unique_info and keep total_error, total_warning, total_info
These unique values are calculated on the fly
emmambd
changed the title
Total number of errors/warnings/info should be # of unique notices, not # of occurrences
Add total # of unique notices grouped by severity
May 27, 2024
Describe the issue
Right now, the total # of errors, warnings, info, etc seems to be a
sum of the number of occurrences of notices with that severity
.Instead, it should be the # of unique notices. For example, in the dataset below, the error count should be 2, not 39399.
Why?
Validator users have consistently given feedback that the number of occurrences is overwhelming, and sometimes a deterrent for producers to actually fix issues, since it isn't clear that they can often fix thousands of occurrences with 1-2 changes. We want to highlight the unique number of validation notices triggered instead to reduce overwhelm and indicate the diversity of problems within a dataset.
Occurrences can be added in the future, and should be included per notice, e.g
block_trips_with_overlapping_stop_times
total_occurrences
is 4.Steps/Code to Reproduce
Go to Swagger: https://mobilitydata.github.io/mobility-feed-api/SwaggerUI/index.html#/
Use mdb-10-202402080058
In
/v1/datasets/gtfs/mdb-10-202402080058
Expected Results
Actual Results
In
/v1/datasets/gtfs/mdb-10-202402080058
Proposed Solution
Add
unique_error_count
,unique_warning_count
,unique_info_count
so it's clear what is being described.Files used
No response
Additional notes
No response
The text was updated successfully, but these errors were encountered: