29
12/8/2015 Geodatabase topology rules and topology error fixes 1/29 Geodatabase topology rules and topology error fixes Resource Center » Professional Library » Data Management » Editing data » Editing topology » Editing geodatabase topology This topic applies to ArcEditor and ArcInfo only. License: You can create simple, temporary topological relationships between features in ArcView. Creating or editing geodatabase topology requires an ArcEditor or ArcInfo license. There are many topology rules you can implement in your geodatabase, depending on the spatial relationships that are most important for your organization to maintain. You should carefully plan the spatial relationships you will enforce on your features. Some topology rules govern the relationships of features within a given feature class, while others govern the relationships between features in two different feature classes or subtypes. Topology rules can be defined between subtypes of features in one or another feature class. 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 culdesac or deadend subtypes. Many topology rules can be imposed on features in a geodatabase. A welldesigned geodatabase will have only those topology rules that define key spatial relationships needed by an organization. Most topology violations have fixes that you can use to correct errors. Some topology rules, however, have no predefined fixes. Once you have discovered the topology errors, you can select the error on the map with the Fix Topology Error tool , or select the error from within the Error Inspector. For a poster of the available topology rules and examples of them, see the ArcGIS Geodatabase Topology Rules PDF. If this link does not work, you can open the topology_rules_poster.pdf from the \Documentation folder in the directory where you installed ArcGIS. To view this document, you need a copy of Adobe Reader. Polygon rules Topology rule Rule description Potential fixes Examples Must Be Larger Than Cluster Tolerance Requires that a feature does not collapse during a validate process. 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. Delete: The Delete fix removes polygon features that would collapse during the validate process based on the topology's cluster tolerance. This fix can be applied to one or more Must Be Larger Than Cluster Tolerance errors. Any polygon feature, such as the one in red, that would collapse when validating the topology is an error.

Geodatabase Topology Rules and Topology Error Fixe

Embed Size (px)

DESCRIPTION

Geodatabase Topology Rules and Topology Error Fixe

Citation preview

Page 1: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

1/29

Geodatabase topology rules and topology error fixesResource Center » Professional Library » Data Management » Editing data » Editing topology » Editing geodatabase topology

This topic applies to ArcEditor and ArcInfo only.

License: You can create simple, temporary topological relationshipsbetween features  in ArcView. Creating or editing geodatabasetopology requires an ArcEditor or ArcInfo  license.

There are many topology rules you can  implement  in your geodatabase, depending on thespatial relationships that are most  important for your organization to maintain. You shouldcarefully plan the spatial relationships you will enforce on your features. Some topology rulesgovern the relationships of  features within a given feature class, while others govern therelationships between features  in two different feature classes or subtypes. Topology rulescan be defined between subtypes of  features  in one or another feature class. This could beused, for example, to require street features to be connected to other street features at bothends, except  in the case of streets belonging to the cul­de­sac or dead­end subtypes.

Many topology rules can be  imposed on features  in a geodatabase. A well­designedgeodatabase will have only those topology rules that define key spatial relationships neededby an organization.

Most topology violations have fixes that you can use to correct errors. Some topology rules,however, have no predefined fixes. Once you have discovered the topology errors, you canselect the error on the map with the Fix Topology Error tool  , or select the error fromwithin the Error Inspector.

For a poster of the available topology rules and examples of them, see the ArcGISGeodatabase Topology Rules PDF.

If this  link does not work, you can open the topology_rules_poster.pdf from the\Documentation folder  in the directory where you  installed ArcGIS. To view this document,you need a copy of Adobe Reader.

Polygon rulesTopologyrule

Ruledescription

Potentialfixes Examples

Must BeLargerThanClusterTolerance

Requires that afeature doesnot collapseduring avalidateprocess. Thisrule ismandatory for atopology andapplies to allline and polygonfeature classes.In instanceswhere this ruleis violated, theoriginalgeometry is leftunchanged.

