-
Notifications
You must be signed in to change notification settings - Fork 2
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
Include ODOT Crash Data into the Live API #26
Comments
do we want just the vehicle, participant, crash tables as previously discussed or is there additional tables to include? |
These tables include plain English versions of some of the attribute values that could be useful for display and understanding, or could be joined to the main tables prior to the API :
Crash_typ
Collis_typ
Cause
Actn
Evnt
Err
Vhcl_typ
wthr_cond
Partic_typ
Thanks,
~ Ben
…On May 30, 2018, 11:10 AM -0700, Brian Grant ***@***.***>, wrote:
do we want just the vehicle, participant, crash tables as previously discussed or is there additional tables to include?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Awesome, thanks @ben-chaney. I did create a foreign key relationship for the crash type and a few other fields in the first iteration, but will look at adding some more |
Example Crash Object:
|
@code-farmhouse when you are able could you check the current models/responses and see what you think? Additional questions:
|
@code-farmhouse , @znmeb if we need to look at the crashes vs. safety hotline I believe we need the gis data for this? Will this be included in next db update? |
Yes - the crash data will be geotagged in the next update. Some rows will have a NULL geometry, however. |
No description provided.
The text was updated successfully, but these errors were encountered: