Solved

Change detector attribute no matching problem

Forum|Forum|8 years ago
August 8, 2017
27 replies
299 views

+5

arxit
Contributor

Hi everyone,

I am using a ChangeDetector, only on one attribute "parcelle", to compare differences between polygon layers, but there is a problem because all of the polygons are detected as "changed" (then they should not, because values of "parcelle" attributes are the same in the two layers) :

Port 1 (Added) :

Port 2 (Deleted) :

I thought that the problem was because of the encoding of these attributes. So I have tried to use the AttributeEncoder Transformer, but it changes nothing :

I also have tried a FeatureMerger on these attributes and it works.

Thank you.

Aurélien

Best answer by trentatsafe

Hello @arxit,

Are you able to attach your workspace or a sample of the data(1feature from each source to an FFS file would work)?

Secondly, on one of the images, 'pict-1.png' it almost appears that there is whitespace at the end of the value so rather than '1391' it looks like it could be '1391 '. Are you able to just verify this? I think I may just be seeing things/stretching it.

Show first post

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.

1
2

Forum|pagination.label 2 / 2

+5

arxit
Author
Contributor
Forum|Forum|8 years ago
August 9, 2017

The AttributeTrimmer suggested yesterday would've fixed your problem.

Yes, it works. I didn't try it yesterday (i had seen only suggestion about StringFormatter, sorry)

Upvote

+49

ebygomm
Evangelist
Forum|Forum|8 years ago
August 9, 2017

Hello @arxit,

Are you able to attach your workspace or a sample of the data(1feature from each source to an FFS file would work)?

Secondly, on one of the images, 'pict-1.png' it almost appears that there is whitespace at the end of the value so rather than '1391' it looks like it could be '1391 '. Are you able to just verify this? I think I may just be seeing things/stretching it.

I guess the next question is should the featuremerger merge when one attribute has a trailing space and one doesn't....

Upvote

1
2

Forum|pagination.label 2 / 2

Community Stats

Sign up

An FME Account is required to contribute

Login to the community

An FME Account is required to contribute

Scanning file for viruses.

This file cannot be downloaded