Delete: TheDelete fixremovespolygonfeatures thatwould collapseduring thevalidateprocess basedon thetopology'sclustertolerance.This fix can beapplied to oneor more MustBe LargerThan ClusterToleranceerrors.

Any polygon feature, such asthe one in red, that wouldcollapse when validating thetopology is an error.

Page 2: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

2/29

Must NotOverlap

Requires thatthe interior ofpolygons notoverlap. Thepolygons canshare edges orvertices. Thisrule is usedwhen an areacannot belongto two or morepolygons. It isuseful formodelingadministrativeboundaries,such as ZIPCodes or votingdistricts, andmutuallyexclusive areaclassifications,such as landcover orlandform type.

Subtract: TheSubtract fixremoves theoverlappingportion ofgeometryfrom eachfeature that iscausing theerror andleaves a gapor void in itsplace. This fixcan beapplied to oneor moreselected MustNot Overlaperrors.

Merge: TheMerge fixadds theportion ofoverlap fromone featureand subtractsit from theothers thatare violatingthe rule. Youneed to pickthe featurethat receivesthe portion ofoverlap usingthe Mergedialog box.This fix can beapplied to oneMust NotOverlap erroronly.

CreateFeature: TheCreateFeature fixcreates a newpolygonfeature out ofthe errorshape andremoves theportion ofoverlap fromeach of thefeatures,causing theerror tocreate aplanar

Page 3: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

3/29

representationof the featuregeometry.This fix can beapplied to oneor moreselected MustNot Overlaperrors.

Must NotHave Gaps

This rulerequires thatthere are novoids within asingle polygonor betweenadjacentpolygons. Allpolygons mustform acontinuoussurface. Anerror will alwaysexist on theperimeter of thesurface. Youcan eitherignore this erroror mark it as anexception. Usethis rule on datathat mustcompletelycover an area.For example,soil polygonscannot includegaps or formvoids—theymust cover anentire area.

CreateFeature: TheCreateFeature fixcreates newpolygonfeatures usinga closed ringof the lineerror shapesthat form agap. This fixcan beapplied to oneor moreselected MustNot HaveGaps errors.If you selecttwo errorsand use theCreateFeature fix,the result willbe onepolygonfeature perring. If youwant onemultipartfeature as aresult, you willneed to selecteach newfeature andclick Mergefrom theEditor menu.Note that thering thatforms theouter boundsof yourfeature classwill be inerror. Usingthe CreateFeature fix forthis specificerror cancreate

You can use Create Feature tocreate a new polygon in thevoid in the center. You canalso use Create Feature ormark the error on the outsideboundary as an exception.

Page 4: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

4/29

overlappingpolygons.Rememberthat you canmark thiserror as anexception.

Must NotOverlapWith

Requires thatthe interior ofpolygons in onefeature class (orsubtype) mustnot overlap withthe interior ofpolygons inanother featureclass (orsubtype).Polygons of thetwo featureclasses canshare edges orvertices or becompletelydisjointed. Thisrule is usedwhen an areacannot belongto two separatefeature classes.It is useful forcombining twomutuallyexclusivesystems of areaclassification,such as zoningand water bodytype, whereareas definedwithin thezoning classcannot also bedefined in thewater bodyclass and viceversa.

Subtract: TheSubtract fixremoves theoverlappingportion ofeach featurethat iscausing theerror andleaves a gapor void in itsplace. This fixcan beapplied to oneor moreselected MustNot OverlapWith errors.

Merge: TheMerge fixadds theportion ofoverlap fromone featureand subtractsit from theothers thatare violatingthe rule. Youneed to pickthe featurethat receivesthe portion ofoverlap usingthe Mergedialog box.This fix can beapplied to oneMust NotOverlap Witherror only.

Must BeCovered ByFeatureClass Of

Requires that apolygon in onefeature class (orsubtype) mustshare all of itsarea withpolygons inanother featureclass (orsubtype). Anarea in the first

Subtract: TheSubtract fixremoves theoverlappingportion ofeach featurethat iscausing theerror so theboundary ofeach feature

Page 5: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

5/29

