Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:00,000 --> 00:00:05,055
ArcMap is a powerful but complex piece of software.
2
00:00:05,055 --> 00:00:08,475
I just want to go through some of the basics to get you started,
3
00:00:08,475 --> 00:00:12,205
that may not be so obvious when you're first beginning to use the program.
4
00:00:12,205 --> 00:00:16,180
So, first, I'm going to show you a canned example using screenshots and PowerPoint,
5
00:00:16,180 --> 00:00:18,329
just so we can focus on the concepts for minute,
6
00:00:18,329 --> 00:00:22,075
and then I'll move over to the software to show you how it works in reality.
7
00:00:22,075 --> 00:00:27,950
So, in ArcMap, you'll notice that in the upper left here, it says,
8
00:00:27,950 --> 00:00:31,420
My first map.mxd- ArcMap,
9
00:00:31,420 --> 00:00:35,260
and that means that we've saved this is what's known as a map document.
10
00:00:35,260 --> 00:00:38,630
So, if I look at this in our catalog,
11
00:00:38,630 --> 00:00:40,270
we can zoom in here a little bit,
12
00:00:40,270 --> 00:00:42,580
you'll see that it has this mxd extension,
13
00:00:42,580 --> 00:00:45,240
so that's indicating that it's a map document.
14
00:00:45,240 --> 00:00:48,080
Of course, it's also labeled over here,
15
00:00:48,080 --> 00:00:50,335
so it's easy for us to understand what it is that we're looking at.
16
00:00:50,335 --> 00:00:52,375
So, what's a map document anyway?
17
00:00:52,375 --> 00:00:56,915
A map document stores what data to show,
18
00:00:56,915 --> 00:00:58,540
where to find the data,
19
00:00:58,540 --> 00:01:00,285
and how to show the data.
20
00:01:00,285 --> 00:01:05,280
It does not store the actual map data itself. So, why not?
21
00:01:05,280 --> 00:01:07,670
So, this is a point of confusion for
22
00:01:07,670 --> 00:01:10,475
a lot of people when they're first starting out with ArcMap,
23
00:01:10,475 --> 00:01:15,790
is that they assume that when you assemble the data in to a map, in ArcMap,
24
00:01:15,790 --> 00:01:18,400
and you put it all together and then you say "Save," that
25
00:01:18,400 --> 00:01:21,420
it's saving all of that data inside the map document.
26
00:01:21,420 --> 00:01:24,270
That's actually not a very efficient way to do things,
27
00:01:24,270 --> 00:01:27,075
for a couple of reasons.
28
00:01:27,075 --> 00:01:32,380
What we'd prefer to do in a map document is only store the data once.
29
00:01:32,380 --> 00:01:36,775
That way, different map documents can show the same data in different ways.
30
00:01:36,775 --> 00:01:38,840
So, for example, in one map document,
31
00:01:38,840 --> 00:01:41,225
you might show road data in
32
00:01:41,225 --> 00:01:45,910
thick black lines and another map document using the same road data,
33
00:01:45,910 --> 00:01:48,180
you could be showing them as red thick lines,
34
00:01:48,180 --> 00:01:49,735
or thin lines, or whatever.
35
00:01:49,735 --> 00:01:51,860
The idea is that different people can access
36
00:01:51,860 --> 00:01:54,650
that same data set and show it the way that they want in
37
00:01:54,650 --> 00:01:57,365
their map document without having to duplicate
38
00:01:57,365 --> 00:02:00,525
that data every time you save the map document.
39
00:02:00,525 --> 00:02:04,740
So that way, imagine you might work in an organization that has hundreds,
40
00:02:04,740 --> 00:02:07,535
or thousands even of map documents.
41
00:02:07,535 --> 00:02:12,590
Imagine if you had to store the road data each time you save that map document,
42
00:02:12,590 --> 00:02:14,330
you might have hundreds of copies of
43
00:02:14,330 --> 00:02:17,030
this road data or thousands of copies of this road data,
44
00:02:17,030 --> 00:02:20,390
which we take up an enormous amount of room on your server,
45
00:02:20,390 --> 00:02:22,790
or hard drive, or wherever it is that you're storing it.
46
00:02:22,790 --> 00:02:27,140
Not only that, but every time you wanted to update the road save,
47
00:02:27,140 --> 00:02:28,850
somebody found a mistake in that dataset,
48
00:02:28,850 --> 00:02:30,965
or they wanted to add a new road to that dataset,
49
00:02:30,965 --> 00:02:35,270
they would have to go through each of those map documents that each have a copy
50
00:02:35,270 --> 00:02:39,530
of the map data or the row data and update it over,
51
00:02:39,530 --> 00:02:42,265
and over, and over again, which would not be very efficient either.
52
00:02:42,265 --> 00:02:46,020
So, what's much better is that we have one copy of the map data,
53
00:02:46,020 --> 00:02:48,140
as many map documents as we want,
54
00:02:48,140 --> 00:02:49,880
and then if we need to update that road data,
55
00:02:49,880 --> 00:02:51,840
we can just update it once.
56
00:02:51,840 --> 00:02:56,495
The next time, each of those map documents is open all it's doing is saying,
57
00:02:56,495 --> 00:02:58,920
"What data do I need to go find?"
58
00:02:58,920 --> 00:03:01,730
So, one of those on its list might be the road data,
59
00:03:01,730 --> 00:03:04,655
and it looks up, "How do I need to show that data."
60
00:03:04,655 --> 00:03:08,480
So, stored in that map document is how to show that actual data,
61
00:03:08,480 --> 00:03:11,430
and then it presents it to you in that particular map document.
62
00:03:11,430 --> 00:03:17,250
So, it's stored once, and it stores how to show it and what data to actually show.
63
00:03:17,250 --> 00:03:18,770
So, that's much more efficient.
64
00:03:18,770 --> 00:03:24,255
But like I said, it's not very intuitive if you're not used to seeing it that way.
65
00:03:24,255 --> 00:03:28,590
Let's have a look at how map documents work inside ArcMap.
66
00:03:28,590 --> 00:03:31,565
We've got our Toronto data here.
67
00:03:31,565 --> 00:03:36,050
I can add fire stations just by dragging and dropping them onto the map area.
68
00:03:36,050 --> 00:03:37,910
I could just as easily go over and use
69
00:03:37,910 --> 00:03:42,000
the Add Data button and click on that and say "Roads" so I could
70
00:03:42,000 --> 00:03:48,320
actually use the control key to select more than one and add them that way.
71
00:03:48,320 --> 00:03:50,210
It's exactly the same thing either way.
72
00:03:50,210 --> 00:03:53,540
Then I could quickly change the symbology.
73
00:03:53,540 --> 00:03:59,925
Let's say I wanted to make these red squares that are maybe ten.
74
00:03:59,925 --> 00:04:01,575
I'm just doing this quickly.
75
00:04:01,575 --> 00:04:08,180
Say "OK." We're going to make our roads thin,
76
00:04:08,180 --> 00:04:12,865
grey lines, say something like that so they're not too obvious.
77
00:04:12,865 --> 00:04:20,985
Then, our vegetation, we'll make that nice screen with no outline.
78
00:04:20,985 --> 00:04:23,120
So, very quickly, I've made a map.
79
00:04:23,120 --> 00:04:24,655
It doesn't look too bad.
80
00:04:24,655 --> 00:04:27,410
So now that I've done that, I want to be able to save this so I can come
81
00:04:27,410 --> 00:04:29,860
back to it later and either continue to work on it,
82
00:04:29,860 --> 00:04:32,330
or show it to someone else, or whatever it is I may want to do.
83
00:04:32,330 --> 00:04:35,244
So, I can just go up to File,
84
00:04:35,244 --> 00:04:40,160
Save, and I can save this as a map document.
85
00:04:40,160 --> 00:04:41,590
You'll see there under Save As type,
86
00:04:41,590 --> 00:04:45,320
it says ArcMap Document (.mxd).
87
00:04:45,320 --> 00:04:47,410
I can just give it whatever name I want.
88
00:04:47,410 --> 00:04:55,780
So, I'll just say, Toronto fire stations and I say "Save."
89
00:04:57,260 --> 00:05:00,660
it's funny is this happens.
90
00:05:00,660 --> 00:05:02,075
Oh, there it is.
91
00:05:02,075 --> 00:05:04,620
It's at the top there, Toronto fire stations.mxd.
92
00:05:04,620 --> 00:05:06,440
What I was going to say is,
93
00:05:06,440 --> 00:05:09,910
sometimes, it may not show up right away and you may have to refresh it.
94
00:05:09,910 --> 00:05:12,920
So, you can do that just by hitting the F5 key,
95
00:05:12,920 --> 00:05:16,665
or you can right-click and just select Refresh there.
96
00:05:16,665 --> 00:05:18,460
Either way, it's the same thing.
97
00:05:18,460 --> 00:05:22,500
So, you'll see that we have that Toronto fire stations.mxd.
98
00:05:22,500 --> 00:05:31,240
So now, if I create a new map document or I just start over again,
99
00:05:31,240 --> 00:05:33,420
let's just do this,
100
00:05:33,520 --> 00:05:39,645
and if I just drag and drop the Toronto fire station.mxd into ArcMap,
101
00:05:39,645 --> 00:05:41,795
it'll open that map document,
102
00:05:41,795 --> 00:05:44,440
we'll go and find the list it has stored in there,
103
00:05:44,440 --> 00:05:46,200
it has all the data that it needs to find,
104
00:05:46,200 --> 00:05:48,690
and how to show that data.
105
00:05:48,710 --> 00:05:54,815
So, we'll actually open that map document exactly like it was when I saved it.
106
00:05:54,815 --> 00:06:00,400
So, here we have our exact same points lines and polygons just as it was when I left off.
107
00:06:00,400 --> 00:06:02,180
So, that's important.
108
00:06:02,180 --> 00:06:03,960
So, the thing is,
109
00:06:03,960 --> 00:06:05,720
of course, is if I wanted to,
110
00:06:05,720 --> 00:06:08,480
I could create a different version of this map document, let's say,
111
00:06:08,480 --> 00:06:10,000
where the fire stations are blue,
112
00:06:10,000 --> 00:06:11,780
or they're triangles, or whatever.
113
00:06:11,780 --> 00:06:13,790
Save that as a different map document,
114
00:06:13,790 --> 00:06:17,110
and then I'll be using the same data file,
115
00:06:17,110 --> 00:06:19,290
the same data that's in the geodatabase,
116
00:06:19,290 --> 00:06:23,200
but I would be able to show it differently using a different map document.
117
00:06:23,200 --> 00:06:25,945
So, that's how map documents work.
118
00:06:25,945 --> 00:06:30,190
To something else that's like a map document,
119
00:06:30,190 --> 00:06:32,355
that can be really handy, which is a layer,
120
00:06:32,355 --> 00:06:34,690
it's an lyr file.
121
00:06:34,690 --> 00:06:37,730
It can be confusing, because sometimes we refer to feature
122
00:06:37,730 --> 00:06:41,305
classes or these things that we see over her,
123
00:06:41,305 --> 00:06:46,020
we;ll sometimes generically refer to those as map layers.
124
00:06:46,020 --> 00:06:47,650
But in Ezri's world,
125
00:06:47,650 --> 00:06:50,085
they have a very specific definition of what a layer is,
126
00:06:50,085 --> 00:06:53,750
which is something different than just calling this feature class a map layer.
127
00:06:53,750 --> 00:06:55,765
What am I talking about? Well, let me show you.
128
00:06:55,765 --> 00:07:02,600
If for example, I wanted to be able to save the fact that my fire stations are
129
00:07:02,600 --> 00:07:05,750
shown as these red squares and be able to use that
130
00:07:05,750 --> 00:07:09,260
in different map documents but have them always look exactly the same,
131
00:07:09,260 --> 00:07:12,200
I can save that as a layer file and then I can add
132
00:07:12,200 --> 00:07:15,700
that layer file into a new map document and save that symbology.
133
00:07:15,700 --> 00:07:17,335
Let me show you how that works.
134
00:07:17,335 --> 00:07:20,325
If I right-click on here and say,
135
00:07:20,325 --> 00:07:27,390
"Save As Layer File," what that will do is I can save that in my set drive,
136
00:07:27,390 --> 00:07:31,935
you'll notice that it's automatically naming that.
137
00:07:31,935 --> 00:07:35,940
So, Fire_Stations.lyr, that's the name of my feature class.
138
00:07:35,940 --> 00:07:38,305
But notice that it has that lyr extension,
139
00:07:38,305 --> 00:07:41,485
and that it's saving it as a layer file.
140
00:07:41,485 --> 00:07:47,780
So, when I do that and click Save,
141
00:07:47,780 --> 00:07:50,890
it's similar to a map document in that that layer file is
142
00:07:50,890 --> 00:07:54,355
storing what data to go and find and how to show that data,
143
00:07:54,355 --> 00:07:56,190
but just for one feature class,
144
00:07:56,190 --> 00:07:58,505
not for an entire map document.
145
00:07:58,505 --> 00:08:08,500
So, for example, if I created a new map document like this,
146
00:08:08,500 --> 00:08:11,165
and if I drag my fire stations layered,
147
00:08:11,165 --> 00:08:18,595
you'll notice that I can now see this layer file inside this folder.
148
00:08:18,595 --> 00:08:20,320
It's stored outside of the geodatabase,
149
00:08:20,320 --> 00:08:22,530
by the way, as the map document.
150
00:08:22,530 --> 00:08:25,100
So, map documents in layer files are
151
00:08:25,100 --> 00:08:27,940
not stored inside geodatabases. You think they would be?
152
00:08:27,940 --> 00:08:30,240
It makes sense, but they aren't.
153
00:08:30,240 --> 00:08:33,510
Anyway. So, we have this Fire_Stations.lyr.
154
00:08:33,510 --> 00:08:35,490
You can see a little icon for it there.
155
00:08:35,490 --> 00:08:38,825
If I drag that
156
00:08:38,825 --> 00:08:42,949
into a brand new map document where I haven't done anything else and I just add it,
157
00:08:42,949 --> 00:08:49,340
it remembers the symbology that I assigned to it in that previous map documents.
158
00:08:49,340 --> 00:08:51,380
So, now, any map document that I use,
159
00:08:51,380 --> 00:08:54,705
if I add the lyr file,
160
00:08:54,705 --> 00:08:57,305
it will show it exactly the way I wanted to.
161
00:08:57,305 --> 00:09:01,375
But, what can be a little confusing is if I remove that,
162
00:09:01,375 --> 00:09:06,905
if I add the Fire_Station data without the lyr,
163
00:09:06,905 --> 00:09:09,290
so here it is here, it does not do that.
164
00:09:09,290 --> 00:09:10,670
It's only the layer file.
165
00:09:10,670 --> 00:09:13,140
That's what's actually storing how to to show it.
166
00:09:13,140 --> 00:09:16,490
So, these are both based on the same data but
167
00:09:16,490 --> 00:09:20,880
the layer file is used to save how to make that data look.
168
00:09:20,880 --> 00:09:24,379
It's really just a thing for convenience maybe you work in a large organization
169
00:09:24,379 --> 00:09:26,180
where you're in charge of making sure that
170
00:09:26,180 --> 00:09:28,070
all the maps have a very consistent look to them.
171
00:09:28,070 --> 00:09:31,280
So, you can be in charge of making all these layer files and then telling people
172
00:09:31,280 --> 00:09:35,630
use these two in order to make sure that the look is always exactly the same.
173
00:09:35,630 --> 00:09:39,725
One other thing that can be confusing while I'm on the topic is that
174
00:09:39,725 --> 00:09:43,210
if I right-click on Fire_Stations and say,
175
00:09:43,210 --> 00:09:46,030
"Save As Layer File," now that we know what a layer file is,
176
00:09:46,030 --> 00:09:48,990
we know that it's not creating a copy of the data.
177
00:09:48,990 --> 00:09:51,410
But because there's this terminology issue,
178
00:09:51,410 --> 00:09:55,280
because we often refer to a feature class as a map layer,
179
00:09:55,280 --> 00:09:57,170
it's very natural for people to think "Well,
180
00:09:57,170 --> 00:09:59,135
if I see Save As Layer File,
181
00:09:59,135 --> 00:10:01,370
that I'm saving a copy of the data."
182
00:10:01,370 --> 00:10:02,955
That is not what's happening.
183
00:10:02,955 --> 00:10:05,140
All that's doing is stating how to show the data.
184
00:10:05,140 --> 00:10:07,580
If you want to save a copy of the data,
185
00:10:07,580 --> 00:10:13,085
then you have to go just above it there to Data and then select Export Data,
186
00:10:13,085 --> 00:10:17,270
and then that will export a copy of the data into a new feature class,
187
00:10:17,270 --> 00:10:19,695
so that you can have a duplicate version of that dataset,
188
00:10:19,695 --> 00:10:21,185
if that's what you're trying to do.
189
00:10:21,185 --> 00:10:23,060
So, I just wanted to make sure that's clear because it's
190
00:10:23,060 --> 00:10:26,690
an easy mistake for people to make or an easy assumption to make.16126
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.