1 of 56

Intro to GIS

Lesson 5: Managing vector data

1

2 of 56

Storing vector features

Vector data are stored as x-y pairs in the form of points, lines, or polygons

Each x-y pair is called a vertex (pl. vertices)

Endpoints of lines are called nodes

A multipart feature may contain several separate pieces

    • Hawaii is single state feature composed of multiple polygons for each island.

2

© McGraw Hill, LLC

3 of 56

Attribute tables

Source: Esri

Features are linked to tables containing data, or attributes, of the features

A unique integer is used to link the feature to its data record

    • Feature I D (F I D).
    • Object I D (O I D).

3

© McGraw Hill, LLC

4 of 56

Feature Classes

Source: Esri

  • A feature class is a collection of similar features stored together as a data set, like these states
  • A feature class includes the spatial features and the table
  • Feature classes may contain only one type of geometry (points or lines or polygons)
  • Feature classes may be stored in a variety of formats, like shapefiles, geodatabases, and so on

4

© McGraw Hill, LLC

5 of 56

Spaghetti models

Source: Esri

Simple vector data formats are called spaghetti models

    • Each state is stored as a separate object unrelated to the others.
    • Adjacent boundaries are stored twice.
    • It is a robust model because of its simplicity.
    • It is often used to transfer data from one G I S to another.

5

© McGraw Hill, LLC

6 of 56

Topological models

Source: Esri

Topological models also store information on how features are spatially related

    • Which states are adjacent.

They can test whether features are adjacent, connect, overlap, or intersect

They can find data errors, such as overlapping states, or a county boundary that falls outside the state

6

© McGraw Hill, LLC

7 of 56

G I S data are different

  • The files can be very large
  • They are often shared by multiple users
  • They come from many sources, in many file types
  • Sometimes they are on the local computer but they may also come from a file server or online source
  • They don’t always follow latest file conventions
  • The formats can be complicated

7

© McGraw Hill, LLC

8 of 56

Tips to manage your G I S Data

Source: Esri

Use well-organized folders

Do NOT use the Desktop or Documents folders

Be aware of where you are saving

    • the project geodatabase is the default but not always the best place.

Name files with descriptive names

    • Snail Habitat, not rastercalc1.

Separate permanent libraries from in-progress work to avoid accidental damage or deletion of valuable data

Put downloads in separate folders for easy archival or deletion later

8

© McGraw Hill, LLC

9 of 56

Best practices for naming folders

NEVER use spaces in folder names

Not ever. Anywhere. Nix. No. Nein. Nyet. Non.

Use letters, numbers, or underscore only

Keep folder names short: approximately 8 to 15 characters

Why?

    • These are recommended practices for many types of large, complicated software products.
    • Certain functions of the G I S may not work properly when these guidelines aren’t followed.
    • It is difficult to fix issues without affecting maps and projects.

9

© McGraw Hill, LLC

10 of 56

File extensions

Extensions are 3-4 letter codes that designates the type of a file

    • .doc, .docx, .xls, .xlsx, .mxd, .tif, .png.

Changing your computer settings to make extensions visible is very helpful when downloading and importing data sets

    • In the Windows File Explorer options, uncheck the box to Hide extensions for known file types.

Source: Microsoft

10

© McGraw Hill, LLC

11 of 56

Data access tips

GIS data are often shared by multiple users

    • Computer systems use file locks to track when files are being used by programs to avoid corrupting files with simultaneous changes.
    • Certain G I S functions, such as editing, will not be available if you or another user has an exclusive lock on a data set.

You cannot edit or modify data sets if you don’t have read-write access

    • These permissions are generally controlled by the computer operating system at the folder level.

11

© McGraw Hill, LLC

12 of 56

Zipping

  • Many downloaded data sets are zipped to reduce the number of files and the storage space
  • Zipped files must be extracted before ArcG I S can use them
  • Several zip utilities are available, such as 7zip, which is free

12

© McGraw Hill, LLC

13 of 56

Importing and exporting

Source: Esri

  • Importing or exporting makes a copy of a data set
  • It may include changing the format or the data model as part of the process
  • They are essentially the same function; the only difference is the direction of the copy (into or out of the database or folder)
  • Both are done using the Feature Class to Feature Class tool or similar tools

13

© McGraw Hill, LLC

14 of 56

Source scale

Source: Esri

When compiling data, pay attention to the source scale

    • The purple, orange and black lines represent source scales of 1:25 million, 1:5 million, and 1:50,000, respectively.

Use the metadata to help decide whether the source scale is suitable for the objective of your database