feature classthat is notcovered bypolygons fromthe otherfeature class isan error. Thisrule is usedwhen an area ofone type, suchas a state,should becompletelycovered byareas ofanother type,such ascounties.

from bothfeatureclasses is thesame. This fixcan beapplied to oneor moreselected MustBe CoveredBy FeatureClass Oferrors.

CreateFeature: TheCreateFeature fixcreates a newpolygonfeature out ofthe portion ofoverlap fromthe existingpolygon sothe boundaryof eachfeature fromboth featureclasses is thesame. This fixcan beapplied to oneor moreselected MustBe CoveredBy FeatureClass Oferrors.

Must CoverEach Other

Requires thatthe polygons ofone featureclass (orsubtype) mustshare all of theirarea with thepolygons ofanother featureclass (orsubtype).Polygons mayshare edges orvertices. Anyarea defined ineither featureclass that is notshared with theother is anerror. This ruleis used whentwo systems of

Subtract: TheSubtract fixremoves theoverlappingportion ofeach featurethat iscausing theerror so theboundary ofeach featurefrom bothfeatureclasses is thesame. This fixcan beapplied to oneor moreselected MustCover EachOther errors.

Create

Page 6: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

6/29

classification areused for thesamegeographicarea, and anygiven pointdefined in onesystem mustalso be definedin the other.One such caseoccurs withnestedhierarchicaldatasets, suchas censusblocks and blockgroups or smallwatersheds andlarge drainagebasins. The rulecan also beapplied tononhierarchicallyrelated polygonfeature classes,such as soiltype and slopeclass.

Feature: TheCreateFeature fixcreates a newpolygonfeature out ofthe portion ofoverlap fromthe existingpolygon sothe boundaryof eachfeature fromboth featureclasses is thesame. This fixcan beapplied to oneor moreselected MustCover EachOther errors.

Must BeCovered By

Requires thatpolygons of onefeature class (orsubtype) mustbe containedwithin polygonsof anotherfeature class (orsubtype).Polygons mayshare edges orvertices. Anyarea defined inthe containedfeature classmust becovered by anarea in thecovering featureclass. This ruleis used whenarea features ofa given typemust be locatedwithin featuresof another type.This rule isuseful whenmodeling areasthat are subsetsof a larger

CreateFeature: TheCreateFeature fixcreates a newpolygonfeature out ofthe portion ofoverlap fromthe existingpolygon sothe boundaryof eachfeature fromboth featureclasses is thesame. This fixcan beapplied to oneor moreselected MustBe CoveredBy errors.

Page 7: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

7/29

surroundingarea, such asmanagementunits withinforests or blockswithin blockgroups.

BoundaryMust BeCovered By

Requires thatboundaries ofpolygonfeatures mustbe covered bylines in anotherfeature class.This rule is usedwhen areafeatures needto have linefeatures thatmark theboundaries ofthe areas. Thisis usually whenthe areas haveone set ofattributes andtheir boundarieshave otherattributes. Forexample,parcels mightbe stored in thegeodatabasealong with theirboundaries.Each parcelmight bedefined by oneor more linefeatures thatstoreinformationabout theirlength or thedate surveyed,and everyparcel shouldexactly matchits boundaries.

CreateFeature: TheCreateFeature fixcreates a newline featurefrom theboundarysegments ofthe polygonfeaturegeneratingthe error. Thisfix can beapplied to oneor moreselectedBoundaryMust BeCovered Byerrors.

AreaBoundaryMust BeCovered ByBoundaryOf

Requires thatboundaries ofpolygonfeatures in onefeature class (orsubtype) becovered byboundaries ofpolygonfeatures in

None

Page 8: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

8/29

another featureclass (orsubtype). Thisis useful whenpolygonfeatures in onefeature class,such assubdivisions,are composedof multiplepolygons inanother class,such as parcels,and the sharedboundaries mustbe aligned.

ContainsPoint

