Get list of NULL or non-matching verification columns

[popovs]

For the bear dens field visit table, extract the following records:

• Field visits where both the field forestry status and verifications are both NULL. In these cases, the numbers from previous years should be copied over.
• Field visits where the number in the verification column differs greatly from the field forestry status. TBD: at which point do you flag vastly different from acceptably different? >10m difference?
• Field visits where the verification column is NULL. In these cases, the verification has not yet been attempted.

[popovs]

I'm working off the following four paired columns for this particular exercise:

• proportion_of_forested_within_60m_of_den / verification_proportion_of_forested_within_60m_of_den
• distance_to_less_than_40_yr_forest / verification_distance_to_less_than_40_yr_forest
• distance_to_greater_than_40_yr_forest / verification_distance_to_greater_than_40_yr_forest
• distance_to_nearest_built_road / verification_distance_to_nearest_built_road

Don't see any other columns that have a 'verified' column to go with it.

[popovs]

Note there are 4 columns at the end of the dataset that have nearly 100% overlap with the above-mentioned verification columns:

• VProportion_Forested_str
• VDistance_Less40YrForest_str
• VDistance_Grtr40YearForest_st
• VDistance_Nearest_Road_str

There are two records where the values in the verification columns don't line up with the values in the 'V' columns at the end:

• OBJECTID 430 - verification_* columns are empty, but the V* cols at the end are not null
• OBJECTID 433 - vise versa - verification_* columns are not null, but the V* columns are

So, for OBJECTID 430, took the values from the V* columns and filled in the verification_* cols with those values. *The redundant `V` cols should be deleted going forward.**

• [ ] Delete redundant V* columns at the end of the table

[popovs]

Need review: what to do in cases where verification column is NOT null but the original value is?

[popovs]

After meeting with Mary:

• Prioritize the 2023 NULL values first - they need to be filled in for the field teams to be able to see those values in the field for this (2024) season
• For cases where the verification column is NOT NULL but the original raw/field value IS NULL, just leave blank for 2023 for field crews to fill out. Then post-field can backfill to previous years once field verfiied