Skip to main content
Solved

Associate Appearance to surface base on feature attribute

  • November 22, 2017
  • 2 replies
  • 40 views
J

Greetings FME Community!

I have a CityGML of buildings [1] and I want to attach new textures to the roof surfaces.

The Appearance should be a texture based on a specific GeoTIFF that was generated for every buildings.

Every GeoTIFF has the CityGML feature unique id as name. I don’t find a way to save every texture in the FMELibray and, mostly, retrieve the right Appearance for every feature of the CityGMLd to

I think this should be related to the AppearanceSetter [2] settings or SharedItemRetriever [3], but I can't figure how to use them properly.

 

Kind regards,

 

[1] http://donnees.ville.montreal.qc.ca/dataset/maquette-numerique-plateau-mont-royal-batiments-lod2-avec-textures

[2] https://docs.safe.com/fme/2017.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/appearancesetter.htm

[3] https://docs.safe.com/fme/2017.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/shareditemretriever.htm

Best answer by takashi

Hi @jeandenis, this workflow illustrates how you can register rasters to the FME Library, retrieve one of them according to its name (unique id), and then map it to surface features as a texture appearance.

However, depending on the scenario, this workflow could work as well.

Hope this helps.

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.

2 replies

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • Best Answer
  • November 23, 2017

Hi @jeandenis, this workflow illustrates how you can register rasters to the FME Library, retrieve one of them according to its name (unique id), and then map it to surface features as a texture appearance.

However, depending on the scenario, this workflow could work as well.

Hope this helps.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
J
  • jeandenis
  • Author
  • 2 replies
  • November 23, 2017

Thank you @takashi !

The variable usage is quite insightful.

I only try the first solution because it seems much more generic than the second.

Best regards,

Community Stats

32,087
Posts
121,869
Replies
39,731
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.