Can anyone please explain why with only 1 feature being read, more than 1 can fail? Any help would be highly appreciated!
Many thanks!!
Question
Geometry validator: 1 input but multiple outputs... why?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+58- Safer
I'm not totally sure, but it could be the one feature failing for different reasons. The IssueLocations port is probably highlighting where the problems occur (like that feature failed with a problem in 265 locations). The invalid parts is similar, highlighting which parts of the feature are bad. If it's an aggregate feature (composed of multiple geometric elements) that might also explain why there are multiple outputs. In short, I think you'd need to visually inspect the output to see what it is composed of.
+4- Contributor
I'm not totally sure, but it could be the one feature failing for different reasons. The IssueLocations port is probably highlighting where the problems occur (like that feature failed with a problem in 265 locations). The invalid parts is similar, highlighting which parts of the feature are bad. If it's an aggregate feature (composed of multiple geometric elements) that might also explain why there are multiple outputs. In short, I think you'd need to visually inspect the output to see what it is composed of.
Many thanks @mark2atsafe . The feature I'm trying to read is an aggregated feature indeed. My problem is weather it is deaggregated or not, the feature is clean prior to writing (image 1), while the simple fact of writing and reading it (ESRI feature class in file geodatabase) makes all these problems appear whether I'm reading the feature as aggregated or deaggregated (image 2). Would you have any idea on how writing the feature could generate errors?
+45- Influencer
Many thanks @mark2atsafe . The feature I'm trying to read is an aggregated feature indeed. My problem is weather it is deaggregated or not, the feature is clean prior to writing (image 1), while the simple fact of writing and reading it (ESRI feature class in file geodatabase) makes all these problems appear whether I'm reading the feature as aggregated or deaggregated (image 2). Would you have any idea on how writing the feature could generate errors?
"Would you have any idea on how writing the feature could generate errors?"
Because it's ESRI :-)
The coordinates that are written in the geometry in the feature class will not necessarily exactly match the coordinates that exist in the feature prior to writing, it is influenced by the XY tolerance and resolution settings
+1- Contributor
I am having this issue currently. I’m inputting Russia as 15 shapes, but it’s like the geometry validator deaggregates the shapes, and the 1,511 shapes are all the small islands around Russia. to make it all the more interesting, im writing this out to a SQL Server and somehow Russia covers the entire world?
