WEBVTT 1 00:00:01.350 --> 00:00:03.300 Welcome back to Module 1. 2 00:00:03.300 --> 00:00:05.400 In Lecture 2, we'll examine feature creation 3 00:00:05.400 --> 00:00:07.950 and editing in ArcGIS. 4 00:00:07.950 --> 00:00:08.970 In our previous work, 5 00:00:08.970 --> 00:00:11.310 we created new feature classes as the outputs 6 00:00:11.310 --> 00:00:15.120 of a geo processing task, like a clip or a buffer. 7 00:00:15.120 --> 00:00:17.550 Suppose instead, you want to create feature class 8 00:00:17.550 --> 00:00:19.620 from scratch, a blank container 9 00:00:19.620 --> 00:00:21.663 that you'll populate with features. 10 00:00:23.220 --> 00:00:26.310 There are two approaches available to you in ArcGIS. 11 00:00:26.310 --> 00:00:29.190 Either way, you'll arrive at the same endpoint, 12 00:00:29.190 --> 00:00:31.200 a new feature class. 13 00:00:31.200 --> 00:00:33.300 You can launch the create feature class wizard 14 00:00:33.300 --> 00:00:35.130 from a geo database. 15 00:00:35.130 --> 00:00:38.400 Right click the geo database, select new and feature class 16 00:00:38.400 --> 00:00:40.260 from the list of options. 17 00:00:40.260 --> 00:00:42.990 That's what we see over in the image on the left. 18 00:00:42.990 --> 00:00:44.670 Alternatively, you can search 19 00:00:44.670 --> 00:00:46.320 the geo processing tool library 20 00:00:46.320 --> 00:00:48.750 for the create feature class tool. 21 00:00:48.750 --> 00:00:51.003 Let's take a closer look at both approaches. 22 00:00:52.290 --> 00:00:55.263 The first of these employs a wizard to help you out. 23 00:00:56.190 --> 00:00:57.750 The wizard leads you step-by-step 24 00:00:57.750 --> 00:01:00.033 through the feature class creation process. 25 00:01:01.110 --> 00:01:03.810 The first step asks you to specify a dataset name 26 00:01:03.810 --> 00:01:06.780 and optionally an alias as well. 27 00:01:06.780 --> 00:01:10.680 Next, specify the geometry point, line, 28 00:01:10.680 --> 00:01:13.500 or polygon of the dataset. 29 00:01:13.500 --> 00:01:15.570 In this case, we'll select polygon 30 00:01:15.570 --> 00:01:18.120 since we want to eventually digitize building footprints 31 00:01:18.120 --> 00:01:19.983 on the capital campus in Montpelier. 32 00:01:20.940 --> 00:01:21.773 You have the option 33 00:01:21.773 --> 00:01:24.720 to set additional geometric properties here too. 34 00:01:24.720 --> 00:01:27.390 The M value stores information about routes 35 00:01:27.390 --> 00:01:31.020 and the Z value stores information about 3D data. 36 00:01:31.020 --> 00:01:33.570 We won't use either of those here. 37 00:01:33.570 --> 00:01:35.130 Lastly, you have the option 38 00:01:35.130 --> 00:01:37.563 to add your output data set to the current map. 39 00:01:39.120 --> 00:01:41.940 The next step is where you can specify additional attributes 40 00:01:41.940 --> 00:01:43.860 and their data types. 41 00:01:43.860 --> 00:01:46.620 Note that ArcGIS already includes the object ID 42 00:01:46.620 --> 00:01:49.320 and shape attributes by default. 43 00:01:49.320 --> 00:01:52.200 You can of course modify your table structure later 44 00:01:52.200 --> 00:01:54.091 if you don't have your field definition specified 45 00:01:54.091 --> 00:01:56.040 at this point. 46 00:01:56.040 --> 00:01:59.670 I added a new attribute here named infrastructure type 47 00:01:59.670 --> 00:02:00.843 as a text field. 48 00:02:03.900 --> 00:02:06.840 Next, choose your spatial reference. 49 00:02:06.840 --> 00:02:08.760 In this case, I'm going to use information 50 00:02:08.760 --> 00:02:11.250 from one of the existing map layers, 51 00:02:11.250 --> 00:02:14.133 NAD 83 Vermont State Plane Meters. 52 00:02:16.830 --> 00:02:19.470 Then specify the dataset tolerance 53 00:02:19.470 --> 00:02:21.780 or leave the default values in place. 54 00:02:21.780 --> 00:02:23.430 The tolerance is used when evaluating 55 00:02:23.430 --> 00:02:26.370 the spatial relationships between coordinates 56 00:02:26.370 --> 00:02:28.120 and whether to consider them equal. 57 00:02:29.700 --> 00:02:32.010 If you know something about the resolution of the dataset, 58 00:02:32.010 --> 00:02:35.070 you can specify that here or once again, 59 00:02:35.070 --> 00:02:36.723 accept the default values. 60 00:02:37.890 --> 00:02:40.080 Lastly, if you'd like to specify something 61 00:02:40.080 --> 00:02:42.510 other than the default configuration keyword, 62 00:02:42.510 --> 00:02:44.580 this is the place to do so. 63 00:02:44.580 --> 00:02:46.280 Then click finish 64 00:02:46.280 --> 00:02:48.413 to complete the create feature class process. 65 00:02:50.670 --> 00:02:51.503 Once you're comfortable 66 00:02:51.503 --> 00:02:54.660 with the overall feature creation process, 67 00:02:54.660 --> 00:02:57.990 the second approach seen here is a solid alternative 68 00:02:57.990 --> 00:02:59.760 to employing the wizard. 69 00:02:59.760 --> 00:03:01.710 You're still specifying the same information 70 00:03:01.710 --> 00:03:03.360 for the most part. 71 00:03:03.360 --> 00:03:05.273 One notable difference 72 00:03:05.273 --> 00:03:07.140 is that you cannot add new attributes interactively 73 00:03:07.140 --> 00:03:09.030 like you could with the wizard. 74 00:03:09.030 --> 00:03:10.950 Instead, you could use a template dataset 75 00:03:10.950 --> 00:03:13.860 to provide the definition of the attribute table, 76 00:03:13.860 --> 00:03:16.410 just the fields, not the data. 77 00:03:16.410 --> 00:03:18.060 Regardless of your approach, 78 00:03:18.060 --> 00:03:20.193 you will end up with a new feature class. 79 00:03:23.160 --> 00:03:26.520 One more item I'd like to talk about before we move on 80 00:03:26.520 --> 00:03:29.010 is the concept of a feature dataset. 81 00:03:29.010 --> 00:03:31.770 We touched on this briefly in the introduction course. 82 00:03:31.770 --> 00:03:33.420 It will make use of feature datasets 83 00:03:33.420 --> 00:03:35.790 throughout the advanced course. 84 00:03:35.790 --> 00:03:37.470 A feature dataset is a collection 85 00:03:37.470 --> 00:03:39.663 of related feature classes. 86 00:03:40.740 --> 00:03:44.040 Unlike a feature class that can only have a single geometry, 87 00:03:44.040 --> 00:03:45.990 a feature dataset can include point, 88 00:03:45.990 --> 00:03:49.170 line and polygon feature classes. 89 00:03:49.170 --> 00:03:51.600 All the feature classes within a feature dataset 90 00:03:51.600 --> 00:03:53.493 share a common coordinate system. 91 00:03:54.420 --> 00:03:56.640 Lastly, feature datasets can be used 92 00:03:56.640 --> 00:03:59.787 to create controller datasets like a topology dataset, 93 00:03:59.787 --> 00:04:02.580 which we'll talk about here in a minute. 94 00:04:02.580 --> 00:04:05.400 So create a feature dataset, 95 00:04:05.400 --> 00:04:09.000 add one or more feature classes to the feature dataset, 96 00:04:09.000 --> 00:04:10.140 and then optionally create 97 00:04:10.140 --> 00:04:12.183 one or more controllers if desired. 98 00:04:14.310 --> 00:04:17.370 From the create feature dataset geo processing tool, 99 00:04:17.370 --> 00:04:20.880 we see that ArcGIS is asking for three parameters, 100 00:04:20.880 --> 00:04:22.890 the output geo database, 101 00:04:22.890 --> 00:04:25.680 the name of the feature dataset you want to create, 102 00:04:25.680 --> 00:04:28.233 and the coordinate system of the feature dataset. 103 00:04:29.100 --> 00:04:31.275 I've expanded the coordinate system dropdown menu 104 00:04:31.275 --> 00:04:33.480 to look at the list of possible options 105 00:04:33.480 --> 00:04:36.000 for the coordinate system definition. 106 00:04:36.000 --> 00:04:39.270 We see the list of dataset included in the current map pane. 107 00:04:39.270 --> 00:04:40.860 You could also click the globe 108 00:04:40.860 --> 00:04:42.210 on the right side of the interface 109 00:04:42.210 --> 00:04:44.790 if you want to specify a coordinate system not included 110 00:04:44.790 --> 00:04:46.113 in the list of options. 111 00:04:48.000 --> 00:04:50.400 We'll select NAD 83 State Plain Vermont 112 00:04:50.400 --> 00:04:51.730 as the coordinate system 113 00:04:52.650 --> 00:04:55.500 for our capital campus assets feature dataset 114 00:04:55.500 --> 00:04:56.643 and then click run. 115 00:04:57.900 --> 00:05:00.180 If I look at my geo database again, 116 00:05:00.180 --> 00:05:04.110 I now see a new feature dataset named Capital Campus Assets. 117 00:05:04.110 --> 00:05:07.470 There are no feature classes or controller datasets included 118 00:05:07.470 --> 00:05:09.483 in the newly created feature dataset. 119 00:05:12.600 --> 00:05:16.140 Either drag and drop a feature class within the geo database 120 00:05:16.140 --> 00:05:18.720 or import/export feature classes 121 00:05:18.720 --> 00:05:21.180 or shape files from an external source 122 00:05:21.180 --> 00:05:23.013 into that feature dataset. 123 00:05:24.120 --> 00:05:26.370 You could also choose to create a new feature class 124 00:05:26.370 --> 00:05:28.380 just like we did in the first couple slides 125 00:05:28.380 --> 00:05:31.713 and store that new feature class within the feature dataset. 126 00:05:33.840 --> 00:05:36.600 The image on the left displays the lab one geo database 127 00:05:36.600 --> 00:05:39.240 before adding the building's feature class 128 00:05:39.240 --> 00:05:40.230 while the image on the right 129 00:05:40.230 --> 00:05:42.651 displays the lab one geo database 130 00:05:42.651 --> 00:05:45.090 after adding the building's feature class 131 00:05:45.090 --> 00:05:47.853 to the capital campus assets feature data set. 132 00:05:51.390 --> 00:05:54.063 Step three is to create a controller data set. 133 00:05:55.020 --> 00:05:56.790 This step is optional. 134 00:05:56.790 --> 00:05:58.740 Sometimes the only benefit you're looking for 135 00:05:58.740 --> 00:05:59.880 out of a feature data set 136 00:05:59.880 --> 00:06:04.140 is data organization within a complex geo database design. 137 00:06:04.140 --> 00:06:06.480 Let's create a topology controller as an example 138 00:06:06.480 --> 00:06:07.830 of what can be done here to help 139 00:06:07.830 --> 00:06:10.290 in the data development process. 140 00:06:10.290 --> 00:06:12.780 What can topology do for us? 141 00:06:12.780 --> 00:06:15.060 Topology defines the spatial relationships 142 00:06:15.060 --> 00:06:18.750 between or among features in one or more data sets. 143 00:06:18.750 --> 00:06:20.820 From a spatial analysis perspective, 144 00:06:20.820 --> 00:06:23.100 topology can manage the shared geometry 145 00:06:23.100 --> 00:06:25.080 between or among features, 146 00:06:25.080 --> 00:06:27.660 define and enforce data integrity rules, 147 00:06:27.660 --> 00:06:31.590 and help identify and correct digitizing errors. 148 00:06:31.590 --> 00:06:34.860 So for example, you can use topology to ensure 149 00:06:34.860 --> 00:06:37.770 that two polygons do not overlap. 150 00:06:37.770 --> 00:06:39.450 Think here about creating parcel data 151 00:06:39.450 --> 00:06:41.580 and the trouble that would arise if two different owners 152 00:06:41.580 --> 00:06:43.530 make a claim to the same piece of land. 153 00:06:45.990 --> 00:06:48.900 Right clicking the capital campus assets feature data set 154 00:06:48.900 --> 00:06:50.460 and selecting new topology 155 00:06:50.460 --> 00:06:53.823 from the list of options opens the Create Topology Wizard. 156 00:06:55.770 --> 00:06:58.980 Since there's only one feature class in our feature dataset, 157 00:06:58.980 --> 00:07:01.800 that is the only option in the list of feature classes. 158 00:07:01.800 --> 00:07:02.850 I'll click the checkbox 159 00:07:02.850 --> 00:07:04.773 to include it in my topology rule set. 160 00:07:05.640 --> 00:07:08.310 ArcGIS assigns a topology name by default 161 00:07:08.310 --> 00:07:09.660 by appending the word topology 162 00:07:09.660 --> 00:07:12.150 to the end of the feature dataset name. 163 00:07:12.150 --> 00:07:13.850 You can change this if you'd like. 164 00:07:15.510 --> 00:07:18.990 Next, let's look at the rule creation process. 165 00:07:18.990 --> 00:07:21.423 Click the add icon to add a new rule, 166 00:07:22.980 --> 00:07:25.890 then choose buildings from the list of feature classes 167 00:07:25.890 --> 00:07:28.590 and set the rule to must not overlap. 168 00:07:28.590 --> 00:07:30.420 This ensures that if new features are added 169 00:07:30.420 --> 00:07:32.070 to the building's feature class, 170 00:07:32.070 --> 00:07:33.670 they cannot overlap one another. 171 00:07:35.220 --> 00:07:37.320 Click next once again to arrive 172 00:07:37.320 --> 00:07:39.960 to the summary of the topology definition. 173 00:07:39.960 --> 00:07:41.910 Review the contents before clicking finish 174 00:07:41.910 --> 00:07:43.323 to complete the process. 175 00:07:44.820 --> 00:07:47.130 If we look again at the lab one geo database 176 00:07:47.130 --> 00:07:48.240 and expand the contents 177 00:07:48.240 --> 00:07:51.540 of the capital campus assets feature dataset, 178 00:07:51.540 --> 00:07:54.106 we now see the topology controller we just created 179 00:07:54.106 --> 00:07:56.220 in addition to the building's feature class 180 00:07:56.220 --> 00:07:57.273 we added earlier. 181 00:07:59.190 --> 00:08:00.400 Let's use the topology 182 00:08:01.249 --> 00:08:02.280 to validate a data set we're working on 183 00:08:02.280 --> 00:08:04.443 as part of our capital campus inventory. 184 00:08:06.660 --> 00:08:08.820 The image on this slide shows a blue polygon 185 00:08:08.820 --> 00:08:10.650 denoting our area of interest, 186 00:08:10.650 --> 00:08:12.963 a portion of the capital campus in Montpelier. 187 00:08:14.130 --> 00:08:17.610 If we navigate to the edit ribbons manage edit section, 188 00:08:17.610 --> 00:08:21.240 we see there's no topology specified from my project. 189 00:08:21.240 --> 00:08:22.830 The dropdown list 190 00:08:22.830 --> 00:08:25.290 displays the list of available topology options. 191 00:08:25.290 --> 00:08:27.390 I don't see the one that I just created, 192 00:08:27.390 --> 00:08:29.820 but that's the one I want to use. 193 00:08:29.820 --> 00:08:32.373 Let's fix that by adding some data to the project. 194 00:08:33.930 --> 00:08:36.600 After adding the buildings feature class to my project, 195 00:08:36.600 --> 00:08:38.130 I now see an additional option 196 00:08:38.130 --> 00:08:40.350 in the topology dropdown menu. 197 00:08:40.350 --> 00:08:42.840 The topology controller we just created, 198 00:08:42.840 --> 00:08:44.343 seems like progress to me. 199 00:08:46.050 --> 00:08:48.660 After selecting capital campus assets topology 200 00:08:48.660 --> 00:08:53.010 from the list of options, click the error inspector button 201 00:08:53.010 --> 00:08:56.010 to open the error inspector interface. 202 00:08:56.010 --> 00:08:59.250 Notice the message indicating the need for more information. 203 00:08:59.250 --> 00:09:02.910 In this case, a map that contains the error layers. 204 00:09:02.910 --> 00:09:04.830 This terminology is a bit confusing here, 205 00:09:04.830 --> 00:09:07.770 but basically what ArcGIS is asking for 206 00:09:07.770 --> 00:09:11.490 is the topology controller to be added to the project. 207 00:09:11.490 --> 00:09:13.650 Let's do that the same way we add a feature class 208 00:09:13.650 --> 00:09:16.893 to a project, drag and drop it into the map pane. 209 00:09:20.430 --> 00:09:21.870 Once that's been added, you might be in 210 00:09:21.870 --> 00:09:23.910 for a little bit of a surprise. 211 00:09:23.910 --> 00:09:27.270 Closer inspection of the capital campus assets topology 212 00:09:27.270 --> 00:09:29.610 reveals four different items: 213 00:09:29.610 --> 00:09:34.080 Dirty areas, plus point, line, and polygon errors. 214 00:09:34.080 --> 00:09:36.360 Since we're working with a polygon data set, 215 00:09:36.360 --> 00:09:39.600 we should only concern ourselves with the polygon errors. 216 00:09:39.600 --> 00:09:43.113 The dirty area denotes potential problems in the data. 217 00:09:44.070 --> 00:09:47.130 Let's return to the error inspector one more time. 218 00:09:47.130 --> 00:09:49.290 Looks good this time around. 219 00:09:49.290 --> 00:09:52.530 Click the validate button to check your data for errors. 220 00:09:52.530 --> 00:09:55.890 Fortunately, I didn't find any problems, but at this point, 221 00:09:55.890 --> 00:09:57.960 there are just those two building polygons 222 00:09:57.960 --> 00:10:00.813 and they're very clearly distinct from one another. 223 00:10:02.490 --> 00:10:03.840 Be sure to click the save button 224 00:10:03.840 --> 00:10:05.959 after you validate your data 225 00:10:05.959 --> 00:10:08.580 because ArcGIS has made changes to the topology data set, 226 00:10:08.580 --> 00:10:11.673 noting that in this case there are no topology errors. 227 00:10:13.380 --> 00:10:15.600 Suppose I digitize a new building footprint 228 00:10:15.600 --> 00:10:17.400 in the study area that overlaps 229 00:10:17.400 --> 00:10:19.950 one of the existing building footprints. 230 00:10:19.950 --> 00:10:22.050 You see, I've drawn a triangular shaped footprint 231 00:10:22.050 --> 00:10:23.730 that most definitely overlaps 232 00:10:23.730 --> 00:10:25.480 with one of the existing buildings. 233 00:10:26.430 --> 00:10:28.129 If we go back into the error inspector 234 00:10:28.129 --> 00:10:32.010 and validate the data, we notice a couple of things. 235 00:10:32.010 --> 00:10:34.410 The topology rule identified an error 236 00:10:34.410 --> 00:10:37.350 and the error inspector provides us with a zoomed in view 237 00:10:37.350 --> 00:10:39.270 of the error itself. 238 00:10:39.270 --> 00:10:41.280 In this case, there's just a single error, 239 00:10:41.280 --> 00:10:42.810 but if there are multiple errors, 240 00:10:42.810 --> 00:10:46.500 they'd all be listed here each with its own preview. 241 00:10:46.500 --> 00:10:48.540 If we look at the details, we see that the rule 242 00:10:48.540 --> 00:10:52.140 that's been violated is that the buildings must not overlap. 243 00:10:52.140 --> 00:10:55.040 They clearly do, and that area of overlap is identified 244 00:10:55.040 --> 00:10:57.243 by the red polygon we see above. 245 00:10:58.890 --> 00:11:01.920 There are three possible solutions to this error. 246 00:11:01.920 --> 00:11:04.140 I could create a new feature of the problem area 247 00:11:04.140 --> 00:11:06.630 distinct from the other two polygons. 248 00:11:06.630 --> 00:11:09.120 In this case, we'd end up with three polygons representing 249 00:11:09.120 --> 00:11:11.040 the two building footprints. 250 00:11:11.040 --> 00:11:13.050 Not a good solution as far as I can tell. 251 00:11:13.050 --> 00:11:16.710 I could also choose to remove the overlap. 252 00:11:16.710 --> 00:11:18.600 That would delete the polygon from the dataset, 253 00:11:18.600 --> 00:11:21.570 which would produce a gap in the building footprints, 254 00:11:21.570 --> 00:11:23.493 also not an ideal solution. 255 00:11:24.540 --> 00:11:27.720 The best option here is to merge the problem polygon 256 00:11:27.720 --> 00:11:30.520 with one of the other two of polygons it is adjacent to. 257 00:11:32.010 --> 00:11:34.620 Click the merge icon and a new window appears, 258 00:11:34.620 --> 00:11:36.390 listing the potential merge candidates 259 00:11:36.390 --> 00:11:37.640 for the offending region. 260 00:11:38.520 --> 00:11:40.020 You can click an item in the list 261 00:11:40.020 --> 00:11:43.560 so that you can identify it as it flashes in the map pane. 262 00:11:43.560 --> 00:11:46.170 I'm going to merge the problem area into building two, 263 00:11:46.170 --> 00:11:48.390 the actual capital building itself, 264 00:11:48.390 --> 00:11:50.990 and leave the rest of the triangle as a new polygon. 265 00:11:52.080 --> 00:11:55.050 I make my choice, the merge happens, 266 00:11:55.050 --> 00:11:56.790 and now there are no longer any errors listed 267 00:11:56.790 --> 00:11:58.263 in the error inspector pane. 268 00:11:59.370 --> 00:12:01.050 If I click validate again, 269 00:12:01.050 --> 00:12:03.270 we confirm that no errors are present. 270 00:12:03.270 --> 00:12:05.370 Click save and note that all dirty areas 271 00:12:05.370 --> 00:12:07.080 have been cleaned up. 272 00:12:07.080 --> 00:12:10.230 Lots more to explore here, but I'll stop there for now. 273 00:12:10.230 --> 00:12:12.054 You'll get some practice creating feature classes 274 00:12:12.054 --> 00:12:14.910 and features during your lab exercise, 275 00:12:14.910 --> 00:12:16.650 and while this is valuable to learn, 276 00:12:16.650 --> 00:12:18.390 you'll also appreciate the limited amount 277 00:12:18.390 --> 00:12:20.940 of digitizing required to complete your assignment.