Skip to content

Conversation

@fabanc
Copy link

@fabanc fabanc commented Nov 16, 2017

Some null geometries seem to be generated. They appear at step 6.5 even though the content read by the search cursor is actually populated at step 5. My take is that the if a geometry is smaller then the feature class tolerance or resolution a null geometry replaces the geometry written in step 5, and is read at step 6.5. The code change allows the code to display a warning with the problematic way_id at step 6.5 and keep working instead of terminating with an error.

Some null geometries seem to be generated. They appear at step 6.5 even though the content being read by the search cursor is actually populated at step 5. My take is that the if geometry is smaller then the feature class tolerance or resolution a null geometry replaces the geometry written in step 5, and is read at step 6.5. The code change allow the code to display a warning with the problematic way_id and keep working instead of crashing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant