-
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
322 Add big misses from all years #323
base: 2025-assessment-year
Are you sure you want to change the base?
322 Add big misses from all years #323
Conversation
model_big_misses_full <- assessment_pin %>% | ||
mutate(township_name = ccao::town_convert(meta_township_code)) %>% | ||
filter( | ||
meta_triad_code == run_triad_code, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems as though sv_outliers are filtered here,
model-res-avm/pipeline/00-ingest.R
Line 465 in 84708c4
filter(!sv_is_outlier) %>% |
`Est. FMV` = pred_pin_final_fmv_round | ||
) %>% | ||
mutate( | ||
Difference = (`Est. FMV` - `Sale 1 Price`), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want difference by max of any sale price
Finding erroneously priced sales led to issues such as #311, where we tried to identify incorrect data. This creates a new table which looks at all sales, and identifies the largest and smallest decreases in FMV to Sale Price (organized by township).
In essence, if we find a sale where the difference is $20,000,000, even if the sale was in 2018, that would be a pin where we might want to investigate if it should be an outlier / if something was input incorrectly.