gis brownbag series attributes. in the beginning… earliest gis systems did not have attributes...

41
GIS Brownbag Series Attributes

Post on 20-Jan-2016

213 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

GIS Brownbag Series

Attributes

Page 2: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

In the beginning…

Earliest GIS systems did not have attributes

Needed separate layers for labels (e.g. names)

CAD software still maintains different separate layers

Page 3: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Amelia Earhart

Page 4: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Shapefile showing Amelia’s last flight

Right-click on the name of the shapefile for the flight path to open attribute table

Page 5: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

LENGTH FROM_CITY TO_CITY

1414.502 Oakland Tucson

2323.930 Tucson New Orleans

1186.745 New Orleans Miami

1783.788 Miami San Juan

974.294 San Juan Caripito

1004.282 Caripito Paramaribo

Attributes:

•Length

•FROM_CITY

•TO_CITY

Page 6: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Feeding sites of a chimp called “Fifi”

Aerial photograph ofGombe National Park.

Feeding sites stored in a shapefile or personal geodatabase

Aerial photograph stored as a raster

Page 7: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Raster attributes

Number of attributes attached to rasters is limited

Page 8: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Shapefile or Personal Geodatabase Attributes

Many attributes can be attached to each feature

OBJECTID and Shape attributes are automatically

generated by ArcGIS

Page 9: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Attributes can be:

• Numbers (whole or with decimal places)

• Names or text

• Dates

• Hyperlinks

Page 10: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Depending on type of attribute different maps can be created

This map was created based on text attribute

Numbers allow to display population size

Page 11: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Depending on type of attribute different analysis can be done

What if you want to show the area for

each County?

Page 12: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Adding fields to an attribute table

Step 1: Create a new attribute that will hold the area

B. Click “Options” button. Then select “Add

Field”

A. Open attribute table

If “Add Field..” is “greyed-out” stop edit session and try again

Page 13: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Pick any name you like. Must be < 11 characters

Other choices: Text, Date, Short or Long Integer

Number of spaces to store a number

Number of decimals. E.g. 1.1234

Page 14: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

The new attribute “Area” has been added!

Right-click on “AREA” and select

Calculate Geometry

Notice how all the area’s are set to “0”

Step 2: Calculate the area

Page 15: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software
Page 16: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software
Page 17: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Joining other data to attribute tables

Table with population size for each County

Goal: show those numbers on a map

Solution: join this data to the shapefile from previous slide

Step 1: Save your data in Excel as a DBF4 file

Page 18: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Add your .dbf file to ArcMap

Page 19: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Determine how you are going to join your data

Join “population” table to shapefile

Look for a primary key: an attribute that both tables have in common and that can be used for the join.

Here: both tables have County names

Page 20: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Joining tables

Right-click on the shapefile

Page 21: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Choose “No”

Make sure that primary key is the same data type in both tables:

E.g. you can not join numbers to text.

Page 22: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Data from shapefile

Data from “population” table we joined to the

shapefile

Page 23: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Tip: export joined table to new shapefile

Page 24: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Map showing population size for each County

Maybe population density would be a more informative map..

Page 25: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Density is “POPULATION” / “AREA”

Page 26: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Add a new field to store density attribute

Page 27: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Right-click on

DENSITY

Page 28: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software
Page 29: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software
Page 30: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Types of Relationships

This is a one-to-one relationship

One record in the shapefile matches one record in the population table

Page 31: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

FID Name

0 Joe

1 Kelly

2 Dan

3 George

4 Spencer

5 Mike

Name Pet

Joe Cat

Joe Dog

Kelly Cat

Dan Dog

Mike Snake

Mike Cat

Mike Hamster

Is this a one-to-one relationship?

?

Types of Relationships

Can we join this data?

NO! Instead of “join”, use a “relate”

NO! It is a one-to-many

Page 32: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Relates: Example

DBF table with information about a few

different laterals

Goal: we want to look at those laterals on a map

Page 33: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

This is the NHD: it has the geometry

Relate NHD to the laterals table

This is a one-to-many relationship

Page 34: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software
Page 35: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software
Page 36: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software
Page 37: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

H Canal is selected

Page 38: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Use “info” tool on this line segment

Attributes for that line segment

By clicking the + you see related

tables

Page 39: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Tables that NHDFlowline layer is

related to

By relating tables the user has much more

information at “his/her fingertips”

Page 40: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software
Page 41: GIS Brownbag Series Attributes. In the beginning… Earliest GIS systems did not have attributes Needed separate layers for labels (e.g. names) CAD software

Upcoming Brownbag Lectures

May 20: Model Builder

June 17: How to make maps that communicate

Check out previous Brownbag Presentations on WEnet