There are many topology rules you can implement in your geodatabase, depending on the spatial relationships that are most important for your. Errors in GIS data mean any information or decisions based on that data are flawed. Geodatabase topology provides an automated, rule-based solution to. Topology in ESRI® ArcGIS® allows you to model spatial relationships between feature model. Topology errors are violations of the rules that you can easily.
|Published (Last):||9 March 2017|
|PDF File Size:||19.87 Mb|
|ePub File Size:||9.75 Mb|
|Price:||Free* [*Free Regsitration Required]|
The Subtract fix removes the overlapping portion of each feature that is causing the error so the boundary of each feature from both feature classes is the same. Note that applying the Simplify fix can result in multipart features.
If you want one multipart feature as a result, you will need to select each new feature and click Merge from the Editor menu. The Arcgiw fix removes line features that would collapse during the validate process based on the topology’s cluster tolerance.
You can also use Create Feature or mark the error on the outside boundary as an dules. Any polygon feature, such as the one in red, that would collapse when validating the topology is an error.
ArcGIS Desktop Help – Topology rules
A bus route feature class must not depart from the streets defined in the street feature class. This is useful for modeling logically different but spatially coincident lines, such as routes and streets.
This fix can be applied to one or more Must Be Single Part errors. The Subtract fix removes line segments that are not coincident with the boundary of polygon features. This rule is used where line segments should not be duplicated, for example, in a stream feature class. This geodqtabase can be applied to one or more Must Not Intersect errors. For steps to validate a geodatabase topology and fix errors, see Validate and fix geodatabase topology.
The Create Feature fix adds a new point feature at the endpoint of the line feature that is in error. Points in one feature class or subtype must be covered by lines in another feature class or subtype. They can cross or touch themselves but must not have coincident segments. Geodatxbase rule is used when there argis lines from two layers that should never cross each other or in cases topoolgy the intersection of lines should only occur at endpoints, such as streets and railroads.
Requires that a line in one feature class or subtype must only touch other lines of another feature class or subtype at endpoints.
This rule is used when an area cannot belong to two separate feature classes. Points in one feature class or subtype must touch boundaries of polygons from another feature class or subtype. This is useful for cases where points must be covered by other points, such as transformers must coincide with power poles in electric distribution heodatabase and observation points must coincide with stations.
Use this rule when points within one feature class or subtype should never occupy the same space, for example, when fittings in a water distribution network should not overlap. This could be used, for example, to require street features to be connected to other street features at both ends, except in the case of streets belonging to the topo,ogy or dead-end subtypes.
Where a red point and a blue point overlap is an error. This rule is useful for points that fall along a set of lines, such ruls highway signs along highways.
It does not constrain the covering portion of the line to be an endpoint. Requires that line features from one feature class or subtype not cross or overlap lines from another feature class or subtype. Requires that lines from one feature class or subtype must be covered by the lines in another feature class or subtype.
Requires that the endpoints of line features must be covered by point features in another feature class. Use this rule on data that must completely cover an area. The square on the right indicates an error because it is a point that is not on the boundary of the polygon.
This rule is used when line features must form closed loops, such as when they are defining the boundaries of polygon features.
This rule is used where line features must form closed loops, such as when they define the boundaries of polygons or when line features logically must connect to two other line features at each end, as with segments in a stream network, with exceptions being marked for the originating ends of first-order streams.
Geodatabase topology rules and topology error fixes
In instances where this rule is violated, the original geometry is left unchanged. For example, parcels might be stored in the geodatabase along with their boundaries. Also, if several errors were selected, the fix will simply skip the features that it cannot extend and attempt to extend the next feature in the gdodatabase.
Points cannot overlap within the same feature class or subtype.
Requires that points in one feature class be covered by lines in another feature class. Requires that a line feature must touch lines from the same feature class or subtype at both endpoints.
Geodatabase topology rules and topology error fixes—Help | ArcGIS for Desktop
A well-designed geodatabase will have only those topology rules that define key spatial relationships needed by an organization. Requires that line features from the same feature class or subtype not cross or overlap each other. An endpoint that is not connected to another line is called a dangle.