Skip to main content
Question

Personal geodatabase multi arc feature differences between ArcGIS and FME

  • February 19, 2018
  • 3 replies
  • 14 views

jorge_rosales
Contributor
Forum|alt.badge.img+8

I have a multi-arc feature in ArcGIS (4 parts) but FME treats it differently. Any suggestion?

The personal geodatabase:

Thanks in advance.

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

david_r
Celebrity
  • 8394 replies
  • February 19, 2018

Just based on your screenshot I'm guessing that "Parte 1" (in the ArcGIS screenshot) got collapsed into a single point by FME and then removed since it was no longer a line segment.


jorge_rosales
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • 44 replies
  • February 19, 2018

Just based on your screenshot I'm guessing that "Parte 1" (in the ArcGIS screenshot) got collapsed into a single point by FME and then removed since it was no longer a line segment.

For quality control purpouses that behavior could be a problem because I can´t check "Parte 1" related issues. Is there a way to avoid the collapse? Any suggestion about the nested elements in "Part 0" (FME)?

 

 


david_r
Celebrity
  • 8394 replies
  • February 19, 2018
For quality control purpouses that behavior could be a problem because I can´t check "Parte 1" related issues. Is there a way to avoid the collapse? Any suggestion about the nested elements in "Part 0" (FME)?

 

 

I agree completely about the quality control aspect, but unfortunately I don't know the answer in this case. You should contact Safe support for this issue. Link them to this post as well.

 

 

On a general note: I work a lot with datasets containing arcs and they are a constant source of problems. I've heard that FME 2018 will have a lot of improvements in this regard, but I haven't had the chance to test yet.

 

 

There is an outstanding issue in FME 2017.1.2.1 with arc definitions that sometimes change when writing to ArcSDE Geodatabases, but I'm not sure if it's linked to the behavior you're observing.