Skip to main content
Solved

File GDB Reader vs Geodatabase Bug - Null Geometry

  • January 19, 2018
  • 3 replies
  • 8 views
dfresh
Forum|alt.badge.img

I think this could be either a bug, or an issue with my understanding.

image below, why would the exact same feature class, put through the exact same geometry validator yield different results between readers

  • Top scenario in image is with Geodatabase File Reader
  • Bottom in image, is with File GDB reader

Best answer by takashi

Hi @dfresh, I think it has been caused by a difference between implementations of extrenal libraries - Esri ArcObjects (GEODATABASE_FILE) and File Geodatabase Open API (FILEGDB). Esri ArcGIS has some tolerance internally, so I suspect that the GEODATABASE_FILE reader (Arc Objects) could repair invalid geometries implicitly in some cases.

I'm interested in what happens if you insert the ArcSDEGridSnapper after the FILEGDB reader.

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

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • Best Answer
  • January 20, 2018

Hi @dfresh, I think it has been caused by a difference between implementations of extrenal libraries - Esri ArcObjects (GEODATABASE_FILE) and File Geodatabase Open API (FILEGDB). Esri ArcGIS has some tolerance internally, so I suspect that the GEODATABASE_FILE reader (Arc Objects) could repair invalid geometries implicitly in some cases.

I'm interested in what happens if you insert the ArcSDEGridSnapper after the FILEGDB reader.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
david_r
Celebrity
  • david_rCelebrity
  • 8394 replies
  • January 22, 2018

Hi @dfresh, I think it has been caused by a difference between implementations of extrenal libraries - Esri ArcObjects (GEODATABASE_FILE) and File Geodatabase Open API (FILEGDB). Esri ArcGIS has some tolerance internally, so I suspect that the GEODATABASE_FILE reader (Arc Objects) could repair invalid geometries implicitly in some cases.

I'm interested in what happens if you insert the ArcSDEGridSnapper after the FILEGDB reader.

I agree. Maybe even try a CoordinateRounder after both of the readers and before the GeometryValidators..
tim_wood
Contributor
Forum|alt.badge.img+8
  • tim_woodContributor
  • Contributor
  • 311 replies
  • January 25, 2018

What happens if you attach a GeometryFilter to each Reader?

Are they single part or multi-part features? Would de-aggregating help?

Note also that the ordering of the issues in the GeometryValidator can change the output geometries.

These links may also be useful:

https://knowledge.safe.com/articles/173/what-is-the-arcsdegridsnapper.html

http://edndoc.esri.com/arcsde/9.3/concepts/geometry/shapes/verificationrules.htm

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//006z00000028000000

Community Stats

32,087
Posts
121,857
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.