Requires that apolygon in onefeature classcontain at leastone point fromanother featureclass. Pointsmust be withinthe polygon, noton theboundary. Thisis useful whenevery polygonshould have atleast oneassociatedpoint, such aswhen parcelsmust have anaddress point.

CreateFeature: TheCreateFeature fixcreates a newpoint featureat thecentroid ofthe polygonfeature that iscausing theerror. Thepoint featurethat iscreated isguaranteed tobe within thepolygonfeature. Thisfix can beapplied to oneor moreselectedContains Pointerrors.

The top polygon is an errorbecause it does not contain apoint.

ContainsOne Point

Requires thateach polygoncontains onepoint featureand that eachpoint featurefalls within asingle polygon.This is usedwhen theremust be a one­to­onecorrespondencebetweenfeatures of apolygon featureclass and

None

The top polygon is an error

Page 9: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

9/29

features of apoint featureclass, such asadministrativeboundaries andtheir capitalcities. Eachpoint must beproperly insideexactly onepolygon andeach polygonmust properlycontain exactlyone point.Points must bewithin thepolygon, not onthe boundary.

because it contains more thanone point. Points are errorswhen they are outside apolygon.

Polygon  rules

Line rules

Topology rule Ruledescription

Potentialfixes Examples

Must Be LargerThan ClusterTolerance

Requires thata featuredoes notcollapseduring avalidateprocess. Thisrule ismandatoryfor atopology andapplies to allline andpolygonfeatureclasses. Ininstanceswhere thisrule isviolated, theoriginalgeometry isleftunchanged.

Delete: TheDelete fixremovesline featuresthat wouldcollapseduring thevalidateprocessbased onthetopology'sclustertolerance.This fix canbe appliedto one ormore MustBe LargerThanClusterToleranceerrors.

Any line feature, such as theselines in red, that wouldcollapse when validating thetopology is an error.

Must NotOverlap

Requires thatlines notoverlap withlines in thesame featureclass (orsubtype).This rule isused whereline

Subtract:TheSubtract fixremovestheoverlappinglinesegmentsfrom thefeature

Page 10: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

10/29

segmentsshould notbeduplicated,for example,in a streamfeatureclass. Linescan cross orintersect butcannot sharesegments.

causing theerror. Youmust selectthe featurefrom whichthe errorwill beremoved. Ifyou haveduplicatelinefeatures,select theline featureyou want todelete fromtheSubtractdialog box.Note thattheSubtract fixwill createmultipartfeatures, soif theoverlappingsegmentsare not atthe end orstart of aline feature,you mightwant to usethe Explodecommandon theAdvancedEditingtoolbar tocreatesingle­partfeatures.This fix canbe appliedto oneselectedMust NotOverlaperror only.

Must NotIntersect

Requires thatline featuresfrom thesame featureclass (orsubtype) notcross oroverlap eachother. Linescan share

Subtract:TheSubtract fixremovestheoverlappinglinesegmentsfrom thefeature

Page 11: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

11/29

endpoints.This rule isused forcontour linesthat shouldnever crosseach otheror in caseswhere theintersectionof linesshould onlyoccur atendpoints,such asstreetsegmentsandintersections.

causing theerror. Youmust selectthe featurefrom whichthe errorwill beremoved. Ifyou haveduplicatelinefeatures,select theline featureyou want todelete fromtheSubtractdialog box.Note thattheSubtract fixwill createmultipartfeatures, soif theoverlappingsegmentsare not atthe end orstart of aline feature,you mightwant to usethe Explodecommandon theAdvancedEditingtoolbar tocreatesingle­partfeatures.This fix canbe appliedto one MustNotIntersecterror only.

Split: TheSplit fixsplits theline featuresthat crossone anotherat theirpoint ofintersection.If two linescross at a

Page 12: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

12/29

single point,applying theSplit fix atthatlocation willresult infourfeatures.Attributesfrom theoriginalfeatures willbemaintainedin the splitfeatures. Ifa split policyis present,theattributeswill beupdatedaccordingly.This fix canbe appliedto one ormore MustNotIntersecterrors.

