Skip to main content
Solved

Boundary and geometryname

  • September 28, 2015
  • 5 replies
  • 39 views
M
Forum|alt.badge.img
Hi everyone,

 

 

Is it possible to change geometry names for a boundary too? I used the GeometryPropertySetter to set the GeometryName and Traits (see pic below), but it also changes the geometry name for the Boundary IFMELine. I want to set the name for the boundary to curveMember (see Example 2nd pic).

 

The Problem is, that FME is creating a LinearRing for an ElevatedSurface, but i need an GeodesicString. I hope that the geometryname will help me with that.

 

 

My geometry:

 

 

It should look similar to this:

 

 

 

thanks,

 

Mel

Best answer by takashi

Hi Mel,

 

 

You can specify a geometry part which should be overwritten its name, through the Geometry XQuery parameter of the GeometryPropertySetter.

 

For example, this setting specifies polygon boundary (i.e. child of a polygon).

 

 

 

Takashi
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.

5 replies

takashi
Celebrity
  • takashiCelebrity
  • Best Answer
  • September 29, 2015
Hi Mel,

 

 

You can specify a geometry part which should be overwritten its name, through the Geometry XQuery parameter of the GeometryPropertySetter.

 

For example, this setting specifies polygon boundary (i.e. child of a polygon).

 

 

 

Takashi
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
M
Forum|alt.badge.img
  • me1
  • Author
  • September 29, 2015
Thank you! Sadly it didn't work for the GeodesicString but I think I am on the right path.

 

Do you know if its possible to insert an IFMEPath before my IFMELine? So that it looks like the second picture?

 

 

Meli
takashi
Celebrity
  • takashiCelebrity
  • September 29, 2015
A possible way I can think of is:

 

- decompose the multi area into individual polygons (Deaggregator),

 

- transform the polygons into lines (GeometryCoercer),

 

- build paths from the lines (PathBuilder, Connection Break Attributes: feature ID, _part_number),

 

- build polygons from the paths (AreaBuilder, Group By: feature ID, _part_number),

 

- aggregate the polygons to restore multi area  (Aggregator, Group By: feature ID).

 

 

Assuming that the original multi area feature has unique feature ID attribute and there isn't donut geometry.

 

If there were donut geometries, it would be a little complicated.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
takashi
Celebrity
  • takashiCelebrity
  • September 29, 2015
Note that the original attributes other than feature ID will be lost through the reconstructing procedure. If you need to preserve the original attributes, consider merging them after reconstructing by the FeatureMerger, using the feature ID as the "Join On" attribute.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
M
Forum|alt.badge.img
  • me1
  • Author
  • September 29, 2015
Thank you again, its working :)

Community Stats

32,154
Posts
122,043
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.