{"id":178571,"date":"2012-03-28T22:34:47","date_gmt":"2012-03-29T05:34:47","guid":{"rendered":"http:\/\/www.esri.com\/arcgis-blog\/?post_type=blog&p=178571"},"modified":"2021-10-17T14:18:55","modified_gmt":"2021-10-17T21:18:55","slug":"invalid-geometry-check-explained","status":"publish","type":"blog","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/data-reviewer\/data-management\/invalid-geometry-check-explained","title":{"rendered":"Invalid Geometry Check Explained\u2026"},"author":288792,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_acf_changed":false,"_searchwp_excluded":""},"categories":[23851,22941],"tags":[38701,27971,155352],"industry":[],"product":[37001,36991],"class_list":["post-178571","blog","type-blog","status-publish","format-standard","hentry","category-data-management","category-mapping","tag-data-collection-and-management","tag-editing","tag-quality-assurance","product-data-reviewer","product-arcgis-desktop"],"acf":{"short_description":"What exactly does Data Reviewer\u2019s Invalid Geometry check find? Before I provide an answer, let\u2019s explore how invalid geometries are introduced","flexible_content":[{"acf_fc_layout":"content","content":"

What exactly does Data Reviewer\u2019s\u00a0Invalid Geometry<\/a>\u00a0check find? Before I provide an answer, let\u2019s explore how invalid geometries are introduced in your geodatabase in the first place. Typically loading data from shapefiles or CAD files can introduce invalid geometries. When data is migrated into an enterprise geodatabase using the simple loader invalid geometries such as empty, null, and no envelope will be filtered. However, if you\u2019re using a third party data\u00a0migration tool, all features including invalid geometries could be migrated. Similarly, when importing data into a personal or file geodatabase all geometries will be copied over. While the\u00a0Check Geometry<\/a>\u00a0geoprocessing tool reports such geometry problems, it only works on shapefiles and personal or file geodatabases, and not on enterprise geodatabases. That\u2019s where Data Reviewer\u2019s Invalid Geometry check is helpful.<\/p>\n

\"\"<\/a><\/p>\n

The check returns features that meet one of the following conditions:<\/p>\n

1. Nothing<\/p>\n

2. Empty<\/p>\n

3. Has an empty envelope<\/p>\n

4. Not simple<\/p>\n

Okay, so what do these conditions mean?<\/strong><\/p>\n

Let me address the first three conditions as they are somewhat related.\u00a0 You might ask, \u201cif they are related why is Data Reviewer reporting these issue(s) independently?\u201d For each feature the three conditions have different meanings. Furthermore, the issues\u00a0could have been caused by different workflow errors. As a user, all you really need to know is that the feature has no geometry.\u00a0 However, I\u2019d like to explore these conditions a bit more and\u00a0provide a brief description of each.<\/p>\n

Nothing<\/em><\/p>\n

The feature has\u00a0nothing<\/strong>\u00a0in the\u00a0SHAPE field<\/strong>\u00a0(SHAPE = <Null><\/em>). This type of error is returned\u00a0when Data Reviewer is unable to retrieve the geometry information for that feature.<\/p>\n

Empty geometry<\/em><\/p>\n

The geometry of a feature is considered empty if it has\u00a0zero or no points<\/strong>\u00a0and it does not contain geometric information (represented by\u00a0SHAPE _LEN\u00a0<\/em>and\/or\u00a0SHAPE_AREA\u00a0<\/em>fields) beyond its original initialization state.<\/p>\n

Note:<\/strong><\/em><\/p>\n

 <\/p>\n