Small scale data are often easier to find, but may not be adequate for a project’s purpose

14

© McGraw Hill, LLC

15 of 56

Mapping x-y coordinates in a table

Source: Esri

  • A table with coordinates can have the locations displayed on a map as an event layer, or saved as a point feature class
  • These climate station latitude-longitude values are displayed on a map of Oregon
  • The coordinate system of the locations may be different from the map, but it must be specified in the X Y Table to Point tool

15

© McGraw Hill, LLC

16 of 56

Geocoding

Source: Esri

  • Geocoding displays addresses on a map by matching postal data fields to a street data set
  • It requires suitable street data and rules for coding, packaged as a locator
  • Fields in the address table must be matched to fields in the street data (highlighted fields)
  • Users with suitable data can build their own locators
  • ArcG I S Online has a World locator. Single addresses are free, but geocoding multiple addresses in a table uses service credits

16

© McGraw Hill, LLC

17 of 56

Extracting data

Source: Esri

  • Users may extract a subset of features when importing or exporting
  • Queries are used to extract data using an expression based on an attribute field
  • A clip extracts features within a bounding polygon from another feature class
  • An erase extracts the features outside of a bounding polygon from another feature class

17

© McGraw Hill, LLC

18 of 56

Merging

  • Merging combines all features from two or more data sets into a single new feature class
  • It is typically used to combine adjacent feature classes like these two geology maps
  • It works best when the attribute tables have the same fields.
  • If the tables don’t match, merge rules must be set up to combine the table data in a logical and useful way

Source: South Dakota Geological Survey

18

© McGraw Hill, LLC

19 of 56

Merge rules

Source: Esri

a) The Field Map function defines how attributes fields are combined. The Fm_Name field exists in both tables, but the Unit field has different names in the two tables, although they contain the same information.

b) The Unit field in the MtRushmoreGeology data is matched to the Formation_ field in the HillCityGeology table.

c) The other fields share no common information, so they are deleted from the field map, leaving only Fm_Name and Unit after the merge is complete.

19

© McGraw Hill, LLC

20 of 56

Appending

Append is similar to merge except that

    • The target data set already exists.
    • No field mapping is available.
    • Fields in the source that don’t match the target fields will have their data dropped during the append operation.

Source: South Dakota Geological Survey

20

© McGraw Hill, LLC

21 of 56

Generalizing

Source: Esri

  • Generalizing is used to remove vertices from a data set to simplify it
  • This green polygon has been simplified to the black outline by specifying a minimum distance between vertices
  • It is often used on large scale data to reduce its size and speed display at small scales
  • It affects both precision and accuracy of the data

21

© McGraw Hill, LLC

22 of 56

Dissolving

Source: Black Hills National Forest

Dissolving removes boundaries of features with the same value in the specified attribute field(s)

a) These forest stands contain the same tree species but the smaller polygons indicate different ages and sizes of trees

b) After dissolving on the species field, the age information is dropped and only the species information is retained

22

© McGraw Hill, LLC

23 of 56

Metadata

  • Metadata is data about a data set that helps the user assess its purpose and quality
  • It travels with the data as a separate file or as part of the feature class in ArcG I S
  • Minimal metadata should be created for each data set to record its source and citation and processing
  • Standards-based metadata is often required when publishing data for clients or organizations

Source: Esri

23

© McGraw Hill, LLC

24 of 56

Basic metadata sections

  • Tags: terms used to search for the data
  • Summary: brief information about the purpose of the data
  • Description: longer description of the data set contents, sources, and processing
  • Credits: citation of the data creator and source information
  • Use Limitation: restrictions on the use or re-distribution of the data; may include a disclaimer
  • Appropriate Scale Range: the source scale or scale at which the data are intended to be used
  • Bounding Box: coordinate extent of the data in degrees

24

© McGraw Hill, LLC

25 of 56

Types of data used in ArcG I S

25

File type

Description

Shapefiles

Shapefiles are vector feature classes developed for the early version of ArcView and have been carried over into ArcGIS.

Coverages

A coverage is the vector data format developed for Arc/Info and is the oldest of the data formats. Not read by ArcGIS Pro.

Geodatabases

Geodatabases are the recommended model for storing spatial information for ArcGIS.

Database connections

Database connections permit users to log in to and utilize data from an RDBMS geodatabase.

Layer files

A layer file references a feature class and stores information about its properties, such as how it should be displayed.

Tables

Tables can exist as separate data objects that are unassociated with a spatial data set.

TINs

TINs are Triangulated Irregular Networks that store 3D surface information, such as elevation, using a set of nodes and triangles.

CAD drawings

Data sets created by CAD programs can be read by ArcGIS, although they cannot be edited or analyzed unless they are converted to shapefiles or geodatabases.

© McGraw Hill, LLC

26 of 56

Geodatabase format

Source: Esri

  • Geodatabases are the native and recommended format for ArcG I S Pro
  • They contain many types of data including feature classes, rasters, tables, and more
  • A geodatabase is stored in a folder, which should contain only the geodatabase data sets created in ArcG I S

26

© McGraw Hill, LLC

27 of 56

Three types of geodatabases

Personal geodatabases (not recognized by Pro)

    • Stored in a Microsoft Access database format.
    • For single users or small workgroups.
    • 2 G B size limitation on feature classes.

File geodatabases

    • Stored as files in a geodatabase folder.
    • For single users or small workgroups.
    • Platform independent.

Enterprise geodatabases

    • Stored in a commercial Relational Database Management System (D B M S) such as Oracle or SQLServer.
    • Designed for multiple users and large workgroups.
    • Supports multi-user editing, versioned editing, etc.
    • Requires R D B M S license.

27

© McGraw Hill, LLC

28 of 56

Shapefile format

Source: Esri

Shapefiles are stored in a spaghetti data format that has a simple structure

They can be read by many programs and are often used to transfer data

They appear as one file in the ArcG I S Catalog, but are actually composed of many files

    • Care must be taken when copying or renaming shapefiles outside of ArcG I S.

28

© McGraw Hill, LLC

29 of 56

Coverage format

Source: Esri

Coverages are an old vector format that is no longer recognized by ArcG I S Pro

They must be converted to a shapefile or geodatabase in ArcMap

They are composed of multiple feature classes

They include topology fields that are not needed in the output file

    • # fields, area/length/perimeter fields, and the I D fields.

29

© McGraw Hill, LLC

30 of 56

Other data types

Database connections

    • Pro can connect to R D B M S systems that contain non-spatial data.
    • Connections include public databases or those requiring a login.

C A D files

    • Pro can read and display C A D files, but cannot edit them.

30

© McGraw Hill, LLC

31 of 56

Sharing data

Source: Esri

  • G I S data are often shared
  • Data remain in place but are accessed by multiple users (or many times by the same user)
  • Access rights are often used to prevent accidental changes
  • Groups sharing data must develop procedures to prevent simultaneous editing

31

© McGraw Hill, LLC

32 of 56

Pathnames

  • Pathnames are used to locate the source of a data set in place
  • Absolute paths start at the drive letter and go down the folder tree

C:\gisclass\mgisdata\Oregon\oregondat\counties

  • Relative paths start at the project file and go up or down the folder tree

..\..\mgisdata\Oregon\oregondat\counties

  • In Pro, path types are assigned automatically

32

© McGraw Hill, LLC

33 of 56

Using pathnames

Pro assigns the pathname type automatically

    • relative paths for data on the local hard drive.
    • absolute paths for data on a network fileserver.
    • U N C paths for Internet data services.

This strategy usually works well

When copying projects, be sure to copy the entire project folder, not just the .aprx file or the geodatabase

33

© McGraw Hill, LLC

34 of 56

Preserving pathnames

If data are deleted, moved, or renamed, projects will lose track of the location

    • a red exclamation point appears by the map layer.
    • the path can be re-established if the data still exist and the location can be identified.

Never use spaces in folder names

    • correcting spaces will cause projects to lose track of the data.

Projects cannot be renamed because doing so would disrupt the pathnames of the internal components

    • Save As only creates a copy of the .aprx file, not the entire project.

Source: Esri

34

© McGraw Hill, LLC

35 of 56

Environment settings

Source: Esri

Environment settings affect the operation of tools such as

    • specifying an output location.
    • saving all output in a specified coordinate system.

Tools have an Environments tab that contains settings that affect the tool when it is run (that one time)

Settings on the Environments button of the Analysis ribbon affect all tools all the time

35

© McGraw Hill, LLC

36 of 56

Coordinate system reminders

Source: Esri

  • When compiling data, you should usually pick a suitable coordinate system and use it for all data in the project or geodatabase
  • Remember that the standard datum should usually be used unless someone has directed you to use a specialized one
  • The map properties window is a good place to check whether all data in a map have the same coordinate system

36

© McGraw Hill, LLC

37 of 56

© 2023 McGraw Hill, LLC. All rights reserved. Authorized only for instructor use in the classroom.

