Skip to main content
Question

AttributeKeeper does not keep coordinates

  • June 27, 2016
  • 4 replies
  • 27 views
G

I'm try to establish an SHP-Minecraft translation, but in the 2016 version of FME, I had some trouble with the AttributeKeeper. I have an input SHP (point), connected with a coordinate extractor. After that, I attached an AttributeKeeper. I want to keep some SHP attributes, and the coordinates, extracted by the CoordinateExtractor. For some reason, the Keeper lost the XYZ coordinates. If I took try the same in FME 2015, the keeper will keep the attributes. Is it a version error, or I missed something?

The following pictures shows the connection, and the settings. In the keeper, I cannot tick the mother attribute, just the children attributes (XYZ).

Thanks for your help.

Bálint

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.

4 replies

M
Forum|alt.badge.img+5

Hi @gulkhanra

Because the x/y/z are being extracted as a 'list' type of attribute, instead of using the Attributes to Keep parameter, you should use the Lists to Keep parameter, like so:

Hope this helps

Mark

takashi
Celebrity
  • takashiCelebrity
  • June 28, 2016

Hi @gulkhanra, alternatively you can use the 'Specify Coordinate' option for the 'Mode' parameter. The transformer with this mode is equivalent to the one in FME 2015 and earlier.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
takashi
Celebrity
  • takashiCelebrity
  • June 28, 2016

Hi @gulkhanra, alternatively you can use the 'Specify Coordinate' option for the 'Mode' parameter. The transformer with this mode is equivalent to the one in FME 2015 and earlier.

In addition, it might be better if the AttributeKeeper could be improved to expose list elements which the user specify in the 'Attributes to Keep' parameter.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
G
  • gulkhanra
  • Author
  • June 29, 2016

Thank you guys:)

 

I tried both, and both is good, but I prefered the AttributeKeeper version:)

 

I' can proceed now with my research:)

 

Thanks again:)

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.