SQL Database Enterprise Geodatabase Overlapping Polygons Feature Class

Question

Hello All,

I started working with Esri GIS products around 1995. Being old school, I never create polygon feature classes that allow features to overlap each other. It’s the number one rule of topology (https://resources.arcgis.com/en/help/main/10.2/01mm/pdf/topology_rules_poster.pdf) and the fact that I started with ArcInfo coverages may have something to do with it, also. Has anyone heard of ArcInfo? Around 2006, I was responsible for converting an Autodesk MapGuide Land System to our company Esri platform that included ArcGIS Server. I guess this was around the time SDE connected ArcMap to the SQL Database. I recall when appending overlapping polygons into an existing polygon feature class, the routine would error out. In my old land system (circa 2006), that is still being used today with ArcMap 10.0, adding overlapping polygons to the enterprise geodatabase continues to error out. Somewhere along the way, Esri decided to allow overlapping polygons within a single polygon feature class, but I still don’t. Now, I am reviewing someone else’s data that is part of an ArcGIS Enterprise and I notice around 50% overlap. Most of the overlap are slivers from data that was not cleaned properly, build and clean in ArcInfo. My OCD monster wants to clean these layers for them, but maybe I should let it go as other commitments keep me very busy.

It’s so difficult to explain this concept, so I have the following questions:

* Are overlapping polygons a normal approach when building polygon feature classes today?
* What reasons could I argue for the additional time it would take to clean up all the slivers and gaps?
* What are all the issues that overlapping polygons cause in the future (i.e., spatial query, buffer, distance measurement)?
* What was Esri’s frame of mind when they decided to allow this? Chime in Esri.
* Do I look the other way and hope no issues arise later?

Will sum,

Gerry

Anonymous User · Answer

Hi @GerryGarza ,

Thank you for the information,

Do you have an option of using the land management layer as the basis of your data and then using Symbology to represent the Attributes "Owned polygon feature class, Lease polygon feature class, and Options polygon feature class" then when you visualize and analyze the map you see the polygons, and these are then highlighted by the colors.

This can be done by adding a field called Land use and then populate that field with the new data.

This can also allow you to run report and analysis on the field, so you can have the three areas separated or you can export the information into a separate export document if you want to maintain a separate report of each layer

Introduction to query expressions—ArcGIS Pro | Documentation

Export a query layer—ArcGIS Pro | Documentation

Though if two options cover one polygon area that could be tricky.

Also, Configurations of Pop-ups is very useful as well Configure pop-ups—ArcGIS Pro | Documentation

These are just some ideas that can help with future management and the expansion of your map into other aspects of the organization.

GerryGarza · Answer

Tim,

Thanks for the region reminder. This layer does not maintain time series of land (see above). I actually have a point layer that has stacked points representing a time series. It had to be done that way because management wanted to query and filter it a certain way in ArcGIS Enterprise.

Regards,

Gerry

GerryGarza · Answer

Keiren,

Thank you for your reply. In this case, all polygons are in one feature class (layer). Coordinate systems are not an issue because these layers are maintained in ArcGIS Enterprise which uses WGS 1984 Web Mercator. The layer pertains to land management and stacked features represent different instruments. There are larger owned parcels representing surface rights, minerals rights, both, and ROW easements. Then, there are also leases representing the same as for owned property and options with the same combination. My approach on my legacy system is to maintain three separate layers, Owned polygon feature class, Lease polygon feature class, and Options polygon feature class. If overlap is necessary after splitting them up, then that is acceptable.

Thanks again,

Gerry