HOW TO
Representation geometry overrides were a feature in ArcMap that allowed users to create and store secondary versions of feature geometry within a single feature class. This was often used to store generalized versions of features for display in maps at smaller scales. Updates to the data such as feature additions or deletions were performed in one feature class.
The ability to create representations and geometry overrides is not a feature of ArcGIS Pro, but the functionality of creating secondary geometries and propagating updates to the necessary layers can be replaced by an alternative workflow using multiple feature classes and joins. Additionally, while Representation required a geodatabase, this approach is usable with a wider variety of data sources, such as shapefiles.
This workflow requires two key components:
When data is added or deleted in the primary database, the changes must be propagated to the secondary databases. This is possible using selection queries and joins, which join multiple tables via a common field known as a key. A field of unique values must be present in the primary data to act as the key, and the key is used to create joins between the primary and secondary databases. While any unique identifier will work as a key, the Global ID and GUID data types may be useful options. See additional information about these datatypes to review their applications and limitations before deciding to use them.
The following steps illustrate how to create a primary database, generate a secondary database modified by the Disperse Markers geoprocessing tool, and propagate additions/deletions in the primary database to the secondary database using joins and a GUID field. The Disperse Markers tool is used only as an example of a geoprocessing tool that modifies the input data; any other such tool is compatible with this workflow.
POIs_primary.GUID IS NULL
Note:
Schema differences will not impact the data to be deleted from the POIs_5K data.
Note: Use the field map to reconcile field differences in case the schema of both datasets does not match.
Article ID: 000032948
Get help from ArcGIS experts
Download the Esri Support App