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
Some rows have higher values for the type of person injured or killed than "number_of_persons_killed" or "number_of_persons_injured". For example, a row may have a value of 3 for "number_of_pedestrians_killed" but then have a value of 2 or 1 or 0 for "number_of_persons_killed". Typically in the data it seems that "number_of_persons_killed" reflects a total for all three categories of person killed: cyclist, motorist, and pedestrian. Same for "number_of_persons_injured".
As such the columns "number_of_persons_injured" and "number_of_persons_killed" should be treated with suspect.
Here is a screenshot of selecting such rows in CARTO:
The text was updated successfully, but these errors were encountered:
clhenrick
changed the title
Data issues: "persons" doesn't seem to always match total count
"persons_"* fields don't seem to always match total counts for person types
Feb 2, 2017
Some rows have higher values for the type of person injured or killed than
"number_of_persons_killed"
or"number_of_persons_injured"
. For example, a row may have a value of 3 for"number_of_pedestrians_killed"
but then have a value of 2 or 1 or 0 for"number_of_persons_killed"
. Typically in the data it seems that"number_of_persons_killed"
reflects a total for all three categories of person killed: cyclist, motorist, and pedestrian. Same for"number_of_persons_injured"
.As such the columns
"number_of_persons_injured"
and"number_of_persons_killed"
should be treated with suspect.Here is a screenshot of selecting such rows in CARTO:
The text was updated successfully, but these errors were encountered: