Solved

AttributeCreator eating features

  • 10 October 2019
  • 8 replies
  • 0 views

Userlevel 1
Badge +21

I'm using the attribute creator to create a new attribute from the value of an existing and setting the value to another attribute. 19 features go in, but only 18 come out!

This is in 2019.1.0.0 (Build 19608 WIN32) - same process works fine in 2018.1

icon

Best answer by hollyatsafe 21 October 2019, 19:34

View original

8 replies

Badge +21

What is the value of the 19 features on the Group attribute? I suspect that there might be an empty row or somethinging in the excel-sheet?

Userlevel 4

Seems to work fine in FME 2019.1.2.0

Badge

Seems to work fine in FME 2019.1.2.0

And in 2020 Beta

Badge +21

Also ok on FME 2019.0.0.0 (20190328 - Build 19238 - WIN64)

Userlevel 4

Seems to work fine in FME 2019.1.2.0

Also tested OK with FME 2019.0.1.0

Badge +2

Hi @egomm,

I can reproduce the issue with the attached workspace - it looks like this also happens if I use the AttributeManager. Interestingly if I put certain transformers before the AC, e.g. Decelerator, then all 19 features seem to pass through. However if I put a Tester before it, and input both the Passed and Failed port I lose 2 features, or TestFilter with 3 output ports, 3 features lost etc. So there is something very odd going on here!

I have tested in b19630, b19778 and b20090 Mac OS so I'll file an issue for this and let you know if I find anything else.

Userlevel 1
Badge +21

Hi @egomm,

I can reproduce the issue with the attached workspace - it looks like this also happens if I use the AttributeManager. Interestingly if I put certain transformers before the AC, e.g. Decelerator, then all 19 features seem to pass through. However if I put a Tester before it, and input both the Passed and Failed port I lose 2 features, or TestFilter with 3 output ports, 3 features lost etc. So there is something very odd going on here!

I have tested in b19630, b19778 and b20090 Mac OS so I'll file an issue for this and let you know if I find anything else.

Thanks, I often use the AttributeCreator like this and didn't notice any issues when I moved over to 2019 (but i haven't looked closely). I was just creating a simple example to share with a colleague when I found this.

Badge +2

Hi @ebygomm,

The issue with the AttributeCreator/Manager dropping features has now been resolved and was verified fixed in b19643, b19785 and b20105. You can download the latest betas here.

Reply