Introducción a la base de datos geográficos.

Time

Caption

0:01

Let’s get started with some maps to look at the ways that their

0:04

data is organized. We will begin with this map of the Esri campus

0:08

in Redlands, California. In this ArcMap document, in the table of

0:14

contents, we see the list of layers for the map, including trees,

0:18

roads, and sidewalks that are features of the campus. Let's look

0:24

behind the scenes to learn what is going on and where the data

0:27

is coming from. I'll click List By Source and hover over the

0:31

geodatabase to display the path to the data. I'll expand the

0:36

geodatabase and scroll down to some of the same layers that

0:41

we saw earlier, such as trees and roads. This indicates that the

0:46

map is organized by layers. Now that we know one way to view

0:51

geodatabase data, let's use another. I'll open the Catalog window

0:57

and expand the geodatabase. You're probably already familiar

1:02

with feature classes. And here are a few: we have Boulders as a

1:06

point feature class, BuildingFootprints as a polygon feature

1:10

class. Contours and Fences are line feature classes. You could

1:16

use this geodatabase data to create maps for utilities, facilities

1:22

management, or even floor plans to share with emergency

1:26

responders. In this next map, you see infrastructure for the city of

1:32

Fort Pierce in Florida. From the Catalog window, let's look at

1:38

how they've organized their data in this geodatabase. Here you

1:42

see an icon that you may not know about. It represents a feature

1:46

dataset. When we look inside, we see feature classes that, in

1:51

this case, have been organized thematically. Data like this can be

1:56

used by hydrologists or highway engineers. So now you've seen

2:01

a feature dataset as another way of organizing data in your

2:04

geodatabase. Now, let's look at the data behind this map of the

2:11

Mount Baker area in northwest Washington state. You see the

2:16

already familiar icon for a feature dataset. In addition, there are

2:21

several non-spatial tables that you can store in the geodatabase.

2:26

These tables store additional attributes that are not necessarily

2:31

related to geography, but they're stored in the same geodatabase

2:35

as your feature classes. This is just another example of ways to

2:39

organize your data in your geodatabase in order to keep all of

2:44

your data together. You will cover all of this information–feature

2:49

classes, feature datasets, and non-spatial tables–in this course.

2:57

But there is even more to the geodatabase than what you have

3:00

seen so far. The geodatabase can also store more advanced

3:04

data types that are not covered, and I want to show them to you

3:08

so you can begin to see even more advantages of the

3:11

geodatabase. When we expand the GeologicMap feature dataset,

3:18

notice the icons for feature-linked annotation. They look like this,

3:22

with two arrows. Here is the icon for annotation. Feature-linked

3:29

annotation is stored as an annotation feature class in the

3:33

geodatabase, along with its associated geographic data, that

3:38

gives you one way to manage text on your map. In this parcel

3:43

map, we'll look at additional advantages of the geodatabase.

3:50

I'll expand TaxParcels. Notice that we have an icon that

3:57

represents a relationship between a feature class and a

4:01

non-spatial table. Here's the non-spatial table and here is the

4:07

feature class: TaxParcel. There's also an icon that represents

4:13

topology. This tells you that some features share geometry, such

4:19

as the shared boundary between two polygon land parcels. In

4:25

summary, after you have learned the basics, you can transition to

4:30

more advanced features of the geodatabase.