Skip to main content
Question

Feature Merger results are not compatible with ArcGIS-Join Results

  • November 30, 2015
  • 5 replies
  • 42 views
H

I have two tables for blocks data, each block in these tables is identified by its block ID, and I want to find the unmatched blocks between these tables.

In ArcMap, I joined the two tables based on the "Block ID" fields, after validating the join, 822 out of 1496 blocks were matched.

However, I tried to do the same thing using FME, I created a workbench that reads from these two tables, and applied a feature merger on them to compare the "Block ID". However, the results were different; there was 1011 matched "merged" blocks!

I could not figure out why FME results are different from ArcGIS ones. What might be the issue here?

Best Regards,

Hani

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

erik_jan
Contributor
Forum|alt.badge.img+26
  • erik_janContributor
  • Contributor
  • November 30, 2015

Could this because of a difference in length of the BLOCK_ID field in both tables. And then FME trimming spaces from the values?

mark2atsafe
Safer
Forum|alt.badge.img+59
  • mark2atsafeSafer
  • Safer
  • December 1, 2015

It could be a number of things. I think the important part is to try and identify one of the features that FME thinks is a join but ArcGIS does not. If you can inspect one of those features (and the feature it allegedly matches to) it will help to clarify what the issue is.

FME Evangelist to the Rich and Famous!!
david_r
Celebrity
  • david_rCelebrity
  • December 2, 2015

I agree with Mark, try to find one single feature that gets a different treatment in FME and ArcGIS.

That said, I kinda suspect an encoding issue here, seeing as you're matching on (what looks like) arabic characters.

bruceharold
Supporter
Forum|alt.badge.img+19
  • bruceharoldSupporter
  • Supporter
  • January 6, 2016

Hi

Like Mark2 hinted, unicode data might be compared by collation order in a geodatabase but byte order by FME, which would cause match differences.

I'm going to pollute the forum with a pointer to an Esri sample that should help you, but hey I do plenty for Safe in my day job :-)

http://www.arcgis.com/home/item.html?id=e638afe069...

fmelizard
Safer
Forum|alt.badge.img+22
  • fmelizardSafer
  • Safer
  • February 6, 2016

Not sure if this ever got resolved. @hani_draidi -- could you send some sample data and the workspace in to support@safe.com and we'll dig in.

Community Stats

32,448
Posts
123,298
Replies
40,601
Members
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.