WEBVTT 1 00:00:00.200 --> 00:00:01.830 In the second part of the lecture, 2 00:00:01.830 --> 00:00:03.750 I'll demonstrate some of the typical types 3 00:00:03.750 --> 00:00:06.903 of calculations we can make using network analysis. 4 00:00:07.770 --> 00:00:09.510 Before we get into that, however, I'd like 5 00:00:09.510 --> 00:00:12.420 to take a closer look at network data sets. 6 00:00:12.420 --> 00:00:15.120 In particular, we'll look at the dataset properties 7 00:00:15.120 --> 00:00:16.860 to understand its definition 8 00:00:16.860 --> 00:00:19.230 and how we can extract important information 9 00:00:19.230 --> 00:00:20.940 for interpreting the outputs 10 00:00:20.940 --> 00:00:23.850 of our network analysis calculations. 11 00:00:23.850 --> 00:00:28.260 Then we'll look at four examples, a route calculation, 12 00:00:28.260 --> 00:00:33.030 a closest facility calculation, a service area definition, 13 00:00:33.030 --> 00:00:36.360 and an origin destination cost matrix. 14 00:00:36.360 --> 00:00:39.363 Let's switch over to our ArcGIS and take a look. 15 00:00:44.040 --> 00:00:46.740 Here we are in my project 16 00:00:46.740 --> 00:00:49.410 and if I look in my Project Geo database, 17 00:00:49.410 --> 00:00:52.110 I see I've got a road network dataset. 18 00:00:52.110 --> 00:00:54.690 It appears that it's a feature dataset. 19 00:00:54.690 --> 00:00:56.080 Let's take a look inside 20 00:00:56.970 --> 00:01:00.060 and we see that feature dataset has three components. 21 00:01:00.060 --> 00:01:02.340 The actual road network itself, 22 00:01:02.340 --> 00:01:03.173 and if you notice 23 00:01:03.173 --> 00:01:05.280 that icon looks just a little bit different 24 00:01:05.280 --> 00:01:08.223 with that red line that appears to go across a graph. 25 00:01:09.060 --> 00:01:11.640 Also included are the network junctions 26 00:01:11.640 --> 00:01:16.640 a point feature class and streets a line feature class. 27 00:01:17.700 --> 00:01:19.860 I've already added the data to the project, 28 00:01:19.860 --> 00:01:22.080 but remember if you wanna add all of the contents 29 00:01:22.080 --> 00:01:25.320 of a feature dataset to a project at one time, 30 00:01:25.320 --> 00:01:27.930 you can right click the feature dataset name 31 00:01:27.930 --> 00:01:29.493 and choose Add To Current Map. 32 00:01:30.840 --> 00:01:34.380 If we look at the properties of those individual components 33 00:01:34.380 --> 00:01:39.380 of the dataset, the first two are junctions 34 00:01:41.610 --> 00:01:42.760 and our streets 35 00:01:46.860 --> 00:01:48.690 look familiar to what we've seen before 36 00:01:48.690 --> 00:01:50.883 when we've investigated layer properties. 37 00:01:51.720 --> 00:01:56.720 However, if we look at our road network itself 38 00:01:57.420 --> 00:02:00.180 and check those properties out, we see something 39 00:02:00.180 --> 00:02:02.430 that looks a little bit different. 40 00:02:02.430 --> 00:02:04.480 Let's focus in on this summary area 41 00:02:05.730 --> 00:02:08.257 and if I expand that, I see the summary details 42 00:02:08.257 --> 00:02:11.463 of the creation of the network dataset. 43 00:02:13.380 --> 00:02:17.130 I can see that there are almost 24,000 edges 44 00:02:17.130 --> 00:02:19.773 and 10,600 junctions. 45 00:02:20.760 --> 00:02:22.740 I didn't specify any turn rules in this, 46 00:02:22.740 --> 00:02:24.603 so none are indicated here. 47 00:02:25.890 --> 00:02:27.783 If I scroll down a bit further, 48 00:02:28.680 --> 00:02:30.840 I notice the cost attributes. 49 00:02:30.840 --> 00:02:34.455 In this case, we've defined cost using minutes 50 00:02:34.455 --> 00:02:37.920 and using distance 51 00:02:37.920 --> 00:02:40.683 and that distance specifically is measured in meters. 52 00:02:41.670 --> 00:02:44.130 We could look more closely at our restrictions 53 00:02:44.130 --> 00:02:46.050 to see what happens 54 00:02:46.050 --> 00:02:48.200 when the network encounters one-way streets 55 00:02:49.140 --> 00:02:51.573 or junctions with specific turn requirements. 56 00:02:52.920 --> 00:02:57.120 The last thing I'll point out is the road class descriptor. 57 00:02:57.120 --> 00:03:01.120 In this case, there's an attribute within my streets dataset 58 00:03:02.040 --> 00:03:04.800 that specifies the road class. 59 00:03:04.800 --> 00:03:08.310 Is it a highway, a ferry, a roundabout, 60 00:03:08.310 --> 00:03:09.873 or maybe just a local road? 61 00:03:10.740 --> 00:03:12.390 Each one of those is considered 62 00:03:12.390 --> 00:03:16.293 and then classified according to that attribute value. 63 00:03:18.330 --> 00:03:21.033 If I look over at my Chittenden street's dataset, 64 00:03:21.870 --> 00:03:24.056 I notice interstates, highways 65 00:03:24.056 --> 00:03:28.503 and others where others seems to represent local streets. 66 00:03:32.280 --> 00:03:35.040 That sort of network data sets in a nutshell, 67 00:03:35.040 --> 00:03:37.020 certainly a lot more to understand if you were trying 68 00:03:37.020 --> 00:03:39.483 to build one of those network data sets yourself. 69 00:03:40.738 --> 00:03:43.230 It's up to you what to display. 70 00:03:43.230 --> 00:03:45.150 I tend to turn the junctions off 71 00:03:45.150 --> 00:03:46.620 and leave my streets on 72 00:03:46.620 --> 00:03:49.290 so I can see the different street types 73 00:03:49.290 --> 00:03:51.303 that are being used in the analysis. 74 00:03:52.320 --> 00:03:55.623 Okay, let's take a look at some network analysis examples. 75 00:03:57.060 --> 00:04:00.220 This first example, we'll look at a simple route calculation 76 00:04:01.890 --> 00:04:05.130 to calculate a route using network analysis 77 00:04:05.130 --> 00:04:09.116 in ArcGIS select the Analysis ribbon 78 00:04:09.116 --> 00:04:11.613 and then choose the Network Analysis dropdown. 79 00:04:12.870 --> 00:04:15.330 Before you make any calculations however, 80 00:04:15.330 --> 00:04:17.320 be sure that you specified 81 00:04:18.630 --> 00:04:21.240 the appropriate network data source. 82 00:04:21.240 --> 00:04:23.226 Again, you wanna use something local. 83 00:04:23.226 --> 00:04:25.440 We don't have the credits to support 84 00:04:25.440 --> 00:04:29.400 the cloud computing version of network analysis. 85 00:04:29.400 --> 00:04:30.233 Once you've ensured 86 00:04:30.233 --> 00:04:33.870 that you're using a local network data set from there, 87 00:04:33.870 --> 00:04:37.293 choose route to find the shortest path between stops. 88 00:04:38.220 --> 00:04:40.462 ArcGIS will make a route analysis layer 89 00:04:40.462 --> 00:04:44.280 that feature data set that includes all the inputs 90 00:04:44.280 --> 00:04:46.390 and outputs from a route analysis 91 00:04:48.960 --> 00:04:51.090 we see that's been created over here 92 00:04:51.090 --> 00:04:52.893 in our contents pane on the left. 93 00:04:54.150 --> 00:04:57.049 We also notice that with the route selected, 94 00:04:57.049 --> 00:05:02.049 I have a route option on the ribbon across the top 95 00:05:02.400 --> 00:05:04.620 of the software interface. 96 00:05:04.620 --> 00:05:07.717 One other thing to note, this says route two. 97 00:05:07.717 --> 00:05:09.710 That's because I already computed a route 98 00:05:09.710 --> 00:05:12.030 within this project. 99 00:05:12.030 --> 00:05:16.410 ArcGIS will just sequentially number these data sets 100 00:05:16.410 --> 00:05:18.960 as you create additional ones. 101 00:05:18.960 --> 00:05:22.533 Okay, next step, let's import our stops. 102 00:05:23.580 --> 00:05:27.030 In this case, I've already created two points 103 00:05:27.030 --> 00:05:27.960 that I wanna navigate 104 00:05:27.960 --> 00:05:31.503 between indicated with the backpacker icon. 105 00:05:32.970 --> 00:05:37.970 If I click import stops ArcGIS automatically knows 106 00:05:38.070 --> 00:05:41.770 that I'm using Route two for my network analysis layer 107 00:05:43.347 --> 00:05:46.650 that the sublayer I'm gonna populate here is called Stops 108 00:05:46.650 --> 00:05:49.440 and again, we see that as the first entry in my route 109 00:05:49.440 --> 00:05:51.304 to feature dataset 110 00:05:51.304 --> 00:05:54.246 and I just need to specify my locations 111 00:05:54.246 --> 00:05:57.033 in this case the shortest path. 112 00:05:58.440 --> 00:06:01.709 If I click run here, no, the only thing I'm doing 113 00:06:01.709 --> 00:06:06.709 is adding my stops to my stops feature class. 114 00:06:07.080 --> 00:06:09.090 Now we see values of one 115 00:06:09.090 --> 00:06:12.483 and two symbolized by those green points, 116 00:06:13.920 --> 00:06:16.143 so that's it and its most basic form, 117 00:06:17.220 --> 00:06:19.833 I can click Run to generate that route. 118 00:06:20.670 --> 00:06:23.932 Real quickly before I do, I'll open the attribute table 119 00:06:23.932 --> 00:06:26.823 for the routes feature class. 120 00:06:27.780 --> 00:06:29.880 Notice that there's nothing contained 121 00:06:29.880 --> 00:06:32.043 within that attribute table just yet. 122 00:06:33.120 --> 00:06:35.270 If I come back to my network Analyst ribbon 123 00:06:36.111 --> 00:06:40.050 and click Run, we'll notice 124 00:06:40.050 --> 00:06:41.730 that my features are all locked down 125 00:06:41.730 --> 00:06:44.730 while ArcGIS makes that calculation 126 00:06:44.730 --> 00:06:49.730 and once done, we see the route highlighted here in green 127 00:06:50.460 --> 00:06:54.933 and we see the record populated in my routes table. 128 00:06:56.040 --> 00:06:58.110 If I scroll to the right a bit, 129 00:06:58.110 --> 00:07:01.170 I can see that my first stop was number one, 130 00:07:01.170 --> 00:07:03.213 my last stop was number two. 131 00:07:06.196 --> 00:07:10.800 The total distance in meters was almost 5,200 132 00:07:10.800 --> 00:07:15.300 and my total cost was about 4.68. 133 00:07:15.300 --> 00:07:18.210 Remember that total distance is being measured in meters 134 00:07:18.210 --> 00:07:21.210 and the total cost is being measured in minutes. 135 00:07:21.210 --> 00:07:22.440 We saw that information 136 00:07:22.440 --> 00:07:24.930 when we looked at the network dataset definition. 137 00:07:24.930 --> 00:07:26.460 One more thing to note here, 138 00:07:26.460 --> 00:07:28.360 I can click the Show Directions button 139 00:07:29.340 --> 00:07:33.750 to list the directions that define that route. 140 00:07:33.750 --> 00:07:35.670 I could print them for here 141 00:07:35.670 --> 00:07:39.780 or use the directions geo processing tool to export them 142 00:07:39.780 --> 00:07:43.980 to a text HTML or XML format. 143 00:07:43.980 --> 00:07:46.560 Let's look at one more route example here. 144 00:07:46.560 --> 00:07:48.439 In this case, suppose you want to travel 145 00:07:48.439 --> 00:07:52.050 among more than two point locations 146 00:07:52.050 --> 00:07:55.080 and so have I highlighted a bunch of restaurant locations 147 00:07:55.080 --> 00:07:57.390 in and around the Burlington area. 148 00:07:57.390 --> 00:07:59.489 I've already created my route analysis layer 149 00:07:59.489 --> 00:08:02.523 and imported those restaurant locations as stops. 150 00:08:04.050 --> 00:08:07.078 If I look at the attribute table for that stops data set, 151 00:08:07.078 --> 00:08:10.710 I see that I've got 13 locations that each one 152 00:08:10.710 --> 00:08:13.260 of those locations has been assigned a name 153 00:08:13.260 --> 00:08:15.892 that comes from the original object ID 154 00:08:15.892 --> 00:08:18.033 and also a sequence number. 155 00:08:19.290 --> 00:08:20.640 Let's look at the route tab 156 00:08:22.110 --> 00:08:24.963 and our interface to see what that sequence is all about. 157 00:08:25.950 --> 00:08:28.320 We see here a sequence parameter 158 00:08:28.320 --> 00:08:32.804 and this specifies to use the current, so if I click run 159 00:08:32.804 --> 00:08:36.824 and solve for this, using that current sequence, 160 00:08:36.824 --> 00:08:41.824 ArcGIS will generate the best route. 161 00:08:42.750 --> 00:08:47.250 Again, this means I'm going from one to two to three to four 162 00:08:47.250 --> 00:08:51.030 and so on based on that location 163 00:08:51.030 --> 00:08:53.073 and sequence number that we see here. 164 00:08:54.390 --> 00:08:59.390 Now if I change that sequence from use current 165 00:09:00.000 --> 00:09:03.690 to one of the others, we'll get a different output. 166 00:09:03.690 --> 00:09:04.523 Before we do that, 167 00:09:04.523 --> 00:09:06.900 let's just consult the routes table real quickly 168 00:09:09.030 --> 00:09:11.580 to see that we've got a single route. 169 00:09:11.580 --> 00:09:15.060 First stop is one, the last stop is 13. 170 00:09:15.060 --> 00:09:19.560 There's 13 total stops with a total travel cost 171 00:09:19.560 --> 00:09:21.663 of just over 27 minutes. 172 00:09:22.590 --> 00:09:27.273 Okay, let's change from use current to find best. 173 00:09:29.070 --> 00:09:30.790 Click Run once again to solve 174 00:09:34.170 --> 00:09:36.020 and we'll see what the difference is. 175 00:09:39.030 --> 00:09:40.930 ArcGIS is computed a new route 176 00:09:42.330 --> 00:09:45.780 and if we look at the routes attribute table, 177 00:09:45.780 --> 00:09:50.760 we see that the new route only costs about 16 minutes 178 00:09:50.760 --> 00:09:54.540 of time instead of the 27 minutes we saw before. 179 00:09:54.540 --> 00:09:56.490 In this next example, 180 00:09:56.490 --> 00:09:59.190 we'll look at the closest facility analysis. 181 00:09:59.190 --> 00:10:00.960 There's been an accident on the highway 182 00:10:00.960 --> 00:10:04.500 and we wanna figure out which fire station should respond. 183 00:10:04.500 --> 00:10:07.110 Notice that for the closest facility analysis, 184 00:10:07.110 --> 00:10:11.970 it requires two inputs, facilities and incidents. 185 00:10:11.970 --> 00:10:15.180 Okay, let's import our incidents first. 186 00:10:15.180 --> 00:10:17.010 That's gonna be the traffic accident 187 00:10:17.010 --> 00:10:20.193 that we see with the icon in the middle of the screen. 188 00:10:21.930 --> 00:10:26.930 I'll add that and I'll import my facilities. 189 00:10:27.300 --> 00:10:28.750 Those are the fire stations 190 00:10:30.420 --> 00:10:32.970 that will be responding to the accident. 191 00:10:32.970 --> 00:10:34.920 Once that tool is completed, 192 00:10:34.920 --> 00:10:37.167 I can hover over my ad locations 193 00:10:37.167 --> 00:10:42.167 and the history pane, scroll down to the messages section 194 00:10:45.060 --> 00:10:47.220 and I can see that 31 features out 195 00:10:47.220 --> 00:10:50.070 of the 31 in my fire station's dataset 196 00:10:50.070 --> 00:10:52.470 were added as facilities. 197 00:10:52.470 --> 00:10:55.050 If I solve for that particular configuration 198 00:10:55.050 --> 00:10:57.810 and then open the routes attribute table, 199 00:10:57.810 --> 00:11:01.380 I see a total travel cost of just over two minutes 200 00:11:01.380 --> 00:11:03.633 between the facility and the incident. 201 00:11:04.530 --> 00:11:06.300 One more thing to note however, 202 00:11:06.300 --> 00:11:08.370 is that my directions parameter seems 203 00:11:08.370 --> 00:11:10.980 to be pointing towards the facility 204 00:11:10.980 --> 00:11:12.300 when what we actually want 205 00:11:12.300 --> 00:11:16.020 is to travel from the fire station to the accident. 206 00:11:16.020 --> 00:11:20.880 Let's change that, set that to away from facilities 207 00:11:20.880 --> 00:11:22.563 and rerun our analysis. 208 00:11:24.630 --> 00:11:27.420 Well, sure enough, we see a different result. 209 00:11:27.420 --> 00:11:30.540 In this case, if you wanna travel from a fire station 210 00:11:30.540 --> 00:11:31.770 to the accident, 211 00:11:31.770 --> 00:11:35.820 the closest fire station is about 3.6 minutes away. 212 00:11:35.820 --> 00:11:39.741 Again, this direction parameter influences the direction 213 00:11:39.741 --> 00:11:42.270 of travel for route planning purposes. 214 00:11:42.270 --> 00:11:44.340 It does not affect which direction you're allowed 215 00:11:44.340 --> 00:11:46.053 to travel on the streets. 216 00:11:47.040 --> 00:11:49.380 Let's look at another example. 217 00:11:49.380 --> 00:11:52.410 In this case, instead of just a single facility responding 218 00:11:52.410 --> 00:11:56.520 to an incident, let's change that to five facilities, 219 00:11:56.520 --> 00:11:58.230 perhaps it's a really bad accident 220 00:11:58.230 --> 00:12:01.773 and you need multiple fire stations to make an appearance? 221 00:12:03.390 --> 00:12:06.610 We'll click Run once again to solve for the parameters 222 00:12:07.950 --> 00:12:10.260 and investigate the output. 223 00:12:10.260 --> 00:12:13.650 If I look at my route's attribute table this time, 224 00:12:13.650 --> 00:12:15.150 not surprisingly, 225 00:12:15.150 --> 00:12:18.090 I see that there are five records in the table. 226 00:12:18.090 --> 00:12:21.420 One for each route between the fire station 227 00:12:21.420 --> 00:12:22.893 and the traffic accident. 228 00:12:24.150 --> 00:12:25.240 Scroll to the right 229 00:12:26.864 --> 00:12:29.130 and I can look at my travel cost information. 230 00:12:29.130 --> 00:12:31.890 Not surprisingly, the fastest fire station 231 00:12:31.890 --> 00:12:34.590 to reach is still at 3.6 minutes. 232 00:12:34.590 --> 00:12:36.573 If I saw in descending order, 233 00:12:37.830 --> 00:12:41.310 I can see that the furthest away fire station 234 00:12:41.310 --> 00:12:44.463 of the five takes almost six minutes to get there. 235 00:12:45.870 --> 00:12:48.750 Now let's take a look at one last example. 236 00:12:48.750 --> 00:12:51.420 Remember I said there were 31 fire stations 237 00:12:51.420 --> 00:12:54.450 that were included in my facilities dataset, 238 00:12:54.450 --> 00:12:58.470 so let's have ArcGIS look at all 31 facilities, 239 00:12:58.470 --> 00:12:59.670 but this time, let's see 240 00:13:00.956 --> 00:13:03.706 how many can make it to the incident within 10 minutes. 241 00:13:04.680 --> 00:13:05.513 Click Run. 242 00:13:06.852 --> 00:13:09.552 Once again to analyze under this current configuration 243 00:13:11.220 --> 00:13:15.870 in ArcGIS finds that there are 10 fire stations 244 00:13:15.870 --> 00:13:17.640 within that 10 minute cutoff time, 245 00:13:17.640 --> 00:13:22.230 so 10 of the 31 fire stations can make it within 10 minutes. 246 00:13:22.230 --> 00:13:25.563 The slowest of those takes about 9.7 minutes. 247 00:13:27.870 --> 00:13:30.374 Okay, that's it for closest facilities for now, 248 00:13:30.374 --> 00:13:34.080 let's switch gears and take a look at service areas. 249 00:13:34.080 --> 00:13:36.990 We'll continue to stick with our fire stations 250 00:13:36.990 --> 00:13:38.493 as our facilities dataset. 251 00:13:39.570 --> 00:13:43.140 I've already set up my service area analysis layer 252 00:13:43.140 --> 00:13:44.820 and imported my facilities. 253 00:13:44.820 --> 00:13:47.793 The 31 fire stations we used in the last example. 254 00:13:49.170 --> 00:13:50.760 A couple of things to note here. 255 00:13:50.760 --> 00:13:53.550 Again, we have control over the direction 256 00:13:53.550 --> 00:13:55.890 and this time once again, we want to compute that direction 257 00:13:55.890 --> 00:13:57.903 as being away from the facilities. 258 00:13:58.830 --> 00:14:01.350 One other thing we can look at are the cutoffs, 259 00:14:01.350 --> 00:14:03.600 and this is the cutoff value in the units 260 00:14:03.600 --> 00:14:05.190 of the travel mode. 261 00:14:05.190 --> 00:14:08.430 In this case, we're talking about minutes, 262 00:14:08.430 --> 00:14:13.263 so let's compute three minute, five minute, 263 00:14:14.430 --> 00:14:19.430 and 10 minute cutoff times away from each of our facilities. 264 00:14:20.190 --> 00:14:23.130 One other thing to note is the output geometry. 265 00:14:23.130 --> 00:14:25.549 You have a choice among polygons, lines 266 00:14:25.549 --> 00:14:28.590 or polygons and lines. 267 00:14:28.590 --> 00:14:31.110 I tend to choose just polygons. 268 00:14:31.110 --> 00:14:34.170 You can also specify whether you want your polygons 269 00:14:34.170 --> 00:14:37.680 to overlap, dissolve, or be split. 270 00:14:37.680 --> 00:14:40.310 Once again, I like the default setting of overlap 271 00:14:40.310 --> 00:14:43.740 and I keep the rings as well so that each one 272 00:14:43.740 --> 00:14:46.697 of those polygons represents that time interval 273 00:14:46.697 --> 00:14:48.513 for the travel cutoff. 274 00:14:49.440 --> 00:14:51.873 Okay, let's solve and see what we get. 275 00:14:54.150 --> 00:14:55.230 In terms of output, 276 00:14:55.230 --> 00:14:59.220 we get the polygon definitions for those cutoff times. 277 00:14:59.220 --> 00:15:00.990 Note three, five, 278 00:15:00.990 --> 00:15:04.443 and 10 match the cutoffs we designate up at the top. 279 00:15:05.280 --> 00:15:07.530 If we look at the attribute table, 280 00:15:07.530 --> 00:15:09.840 we see 93 different polygons, 281 00:15:09.840 --> 00:15:12.240 which makes sense based on our settings. 282 00:15:12.240 --> 00:15:16.590 Three polygons for each of the 31 fire stations. 283 00:15:16.590 --> 00:15:19.320 You can see in the the attribute table, 284 00:15:19.320 --> 00:15:23.790 the from and two break for each one of those fire stations, 285 00:15:23.790 --> 00:15:27.963 so with ID of 170, the zero to three minute polygon, 286 00:15:30.720 --> 00:15:32.673 the three to five minute polygon, 287 00:15:34.230 --> 00:15:36.123 and the five to 10 minute polygon. 288 00:15:37.500 --> 00:15:40.980 The other thing we can note is gaps in coverage. 289 00:15:40.980 --> 00:15:44.160 Everywhere that's not covered by one of these polygon 290 00:15:44.160 --> 00:15:48.630 boundaries that we see in our table of contents means 291 00:15:48.630 --> 00:15:50.160 that no fire station can reach 292 00:15:50.160 --> 00:15:52.533 that location within 10 minutes. 293 00:15:53.670 --> 00:15:55.740 The last of these examples we'll look at 294 00:15:55.740 --> 00:15:59.550 is calculating an origin destination cost matrix. 295 00:15:59.550 --> 00:16:02.450 In this example, I wanna try something a little different. 296 00:16:03.510 --> 00:16:06.060 I've already created my origin destination cost matrix 297 00:16:06.060 --> 00:16:10.440 analysis layer, but instead of importing existing data 298 00:16:10.440 --> 00:16:12.840 for my origins and destinations, 299 00:16:12.840 --> 00:16:15.090 I'm gonna create them on the fly. 300 00:16:15.090 --> 00:16:17.910 Suppose you go out to eat every Thursday night 301 00:16:17.910 --> 00:16:19.590 with three other friends, 302 00:16:19.590 --> 00:16:22.141 you all live in different locations. 303 00:16:22.141 --> 00:16:27.141 Let's create origin points for each one 304 00:16:27.660 --> 00:16:30.963 of the four houses, yours plus your three friends, 305 00:16:32.190 --> 00:16:33.330 so I'll just assign those 306 00:16:33.330 --> 00:16:38.313 to four different network locations. 307 00:16:40.320 --> 00:16:41.583 Click OK. 308 00:16:42.630 --> 00:16:45.570 Note that I've actually modified a data layer, 309 00:16:45.570 --> 00:16:47.373 so I need to save my edits. 310 00:16:48.600 --> 00:16:50.163 Click Yes to save those. 311 00:16:51.390 --> 00:16:53.910 Let's do the same thing for our destinations. 312 00:16:53.910 --> 00:16:55.980 Suppose you've got five different restaurants 313 00:16:55.980 --> 00:16:57.930 that you really like and those are the ones 314 00:16:57.930 --> 00:17:01.620 that you always choose for those weekly outings. 315 00:17:01.620 --> 00:17:04.361 Once again, I'll choose to create them 316 00:17:04.361 --> 00:17:08.290 and this time I'll choose from the destinations template 317 00:17:09.960 --> 00:17:12.842 and I'll just add five destinations 318 00:17:12.842 --> 00:17:16.953 in this little area of downtown Burlington. 319 00:17:18.510 --> 00:17:23.510 Okay, save those changes and we should be ready to go. 320 00:17:24.990 --> 00:17:26.610 We see some of the same functionality 321 00:17:26.610 --> 00:17:29.128 as before in terms of our ability to specify a cutoff 322 00:17:29.128 --> 00:17:32.250 or the number of destinations. 323 00:17:32.250 --> 00:17:34.830 One other thing to point out here is your choice 324 00:17:34.830 --> 00:17:37.410 between no lines and straight lines. 325 00:17:37.410 --> 00:17:39.568 No lines will not render the graph 326 00:17:39.568 --> 00:17:42.450 and straight lines will render the graph 327 00:17:42.450 --> 00:17:45.000 that you might expect as part of your output. 328 00:17:45.000 --> 00:17:46.978 Let's keep the straight lines in 329 00:17:46.978 --> 00:17:49.773 and solve for the parameters we have. 330 00:17:51.600 --> 00:17:55.380 Remember, there's four origin locations, one for each of you 331 00:17:55.380 --> 00:17:59.610 and your friends' houses and five restaurants. 332 00:17:59.610 --> 00:18:03.870 That means we should see 20 records in our output table, 333 00:18:03.870 --> 00:18:05.745 and if I open that lines attribute table, 334 00:18:05.745 --> 00:18:09.123 I do indeed see 20 records included in the table. 335 00:18:10.260 --> 00:18:12.630 There are four different origin IDs 336 00:18:12.630 --> 00:18:15.000 and each one of those origins goes to all five 337 00:18:15.000 --> 00:18:16.980 of the different restaurants. 338 00:18:16.980 --> 00:18:18.480 Using the attribute table, 339 00:18:18.480 --> 00:18:21.480 I could locate the closest restaurant to each one 340 00:18:21.480 --> 00:18:23.456 of our friends' houses. 341 00:18:23.456 --> 00:18:26.880 Be careful using the origin destination cost matrix, 342 00:18:26.880 --> 00:18:28.860 especially with big data sets. 343 00:18:28.860 --> 00:18:33.240 This is very computationally intensive and could take hours 344 00:18:33.240 --> 00:18:35.493 or days to run if you're not careful. 345 00:18:36.570 --> 00:18:40.320 Well, that's it for now with network analysis and ArcGIS. 346 00:18:40.320 --> 00:18:42.690 I think it's time to let you take the reins. 347 00:18:42.690 --> 00:18:45.570 Just remember, it's not safe to geo process and drive, 348 00:18:45.570 --> 00:18:47.250 so make sure to compute those directions 349 00:18:47.250 --> 00:18:48.600 before you leave the house.