Skip to main content
Question

Merging feature

  • April 20, 2018
  • 4 replies
  • 9 views
L
Forum|alt.badge.img

Hello,

I have 4 data sets, parcels(polygon), parcel numbers(point), building(polygon) and building numbers(point). On output end i need to have 1 data set (polygon) combined from all 4 input data sets with attribute table. I assigned parcel numbers to parcels using NeighborFinder, and building numbers to building using another NeighborFinder. Now i need to combine Parcels and buildings into one data set.

I have exception where building is a parcel and in this case i need to have parcel_id and building_id in attribute table, i any other case parcel have parcel_id but building_id need to be null or missing, and buildings building_id and null or missing for parcel_id. I tried FeatureMerger but i don't have any attributes to join on to. When i connect my outputs to inspector i get closely what I need, is there any transformer that do what inspector does?
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

1
Forum|alt.badge.img+1
  • 1spatialmary
  • 59 replies
  • April 20, 2018

hi @luckym - check out the InlineQuerier transformer - it lets you join multiple datasets in your workflow using SQL. So each input dataset becomes a table in the temporary database (SQLite), and then you can write SQL statements to define the output(s)

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • April 20, 2018

Hi @luckym, I don't think you need to add any other transformers to the workspace, since the Inspector has output your desired table to FME Data Inspector already. Try replacing the Inspector with a writer feature type to write the table into a single dataset.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
L
Forum|alt.badge.img
  • luckym
  • Author
  • 39 replies
  • April 20, 2018

hi @luckym - check out the InlineQuerier transformer - it lets you join multiple datasets in your workflow using SQL. So each input dataset becomes a table in the temporary database (SQLite), and then you can write SQL statements to define the output(s)

Thank you @1spatialmary, this transformer will be very useful. I will not yet accept your answer just in case someone else has any other idea.

 

L
Forum|alt.badge.img
  • luckym
  • Author
  • 39 replies
  • April 20, 2018

Hi @luckym, I don't think you need to add any other transformers to the workspace, since the Inspector has output your desired table to FME Data Inspector already. Try replacing the Inspector with a writer feature type to write the table into a single dataset.

Hi @takashi, I need to do some additional work before i can write out my data that is why i need my data in one dataset before writing out, but thank you for your answer.

Community Stats

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