-
Notifications
You must be signed in to change notification settings - Fork 3
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
Source and destination count not matching #276
Comments
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? |
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. |
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:
arcpy.management.GetCount
and treat it as the destination count.add
and use them in the count checkThe text was updated successfully, but these errors were encountered: