-
Notifications
You must be signed in to change notification settings - Fork 6
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
Develop Automated Process for Identifying Bad Count Data #23
Comments
@aharpalaniTO to review README, @sunnyqywang to continue working through identifying bad data |
@aharpalaniTO to provide @sunnyqywang with a list of wavetronics unit artery codes for removal (for now). |
@sunnyqywang to create process for determining bad TMC counts and throwing htem out. |
@sunnyqywang developed a process for flagging and removing anomalous TMC count data. |
Will continue to improve when anomalies are detected; but issue is effectively closed. |
Script written in Postgres for identifying counts (unique combination of arterycode, count_date) for investigation. Unclear whether this will be also involve removal of records from
centreline_volumes
or whether we pass on to Trevor's team (contingent on implementation of #22).The text was updated successfully, but these errors were encountered: