The scope of #483 was specific to setting up the columns required and performing a one-off association for non-CR3 records.
In discussions for that issue we've identified more work that needs to be tackled for the long-term management of associating locations to crashes:
[] Automate CR3 records association to locations
[] Automate non-CR3 records association to locations
[] At a minimum, these association scripts could run as an hourly or daily job, but ideally, each script would run on new record creation, or when coordinates get updated on an existing record
We should hold off on tackling this work until we have a more comprehensive dataset of locations which is currently pending from the VZ team.
The scope of #483 was specific to setting up the columns required and performing a one-off association for non-CR3 records.
In discussions for that issue we've identified more work that needs to be tackled for the long-term management of associating locations to crashes:
[] Automate CR3 records association to locations [] Automate non-CR3 records association to locations [] At a minimum, these association scripts could run as an hourly or daily job, but ideally, each script would run on new record creation, or when coordinates get updated on an existing record
We should hold off on tackling this work until we have a more comprehensive dataset of locations which is currently pending from the VZ team.
Migrated from atd-vz-data #672