Must NotIntersect With

Requires thatline featuresfrom onefeature class(or subtype)not cross oroverlap linesfrom anotherfeature class(or subtype).Lines canshareendpoints.This rule isused whenthere arelines fromtwo layersthat shouldnever crosseach otheror in caseswhere theintersectionof linesshould onlyoccur atendpoints,such asstreets and

Subtract:TheSubtract fixremovestheoverlappinglinesegmentsfrom thefeaturecausing theerror. Youmust selectthe featurefrom whichthe errorwill beremoved. Ifyou haveduplicatelinefeatures,select theline featureyou want todelete fromtheSubtractdialog box.Note that

Page 13: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

13/29

railroads. theSubtract fixwill createmultipartfeatures, soif theoverlappingsegmentsare not atthe end orstart of aline feature,you mightwant to usethe Explodecommandon theAdvancedEditingtoolbar tocreatesingle­partfeatures.This fix canbe appliedto one MustNotIntersectWith erroronly.

Split: TheSplit fixsplits theline featuresthat crossone anotherat theirpoint ofintersection.If two linescross at asingle point,applying theSplit fix atthatlocation willresult infourfeatures.Attributesfrom theoriginalfeatures willbemaintainedin the splitfeatures. Ifa split policyis present,the

Page 14: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

14/29

attributeswill beupdatedaccordingly.This fix canbe appliedto one ormore MustNotIntersectWith errors.

Must Not HaveDangles

Requires thata line featuremust touchlines fromthe samefeature class(or subtype)at bothendpoints.An endpointthat is notconnected toanother lineis called adangle. Thisrule is usedwhen linefeaturesmust formclosed loops,such aswhen theyare definingtheboundariesof polygonfeatures. Itmay also beused incases wherelines typicallyconnect toother lines,as withstreets. Inthis case,exceptionscan be usedwhere therule isoccasionallyviolated, aswith cul­de­sac or dead­end streetsegments.

Extend:The Extendfix willextend thedanglingend of linefeatures ifthey snapto other linefeatureswithin agivendistance. Ifno featureis foundwithin thedistancespecified,the featurewill notextend tothe distancespecified.Also, ifseveralerrors wereselected,the fix willsimply skipthe featuresthat itcannotextend andattempt toextend thenext featurein the list.The errorsof featuresthat couldnot beextendedremain onthe ErrorInspectordialog box.If thedistancevalue is 0,

Page 15: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

15/29

lines willextend untilthey find afeature tosnap to.This fix canbe appliedto one ormore MustNot HaveDangleserrors.

Trim: TheTrim fix willtrimdanglingline featuresif a point ofintersectionis foundwithin agivendistance. Ifno featureis foundwithin thedistancespecified,the featurewill not betrimmed,nor will it bedeleted ifthe distanceis greaterthan thelength ofthe featurein error. Ifthe distancevalue is 0,lines will betrimmedback untilthey find apoint ofintersection.If nointersectionis located,the featurewill not betrimmedand the fixwill attemptto trim thenext featurein error.This fix canbe applied

Page 16: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

16/29

to one ormore MustNot Havedangleserrors.

Snap: TheSnap fix willsnapdanglingline featuresto thenearest linefeaturewithin agivendistance. Ifno linefeature isfound withinthe distancespecified,the line willnot besnapped.The Snapfix will snapto thenearestfeaturefound withinthedistance. Itsearches forendpointsto snap tofirst, thenvertices,and finallyto the edgeof linefeatureswithin thefeatureclass. TheSnap fix canbe appliedto one ormore MustNot HaveDangleserrors.

Must Not HavePseudo Nodes

Requires thata lineconnect to atleast twoother lines ateachendpoint.Lines that

Merge ToLargest:The MergeTo Largestfix willmerge thegeometry ofthe shorter

Page 17: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

17/29

connect toone otherline (or tothemselves)are said tohave pseudonodes. Thisrule is usedwhere linefeaturesmust formclosed loops,such aswhen theydefine theboundariesof polygonsor when linefeatureslogically mustconnect totwo otherline featuresat each end,as withsegments ina streamnetwork, withexceptionsbeingmarked fortheoriginatingends of first­orderstreams.

