search

sfbrigade / datasci-dot-fars

Understanding the Department of Transportation FARS dataset
1 stars 8 forks source link

Data dictionary and related datasets #3

Open judecalvillo opened 7 years ago

judecalvillo commented 7 years ago

Hey @sirwart and DoT FARS team. Like I was saying last meeting, I'd like to help out here. To that end, I can't seem to download the data dictionary at the location/link provided, but, given the 'sad puzzle piece' error I'm getting, it looks like that might be due to some plugin issue (I use Chromium on Ubuntu). Can someone point me to an alternative source for this?

Also, in the dataset referenced in the README, I'm seeing some fields, like county, reference codes (e.g. County codes don't seem to match with FIPS codes). Do we have lookup tables for such fields somewhere? If so, can you point me to these?

Once I've got the above, and perhaps after Monday/Tuesday, I'll take a crack at some Poisson regressions to answer one or more of the prompts we've got so far. Hope you're all having a great weekend!

-Jude

sirwart commented 7 years ago

Hey Jude, I'll checkin the data dictionary since it's just a PDF. I think the codes are FIPS but are missing leading zero padding and the state part of FIPS are in a different column. We never got the temperature into the same dataset, so I could put together a CSV with a row for each bicycle accident, the time, temperature, and full FIPS that I think would be a good base for further analysis. Does that sound right to you?

judecalvillo commented 7 years ago

Sounds great. Thanks, Brian!

---- On Sat, 07 Jan 2017 16:10:29 -0800 sirwart <notifications@github.com> wrote ----

Hey Jude, I'll checkin the data dictionary since it's just a PDF. I think the codes are FIPS but are missing leading zero padding and the state part of FIPS are in a different column. We never got the temperature into the same dataset, so I could put together a CSV with a row for each bicycle accident, the time, temperature, and full FIPS that I think would be a good base for further analysis. Does that sound right to you?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Confidentiality Notice: This email message (including any attachments) may contain confidential, privileged or non-public information and is for the sole use of the designated recipient(s). If you received this communication in error, please notify the sender immediately by replying to this message and then delete the original message and any attachments from your system. Use, dissemination, distribution, or reproduction of this message by unintended recipients is not authorized and may be unlawful.