Skip to main content
Question

Dissolving Multiple Feature Classes with dissolver separately.

  • January 17, 2016
  • 3 replies
  • 82 views
A

Hi FMRs,

I want to dissolve 300+ Area feature classes separately, will only one dissolver be necessary or do I have to dissolve every class separately? If only one dissolver is ok then how do I separate these feature classes and update respective feature classes in the database.

I'm currently using GeometryFilter to combine all the database and using only Area feature port. I've to run it on multiple datasets. Some of the datasets have features in these feature classes while other don't have.

Any Ideas?

Thanks.

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.

3 replies

J
Forum|alt.badge.img+7

Hi ali,

You can use one Dissolver to dissolve based on a specific attribute by using the 'Group By' setting.

Below you can find an example of a workspace using some testdata. Is this an answer on you question?

On the figure below, the input (TOP) and output (BOTTOM) are visualised.

A
  • ali
  • Author
  • January 17, 2016

Hi ali,

You can use one Dissolver to dissolve based on a specific attribute by using the 'Group By' setting.

Below you can find an example of a workspace using some testdata. Is this an answer on you question?

On the figure below, the input (TOP) and output (BOTTOM) are visualised.

Hi @jeroenstiers

I'm currently using the same technique, the problem lies afterwords. some feature classes are empty in some datasets while in others there are features. when I use FeatureTypeFilter, it gives me every feature class from the original dataset including lines and points.

Should I just directly connect the features to the destination for update?

I still need to do lineJoiners to join lines.

and what about the attributes

For the time being, I'm using fme_feature_type as my groupby option.

Thanks

J
Forum|alt.badge.img+7

Hi @jeroenstiers

I'm currently using the same technique, the problem lies afterwords. some feature classes are empty in some datasets while in others there are features. when I use FeatureTypeFilter, it gives me every feature class from the original dataset including lines and points.

Should I just directly connect the features to the destination for update?

I still need to do lineJoiners to join lines.

and what about the attributes

For the time being, I'm using fme_feature_type as my groupby option.

Thanks

I am not sure what you are looking for exactly but if you would like to store the features in the appropriate datasets, maybe the fanout-option might help you?

Community Stats

32,750
Posts
124,202
Replies
41,254
Members
Terms & ConditionsAccessibility 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.