line into thegeometry ofthe longestline. Theattributes ofthe longestline featurewill beretained.This fix canbe appliedto one ormore MustNot HavePseudoNodeserrors.

Merge: TheMerge fixadds thegeometry ofone linefeature intothe otherline featurecausing theerror. Youmust pickthe linefeature intowhich tomerge. Thisfix can beapplied tooneselectedMust NotHavePseudoNodeserror.

Must NotIntersect OrTouch Interior

Requires thata line in onefeature class(or subtype)must onlytouch otherlines of thesame featureclass (orsubtype) at

Subtract:TheSubtract fixremovestheoverlappinglinesegmentsfrom thefeature

Page 18: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

18/29

endpoints.Any linesegment inwhichfeaturesoverlap oranyintersectionnot at anendpoint isan error.This rule isuseful wherelines mustonly beconnected atendpoints,such as inthe case oflot lines,which mustsplit (onlyconnect totheendpoints of)back lot linesand cannotoverlap eachother.

causing theerror. Youmust selectthe featurefrom whichthe errorwill beremoved. Ifyou haveduplicatelinefeatures,choose theline featureyou want todelete fromtheSubtractdialog box.TheSubtract fixcreatesmultipartfeatures, soif theoverlappingsegmentsare not atthe end orstart of aline feature,you mightwant to usethe Explodecommandon theAdvancedEditingtoolbar tocreatesingle­partfeatures.This fix canbe appliedto oneselectedMust NotIntersect OrTouchInteriorerror only.

Split: TheSplit fixsplits theline featuresthat crossone anotherat theirpoint ofintersection.

Page 19: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

19/29

If two linescross at asingle point,applying theSplit fix atthatlocation willresult infourfeatures.Attributesfrom theoriginalfeatures willbemaintainedin the splitfeatures. Ifa split policyis present,theattributeswill beupdatedaccordingly.This fix canbe appliedto one ormore MustNotIntersect OrTouchInteriorerrors.

Must NotIntersect OrTouch InteriorWith

Requires thata line in onefeature class(or subtype)must onlytouch otherlines ofanotherfeature class(or subtype)at endpoints.Any linesegment inwhichfeaturesoverlap oranyintersectionnot at anendpoint isan error.This rule isuseful wherelines fromtwo layersmust only be

Subtract:TheSubtract fixremovestheoverlappinglinesegmentsfrom thefeaturecausing theerror. Youmust selectthe featurefrom whichthe errorwill beremoved. Ifyou haveduplicatelinefeatures,choose theline featureyou want todelete from

Page 20: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

20/29

connected atendpoints.

theSubtractdialog box.TheSubtract fixcreatesmultipartfeatures, soif theoverlappingsegmentsare not atthe end orstart of aline feature,you mightwant to usethe Explodecommandon theAdvancedEditingtoolbar tocreatesingle­partfeatures.This fix canbe appliedto oneselectedMust NotIntersect OrTouchInteriorWith erroronly.

Split: TheSplit fixsplits theline featuresthat crossone anotherat theirpoint ofintersection.If two linescross at asingle point,applying theSplit fix atthatlocation willresult infourfeatures.Attributesfrom theoriginalfeatures willbe

Page 21: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

21/29

maintainedin the splitfeatures. Ifa split policyis present,theattributeswill beupdatedaccordingly.This fix canbe appliedto one ormore MustNotIntersect OrTouchInteriorWith errors.

Must NotOverlap With

Requires thata line fromone featureclass (orsubtype) notoverlap withline featuresin anotherfeature class(or subtype).This rule isused whenline featurescannot sharethe samespace. Forexample,roads mustnot overlapwith railroadsordepressionsubtypes ofcontour linescannotoverlap withothercontourlines.

