Skip to content
New issue

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

"persons_"* fields don't seem to always match total counts for person types #16

Closed
clhenrick opened this issue Jan 30, 2017 · 1 comment
Labels

Comments

@clhenrick
Copy link
Collaborator

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:

screen shot 2017-01-30 at 1 00 38 pm

@clhenrick clhenrick added the data label Jan 30, 2017
@clhenrick 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
@gregallensworth
Copy link
Member

This was fixed in the ETL stuff, some months back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants