Skip to main content
Solved

Target attribute containing a colon with TestFilter

  • February 8, 2023
  • 4 replies
  • 23 views
L

I have loaded some features from an Open Street Map file (.OSM). Some features have the attribute "oneway" and "oneway:bicycle". I'm a able to create a test clause targeting "oneway". When I try to do the same for "oneway:bicycle", I get an error: "Specified attribute does not exist" (see image at the end).

 

This causes the software to show a warning before running the workflow. Strangely enough, the filter is applied perfectly fine! Am I doing something wrong? Or can the warning maybe be a bug?

 

fme-issuefme-issue2

Best answer by ebygomm

Is the attribute actually exposed? Just because it is available in the feature information window doesn't mean it's available on the canvas. It does exist, hence why your workflow still runs, despite the warning, but if it's not exposed you can't reference it in a transformer

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

dustin
Influencer
Forum|alt.badge.img+31
  • dustinInfluencer
  • Influencer
  • February 8, 2023

Try exposing oneway:bicycle prior to your TestFilter using an AttributeExposer.

ebygomm
Influencer
Forum|alt.badge.img+46
  • ebygommInfluencer
  • Influencer
  • Best Answer
  • February 8, 2023

Is the attribute actually exposed? Just because it is available in the feature information window doesn't mean it's available on the canvas. It does exist, hence why your workflow still runs, despite the warning, but if it's not exposed you can't reference it in a transformer

L
  • lucz
  • Author
  • February 8, 2023

Try exposing oneway:bicycle prior to your TestFilter using an AttributeExposer.

That did the trick, thank you!

L
  • lucz
  • Author
  • February 8, 2023

Is the attribute actually exposed? Just because it is available in the feature information window doesn't mean it's available on the canvas. It does exist, hence why your workflow still runs, despite the warning, but if it's not exposed you can't reference it in a transformer

Adding the AttributeExposer did indeed work, thank you!

Community Stats

32,154
Posts
122,048
Replies
39,812
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.