Subtract:TheSubtract fixremovestheoverlappinglinesegmentsfrom thefeaturecausing theerror. Youmust selectthe featurefrom whichthe errorwill beremoved. Ifyou haveduplicatelinefeatures,choose theline featureyou want todelete fromtheSubtractdialog box.TheSubtract fixcreatesmultipartfeatures, soif theoverlappingsegmentsare not atthe end orstart of a

Where the purple lines overlapis an error.

Page 22: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

22/29

line feature,you mightwant to usethe Explodecommandon theAdvancedEditingtoolbar tocreatesingle­partfeatures.This fix canbe appliedto oneselectedMust NotOverlapWith erroronly.

Must Be CoveredBy Feature ClassOf

Requires thatlines fromone featureclass (orsubtype)must becovered bythe lines inanotherfeature class(or subtype).This is usefulfor modelinglogicallydifferent butspatiallycoincidentlines, suchas routesand streets.A bus routefeature classmust notdepart fromthe streetsdefined inthe streetfeatureclass.

None

Where the purple lines do notoverlap is an error.

Must Be CoveredBy Boundary Of

Requires thatlines becovered bytheboundariesof areafeatures.This is usefulfor modelinglines, such

Subtract:TheSubtract fixremoveslinesegmentsthat are notcoincidentwith theboundary of

Page 23: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

23/29

as lot lines,that mustcoincide withthe edge ofpolygonfeatures,such as lots.

polygonfeatures. Ifthe linefeaturedoes notshare anysegments incommonwith theboundary ofa polygonfeature, thefeature willbe deleted.This fix canbe appliedto one ormore MustBe CoveredByBoundary Oferrors.

Must Be Inside Requires thata line iscontainedwithin theboundary ofan areafeature. Thisis useful forcases wherelines maypartially ortotallycoincide withareaboundariesbut cannotextendbeyondpolygons,such asstatehighwaysthat must beinside stateborders andrivers thatmust be

Delete: TheDelete fixremovesline featuresthat are notwithinpolygonfeatures.Note thatyou can usethe Edit tooland movethe lineinside thepolygonfeature ifyou do notwant todelete it.This fix canbe appliedto one ormore MustBe Insideerrors.

Page 24: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

24/29

withinwatersheds.

Endpoint MustBe Covered By

Requires thattheendpoints ofline featuresmust becovered bypointfeatures inanotherfeatureclass. This isuseful formodelingcases wherea fitting mustconnect twopipes or astreetintersectionmust befound at thejunction oftwo streets.

CreateFeature:The CreateFeature fixadds a newpointfeature attheendpoint ofthe linefeature thatis in error.The CreateFeature fixcan beapplied toone or moreEndpointMust BeCovered Byerrors.

The square at the bottomindicates an error, becausethere is no point covering theendpoint of the line.

Must Not Self­Overlap

Requires thatline featuresnot overlapthemselves.They cancross ortouchthemselvesbut must nothavecoincidentsegments.This rule isuseful forfeatures,such asstreets,wheresegmentsmight touchin a loop butwhere thesame streetshould notfollow thesame coursetwice.

Simplify:The Simplifyfix removesself­overlappinglinesegmentsfrom thefeature inerror.Applying theSimplify fixcan result inmultipartfeatures,which youcan detectusing theMust BeSingle Partrule. TheSimplify fixcan beapplied toone or moreMust NotSelf­Overlaperrors.

The individual line featureoverlaps itself, with the errorindicated by the coral line.

Must Not Self­Intersect

Requires thatline featuresnot cross oroverlapthemselves.This rule is

Simplify:The Simplifyfix removesself­overlappingline

Page 25: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

25/29

useful forlines, suchas contourlines, thatcannot crossthemselves.

segmentsfrom thefeature inerror. Notethatapplying theSimplify fixcan result inmultipartfeatures.You candetectmultipartfeaturesusing theMust BeSingle Partrule. This fixcan beapplied toone or moreMust NotSelf­Intersecterrors.

Must Be SinglePart

Requires thatlines haveonly onepart. Thisrule is usefulwhere linefeatures,such ashighways,may nothave multipleparts.

