Closed ccao-jardine closed 3 weeks ago
Missing townships are expected. Some parcels are simply missing values for user1
in legdat
.
As for empty classes and values only for mailed stage, this is an annoying product of some PINs existing in asmt_all
for a given year but not in pardat
. Here's output for pin 32182130040000:
par_taxyr | par_class | asmt_taxyr | asmt_class |
---|---|---|---|
2021 | 592 | ||
2020 | 592 | 2020 | 592 |
2020 | 592 | 2020 | 592 |
2020 | 592 | 2020 | 592 |
2019 | 592 | 2019 | 592 |
2019 | 592 | 2019 | 592 |
2019 | 592 | 2019 | 592 |
2018 | 592 | 2018 | 592 |
2018 | 592 | 2018 | 592 |
2018 | 592 | 2018 | 592 |
2017 | 592 | 2017 | 592 |
2017 | 592 | 2017 | 592 |
2017 | 592 | 2017 | 592 |
2016 | 592 | 2016 | 592 |
2016 | 592 | 2016 | 592 |
2016 | 592 | 2016 | 592 |
2015 | 592 | 2015 | 592 |
2015 | 592 | 2015 | 592 |
2015 | 592 | 2015 | 592 |
2014 | 592 | 2014 | 592 |
We could do an inner join
rather than a left join
to make sure a parcel has data in both pardat
and asmt_all
in order to make it into the view, if we'd like.
Yep, inner join seems reasonable to me. Thanks for checking into it!
These are all prior tax years so hopefully this is resolved in ias moving forward...🤞
In our Open Data: Assessed Values dataset, there are 362 PINs with null class, township_code, township_name, and neighborhood_code. They also only have AVs only for the mailed stage.
I'm not sure if it's expected/explainable but let's QC this! Low-priority because it's a small number of PINs across all tax years.