ARCGIS GEODATABASE TOPOLOGY RULES PDF

Dies ist eine obligatorische Topologieregel, die auf alle Polygon-Feature-Classes angewendet wird. Das Ergebnis ist eine planare Darstellung der Feature-Geometrie. Verwenden Sie diese Regel, wenn jedes Polygon in einer Feature-Class oder einem Subtype von allen Polygonen einer anderen Feature-Class oder eines anderen Subtypes abgedeckt sein sollten, z. Fehler Polygon-Fehler werden dort erstellt, wo ein Teil eines Polygons nicht durch ein oder mehrere Polygone in der anderen Feature-Class oder im anderen Subtype abgedeckt ist.

Author:Faura Gardarg
Country:Libya
Language:English (Spanish)
Genre:Literature
Published (Last):11 January 2019
Pages:265
PDF File Size:7.76 Mb
ePub File Size:7.68 Mb
ISBN:513-4-76814-714-7
Downloads:2456
Price:Free* [*Free Regsitration Required]
Uploader:Dougal



This rule is mandatory for a topology and applies to all line and polygon feature classes. In instances where this rule is violated, the original geometry is left unchanged. Any line feature, such as these lines in red, that would collapse when validating the topology is an error. Must Not Overlap Requires that lines not overlap with lines in the same feature class or subtype.

This rule is used where line segments should not be duplicated, for example, in a stream feature class. Lines can cross or intersect but cannot share segments. Subtract: The Subtract fix removes the overlapping line segments from the feature causing the error. You must select the feature from which the error will be removed. If you have duplicate line features, select the line feature you want to delete from the Subtract dialog box.

Note that the Subtract fix will create multipart features, so if the overlapping segments are not at the end or start of a line feature, you might want to use the Explode command on the Advanced Editing toolbar to create single-part features.

This fix can be applied to one selected Must Not Overlap error only. Must Not Intersect Requires that line features from the same feature class or subtype not cross or overlap each other. Lines can share endpoints. This rule is used for contour lines that should never cross each other or in cases where the intersection of lines should only occur at endpoints, such as street segments and intersections. This fix can be applied to one Must Not Intersect error only.

Split: The Split fix splits the line features that cross one another at their point of intersection. If two lines cross at a single point, applying the Split fix at that location will result in four features. Attributes from the original features will be maintained in the split features. If a split policy is present, the attributes will be updated accordingly.

This fix can be applied to one or more Must Not Intersect errors. Must Not Intersect With Requires that line features from one feature class or subtype not cross or overlap lines from another feature class or subtype. This rule is used when there are lines from two layers that should never cross each other or in cases where the intersection of lines should only occur at endpoints, such as streets and railroads.

This fix can be applied to one Must Not Intersect With error only. This fix can be applied to one or more Must Not Intersect With errors. Must Not Have Dangles Requires that a line feature must touch lines from the same feature class or subtype at both endpoints.

An endpoint that is not connected to another line is called a dangle. This rule is used when line features must form closed loops, such as when they are defining the boundaries of polygon features.

It may also be used in cases where lines typically connect to other lines, as with streets. In this case, exceptions can be used where the rule is occasionally violated, as with cul-de-sac or dead-end street segments. Extend: The Extend fix will extend the dangling end of line features if they snap to other line features within a given distance. If no feature is found within the distance specified, the feature will not extend to the distance specified.

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 list. The errors of features that could not be extended remain on the Error Inspector dialog box. If the distance value is 0, lines will extend until they find a feature to snap to. This fix can be applied to one or more Must Not Have Dangles errors. Trim: The Trim fix will trim dangling line features if a point of intersection is found within a given distance.

If no feature is found within the distance specified, the feature will not be trimmed, nor will it be deleted if the distance is greater than the length of the feature in error. If the distance value is 0, lines will be trimmed back until they find a point of intersection. If no intersection is located, the feature will not be trimmed and the fix will attempt to trim the next feature in error. This fix can be applied to one or more Must Not Have dangles errors. Snap: The Snap fix will snap dangling line features to the nearest line feature within a given distance.

If no line feature is found within the distance specified, the line will not be snapped. The Snap fix will snap to the nearest feature found within the distance. It searches for endpoints to snap to first, then vertices, and finally to the edge of line features within the feature class. Must Not Have Pseudo Nodes Requires that a line connect to at least two other lines at each endpoint. Lines that connect to one other line or to themselves are said to have pseudo nodes.

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.

Merge To Largest: The Merge To Largest fix will merge the geometry of the shorter line into the geometry of the longest line.

The attributes of the longest line feature will be retained. Merge: The Merge fix adds the geometry of one line feature into the other line feature causing the error. You must pick the line feature into which to merge.

