Open edwardsmarc opened 1 month ago
Thanks for flagging these layers Marc.
Looking at T_NAT_ECCC_SAR_NOS_COSEWIC_882
.
The source data is an oval with 1 vertex
When I intersect with the vector grid, it creates a bunch of these slivers and a random little oval:
So this is whats causing the values on the edge of the range to > 100. Some double, tripping counting going on.
I dissolve the feature, and its still giving those slivers. Really odd. Is this some weird bug in Pro?
I am currently using arcpy.analysis.Intersect
. I tried arcpy.analysis.PairwiseIntersect
and it gave the expected output
Still need to wrap my head around the difference between the two different intersect tools in Pro...
Looking at T_NAT_ECCC_CH_END_COSEWIC_846
There are two polygons that overlap. This is causing a double count to 200 ha.
This turtle has two SARA status, 3 & 2 whic must be an error in the source data?
The recovery strategy doc says this turtle is threated (SARA 3) https://wildlife-species.canada.ca/species-risk-registry/virtual_sara/files/plans/rs_blandings_turtle_e_final.pdf
Found a few more with same COSEWIC ID but different SARA status OR different English names: CH
Looking at T_NAT_ECCC_CH_THR_COSEWIC_951
the Chimney swift data are tiny little circles. Likely buffers around nests?
Found 3 ECCC layers where the values get set to objectid values due to a bug in the python prep script. Found these using:
Layers that need fixing are:
T_NAT_ECCC_CH_END_COSEWIC_846
T_NAT_ECCC_CH_THR_COSEWIC_951
T_NAT_ECCC_SAR_NOS_COSEWIC_882