No reproduction or further distribution permitted without the prior written consent of McGraw Hill, LLC.

Because learning changes everything.®

www.mheducation.com

38 of 56

Accessibility Content: Text Alternatives for Images

38

© McGraw Hill, LLC

39 of 56

Storing vector features - Text Alternative

The graph representing the vector features shows horizontal direction on the x-axis by a right arrow and vertical direction on the y-axis by an upward arrow respectively. Three markings are present near the origin labeled points. An irregular line with vertices and two red nodes is present on both ends. An irregular structure made up of vertices on the boundaries is labeled as a polygon.

39

© McGraw Hill, LLC

40 of 56

Tips to manage your G I S Data - Text Alternative

The subfolders are Austin, Black Hills, Map Documents, Metadata, Oregon, Rapid city, the USA, and the world.

40

© McGraw Hill, LLC

41 of 56

File extensions - Text Alternative

In the View tab of the File Explorer Options window, the box next to 'Hide extensions for known file types' should be unchecked.

41

© McGraw Hill, LLC

42 of 56

Importing and exporting - Text Alternative

The first line of the feature class to feature class dialogue box shows the tabs 'Parameters and environments.' Under parameters, the Input features box depicts the state, the output location box depicts New Jersey dot gdb, and the output feature class box depicts nj bound. Followed by the output feature class box the Expression option with a small image of SQL icon is located. STATE underscore NAME is Equal to New Jersey. Add Clause button. Small icons of a book, tick mark, folder, and save. A tick mark with SQL Expression is valid.

42

© McGraw Hill, LLC

43 of 56

Mapping x-y coordinates in a table - Text Alternative

The spreadsheet has six rows. Row 1: header row, COOPID, LAT, LON, and station. Row 2: 350036, 42.183333, negative 119.900000, and ADEL. Row 3: 350118, 42.966667, negative 120.000000, and Alkali lake. Row 4: 350145, 44.400000, negative 123.750000, Alsea FH Fall. Row 5: 350197, 44.916667, negative 120.733333 and Antelope 1 NVV. Row 6: 350217, 42.250000, negative 123.166667, and Applegate.

Input table. Drop-down folder name climate stations 2005. Output Feature Class. Drop-down folder name n j climate stations. X Field. Drop-down – Long. Y Field. Drop-down L a t. Z Field. Drop-down empty form. Coordinate system GCS Drop-down-North_American_1983.

43

© McGraw Hill, LLC

44 of 56

Geocoding - Text Alternative

The data are given in the screenshot are as follows: A tab with a note this tool consumes credits when used is given. Parameters, Environment: Input table: NJWalmarts. Input address locator: ArcGIS world geocoding service. Input address field: Multiple fields. Field name: Alias name. Address or place: STREETADDR. Address 2: <None>. Address 3: <None>. Neighborhood: <None>. City: STRCITY. Subregion: County. State: <None>. ZIP: ZIPCODE. ZIP4: <None>. Country: <None>. Output feature class: NJWalmartPts. Checkbox: Dynamic output feature class.

44

© McGraw Hill, LLC

45 of 56

Extracting data - Text Alternative

The data given in the expression dialogue box are as follows: A SQL icon with a small image. POP2014 is Greater than 100000. Add Clause button. Small icons of a book, tick mark, folder, and save. A checkbox of invert where clause.

The illustration shows the following data: Clip: A square with two diagonal lines inside it combines with a circle having a smaller circle inside it to produce a circle with two diagonals inside it. Erase: A square with two diagonal lines inside it combines with a circle having a smaller circle inside it to produce a square with two diagonals inside it. The square also has a circular gap inside it.

45

© McGraw Hill, LLC

46 of 56

Merge rules - Text Alternative

The data given in the first part are as follows: Output fields (Plus button), source, and properties. Formation underscore, Merge rule: First (Dropdown box). Formation 1, Mt Rushmore Go. Shape Length: Fm underscore Name (Dropdown box). Shape underscore area (2). Area underscore ac: Hillcity Geology. Fm underscore Name 2 (Marked in a box). Unit, Add new source (Dropdown box). Shape underscore Le underscore 1. The data given in the second part are as follows: Output fields (Plus button), source, and properties. Formation underscore, Merge rule: First (Dropdown box). Formation 1, Mt Rushmore Go. Shape Length: Fm underscore Name (Dropdown box). Shape underscore area (2). Area underscore ac: Hillcity Geology. Fm underscore Name (2).Unit 2 (Marked in a box). Add new source (Dropdown box). Shape underscore Le underscore 1. The data given in the third part are as follows: Output fields (Plus button). Fm underscore Name (2). Unit (2).

