The Coincident Boundary Model is based on the concept of using common geography to represent multiple features. To accomplish this, a linear feature class is created in the geodatabase that stores all boundary features. Then, a destination table is created that stores feature designations for each boundary. For example, a single cadastral line that represents parcel, lot and subdivision line in the real world will have three associated records in the destination table; one for parcel, one for lot and one for subdivision. Furthermore, a separate table will be introduced that contains cartographic prioritization rules defining which feature symbology will be used to draw the line. If priority is given to subdivision line over the others, the shared boundary will be drawn using the subdivision boundary symbology.
After making changes, existing feature classes can be rebuilt by querying and extracting lines attributed with the appropriate features from the cadastral line layer. The feature class can then be used to manage polygon features with coincident boundaries. Because coincident polygon boundaries can be derived from the same geometry of the line, there is less chance for topology issues across data layers.