Using geodatabase topology to fix line Errors

Exercise 4b: Using geodatabase topology to fix line Errors

About geodatabase topology

Geodatabase topology is a set of rules that define how the features in one or more feature classes share geometry. Geodatabase topology is created in the Catalog window or ArcCatalog and can be added to ArcMap as a layer, just like any other data. After editing has been performed on the feature classes, you validate the geodatabase topology to see if the edits break any of the topology's rules.

An ArcEditor or ArcInfo license is required to create, edit, or validate geodatabase topology.

In this exercise, you will create a simple geodatabase topology rule to help you find digitizing errors in lot line data that has been imported from CAD, then use the topology and editing tools to fix these errors.

License: This tutorial requires an ArcEditor or ArcInfo license to complete.

Creating a geodatabase topology

Prerequisite:

Start ArcMap and display the Editor and Topology toolbars.

Steps:

1. Click the Open button on the Standard toolbar.

2. Navigate to the GeodatabaseTopology.mxd map document located in the \Editing\Topology directory where you installed the tutorial data. (C:\ArcGIS\ArcTutor is the default location.)

3. Click the map and click Open.

4. If you still have the map document open from the previous exercise and are prompted to close it, you can do so without saving your changes. This map contains two layers, one for parcel lot lines and another one showing the area you are studying. You need to create a geodatabase topology so you can find and fix any spatial errors in the lot lines data.

5. If the Catalog window is not already open, click the Catalog Window button on the Standard toolbar to display it. The Catalog window allows you to manage your datasets and is where you will add the topology. You can dock the window to the ArcMap user interface by clicking the pin in the upper righthand corner.

6. If necessary, expand the Home - Editing\Topology folder, which displays the contents of the Topology folder installed with the tutorial data.

7. Expand the Topology geodatabase, if needed, and click the StudyArea feature dataset. Now you will create a geodatabase topology to help you find errors in the lot lines data. The topology will be simple, involving one feature class and one topology rule.

8. Right-click the StudyArea dataset, point to New, then click Topology.

9. Click Next on the introduction.

On the next panel of the wizard, you can set the cluster tolerance. The cluster tolerance is the minimum distance that separate parts of features can be from each other. Vertices and edges of features that fall within the cluster tolerance are snapped together. By default, the wizard gives the smallest possible cluster tolerance, which is determined by the precision of the spatial reference of the dataset. The precision of a dataset defines how many system units can be stored per unit of linear measure and controls how precisely coordinates are stored in the dataset.

10. Accept the default name and cluster tolerance and click Next.

11. Now you can choose which feature classes in the dataset to include in the topology.

Check LotLines and click Next. When you have more than one feature class in a topology, you can give them different ranks. When vertices or edges of features fall within the cluster tolerance of each other, the feature class rank controls which is moved to the other's location. Feature classes of a lower rank will be snapped to feature classes of a higher rank. The highest rank is 1; the lowest is 50. Parts of features of the same rank that fall within the cluster tolerance are geometrically averaged.

12. Accept the default ranks and click Next. When you build a topology, you can pick the rules that will govern the allowable spatial relationships between features.

13. Click Add Rule.

14. Click the Rule arrow and click Must Not Have Dangles.

  

Dangles are the endpoints of lines that are not snapped to other lines in the feature class. You will

want to find the dangles in the LotLines feature class, because they represent places where the imported CAD line work is not connected properly.

15. Click OK.

16. The rule is added to the list of topology rules. Click Next.

17. Review the summary and click Finish.

A message appears informing you that the topology is being built, then another asks whether you want to validate the topology now. Validation discovers errors in the layer.

18. Click Yes.

A message appears informing you that the topology is being validated, and the new topology appears in the StudyArea dataset.

Adding the topology to the map

Now you'll use the topology to help you find the dangle errors in the lot lines data. In the future, you may need to build polygon lot features from these lines. Therefore, it is important to clean up this data first because only one lot polygon will be created if a line dividing two lots does not completely separate them.

Steps:

1. In the Catalog window, expand the StudyArea feature dataset, if needed, then click StudyArea_Topology and drag it onto the map.

2. Click No when you are asked whether to add all the layers that participate in the topology, since the layers are already in the map.

3. Close the Catalog window.

The topology layer shows all the topology errors. Notice that in the ArcMap table of contents, the topology layer can show area, line, and point errors. This topology only has one feature class and one rule, so all the topology errors relate to that rule. The topology rule specifies that lot lines must not have dangles. The error geometry for dangles is a point, located at the dangling end of a line feature. All the red error features on the map are dangles.

Finding topology errors

The next step to make this data useful is to identify the topology errors that are present. Lot lines that have a dangle, where one end of the line is not connected to another lot line, are errors that you need to find to clean up this data so you can create lot polygons. Some dangles need to be extended to close a polygon;

others overshoot the line that they should snap to and need to be trimmed. You will find some of these errors now.

Steps:

1. Click Bookmarks and click Dangle errors. The map zooms to the bookmarked area. Now you can see three dangle errors, which you will fix in this exercise.

2. Click the Editor menu on the Editor toolbar and click Start Editing.

3. Close the Create Features window. You will not need it in this exercise.

4. Click Error Inspector on the Topology toolbar.

The Error Inspector window allows you to manage and interact with all the topology errors on your map.

5. Make you sure can see the same three errors on the map with the Error Inspector window open. You may need to pan the map to make them visible again.

6. Check the Errors and Visible extent only check boxes on the Error Inspector window.

7. Click Search Now on the Error Inspector window.

Correcting an overshoot error

All the errors on the map are violations of the Must Not Have Dangles rule. However, there are several different problems that can cause this type of error. A dangle error can be caused by a line that extends too far beyond the line it is supposed to touch or by a line that doesn't extend quite far enough. These are

overshoots and undershoots, respectively.

Dangles can also occur where features have been digitized from adjacent map sheets. These lines sometimes need to be snapped together so they connect to form a continuous line. Other dangle errors occur at the edge of map sheets, where a line is cut off on the original source data.

You will now correct one of the errors on this map.

Steps:

1. Click in the Feature 1 column on the Error Inspector window until the northernmost feature on the map flashes and turns black to show that it is selected.

2. Zoom in to the error until you can see where the lot line with the error crosses the other lot line.

This is an overshoot error, a type of error that is often found in line work imported from CAD

programs or digitized without using snapping to control the connectivity of the line features.

3. Right-click the error on the Error Inspector window and click Trim.

4. Type 3 in the Maximum Distance text box and press ENTER

The dangling segment is trimmed back to where the lines intersect, and the error disappears. The Error Inspector shortcut menu provides a list of potential fixes for this error. You trimmed the line feature to fix this error. You also could have marked the error as an exception or snapped or extended the line until it reached another feature.

Correcting an undershoot error

Steps:

1. Click the Go Back To Previous Extent button on the Tools toolbar until you can see the two remaining errors in this area of the data. Now you'll correct another type of dangle error.

2. Zoom in to the westernmost of the two remaining errors.

3. Zoom in again, if necessary, until you can see where the lot line with the error fails to connect to the other lot line. This is an undershoot error, another type of error that is often found in line work imported from CAD programs or digitized without using snapping to control the connectivity of the line features. The end of this line fell short by a little more than half a meter. You'll fix this error by extending the undershoot until it meets the line to which it should have been snapped.

4. Click the Fix Topology Error tool on the Topology toolbar. This tool lets you interactively select and apply predefined fixes to topology errors on the map.

5. Drag a box around the error.

6. Right-click the map and click Extend.

7. Type 3 in the Maximum Distance text box and press ENTER.

You have corrected the undershoot by extending the line with the dangle to the other line. If the distance to the next line had been greater than the three-meter maximum distance you specified, the line would not have been extended.

Correcting a double-digitized line

Sometimes a given line or part of a line is digitized twice in the course of creating the data. This may happen with CAD drawings or with lines digitized on a digitizing tablet.

Steps:

1. Click the Go Back To Previous Extent button on the Tools toolbar until you can see the one remaining error in this area of the data.

2. Zoom in to the remaining error.

3. Click Search Now on the Error Inspector window.

4. Click the numeric value in the Feature 1 column.

The line feature with the dangle flashes. Notice that the whole lot line did not flash.

5. Zoom in until you can see that there are two nearly parallel lot lines, one of which has the dangle.

You'll correct this error by deleting the extra line.

6. Right-click the numeric value in the Feature 1 column, click Select Features, then press the DELETE key. This deletes the extra line.

7. Click the Go Back To Previous Extent button on the Tools toolbar until you can see the area in which you have been working.

Reviewing the areas you have edited

You have fixed three errors that resulted from violations of the Must Not Have Dangles rule. In each case, the error was corrected by editing the geometry of a lot line feature by trimming, extending, or deleting the feature.

Viewing topology errors is useful for tracking where there are problems with your data, but correcting the error requires you to correct the data—you cannot edit the topology error feature layer directly.

When you edit features in a topology, the topology tracks where changes have been made. These places are called dirty areas because a topology rule could potentially have been violated by the edits, but the error, if it exists, cannot be found until the dirty area is validated again. When you validate the topology again, it just checks the dirty areas.

You can see the areas that have been edited by showing the dirty areas in the topology layer.

Steps:

1. Right-click the topology in the table of contents and click Properties.

2. Click the Symbology tab.

3. Check Dirty Areas.

4. Click OK.

  

Now you can see the dirty areas on the map. The dirty areas cover the features that you edited. Dirty areas optimize the validation process, as only these must be checked for errors. Zoom out, if

needed, so you can see all the entire extent of the dirty area boxes.

5. Click the Validate Topology In Specified Area button on the Topology toolbar.

6. Drag a box around the northern dirty area.

The dirty area is removed, and no errors are found in the area you validated.

7. Click the Validate Topology In Current Extent button on the Topology toolbar.

  

The topology is validated for the other areas you edited, and the dirty area is removed.

Creating a report of the status of the data

Steps:

Next you will generate a report summarizing the number of topology errors remaining in the data.

1. Right-click the topology in the table of contents and click Properties.

2. Click the Errors tab.

3. Click Generate Summary. The summary shows the number of topology errors and exceptions; you could have a different number of errors. You can save this report to a text file to document the status of the data, but you do not need to for this exercise.

4. Click OK.

Fixing multiple errors at once

Many errors, like the double-digitized line, need to be fixed one at a time by deleting, modifying, or moving individual features. Some errors must be fixed by creating new features. However, sometimes a feature class contains a number of errors, such as overshoots and undershoots, that are simple to fix. When this is the case, you can select multiple errors at once with the Fix Topology Error tool and apply the same fix to all of them. If you prefer, you can individually check each error using the Error Inspector window. This is a workflow and quality assurance decision that your organization should make before you begin applying topology fixes to multiple errors.

It is also a good idea to look at your data and evaluate whether the fixes are appropriate. You would not want to trim lines with dangles that actually needed to be snapped to another line, or extend a line that actually needed to be trimmed. In this case, if you extend dangling lines that are within three meters of another line, you're not likely to cause problems with your data, since the parcels and rights-of-way are larger than three meters.

Now you'll use this method to clean up several errors at one time.

Steps:

1. Click the Full Extent button on the Tools toolbar.

2. Click the Fix Topology Error tool on the Topology toolbar.

3. Drag a box around all the errors on the map. This selects all of the errors. Now you'll fix the undershoots.

4. Right-click the map and click Extend.

5. The maximum distance you set when you fixed the other undershoot is fine, so press ENTER. The process may take a few seconds while all the features with dangles are checked to see if there is a feature within three meters to which they can be extended.

The undershoots are fixed, and a number of dirty areas appear on the map. Each dirty area marks the bounding box of a feature that was edited by the extend error fix.

6. Click Search Now on the Error Inspector window. (If you closed the Error Inspector window, you can open it again from the Topology toolbar.) The number of topology errors is displayed to the right of the Show drop-down menu. Notice that many have not been fixed. You can trim the remaining errors and continue fixing topology errors to clean up this data if you want.

7. Click the Editor menu on the Editor toolbar and click Stop Editing.

8. Click Yes to save your edits.

9. Close ArcMap if you are done working with the tutorial. You do not need to save the map document.

10. To continue to the next exercise, click Exercise 5a: Transforming data.

In this exercise, you created a geodatabase topology with simple rules to help you clean up data. You learned how to use the Error Inspector to find errors of a particular type and how to use some of the editing tools to fix errors in your data.