Must Not Intersect Or Touch Interior Requires that a line in one feature class or subtype must only touch other lines of the same feature class or subtype at endpoints. Any line segment in which features overlap or any intersection not at an endpoint is an error. This rule is useful where lines must only be connected at endpoints, such as in the case of lot lines, which must split only connect to the endpoints of back lot lines and cannot overlap each other.

If you have duplicate line features, choose the line feature you want to delete from the Subtract dialog box. The Subtract fix creates multipart features, so if the overlapping segments are not at the end or start of a line feature, you might want to use the Explode command on the Advanced Editing toolbar to create single-part features.

Must Not Intersect Or Touch Interior With 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 useful where lines from two layers must only be connected at endpoints. Must Not Overlap With Requires that a line from one feature class or subtype not overlap with line features in another feature class or subtype.

This rule is used when line features cannot share the same space. For example, roads must not overlap with railroads or depression subtypes of contour lines cannot overlap with other contour lines. This fix can be applied to one selected Must Not Overlap With error only. Where the purple lines overlap is an error.

Must Be Covered By Feature Class Of Requires that lines from one feature class or subtype must be covered by the lines in another feature class or subtype. This is useful for modeling logically different but spatially coincident lines, such as routes and streets. A bus route feature class must not depart from the streets defined in the street feature class. None Where the purple lines do not overlap is an error.

This is useful for modeling lines, such as lot lines, that must coincide with the edge of polygon features, such as lots. Subtract: The Subtract fix removes line segments that are not coincident with the boundary of polygon features. If the line feature does not share any segments in common with the boundary of a polygon feature, the feature will be deleted. Must Be Inside Requires that a line is contained within the boundary of an area feature. This is useful for cases where lines may partially or totally coincide with area boundaries but cannot extend beyond polygons, such as state highways that must be inside state borders and rivers that must be within watersheds.

Delete: The Delete fix removes line features that are not within polygon features. Note that you can use the Edit tool and move the line inside the polygon feature if you do not want to delete it. This fix can be applied to one or more Must Be Inside errors. Endpoint Must Be Covered By Requires that the endpoints of line features must be covered by point features in another feature class. This is useful for modeling cases where a fitting must connect two pipes or a street intersection must be found at the junction of two streets.

Create Feature: The Create Feature fix adds a new point feature at the endpoint of the line feature that is in error. The square at the bottom indicates an error, because there is no point covering the endpoint of the line. Must Not Self-Overlap Requires that line features not overlap themselves. They can cross or touch themselves but must not have coincident segments. This rule is useful for features, such as streets, where segments might touch in a loop but where the same street should not follow the same course twice.

Simplify: The Simplify fix removes self-overlapping line segments from the feature in error. Applying the Simplify fix can result in multipart features, which you can detect using the Must Be Single Part rule. The individual line feature overlaps itself, with the error indicated by the coral line.

Must Not Self-Intersect Requires that line features not cross or overlap themselves. This rule is useful for lines, such as contour lines, that cannot cross themselves.

Note that applying the Simplify fix can result in multipart features. You can detect multipart features using the Must Be Single Part rule.

This fix can be applied to one or more Must Not Self-Intersect errors. Must Be Single Part Requires that lines have only one part. This rule is useful where line features, such as highways, may not have multiple parts. Explode: The Explode fix creates single-part line features from each part of the multipart line feature that is in error. This fix can be applied to one or more Must Be Single Part errors.

Multipart lines are created from a single sketch. Line rules.

ECUACIONES DIFERENCIALES WILLIAM E.BOYCE PDF

Geodatabase topology rules and topology error fixes

Geodatabase topology rules allow you to define relationships between features in the same feature class or subtype or between two feature classes or subtypes. The status of a topology, including errors and exceptions, is saved to the source geodatabase. In the Contents pane, geodatabase topology rules appear as group layers containing sublayers that symbolize modified areas, and errors organized by geometry type. This topic explains the topology rules available for point features and their predefined fixes.

ACFA CARDIOLOGIE PDF

Geodatabase-Topologieregeln und Reparatur von Topologiefehlern für Polygon-Features

Geodatabase topology rules allow you to define relationships between features in the same feature class or subtype or between two feature classes or subtypes. The status of a topology, including errors and exceptions, is saved to the source geodatabase. In the Contents pane, geodatabase topology rules appear as group layers containing sublayers that symbolize modified areas, and errors organized by geometry type. This topic explains the topology rules available for polygon features and their predefined fixes. For steps to validate a geodatabase topology and fix errors, see Validate and fix geodatabase topology.

ANTONINA KOSKOWSKA SOCJOLOGIA KULTURY PDF

Geodatabase topology rules and fixes for point features

.

Related Articles