Skip to main content
Question

Geometry validator: 1 input but multiple outputs... why?


benji
Contributor
Forum|alt.badge.img+4
  • Contributor

Capture

Can anyone please explain why with only 1 feature being read, more than 1 can fail? Any help would be highly appreciated!

Many thanks!!

4 replies

mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • August 25, 2020

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.


benji
Contributor
Forum|alt.badge.img+4
  • Author
  • Contributor
  • August 26, 2020
mark2atsafe wrote:

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?FME01

FME02


ebygomm
Influencer
Forum|alt.badge.img+32
  • Influencer
  • August 26, 2020
benji wrote:

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?FME01

FME02

"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


laddysmurf19
Contributor
Forum|alt.badge.img+1

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?
 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings