Skip to main content
  • EN

Hi!

I have an issue that I just don't understand.

 

Using a FeatureMerger that outputs the correct attributes från the supplier, but it's values are all wrong.

 

First off, I have a TestFilter with output ports depending on if the attribute "Version" is 0, 1 or 2. In this case the output for Version 2 contains 4 points with relevant attributes according to the image below. They are all "Version" 2 and have missing values for "Avslut-datum".

Testfilter outputNext, I want to use a FeatureMerger to merge this with a bigger database with hundreds of points, to assign the attributes of Version 2 to those said points, if they match. I want to merge the points from the bigger database srequestor] to the output from my "Version 2" tsupplier]. See the FeatureMerger parameters in the image below.

FeatureMerger parametersHowever, the merged data does not contain the attributes from "Version 2". For example the attribute "Avslut-datum" should be <missing> and the "Version" attribute should be "2". Note that the attributes "Version" and "Avslut-datum" does not exist in the requestor. See image below were the point P-K-004 from the requestor has merged with the supplier.

FeatureMerger outputI just can't get my head around how the points can be assigned these attribute values that don't exist from the supplier. Somehow other values fill the attributes.

 

Hopefully, I provided enough data to understand the issue!

 

Best regards

Victor

Your Conflict Resolution is set to "Use Requestor", do those attributes exist already on the requestor?

 

In cases like this it would be very helpful if you could also show what the other data looks like.

Your Conflict Resolution is set to "Use Requestor", do those attributes exist already on the requestor?

 

In cases like this it would be very helpful if you could also show what the other data looks like.

Hi!

No the requestor does not contain any of those attributes. That's what baffles me. However, I'm pretty sure the attribute values that are seen exist earlier on before I used the testfilter. Like all the other versions that were filtered out. They somehow reappear...

​

There is of course a lot of data in the file that I'm filtering out. Any data in particular I should display?

Hi!

No the requestor does not contain any of those attributes. That's what baffles me. However, I'm pretty sure the attribute values that are seen exist earlier on before I used the testfilter. Like all the other versions that were filtered out. They somehow reappear...

​

There is of course a lot of data in the file that I'm filtering out. Any data in particular I should display?

Could it be a case of them existing on the feature, but not being exposed? As they pass through the featuremerger they're then exposed and chosen in preference to the supplier (as per your conflict resolution)

Hi!

No the requestor does not contain any of those attributes. That's what baffles me. However, I'm pretty sure the attribute values that are seen exist earlier on before I used the testfilter. Like all the other versions that were filtered out. They somehow reappear...

​

There is of course a lot of data in the file that I'm filtering out. Any data in particular I should display?

Yes, that must somehow be the case. But those attributes have never existed in the requestor, so somehow they get exposed from the supplier even though they where filtered out from the previous testfilter on the supplier side. Is that even possible? Is there away of keeping the supplier clean of whatever has been previously filtered out?

Hi!

No the requestor does not contain any of those attributes. That's what baffles me. However, I'm pretty sure the attribute values that are seen exist earlier on before I used the testfilter. Like all the other versions that were filtered out. They somehow reappear...

​

There is of course a lot of data in the file that I'm filtering out. Any data in particular I should display?

Try putting an attribute remover in. You'll have to manually enter the attribute and it will show up as red, but will be another step to ensure that attribute doesn't exist on the feature

image 

Otherwise, are you able to run the process with feature caching on (on a subset of the data) and save it as a template and share it here?

Hi!

No the requestor does not contain any of those attributes. That's what baffles me. However, I'm pretty sure the attribute values that are seen exist earlier on before I used the testfilter. Like all the other versions that were filtered out. They somehow reappear...

​

There is of course a lot of data in the file that I'm filtering out. Any data in particular I should display?

Thank for that suggestion. Right now I cannot get that error I defined in this question, which is interesting...

 

However, what I did before your suggestion was to set the Feature Merger to "prefix supplier attributed". Later on, I remove the prefix. That should do the same as removing the attribute from the requestor. They both make sure the attributes from the supplier are unique.

Still dont understand why I got this problem to start with.

 

Ill get back if the problem comes back though! Thank you! @hkingsbury​ 

Reply


Community Stats

30,120
Posts
114,320
Replies
37,748
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.