Skip to main content
Solved

File GDB Reader vs Geodatabase Bug - Null Geometry


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.

View original
Did this help you find an answer to your question?

3 replies

takashi
Contributor
Forum|alt.badge.img+19
  • Contributor
  • 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.


david_r
Evangelist
  • January 22, 2018
takashi wrote:

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
  • Contributor
  • 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


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings