Lab 4: Advanced Editing and Topology - GIS Courses ?· Advanced Editing 1 Lab 4: Advanced Editing and…

  • Published on

  • View

  • Download

Embed Size (px)


<p> Advanced Editing </p> <p> 1 </p> <p>Lab 4: Advanced Editing and Topology </p> <p>What Youll Learn: Image interpretation, more editing, and topology. You should read the section on topology in Chapter 2, and Chapter 4 on image interpretation of the GIS Fundamentals textbook before starting this Lab. Data: The several data layers are in the Lab 4 subdirectory, all in the UTM, NAD83(2011) zone 15 coordinate system, for a portion of Big Marine Lake, in Washington County, Minnesota: BigMarSum.img, a summer infrared image, with a 1 meter cell size, RectSpring.img, a spring infrared image with 1 meter cell size, NWILakes, MNDOTLakes, DNRLakes, various renditions of lake boundaries, SouthBayArea, a shapefile for a work area in the second part of this lab. Background: Multi-temporal images are commonly used for updating information, or documenting change. Data often arent current or consistent, and as images get better, we use them to improve our data. Digitizing Tools and Techniques Load the BigMarSum &amp; RectSpring images in a data frame, and also the NWI, MNDOT, and DNR lakes data. Examine each layers; note how the various lakes data differ from each other, and from the lake boundary in the images. While the DNR data matches best, it still has some errors for our intended use, so we need to digitize a new lake boundary before adding vegetation data. You will be digitizing the current boundary only for Big Marine Lake, the biggest lake in the view, based on the RectSpring image. Use the map at the end of this section for guidance, and the examples below that illustrate the land/water boundary for the lake. First, In Arc Catalog, set the path to your Lab 4 data folder, then create a new empty polygon, lake layer (shape file or in a geodatabase) named Lake_2000, (Projected Coordinate SystemsUTMNorth AmericaNAD 1983 (2011) UTM Zone 15N), add it to your data frame, and set display, snapping, and sampling options as appropriate (refer to Lab 3 if youre fuzzy on how to do this). Use a scale of about 1:3,000 or larger (e.g., 1:800) when digitizing in this exercise to record sufficient detail. </p> <p> When creating large complex polygons, it may be useful to digitize the lake a section at a time, to contain errors and allow frequent saves. One approach (in video last week on polygon digitizing) is to </p> <p> first digitize a new polygon ( in the Create Features window), and digitize a portion of the lake, and then </p> <p> Advanced Editing </p> <p> 2 </p> <p> add to the polygon with the auto complete tool ( in the Create Features window) </p> <p> Remember with Auto Complete Polygon your actually create a new polygon adjacent to your original polygon. You will have to merge these separate parts of the lake with the EditMerge (may sure at least two adjacent pieces of the lake are selected). </p> <p> When auto-completing polygons, you need to be careful to start and end at the shores where the new polygon connects to the old polygon. See the videos on autocomplete polygons in last weeks lab if for help. You can also use a streaming version of auto-completion they call Auto </p> <p>Complete Freehand ( ) as noted in the videos for Lab 3 which turns on a streaming mode. This means you dont have to laboriously click each vertex, it inserts them automatically. However, you need a steady hand, and can more easily create overlaps, loops, and odd digitizing artifacts, so use with care. Another choice is to add a small polygon and use the Modify Feature Edit tool to add new sections on to your initial polygon (See Video: Merge_AutoComplete_Reshape_Save_Edits) Save your Edits FREQUENTLY. Make sure to digitize the bays, but dont digitize the boat docks as part of the shore. See the example map at the end of this section for guidance. You must digitize islands both in the lake and near shore, as shown in the example map. Perhaps the easiest way to digitize and island is: </p> <p> First digitize the lake, covering the islands. </p> <p> Turn the lake fill semi-transparent (properties, then display, set transparency something like 40 50%) </p> <p> Then digitize a polygon that outlines an island on top of the lake polygon. </p> <p> Select the island polygon </p> <p> From the main Editor menu, select the Clip option (see figure) </p> <p> A window will pop up, make sure the buffer distance is 0 and the discard overlap option is selected </p> <p>See the Lab 4 video, ClipDigitizing This will clip out the island, but you still have an island polygon. We dont want to include this in our lake layer. </p> <p> Advanced Editing </p> <p> 3 </p> <p> Select the island polygon, right click over it, and then select delete from the window that appears. Also note that there is substantial marshland that is considered part of the lake, and not land, along some sections. You will have to do your best job of identifying the land/water boundary, which is difficult because of similar appearing upland and lake vegetation near shore. Here, well call most wetlands part of the lake, that is, well lump wetland vegetation with the lake. Some wetland grasses grow both in shallow water and upland wet soils, and cattails are rooted but grow out of the water. The RectSpring image is generally much better for identifying the land/water boundary, as much of the aquatic vegetation is dead; there are still dense cattail beds that are part of the lake, but may at first appear like land. Use the examples below to guide you. The two example images illustrate the task. These are of the north shore of the eastern lobe of Big Marine Lake. An approximation of the land/water boundary is shown in yellow. The spring image is shown first. Note the water is dark blue, and cattails/wetland grasses show as dark grey. Roads are also grey, but uniform in color and straight-sided, so shape and texture sets them apart. Upland grasses are white, through pinks to red, so the boundary (in yellow) between upland and lowland is somewhat obvious for most of this stretch. There is a near-shore area of upland, labeled A on the images. This is a bit more complicated and subjective to delineate, because the both the marsh cattails and wetland grasses and the upland grass are shades of grey, so it isnt obvious where the land/water boundary should be. In addition, there are small patches of cattail embedded in the upland, which we include as part of the upland polygon because we cant spend all day digitizing. The summer image (2nd image shown below) helps, because the various shades of light red and pink are upland grass/forbs, while the emergent wetland cattails are blue/black to very dark red. Floating vegetation is also white/pink/light red, but their texture and location (areas that are water in spring, vegetation in summer) gives them away. </p> <p> Advanced Editing </p> <p> 4 </p> <p> Spring Image: Summer Image: </p> <p>A </p> <p>A </p> <p> Advanced Editing </p> <p> 5 </p> <p>Note that you should be especially careful in digitizing the shoreline in the connected bay at the south end of Big Marine Lake (inside the yellow rectangle, figure to the right). This appears to be a separate lake, but youll see when you zoom in that it is connected to the main body of the lake by a narrow channel. This happens a couple of other places around the lake, and you might notice if you carefully check the example map we provide that we dont always digitize these connected lakes as part of the Big Marine Lake; however, be especially careful in identifying and digitizing the land/water margin in this yellow box. We will use it later in this lab to make topologically consistent layers. </p> <p> Advanced Editing </p> <p> 6 </p> <p>When you are done digitizing the entire lake boundary, create a map that includes the lake polygon you digitized and one of the images as a background (data frame as in the example below). Add a descriptive title, your name, a north arrow and scale bar. Create a pdf document for your map, and turn it in. Lake Boundary to Digitize: </p> <p> Advanced Editing </p> <p> 7 </p> <p>Digitizing into a Geodatabase with Topology We often need to create vector data with topological constrains, e.g., making sure that upland polygons dont overlap with adjacent lake polygons, or that there are no gaps between lakes and uplands, and aquatic vegetation only occurs in lakes. As noted in Lab 1, we can enforce these constraints in a geodatabase, with topology. Well practice creating and digitizing into topology here. First, create a new ArcMap project, and add the lake boundary you digitized in the previous part of this exercise, and the RectSpring and BigSumUTM images. We wish to have four polygon layers in our geodatabase: uplands, lakes and ponds, emergent aquatic vegetation, and floating aquatic vegetation. Create an empty geodatabase. See the end of Lab 1 about topology, and Lab3 for instructions and videos if you are fuzzy on these first few steps on creating a geodatabase. Open ArcCatalog (filing cabinet icon) and right-click within a target directory to add a new geodatabase: </p> <p> This will open a dropdown list showing a directory tree. You can navigate to a subdirectory where you want to store your new geodatabase. Left click on the subdirectory to select it, then Right click over the directory to open a menu. Select New, then Personal Geodatabase from the menu. </p> <p> Advanced Editing </p> <p> 8 </p> <p>Here I named it BML_Topol. Within the new geodatabase, create a Feature Data Set (right click on the geodatabase, then NEW), </p> <p> name it something like BML_Layers, and </p> <p> select the UTM zone 15 (NAD83_2011) horizontal coordinate system, and </p> <p> use defaults for the rest of your choices. Now to add some data (see Video TopologyRules): right click on the BML_Layers feature data set, then Import: Import the polygon layer for the lakes boundary you just digitized (named Lakes_2000 in this example), also specifying the target location (your geodatabase), and the new name (Sublakes): This creates a copy of your data, as a feature layer in your feature data set within your new geodatabase. Lets repeat the import, now with the polyline shapefile named SouthBayArea.shp, this will be a bounding area for our work, and next import the Lakes_2000 file again, but name this second copy Uplands. </p> <p> Advanced Editing </p> <p> 9 </p> <p>It might not be clear now why we import the lake a second time, and into the Uplands layer, but there is a trick to speed up digitizing that well explain later. Finally, Create/add two new, empty, vegetation polygon layers (feature classes) to your feature data set name BML_Layers in your geodatabase. As noted before, you create these by </p> <p> opening the target geodatabase (BML_Topol), then </p> <p> right clicking on the feature data set (BML_Layers), then </p> <p> selecting New and Feature Class from the drop-down menu: </p> <p> Make sure you specify appropriate names, here I used Emerg_Aveg, and Float_Aveg Also be sure to specify a polygon type for each layer (usually the default), and accept the default values for all the other options. When youre finished you should have a geodatabase that looks something like: Now to set up the topology. First, review the introduction to topology in the textbook, and the short section on topology in ArcGIS at the end of Lab 1, and see the Video for this lab Topology Rules. We want to enforce a set of topological rules, so we create an empty topology, and build the rules. </p> <p> Right click on the in your BML_Layers feature data set, then </p> <p> New Topology </p> <p> Advanced Editing </p> <p> 10 </p> <p>This will open a Topology Wizard that steps you through setting up the topology. First, we envision four layers, the Lake, the Uplands, emergent aquatic vegetation, and floating aquatic vegetation. There is a fifth layer the defines the boundary or our study area, in our example named SouthBayArea_db. We want the layers to play nicely, in that we want them to be consistent with our ideas about the real-world features they represent. We wish to enforce the following rules: </p> <p>1) the lakes and uplands layer dont overlap (you cant have both a lake and upland in the same place) </p> <p>2) the emergent aquatic vegetation is contained within the lakes layer (it cant occur on the uplands) </p> <p>3) the floating aquatic vegetation is contained within the lakes layer (again, none on the uplands) </p> <p>4) the floating and emergent vegetation layers cant overlap 5) we dont want any gaps between the lakes and uplands layers </p> <p> Your first screen in the topology wizard just tells you it is there to help. The second screen lets you name it, and set a cluster tolerance, sort of like a snapping tolerance when it checks for errors. This is the distance at which it considers two points the same, and moves them to be co-incident. It is good to set your digitizing snapping tolerance about the same as your cluster tolerance. Here, I named the topology BML_Layers_Topology, and set the cluster tolerance at about 2 meters. As you should know from the readings, you set the tolerance in accordance with your accuracy of your base source, and your analysis requirements. Since the image data have about a 2 meter error, so the cluster tolerance shouldnt be much smaller. The next screen lets you select the features that will participate in the topology, those that will be used in rules: Click Next, and screen lets you set a Rank of Importance. From the reading, you should know that while fixing </p> <p> Advanced Editing </p> <p> 11 </p> <p>topology, the software can move vertices in your data to snap them into agreement. Here you can say which data are most accurate, or to which you want to snap other layers. If the numbers are equal, it snaps whichever vertex it selects first. However, if you set a rank numbers, it always snaps higher numbers to lower number layers, e.g., data for a layer with a rank of 2 are always snapped to a rank of 1. Leave these all equal, and just hit Next. Now we add rules. This next screen initially shows no rules, with options on the right margin of the window. Click on the Add Rule. button, you should see the following window: </p> <p> Each of entry lines on the left side of the window gives you a pick list, for the feature classes (top and sometimes bottom entry lines), and the rule you want to apply to the feature classes (middle entry line): </p> <p>EXAMPLE: Details to Follow </p> <p> Advanced Editing </p> <p> 12 </p> <p> We build rules by selecting the participating data and rule from the pick lists. For example, to create our Rule #1 listed at the start of this section, that lakes and uplands layers dont overlap, </p> <p> I select the SubLakes layer in the upper line, </p> <p> select the Uplands layer in the bottom line, and </p> <p> select Must Not Overlap With rule from the middle line: </p> <p> When I click O.K., the rule is added to my topology: </p> <p>EXAMPLE: Details to Follow </p> <p> Advanced Editing </p> <p> 13 </p> <p>If we make a mistake, we can click on a rule in the list and the...</p>