46

© McGraw Hill, LLC

47 of 56

Generalizing - Text Alternative

In the map, the water is marked in blue and the land is marked in green. The coastline of the land from water is marked in black to remove the vertices and simplify it into a shape.

47

© McGraw Hill, LLC

48 of 56

Dissolving - Text Alternative

The first map (b) shows the different regions inside the land which is before dissolving. The second map (c) shows the land after dissolving which removes the boundaries.

48

© McGraw Hill, LLC

49 of 56

Metadata - Text Alternative

The map of the generalized states of the U.S. shows the following data: Type: File Geodatabase Feature Class. Tags: polygon, area, population, households, demographics, society, boundaries, farming, United States, U.S. States, States, 2002, 2010, 2012, 1992, 2011, 2013, 2014. Summary: U.S. States (Generalized) provides 2010 U.S. Census demographic information and generalized state boundaries to improve draw performance and be used effectively at a national level. Description: U.S. States (Generalized) represents the 50 states and the district of Columbia of the united states. Credits: ESRI Data and maps (ESRI, Inc., Redlands, CA).

49

© McGraw Hill, LLC

50 of 56

Geodatabase format - Text Alternative

The data on the chart is as follows: Oregon data dot gdb: geodatabase, transportation: feature dataset, airport: point feature class, highways: line feature class, rail100k, water, cities, and counties: polygon feature class, and gtopo1km: raster.

50

© McGraw Hill, LLC

51 of 56

Shapefile format - Text Alternative

Parcels.d b f, parcels.p r j shapefile in windows explorer, parces.s b n, parcels.s b x, parcels.s h p, parces.s h p.x m (notes hide the text), and parcels.s h x. parcels.s h p is shapefile in the catalog and r c_roads.s h p.

51

© McGraw Hill, LLC

52 of 56

Coverage format - Text Alternative

Archive with city b n d and landuse with coverages store arc, label, polygon ant tic. The layer of files are Area (float), perimeter (float), landuse hash (long), landuse-I D (long), F node has (long), T node hash (long), L poly has (long), R poly hash (long), length (float), landuse hash (long) and landuse I D (long).

52

© McGraw Hill, LLC

53 of 56

Sharing data - Text Alternative

The map of the counties' feature class is depicted in three types: Mike's map, Taylor's map, and Judy's map.

53

© McGraw Hill, LLC

54 of 56

Pathnames - Text Alternative

Absolute path: C colon backward slash g i s class backward slash e n g i s data backward slash Oregon backward slash Oregon dat backward slash counties. g i s class Relative path: underscore, backward slash underscore backward slash underscore backward slash e n g i s data backward slash Oregon backward slash Oregon dat backward slash counties. The g i s class to m g I s data and class projects. The m g I s data to Oregon and followed by Oregan dat counties, rivers, and highways. The g i s class to the Oregon dat, counties rivers and highways. The class project transforms to the crater lake. The crater lake is for geology, faults, and vents. The crater lake is craterLake.a p r x.

54

© McGraw Hill, LLC

55 of 56

Environment settings - Text Alternative

The first line of the copy features dialogue box shows the tabs 'Parameters and environments.' Under environments, the output coordinate system is empty, the geographic transformation is empty, and the output CONFIG keyword is empty (Dropdown box). The 'Extend is default' (Dropdown box). The Auto commit box is 1000. The Maintain attachments checkbox is selected. The output XY domain is the same as the input (Dropdown box). The output M domain is the same as the input (Dropdown box). The output Z domain is the same as the input (Dropdown box). The Maintain fully qualified field names checkbox is selected.

55

© McGraw Hill, LLC

56 of 56

Coordinate system reminders - Text Alternative

NAD 1983 (CORS 96) (I n t l Feet). NAD 1983 (CORS 96) (Meters). NAD 1983 (CORS 96) (US Feet). NAD 1983 (I n t l Feet). NAD 1983 (Meters) selected. NAD 1983 (PA 1 1) (Meters). NAD 1983 (PA 1 1) (US Feet). NAD 1983 (US Feet). NAD 1983 HARN (I n t l Feet).

Layers selected. NAD 1983 State plane New Jersey FIPS 2900. n j quakes. n j cities. n j roads. n j golf. n j bound_d t l. n j c d 113. n j districts. n j counties. WGS 1984 Web Mercator Auxiliary Sphere Topographic.

56

© McGraw Hill, LLC