Explode:The Explodefix createssingle­partline featuresfrom eachpart of themultipartline featurethat is inerror. Thisfix can beapplied toone or moreMust BeSingle Parterrors.

Multipart lines are createdfrom a single sketch.

Line  rules

Point rules

Topology rule Ruledescription

Potentialfixes Examples

Must CoincideWith

Requiresthat pointsin onefeature

Snap:The Snapfix willmove a

Page 26: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

26/29

class (orsubtype) becoincidentwith pointsin anotherfeatureclass (orsubtype).This isuseful forcases wherepoints mustbe coveredby otherpoints, suchastransformersmustcoincidewith powerpoles inelectricdistributionnetworksandobservationpoints mustcoincidewithstations.

pointfeature inthe firstfeatureclass orsubtypeto thenearestpoint inthesecondfeatureclass orsubtypethat islocatedwithin agivendistance.If nopointfeature isfoundwithin thetolerancespecified,the pointwill notbesnapped.The Snapfix can beapplied toone ormoreMustCoincideWitherrors.

Where a red point is notcoincident with a blue point is anerror.

Must Be Disjoint Requiresthat pointsbeseparatedspatiallyfrom otherpoints in thesamefeatureclass (orsubtype).Any pointsthat overlapare errors.This isuseful forensuringthat pointsare notcoincidentor

None

Where a red point and a bluepoint overlap is an error.

Page 27: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

27/29

duplicatedwithin thesamefeatureclass, suchas in layersof cities,parcel lot IDpoints,wells, orstreetlamppoles.

Must Be CoveredBy Boundary Of

Requiresthat pointsfall on theboundariesof areafeatures.This isuseful whenthe pointfeatureshelp supporttheboundarysystem,such asboundarymarkers,which mustbe found onthe edges ofcertainareas.

None

The square on the right indicatesan error because it is a point thatis not on the boundary of thepolygon.

Must BeProperly Inside

Requiresthat pointsfall withinareafeatures.This isuseful whenthe pointfeatures arerelated topolygons,such aswells andwell pads oraddresspoints andparcels.

Delete:TheDelete fixremovespointfeaturesthat arenotproperlywithinpolygonfeatures.Note thatyou canuse theEdit tooland movethe pointinside thepolygonfeature ifyou donot wantto deleteit. This fix

The squares are errors wherethere are points that are notinside the polygon.

Page 28: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

28/29

can beapplied toone ormoreMust BeProperlyInsideerrors.

Must Be CoveredBy Endpoint Of

Requiresthat pointsin onefeatureclass mustbe coveredby theendpoints oflines inanotherfeatureclass. Thisrule issimilar tothe line ruleEndpointMust BeCovered Byexcept that,in caseswhere therule isviolated, itis the pointfeature thatis markedas an errorrather thanthe line.Boundarycornermarkersmight beconstrainedto becovered bytheendpoints ofboundarylines.

Delete:TheDelete fixremovespointfeaturesthat arenotcoincidentwith theendpointof linefeatures.Note thatyou cansnap thepoint tothe lineby settingedgesnappingto theline layer,thenmovingthe pointwith theEdit tool.This fixcan beapplied toone ormoreMust BeCoveredByEndpointOf errors.

The square indicates an errorwhere the point is not on anendpoint of a line.

Must Be CoveredBy Line

Requiresthat pointsin onefeatureclass becovered bylines inanotherfeatureclass. Itdoes not

None

The squares are points that arenot covered by the line.

Page 29: Geodatabase Topology Rules and Topology Error Fixe

12/8/2015 Geodatabase topology rules and topology error fixes

29/29

constrainthe coveringportion ofthe line tobe anendpoint.This rule isuseful forpoints thatfall along aset of lines,such ashighwaysigns alonghighways.

Point  rules

Copyright © 1995­2011 Esri. All rights reserved.

5/6/2011

URL: http://help.arcgis.com/en/arcgisdesktop/10.0/help/001t/001t000000sp000000.htm