As it stands now, the file odot_crash_data.sql Is generated by code in another repository, https://github.com/hackoregon/crash-data-wrangling, from the original MDB file we received from ODOT. It only takes a few minutes to generate the SQL file and it's fully automated in containers now, so the code should be moved here.
My plan is to do it as soon as the API is up and running against the SQL dump file we already have; the process as it now stands leaves a fully-populated database container service running, so we can either run it separately to generate the dump and then start a new container from it, or just bring up the database container with the raw data file.
As it stands now, the file
odot_crash_data.sql
Is generated by code in another repository, https://github.com/hackoregon/crash-data-wrangling, from the original MDB file we received from ODOT. It only takes a few minutes to generate the SQL file and it's fully automated in containers now, so the code should be moved here.My plan is to do it as soon as the API is up and running against the SQL dump file we already have; the process as it now stands leaves a fully-populated database container service running, so we can either run it separately to generate the dump and then start a new container from it, or just bring up the database container with the raw data file.