Source and destination count not matching

[keatonwalker]

There is a PLSSQuarterSections_GCDB polygon that has zero area but some length. Although the polygon is messed up, it doesn't come back None in _hash. After project_management happens, the bad polygon turns into a null geometry.

Here are 3 possible solutions:

1. Check the count after project with arcpy.management.GetCount and treat it as the destination count.
2. Count null geos exlcuded in add and use them in the count check
3. Let null geo into the destination data and keep counting as we are now.

[steveoh]

Skipping 3 because it's bad™, what would the implementations look like for 1 and 2?

What would the breakdown be in speed, simplicity, and development difficulty?

[steveoh]

@keatonwalker 🚪✊

[keatonwalker]

Although 2 is a little more complex than the others, I like it best. It seems like the way to get the most accurate information.

We will have to count every time the null check in adds is hit for a crate, then pass the null count into _check_counts to be added to the destination_rows count.