1 of 382

Spatial Data Types

​

Jeff Jenness

jeffj@jennessent.com (928) 607-4638

2 of 382

Main Topics

3 of 382

Main Topics

  • Managing Spatial Datasets; copying, sharing, etc.

​

​

4 of 382

Main Topics

  • Managing Spatial Datasets; copying, sharing, etc.
  • Workspaces

​

​

5 of 382

Main Topics

  • Managing Spatial Datasets; copying, sharing, etc.
  • Workspaces
  • Vector Data

​

​

6 of 382

Main Topics

  • Managing Spatial Datasets; copying, sharing, etc.
  • Workspaces
  • Vector Data
  • Raster Data

​

​

7 of 382

Main Topics

  • Managing Spatial Datasets; copying, sharing, etc.
  • Workspaces
  • Vector Data
  • Raster Data
  • Special cases of Spatial Data

​

​

8 of 382

Main Topics

  • Managing Spatial Datasets; copying, sharing, etc.
  • Workspaces
  • Vector Data
  • Raster Data
  • Special cases of Spatial Data
  • Metadata

​

​

9 of 382

Main Topics

  • Managing Spatial Datasets; copying, sharing, etc.
  • Workspaces
  • Vector Data
  • Raster Data
  • Special cases of Spatial Data
  • Metadata
  • Data Management Strategies

​

​

10 of 382

Spatial Data

  • Spatial data is tricky to work with outside of a GIS.

​

11 of 382

Spatial Data

  • Spatial data is tricky to work with outside of a GIS.
  • A single dataset is often composed of multiple files, sometimes distributed into different folders.

12 of 382

Spatial Data

  • Spatial data is tricky to work with outside of a GIS.
  • A single dataset is often composed of multiple files, sometimes distributed into different folders.
  • This makes it harder to share spatial data. Not easy to just email someone a spatial dataset, like you can with other files.

13 of 382

For Example:

Shapefile datasets:

  • Relatively simple
  • Composed of at least 3 and often many more files, all in the same folder and all named with the same name.

The single spatial dataset named Beale_Wagon_Road_Campsites (seen in Catalog on the top) requires eight separate files on your hard drive (as seen in Windows File Explorer on the bottom).

14 of 382

TIN datasets:

  • Triangulated Irregular Network
  • A bit more complicated
  • Composed of a folder of files, plus
  • Additional files in an “Info” folder

The single spatial dataset named Wallow_Burn_Severity (seen in Catalog on the top) requires two separate folders on your hard drive (as seen in Windows File Explorer on the bottom).

15 of 382

The single spatial dataset named mdow_hlshd (seen in Catalog on the top) actually requires two separate folders and one additional file on your hard drive (as seen in Windows File Explorer on the bottom).

GRID datasets:

  • Proprietary Esri raster format
  • Even more complicated
  • Composed of a folder of files, plus
  • Additional files in an “Info” folder
  • Additional files in containing folder

16 of 382

Catalog (on the top) shows you a single spatial dataset in this geodatabase. Windows File Explorer (on the bottom) is not able to view or extract this dataset at all.

Geodatabases:

  • Wonderful way to store data
  • Requires GIS to view
  • No way to identify individual datasets using Windows File Explorer.

17 of 382

  • It is certainly possible to share spatial datasets. You just have to be careful about how you do it.

18 of 382

  • It is certainly possible to share spatial datasets. You just have to be careful about how you do it.
    • Shapefiles: Good idea to compress all individual sub-files into single zip file.

19 of 382

  • It is certainly possible to share spatial datasets. You just have to be careful about how you do it.
    • Shapefiles: Good idea to compress all individual sub-files into single zip file.
    • Other complex datasets: Export them into an empty folder or workspace, then compress that entire workspace into a single zip file.

20 of 382

  • It is certainly possible to share spatial datasets. You just have to be careful about how you do it.
    • Shapefiles: Good idea to compress all individual sub-files into single zip file.
    • Other complex datasets: Export them into an empty folder or workspace, then compress that entire workspace into a single zip file.
    • If you don’t have an alternative, 7-Zip is a good free compression utility for Windows and Linux (www.7-zip.org). WinZip is a good commercial utility (www.winzip.com).

21 of 382

  • It is certainly possible to share spatial datasets. You just have to be careful about how you do it.
    • Shapefiles: Good idea to compress all individual sub-files into single zip file.
    • Other complex datasets: Export them into an empty folder or workspace, then compress that entire workspace into a single zip file.
    • If you don’t have an alternative, 7-Zip is a good free compression utility for Windows and Linux (www.7-zip.org). WinZip is a good commercial utility (www.winzip.com).
  • Use Catalog to review, move, copy and/or delete spatial datasets.

22 of 382

  • Just FYI: Esri also offers a system for sharing spatial data called ArcGIS Online (aka “AGOL”).

​

23 of 382

  • Just FYI: Esri also offers a system for sharing spatial data called ArcGIS Online (aka “AGOL”).
    • Alternatively, Portal, which looks and acts the same as ArcGIS Online, but it is hosted by your organization.

​

24 of 382

  • Just FYI: Esri also offers a system for sharing spatial data called ArcGIS Online (aka “AGOL”).
    • Alternatively, Portal, which looks and acts the same as ArcGIS Online, but it is hosted by your organization.
  • Both ArcGIS Online and Portal let you store your data “in the cloud”.

​

25 of 382

  • Just FYI: Esri also offers a system for sharing spatial data called ArcGIS Online (aka “AGOL”).
    • Alternatively, Portal, which looks and acts the same as ArcGIS Online, but it is hosted by your organization.
  • Both ArcGIS Online and Portal let you store your data “in the cloud”.
  • Makes it easier to share data with the world or with your organization, but not necessarily with specific individuals.

​

26 of 382

So what is a Workspace?

  • Before discussing individual types of datasets, you should understand what a Workspace is.

27 of 382

So what is a Workspace?

  • Before discussing individual types of datasets, you should understand what a Workspace is.
    • ArcGIS Pro tools, commands and help files refer to workspaces a lot.

28 of 382

So what is a Workspace?

  • Before discussing individual types of datasets, you should understand what a Workspace is.
    • ArcGIS Pro tools, commands and help files refer to workspaces a lot.
    • Simply a location where data is kept.

29 of 382

So what is a Workspace?

  • Before discussing individual types of datasets, you should understand what a Workspace is.
    • ArcGIS Pro tools, commands and help files refer to workspaces a lot.
    • Simply a location where data is kept.
    • The “workspace” does not imply that all your work must be done in that location, or that all your data must be stored there. Often you will access several workspaces in any particular GIS project.

30 of 382

Two Broad Categories of Workspace�(with a few exceptions)

31 of 382

Two Broad Categories of Workspace�(with a few exceptions)

  • Folders

32 of 382

Two Broad Categories of Workspace�(with a few exceptions)

  • Folders
    • Simply directories or folders on the hard drive.

33 of 382

Two Broad Categories of Workspace�(with a few exceptions)

  • Folders
    • Simply directories or folders on the hard drive.
    • If your data are in a folder, those data are called file-based data.

34 of 382

Two Broad Categories of Workspace�(with a few exceptions)

  • Folders
    • Simply directories or folders on the hard drive.
    • If your data are in a folder, those data are called file-based data.

​

  • Geodatabases

35 of 382

Two Broad Categories of Workspace�(with a few exceptions)

  • Folders
    • Simply directories or folders on the hard drive.
    • If your data are in a folder, those data are called file-based data.

​

  • Geodatabases
    • Specialized workspaces that allow you to save your data in a more sophisticated manner.

36 of 382

Two Broad Categories of Workspace�(with a few exceptions)

  • Folders
    • Simply directories or folders on the hard drive.
    • If your data are in a folder, those data are called file-based data.

​

  • Geodatabases
    • Specialized workspaces that allow you to save your data in a more sophisticated manner.
    • In most cases, geodatabases allow you to load, view and analyze data faster than file-based data.

37 of 382

Warning! Tedious slides to follow

  • It’s hard to make an interesting graphic of a database…

38 of 382

Geodatabases, continued…

  • Two general types of geodatabases

39 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases: These can store all your individual datasets, plus:

40 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases: These can store all your individual datasets, plus:
      • Relationships between datasets

41 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases: These can store all your individual datasets, plus:
      • Relationships between datasets
      • History of changes to the data

42 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases: These can store all your individual datasets, plus:
      • Relationships between datasets
      • History of changes to the data
      • Different versions of the data

43 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases: These can store all your individual datasets, plus:
      • Relationships between datasets
      • History of changes to the data
      • Different versions of the data
      • Special symbology and display parameters for the data

44 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases: These can store all your individual datasets, plus:
      • Relationships between datasets
      • History of changes to the data
      • Different versions of the data
      • Special symbology and display parameters for the data
      • Lots of concurrent users

45 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases: These can store all your individual datasets, plus:
      • Relationships between datasets
      • History of changes to the data
      • Different versions of the data
      • Special symbology and display parameters for the data
      • Lots of concurrent users
      • Set sophisticated permission levels for users

46 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases: These can store all your individual datasets, plus:
      • Relationships between datasets
      • History of changes to the data
      • Different versions of the data
      • Special symbology and display parameters for the data
      • Lots of concurrent users
      • Set sophisticated permission levels for users

​

      • Used more for larger data-centers, not so much for smaller organizations that focus more on analytical work.

​

47 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases, continued
      • Generally they are “relational database management systems” (RDBMS) produced by other companies. ArcGIS connects to them using ArcSDE (Spatial Database Engine).

48 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases, continued
      • Generally they are “relational database management systems” (RDBMS) produced by other companies. ArcGIS connects to them using ArcSDE (Spatial Database Engine).
      • Relational geodatabases are a big thing in ArcGIS. Many people make an entire career out of database administration.

49 of 382

Geodatabases, continued…

  • Two general types of geodatabases
    • Relational Geodatabases, continued
      • Generally they are “relational database management systems” (RDBMS) produced by other companies. ArcGIS connects to them using ArcSDE (Spatial Database Engine).
      • Relational geodatabases are a big thing in ArcGIS. Many people make an entire career out of database administration.
      • We won’t go into relational geodatabases in this class. The topic requires much more time than we have, and we don’t need them for the work you are doing in this class.

50 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases: These store all your individual datasets, plus:

51 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases: These store all your individual datasets, plus:
      • Relationships between datasets, although not to the degree that relational geodatabases can.

52 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases: These store all your individual datasets, plus:
      • Relationships between datasets, although not to the degree that relational geodatabases can.

​

      • Two specific types of Non-Relational Geodatabases:

53 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases: These store all your individual datasets, plus:
      • Relationships between datasets, although not to the degree that relational geodatabases can.

​

      • Two specific types of Non-Relational Geodatabases:
        • Mobile Geodatabase: A geodatabase built for Esri’s mobile apps. Exists as a single file, and appears to only hold vector and tabular data.

54 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases: These store all your individual datasets, plus:
      • Relationships between datasets, although not to the degree that relational geodatabases can.

​

      • Two specific types of Non-Relational Geodatabases:
        • Mobile Geodatabase: A geodatabase built for Esri’s mobile apps. Exists as a single file, and appears to only hold vector and tabular data.
        • File Geodatabase: A special Esri-designed geodatabase that has lots of good features.

​

55 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases: These store all your individual datasets, plus:
      • Relationships between datasets, although not to the degree that relational geodatabases can.

​

      • Two specific types of Non-Relational Geodatabases:
        • Mobile Geodatabase: A geodatabase built for Esri’s mobile apps. Exists as a single file, and appears to only hold vector and tabular data.
        • File Geodatabase: A special Esri-designed geodatabase that has lots of good features.

​

      • In this class, we won’t use the Mobile Geodatabase. We’ll use the File Geodatabase a lot, though!

56 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases, continued…
      • Are these really “non-relational”? That’s debatable.

57 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases, continued…
      • Are these really “non-relational”? That’s debatable.
      • They provide far less functionality than the ArcSDE-connected databases.

58 of 382

Geodatabases, continued…

  • Two general types of geodatabases, Continued…
    • Non-Relational Geodatabases, continued…
      • Are these really “non-relational”? That’s debatable.
      • They provide far less functionality than the ArcSDE-connected databases.
      • Unless you are managing data for a large enterprise, these usually work just fine for most projects.

59 of 382

More on the File Geodatabase

60 of 382

More on the File Geodatabase

  • They allow you to store most Esri spatial data types.

61 of 382

More on the File Geodatabase

  • They allow you to store most Esri spatial data types.
    • Exceptions are cloud-based and online datasets

62 of 382

More on the File Geodatabase

  • They allow you to store most Esri spatial data types.
    • Exceptions are cloud-based and online datasets
  • They can store unlimited amounts of data

63 of 382

More on the File Geodatabase

  • They allow you to store most Esri spatial data types.
    • Exceptions are cloud-based and online datasets
  • They can store unlimited amounts of data
    • Although individual datasets are limited to 1TB.

64 of 382

More on the File Geodatabase

  • They allow you to store most Esri spatial data types.
    • Exceptions are cloud-based and online datasets
  • They can store unlimited amounts of data
    • Although individual datasets are limited to 1TB.
  • They have fast data access times.

65 of 382

More on the File Geodatabase

  • They allow you to store most Esri spatial data types.
    • Exceptions are cloud-based and online datasets
  • They can store unlimited amounts of data
    • Although individual datasets are limited to 1TB.
  • They have fast data access times.
  • They can be compressed with no loss in performance.

66 of 382

More on the File Geodatabase

  • They allow you to store most Esri spatial data types.
    • Exceptions are cloud-based and online datasets
  • They can store unlimited amounts of data
    • Although individual datasets are limited to 1TB.
  • They have fast data access times.
  • They can be compressed with no loss in performance.
  • They show up as a single folder in Windows File Explorer.

67 of 382

What is Not a Workspace?

68 of 382

What is Not a Workspace?

  • No single dataset is a workspace!

69 of 382

What is Not a Workspace?

  • No single dataset is a workspace!
    • Remember that workspaces are containers for data, not the data themselves!

70 of 382

What is Not a Workspace?

  • No single dataset is a workspace!
    • Remember that workspaces are containers for data, not the data themselves!
  • An ArcGIS Pro Project (*.aprx file) is not a workspace!

71 of 382

What is Not a Workspace?

  • No single dataset is a workspace!
    • Remember that workspaces are containers for data, not the data themselves!
  • An ArcGIS Pro Project (*.aprx file) is not a workspace!
    • It is not a container holding data. In fact, it has no data in it at all. It has layers, which tell it where the datasets are located on the hard drive or network, but it does not hold the datasets themselves.

72 of 382

In this class…

  • We will use two types of workspace:

73 of 382

In this class…

  • We will use two types of workspace:
    • Folders (containing shapefiles, tables and some images).

74 of 382

In this class…

  • We will use two types of workspace:
    • Folders (containing shapefiles, tables and some images).
    • File Geodatabases (containing all types of spatial data).

75 of 382

A Note regarding Excel Files

76 of 382

A Note regarding Excel Files

    • In ArcMap (prior to ArcGIS Pro), some of you may have used Excel files (which were actually workspaces because they were Containers holding tables (worksheets).

77 of 382

A Note regarding Excel Files

    • In ArcMap (prior to ArcGIS Pro), some of you may have used Excel files (which were actually workspaces because they were Containers holding tables (worksheets).
      • Great for loading tabular data

78 of 382

A Note regarding Excel Files

    • In ArcMap (prior to ArcGIS Pro), some of you may have used Excel files (which were actually workspaces because they were Containers holding tables (worksheets).
      • Great for loading tabular data
      • Many of us record data in Excel

79 of 382

A Note regarding Excel Files

    • In ArcMap (prior to ArcGIS Pro), some of you may have used Excel files (which were actually workspaces because they were Containers holding tables (worksheets).
      • Great for loading tabular data
      • Many of us record data in Excel
    • ArcGIS Pro no longer recognizes Excel files unless you download and install extra drivers:

80 of 382

A Note regarding Excel Files

    • In ArcMap (prior to ArcGIS Pro), some of you may have used Excel files (which were actually workspaces because they were Containers holding tables (worksheets).
      • Great for loading tabular data
      • Many of us record data in Excel
    • ArcGIS Pro no longer recognizes Excel files unless you download and install extra drivers:

81 of 382

A Note regarding Excel Files

    • In ArcMap (prior to ArcGIS Pro), some of you may have used Excel files (which were actually workspaces because they were Containers holding tables (worksheets).
      • Great for loading tabular data
      • Many of us record data in Excel
    • ArcGIS Pro no longer recognizes Excel files unless you download and install extra drivers:

82 of 382

A Note on Catalog and Workspaces…

83 of 382

A Note on Catalog and Workspaces…

  • Catalog acts a lot like Windows File Explorer, but it will not automatically show you all directories.

84 of 382

A Note on Catalog and Workspaces…

  • Catalog acts a lot like Windows File Explorer, but it will not automatically show you all directories.
    • Also can’t use 7-Zip or WinZip from Catalog

85 of 382

A Note on Catalog and Workspaces…

  • Catalog acts a lot like Windows File Explorer, but it will not automatically show you all directories.
    • Also can’t use 7-Zip or WinZip from Catalog
  • The first time you open it, you may not see any spatial data listed at all.

86 of 382

A Note on Catalog and Workspaces…

  • Catalog acts a lot like Windows File Explorer, but it will not automatically show you all directories.
    • Also can’t use 7-Zip or WinZip from Catalog
  • The first time you open it, you may not see any spatial data listed at all.
  • You need to tell Catalog which folders to “connect” to.

87 of 382

A Note on Catalog and Workspaces…

  • Catalog acts a lot like Windows File Explorer, but it will not automatically show you all directories.
    • Also can’t use 7-Zip or WinZip from Catalog
  • The first time you open it, you may not see any spatial data listed at all.
  • You need to tell Catalog which folders to “connect” to.
    • Connections are stored with your ArcGIS Pro Project.

88 of 382

A Note on Catalog and Workspaces…

  • Catalog acts a lot like Windows File Explorer, but it will not automatically show you all directories.
    • Also can’t use 7-Zip or WinZip from Catalog
  • The first time you open it, you may not see any spatial data listed at all.
  • You need to tell Catalog which folders to “connect” to.
    • Connections are stored with your ArcGIS Pro Project.
    • If you want the connection to be Permanent, add it to your “Favorites”

89 of 382

Finally, a slide that is not all text!

90 of 382

  • You will do this in the lab, and then the data folder will be available to you the next time you open ArcGIS Pro.

91 of 382

Another Note on Catalog and Workspaces…

92 of 382

Another Note on Catalog and Workspaces…

  • Also unlike Windows File Explorer, Catalog does not keep a live connection to a workspace

93 of 382

Another Note on Catalog and Workspaces…

  • Also unlike Windows File Explorer, Catalog does not keep a live connection to a workspace.
    • If you make a change to a workspace (like add a dataset), Catalog will not automatically know you have made the change.

94 of 382

Another Note on Catalog and Workspaces…

  • Also unlike Windows File Explorer, Catalog does not keep a live connection to a workspace.
    • If you make a change to a workspace (like add a dataset), Catalog will not automatically know you have made the change.
    • If you know there is a dataset in a workspace, and Catalog doesn’t show it, then click the [F5] button to refresh Catalog.

95 of 382

Another Note on Catalog and Workspaces…

  • Also unlike Windows File Explorer, Catalog does not keep a live connection to a workspace.
    • If you make a change to a workspace (like add a dataset), Catalog will not automatically know you have made the change.
    • If you know there is a dataset in a workspace, and Catalog doesn’t show it, then click the [F5] button to refresh Catalog.
    • You can also right-click on a workspace and choose “Refresh” from the menu.

96 of 382

Another Note on Catalog and Workspaces…

97 of 382

Now, Actual Spatial Data

98 of 382

Now, Actual Spatial Data

  • Two Broad Categories: Vector and Raster

99 of 382

Now, Actual Spatial Data

  • Two Broad Categories: Vector and Raster
    • Vector Data:

100 of 382

Now, Actual Spatial Data

  • Two Broad Categories: Vector and Raster
    • Vector Data:
      • Precisely-defined spatial objects like Points, Lines and Polygons

101 of 382

Now, Actual Spatial Data

  • Two Broad Categories: Vector and Raster
    • Vector Data:
      • Precisely-defined spatial objects like Points, Lines and Polygons
      • Defined by one or more points called Vertices.

102 of 382

Now, Actual Spatial Data

  • Two Broad Categories: Vector and Raster
    • Vector Data:
      • Precisely-defined spatial objects like Points, Lines and Polygons
      • Defined by one or more points called Vertices.
      • Each vertex has X, Y and sometimes Z coordinates.

103 of 382

Now, Actual Spatial Data

  • Two Broad Categories: Vector and Raster
    • Vector Data:
      • Precisely-defined spatial objects like Points, Lines and Polygons
      • Defined by one or more points called Vertices.
      • Each vertex has X, Y and sometimes Z coordinates.
      • Points are composed of a single vertex.

104 of 382

Now, Actual Spatial Data

  • Two Broad Categories: Vector and Raster
    • Vector Data:
      • Precisely-defined spatial objects like Points, Lines and Polygons
      • Defined by one or more points called Vertices.
      • Each vertex has X, Y and sometimes Z coordinates.
      • Points are composed of a single vertex.
      • Lines (called Polylines in the GIS world) are linear features composed of a series of connected vertices.

105 of 382

Now, Actual Spatial Data

  • Two Broad Categories: Vector and Raster
    • Vector Data:
      • Precisely-defined spatial objects like Points, Lines and Polygons
      • Defined by one or more points called Vertices.
      • Each vertex has X, Y and sometimes Z coordinates.
      • Points are composed of a single vertex.
      • Lines (called Polylines in the GIS world) are linear features composed of a series of connected vertices.
      • Polygons are areal features composed of connected vertices, where the last vertex is connected back to the first vertex.

106 of 382

Vector Example

107 of 382

“Multipart” Vectors

  • All vector objects can be composed of a single or multiple parts.

108 of 382

“Multipart” Vectors

  • All vector objects can be composed of a single or multiple parts.
    • The dataset may contain Hawaii as a single object with seven parts, or as seven separate objects.

109 of 382

“Multipart” Vectors

  • All vector objects can be composed of a single or multiple parts.
    • The dataset may contain Hawaii as a single object with seven parts, or as seven separate objects.
    • Multi-part points are called multipoints, but multipart polylines or polygons are just called polylines or polygons.

110 of 382

Vector Special Cases

111 of 382

Vector Special Cases

  • Almost all vector data are made of some combination of points, polylines or polygons.

112 of 382

Vector Special Cases

  • Almost all vector data are made of some combination of points, polylines or polygons.
  • All vector data we work with in this workshop will be points, polylines or polygons.

113 of 382

Vector Special Cases

  • Almost all vector data are made of some combination of points, polylines or polygons.
  • All vector data we work with in this workshop will be points, polylines or polygons.
  • There are exceptions, especially in CAD (Computer-Aided Design) datasets:

114 of 382

Vector Special Cases

  • Almost all vector data are made of some combination of points, polylines or polygons.
  • All vector data we work with in this workshop will be points, polylines or polygons.
  • There are exceptions, especially in CAD (Computer-Aided Design) datasets:
    • Some datasets contain true curves such as circular arcs, elliptical arcs or Bezier curves.

115 of 382

Common Vector Dataset Types

116 of 382

Common Vector Dataset Types

  1. Feature Class

117 of 382

Common Vector Dataset Types

  1. Feature Class
  2. Feature Dataset

118 of 382

Common Vector Dataset Types

  1. Feature Class
  2. Feature Dataset
  3. Triangulated Irregular Network

119 of 382

1. Feature Class

120 of 382

1. Feature Class

    • The most common example of vector dataset.

121 of 382

1. Feature Class

    • The most common example of vector dataset.
    • Simply a collection of points, polylines or polygons, along with attribute data. Points, Polylines and Polygons are called Shape Types.

122 of 382

1. Feature Class

    • The most common example of vector dataset.
    • Simply a collection of points, polylines or polygons, along with attribute data. Points, Polylines and Polygons are called Shape Types.
    • Any feature class can only contain one shape type! You cannot have a feature class that contains both polygons and points, for example.

123 of 382

1. Feature Class

    • The most common example of vector dataset.
    • Simply a collection of points, polylines or polygons, along with attribute data. Points, Polylines and Polygons are called Shape Types.
    • Any feature class can only contain one shape type! You cannot have a feature class that contains both polygons and points, for example.
    • Individual vector objects are called geometries or shapes.

124 of 382

1. Feature Class

    • The most common example of vector dataset.
    • Simply a collection of points, polylines or polygons, along with attribute data. Points, Polylines and Polygons are called Shape Types.
    • Any feature class can only contain one shape type! You cannot have a feature class that contains both polygons and points, for example.
    • Individual vector objects are called geometries or shapes.
    • Each geometry/shape is paired with a set of attribute data. The combination of geometry and attribute data makes a feature.

125 of 382

1. Feature Class

    • The most common example of vector dataset.
    • Simply a collection of points, polylines or polygons, along with attribute data. Points, Polylines and Polygons are called Shape Types.
    • Any feature class can only contain one shape type! You cannot have a feature class that contains both polygons and points, for example.
    • Individual vector objects are called geometries or shapes.
    • Each geometry/shape is paired with a set of attribute data. The combination of geometry and attribute data makes a feature.
    • Feature classes can be either a shapefile (which is a file-based dataset) or stored in a geodatabase.

126 of 382

Feature Class Example

Features

Attributes

127 of 382

Point Feature Class

  • Points are a single pair of X- and Y-Coordinates
  • They have no area, but they can be symbolized according to attribute values.

128 of 382

Polyline Feature Class

  • Polylines are a connected linear series of vertices.
  • They have no width, but they can be symbolized according to attribute values.

“A line is a dot that went for a walk..” Paul Klee

129 of 382

Polygon Feature Class

  • Polygons are a connected series of vertices, with the last vertex connected back to the first vertex.

130 of 382

Multipatch Feature Class

  • Relatively uncommon.
  • Polygons (usually composed of triangles) form 3-dimensional objects.
  • Used a lot in 3D analysis, but we won’t use them in this class.

131 of 382

2. Feature Dataset

132 of 382

2. Feature Dataset

    • Not an intuitive name!

133 of 382

2. Feature Dataset

    • Not an intuitive name!
    • A set of several feature classes (and possibly other data types) that are related in some way, and stored as a single object.

134 of 382

2. Feature Dataset

    • Not an intuitive name!
    • A set of several feature classes (and possibly other data types) that are related in some way, and stored as a single object.
      • For example, a polyline feature class of water pipes, and a point feature class of pumping stations.

135 of 382

2. Feature Dataset

    • Not an intuitive name!
    • A set of several feature classes (and possibly other data types) that are related in some way, and stored as a single object.
      • For example, a polyline feature class of water pipes, and a point feature class of pumping stations.
    • Almost always stored in a geodatabase.

136 of 382

2. Feature Dataset

    • Not an intuitive name!
    • A set of several feature classes (and possibly other data types) that are related in some way, and stored as a single object.
      • For example, a polyline feature class of water pipes, and a point feature class of pumping stations.
    • Almost always stored in a geodatabase.
      • Exceptions are Coverages, Smart Data Compression datasets and CAD datasets.

137 of 382

Feature Dataset Example

138 of 382

Another Feature Dataset Example

139 of 382

3. Triangulated Irregular Networks (TINs)

140 of 382

3. Triangulated Irregular Networks (TINs)

    • A special type of vector data which forms a 3-dimensional surface covering a landscape.

141 of 382

3. Triangulated Irregular Networks (TINs)

    • A special type of vector data which forms a 3-dimensional surface covering a landscape.
    • Composed of a mesh of 3D triangles.

142 of 382

3. Triangulated Irregular Networks (TINs)

    • A special type of vector data which forms a 3-dimensional surface covering a landscape.
    • Composed of a mesh of 3D triangles.
    • Unlike feature classes, TINs do not store attribute data.

143 of 382

3. Triangulated Irregular Networks (TINs)

    • A special type of vector data which forms a 3-dimensional surface covering a landscape.
    • Composed of a mesh of 3D triangles.
    • Unlike feature classes, TINs do not store attribute data.
    • TINs provide several useful methods to measure slope, aspect or elevation at any point on the TIN surface.

144 of 382

3. Triangulated Irregular Networks (TINs)

    • A special type of vector data which forms a 3-dimensional surface covering a landscape.
    • Composed of a mesh of 3D triangles.
    • Unlike feature classes, TINs do not store attribute data.
    • TINs provide several useful methods to measure slope, aspect or elevation at any point on the TIN surface.
    • TINs are good at illustrating topography and landscape shape.

145 of 382

3. Triangulated Irregular Networks (TINs)

    • A special type of vector data which forms a 3-dimensional surface covering a landscape.
    • Composed of a mesh of 3D triangles.
    • Unlike feature classes, TINs do not store attribute data.
    • TINs provide several useful methods to measure slope, aspect or elevation at any point on the TIN surface.
    • TINs are good at illustrating topography and landscape shape.
    • Also useful for calculating surface area or volume.

146 of 382

TIN Example

147 of 382

Raster Data

  • Remember Two Broad Categories: Vector and Raster

148 of 382

Raster Data

  • Remember Two Broad Categories: Vector and Raster
  • Raster Data:

149 of 382

Raster Data

  • Remember Two Broad Categories: Vector and Raster
  • Raster Data:
    • Composed of square pixels that completely cover a region. Occasionally they have rectangular pixels.

150 of 382

Raster Data

  • Remember Two Broad Categories: Vector and Raster
  • Raster Data:
    • Composed of square pixels that completely cover a region. Occasionally they have rectangular pixels.
    • Each pixel has a value (such as a color or number) which represents the general raster value within the pixel area.

151 of 382

Raster Data

  • Remember Two Broad Categories: Vector and Raster
  • Raster Data:
    • Composed of square pixels that completely cover a region. Occasionally they have rectangular pixels.
    • Each pixel has a value (such as a color or number) which represents the general raster value within the pixel area.
    • Not as precisely defined as vector data. The pixel value is a general descriptor of the cell, not the value at an exact location.

152 of 382

Raster Example

153 of 382

Raster Example

  • They are often images, but with spatial parameters so we know exactly where they are located.

154 of 382

Raster Example

  • They are often images, but with spatial parameters so we know exactly where they are located.
  • The pixel cell size on the ground is called the Resolution.

155 of 382

A Comment on Raster Resolution

156 of 382

A Comment on Raster Resolution

  • The resolution does not automatically imply precision!

157 of 382

A Comment on Raster Resolution

  • The resolution does not automatically imply precision!
  • Both of these rasters have similar resolutions, but the right one is clearly more precise.

158 of 382

Raster File Types

159 of 382

Raster File Types

  • ArcGIS recognizes lots of raster file types, including several that are recognized by other image analysis software.

160 of 382

Raster File Types

  • ArcGIS recognizes lots of raster file types, including several that are recognized by other image analysis software.

​

  • JPEG, GIF, PNG, TIFF, BMP, Imagine, MrSID, etc.

161 of 382

Raster File Types

  • ArcGIS recognizes lots of raster file types, including several that are recognized by other image analysis software.

​

  • JPEG, GIF, PNG, TIFF, BMP, Imagine, MrSID, etc.

​

  • Some image files have spatial information embedded inside the actual image file while others have an associated “World” file.

162 of 382

Raster World File

163 of 382

Raster World File

  • If your image is named “Flagstaff.tiff”, then the world file (if it has one) will be named “Flagstaff.tfw”.

164 of 382

Raster World File

  • If your image is named “Flagstaff.tiff”, then the world file (if it has one) will be named “Flagstaff.tfw”.
  • World files are simple ASCII files, which can be opened in WordPad (or any text editor).

165 of 382

Raster World File

  • If your image is named “Flagstaff.tiff”, then the world file (if it has one) will be named “Flagstaff.tfw”.
  • World files are simple ASCII files, which can be opened in WordPad (or any text editor).

​

  • The numbers tell ArcGIS how to position the raster in the map.

166 of 382

Raster World File

  • If your image is named “Flagstaff.tiff”, then the world file (if it has one) will be named “Flagstaff.tfw”.
  • World files are simple ASCII files, which can be opened in WordPad (or any text editor).

​

  • The numbers tell ArcGIS how to position the raster in the map.

​

  • Not all rasters use world files.

167 of 382

Raster World File

  • In case you’re curious…
  • There is no true spatial reference information here...

168 of 382

Raster World File

  • If you export your map from Map View, you have the option to also create a world file and thereby georeference your map.

169 of 382

Raster World File

  • If you export your map from Map View, you have the option to also create a world file and thereby georeference your map.
  • This world file means that your map could be loaded into ArcGIS Pro just like any other raster dataset.

170 of 382

Raster World File

  • If you export your map from Map View, you have the option to also create a world file and thereby georeference your map.
  • This world file means that your map could be loaded into ArcGIS Pro just like any other raster dataset.

​

  • The world file option is not always available if you export the map from Layout View.

171 of 382

Raster World File

  • If you export your map from Map View, you have the option to also create a world file and thereby georeference your map.
  • This world file means that your map could be loaded into ArcGIS Pro just like any other raster dataset.

​

  • The world file option is not always available if you export the map from Layout View.
    • Exceptions are PDF and TIFF formats

172 of 382

More on Rasters

  • All rasters are composed of either a single or multiple raster bands. Images commonly have at least three raster bands for different electromagnetic wavelengths.

173 of 382

More on Raster Bands

174 of 382

More on Raster Bands

  • Most “true-color” satellite and aerial images are not really true color images at all, but rather a composite of 3 separate images.

175 of 382

More on Raster Bands

  • Most “true-color” satellite and aerial images are not really true color images at all, but rather a composite of 3 separate images.
    • One shows reflectance in the Red wavelength

176 of 382

More on Raster Bands

  • Most “true-color” satellite and aerial images are not really true color images at all, but rather a composite of 3 separate images.
    • One shows reflectance in the Red wavelength
    • One shows reflectance in the Green wavelength

177 of 382

More on Raster Bands

  • Most “true-color” satellite and aerial images are not really true color images at all, but rather a composite of 3 separate images.
    • One shows reflectance in the Red wavelength
    • One shows reflectance in the Green wavelength
    • One shows reflectance in the Blue wavelength

178 of 382

More on Raster Bands

  • Most “true-color” satellite and aerial images are not really true color images at all, but rather a composite of 3 separate images.
    • One shows reflectance in the Red wavelength
    • One shows reflectance in the Green wavelength
    • One shows reflectance in the Blue wavelength
  • ArcGIS shows 3 bands at a time, and each band is shown as Red, Green or Blue.

179 of 382

More on Raster Bands

  • Most “true-color” satellite and aerial images are not really true color images at all, but rather a composite of 3 separate images.
    • One shows reflectance in the Red wavelength
    • One shows reflectance in the Green wavelength
    • One shows reflectance in the Blue wavelength
  • ArcGIS shows 3 bands at a time, and each band is shown as Red, Green or Blue.
    • These are known as the Red, Green and Blue “Color Guns”. They are also referred to as “Channels”.

180 of 382

More on Raster Bands

  • Most “true-color” satellite and aerial images are not really true color images at all, but rather a composite of 3 separate images.
    • One shows reflectance in the Red wavelength
    • One shows reflectance in the Green wavelength
    • One shows reflectance in the Blue wavelength
  • ArcGIS shows 3 bands at a time, and each band is shown as Red, Green or Blue.
    • These are known as the Red, Green and Blue “Color Guns”. They are also referred to as “Channels”.
  • Important Point: Any raster band can be plugged into any color gun/channel!

181 of 382

182 of 382

  • Recall that the visible range is a small part of the electromagnetic spectrum.

183 of 382

  • Recall that the visible range is a small part of the electromagnetic spectrum.
  • Each image shows reflectance at some narrow slice of the electromagnetic spectrum, either inside the visible range our outside of it.

184 of 382

185 of 382

186 of 382

187 of 382

188 of 382

Even More on Raster Bands

189 of 382

Even More on Raster Bands

  • Many satellite and aerial images have far more than just 3 bands.

190 of 382

Even More on Raster Bands

  • Many satellite and aerial images have far more than just 3 bands.
  • Often include bands showing reflectance of wavelengths outside the visible spectrum.

191 of 382

Even More on Raster Bands

  • Many satellite and aerial images have far more than just 3 bands.
  • Often include bands showing reflectance of wavelengths outside the visible spectrum.
  • Landsat Enhanced Thematic Mapper (ETM+) is a good example, with 7 specific bands and 1 “panchromatic” band that sharpens the image.

192 of 382

Even More on Raster Bands

  • Many satellite and aerial images have far more than just 3 bands.
  • Often include bands showing reflectance of wavelengths outside the visible spectrum.
  • Landsat Enhanced Thematic Mapper (ETM+) is a good example, with 7 specific bands and 1 “panchromatic” band that sharpens the image.
    • 3 bands correspond with visible red, green and blue wavelengths, and are used to make “Natural Color” image.

193 of 382

Even More on Raster Bands

  • Many satellite and aerial images have far more than just 3 bands.
  • Often include bands showing reflectance of wavelengths outside the visible spectrum.
  • Landsat Enhanced Thematic Mapper (ETM+) is a good example, with 7 specific bands and 1 “panchromatic” band that sharpens the image.
    • 3 bands correspond with visible red, green and blue wavelengths, and are used to make “Natural Color” image.
    • 4 bands in the Infrared range, used to measure a variety of things such as vegetation health.

194 of 382

Landsat Example: Natural Color

195 of 382

Landsat Example: Some Infrared

196 of 382

197 of 382

Multispectral Imagery

198 of 382

Multispectral Imagery

  • Using multiple images taken at different wavelengths

​

199 of 382

Multispectral Imagery

  • Using multiple images taken at different wavelengths.
  • Landsat Enhanced Thematic Mapper (ETM+) is a multispectral system with 7 wavelengths.

200 of 382

Multispectral Imagery

  • Using multiple images taken at different wavelengths.
  • Landsat Enhanced Thematic Mapper (ETM+) is a multispectral system with 7 wavelengths.
  • Some systems take thousands of images, each at different wavelengths. At this point they start calling it Hyperspectral imagery.

201 of 382

Multispectral Imagery

  • Using multiple images taken at different wavelengths.
  • Landsat Enhanced Thematic Mapper (ETM+) is a multispectral system with 7 wavelengths.
  • Some systems take thousands of images, each at different wavelengths. At this point they start calling it Hyperspectral imagery.
  • Research into how to identify phenomena (such as vegetation health, or presence of water) from multi- and hyperspectral imagery is a very active field in remote sensing.

​

202 of 382

Multispectral Imagery

  • Using multiple images taken at different wavelengths.
  • Landsat Enhanced Thematic Mapper (ETM+) is a multispectral system with 7 wavelengths.
  • Some systems take thousands of images, each at different wavelengths. At this point they start calling it Hyperspectral imagery.
  • Research into how to identify phenomena (such as vegetation health, or presence of water) from multi- and hyperspectral imagery is a very active field in remote sensing.
    • NDVI: Normalized Difference Vegetation Index

​

203 of 382

Multispectral Imagery

  • Using multiple images taken at different wavelengths.
  • Landsat Enhanced Thematic Mapper (ETM+) is a multispectral system with 7 wavelengths.
  • Some systems take thousands of images, each at different wavelengths. At this point they start calling it Hyperspectral imagery.
  • Research into how to identify phenomena (such as vegetation health, or presence of water) from multi- and hyperspectral imagery is a very active field in remote sensing.
    • NDVI: Normalized Difference Vegetation Index
    • NDWI: Normalized Difference Water index

​

204 of 382

Imagery Trivia!

205 of 382

Imagery Trivia!

  • Satellite and Aerial Photography are not the first systems to use multispectral methods to create color images.

206 of 382

Imagery Trivia!

  • Satellite and Aerial Photography are not the first systems to use multispectral methods to create color images.

​

  • Some of the first color photographs used this method, by taking several images of an object and using colored filters for each image.

207 of 382

France, 1877

208 of 382

Russia, 1910

209 of 382

Numeric Rasters

210 of 382

Numeric Rasters

  • Rasters do not have to show imagery.

211 of 382

Numeric Rasters

  • Rasters do not have to show imagery.
  • Many rasters contain some kind of numeric values that describe or measure the landscape in some way.

212 of 382

Numeric Rasters

  • Rasters do not have to show imagery.
  • Many rasters contain some kind of numeric values that describe or measure the landscape in some way.
    • DEM: Digital Elevation Model, containing elevation or bathymetric values

213 of 382

Numeric Rasters

  • Rasters do not have to show imagery.
  • Many rasters contain some kind of numeric values that describe or measure the landscape in some way.
    • DEM: Digital Elevation Model, containing elevation or bathymetric values
    • Slope, Aspect, Curvature, Surface Area rasters

214 of 382

Numeric Rasters

  • Rasters do not have to show imagery.
  • Many rasters contain some kind of numeric values that describe or measure the landscape in some way.
    • DEM: Digital Elevation Model, containing elevation or bathymetric values
    • Slope, Aspect, Curvature, Surface Area rasters
    • Streamflow, flow direction, contributing area (watershed)

215 of 382

Numeric Rasters

  • Rasters do not have to show imagery.
  • Many rasters contain some kind of numeric values that describe or measure the landscape in some way.
    • DEM: Digital Elevation Model, containing elevation or bathymetric values
    • Slope, Aspect, Curvature, Surface Area rasters
    • Streamflow, flow direction, contributing area (watershed)
    • Habitat quality

216 of 382

DEM: Digital Elevation Model

  • Each raster cell contains elevation or bathymetric values.

217 of 382

Any numeric raster can be treated like a DEM.

  • A statistical habitat suitability raster. High points in the Habitat raster indicate good habitat

218 of 382

Any numeric raster can be treated like a DEM.

  • A statistical habitat suitability raster. High points in the Habitat raster indicate good habitat.
    • The blue ridge in the middle is actually a riparian drainage bottom, but it shows up like a ridge because it is high-quality habitat.

219 of 382

Raster Attribute Data

220 of 382

Raster Attribute Data

  • Some rasters have attribute tables, some do not.

221 of 382

Raster Attribute Data

  • Some rasters have attribute tables, some do not.
    • The actual cell values of all rasters are numeric. Attribute tables can add text values (Vegetation Cover Types, for example).

222 of 382

Raster Attribute Data

  • Some rasters have attribute tables, some do not.
    • The actual cell values of all rasters are numeric. Attribute tables can add text values (Vegetation Cover Types, for example).
  • If a raster has an attribute table, then it will have separate attribute tables for each raster band.

223 of 382

Raster Attribute Data

  • Some rasters have attribute tables, some do not.
    • The actual cell values of all rasters are numeric. Attribute tables can add text values (Vegetation Cover Types, for example).
  • If a raster has an attribute table, then it will have separate attribute tables for each raster band.
  • If the raster cells have decimal values (1.0001, for example), then the raster probably will not have an attribute table.

224 of 382

Raster Attribute Data

  • Some rasters have attribute tables, some do not.
    • The actual cell values of all rasters are numeric. Attribute tables can add text values (Vegetation Cover Types, for example).
  • If a raster has an attribute table, then it will have separate attribute tables for each raster band.
  • If the raster cells have decimal values (1.0001, for example), then the raster probably will not have an attribute table.
  • If the raster cells have integer values (1,2,3,4, for example), then the raster probably will have an attribute table.

225 of 382

Raster Attribute Data

  • Some rasters have attribute tables, some do not.
    • The actual cell values of all rasters are numeric. Attribute tables can add text values (Vegetation Cover Types, for example).
  • If a raster has an attribute table, then it will have separate attribute tables for each raster band.
  • If the raster cells have decimal values (1.0001, for example), then the raster probably will not have an attribute table.
  • If the raster cells have integer values (1,2,3,4, for example), then the raster probably will have an attribute table.
  • Raster attributes are associated with specific cell values, not specific cells. This makes them different from feature class attribute tables, which are associated with specific vector objects.

226 of 382

  • Landfire Vegetation Type Raster doesn’t tell us much if we just go by the raster cell values.

227 of 382

  • Raster attributes are associated with cell values, not specific cells. This makes them different from feature class attribute tables, which are associated with specific vector objects.

228 of 382

  • If it has an attribute table, we might be able to symbolize it in a more informative way.

229 of 382

Special Types of Spatial Data

230 of 382

Special Types of Spatial Data

  • Layers

231 of 382

Special Types of Spatial Data

  • Layers
  • Tables

232 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps

233 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files

234 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation

235 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks

236 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets

237 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional

238 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

239 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains

​

240 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains
  • Topology

​

241 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains
  • Topology
  • Pyramids

​

242 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains
  • Topology
  • Pyramids
  • Raster Catalogs

​

243 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains
  • Topology
  • Pyramids
  • Raster Catalogs
  • Relationship Classes

​

244 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains
  • Topology
  • Pyramids
  • Raster Catalogs
  • Relationship Classes
  • Data Models

​

245 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains
  • Topology
  • Pyramids
  • Raster Catalogs
  • Relationship Classes
  • Data Models
  • Mosaic Rasters

​

246 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains
  • Topology
  • Pyramids
  • Raster Catalogs
  • Relationship Classes
  • Data Models
  • Mosaic Rasters
  • Voxels

​

​

247 of 382

Special Types of Spatial Data

  • Layers
  • Tables
  • Web Maps / Apps
  • KML/KMZ files
  • Annotation
  • Geometric Networks
  • Network Datasets
  • Multi-Dimensional
  • LiDAR

​

  • Terrains
  • Topology
  • Pyramids
  • Raster Catalogs
  • Relationship Classes
  • Data Models
  • Mosaic Rasters
  • Voxels
  • Digital Twins (3D models)

​

​

248 of 382

Layers

249 of 382

Tables

  • Attribute Tables
  • Standalone Tables
  • Text Files

250 of 382

Viewing Tables in ArcGIS Pro

251 of 382

Viewing Tables in ArcGIS Pro

  • Tables that are not associated with a feature class or raster are called Standalone Tables.

252 of 382

Viewing Tables in ArcGIS Pro

  • Tables that are not associated with a feature class or raster are called Standalone Tables.
  • You can add them to a map, but they are not spatial so they don’t draw.

​

253 of 382

Viewing Tables in ArcGIS Pro

  • Tables that are not associated with a feature class or raster are called Standalone Tables.
  • You can add them to a map, but they are not spatial so they don’t draw.
    • If the table has fields containing coordinates, it’s easy to convert to a feature class.

​

254 of 382

  • Table of Contents sorted by List by Drawing Order:
  • Standalone Tables in a separate section

255 of 382

Web Maps and Web Apps

  • Museum Fire Example from Mark Manone, Dept. of Geography

256 of 382

Web Maps and Web Apps

  • Biota of Grand Canyon Story Map (Museum of Northern Arizona)

​

257 of 382

Web Maps and Web Apps

258 of 382

KML/KMZ Files

  • Spatial data file invented by Google.

259 of 382

KML/KMZ Files

  • Spatial data file invented by Google.
  • KML = Keyhole Markup Language

260 of 382

KML/KMZ Files

  • Spatial data file invented by Google.
  • KML = Keyhole Markup Language
  • KMZ is a zipped KML file.

261 of 382

KML/KMZ Files

  • Spatial data file invented by Google.
  • KML = Keyhole Markup Language
  • KMZ is a zipped KML file.
  • Can contain both raster and vector data.

262 of 382

Annotation

263 of 382

Annotation

  • Text labels that are locked into a spatial location.

264 of 382

Annotation

  • Text labels that are locked into a spatial location.
  • Zooming into them makes them larger.

265 of 382

Networks

266 of 382

Networks

  • Trace and Utility Networks

267 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.

268 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.
    • Graph Theory, with edges and nodes (aka “Junctions”).

269 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.
    • Graph Theory, with edges and nodes (aka “Junctions”).
    • You can model stream connectivity, for example.

270 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.
    • Graph Theory, with edges and nodes (aka “Junctions”).
    • You can model stream connectivity, for example.
    • Stored in Feature Datasets.

271 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.
    • Graph Theory, with edges and nodes (aka “Junctions”).
    • You can model stream connectivity, for example.
    • Stored in Feature Datasets.
    • Trace Networks are simpler:

​

272 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.
    • Graph Theory, with edges and nodes (aka “Junctions”).
    • You can model stream connectivity, for example.
    • Stored in Feature Datasets.
    • Trace Networks are simpler:
      • Good for finding features that are connected, or finding shortest paths.
      • River systems, Roads

273 of 382

Networks

  • Trace Network, with derived Shortest Path

​

274 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.
    • Graph Theory, with edges and nodes (aka “Junctions”).
    • You can model stream connectivity, for example.
    • Stored in Feature Datasets.
    • Utility Networks help you manage active complex networks with sophisticated behaviors.
      • Electrical, gas or water networks

​

275 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.
    • Graph Theory, with edges and nodes (aka “Junctions”).
    • You can model stream connectivity, for example.
    • Stored in Feature Datasets.
    • Utility Networks help you manage active complex networks with sophisticated behaviors.
      • Electrical, gas or water networks
      • Different components behave differently: High-voltage to Low-Voltage connections

​

276 of 382

Networks

  • Trace and Utility Networks
    • Vector datasets that incorporate connectivity between features.
    • Graph Theory, with edges and nodes (aka “Junctions”).
    • You can model stream connectivity, for example.
    • Stored in Feature Datasets.
    • Utility Networks help you manage active complex networks with sophisticated behaviors.
      • Electrical, gas or water networks
      • Different components behave differently: High-voltage to Low-Voltage connections
      • Model disruptions in the network: Blown transformers, for example

​

​

277 of 382

Networks

  • Network Datasets

​

278 of 382

Networks

  • Network Datasets
    • Similar to Trace Networks, but specifically designed to work with Esri’s Network Analyst extension.

​

279 of 382

Networks

  • Network Datasets
    • Similar to Geometric Networks, but specifically designed to work with Esri’s Network Analyst extension.
    • Also used for finding shortest path between points on a road network.

​

280 of 382

Networks

  • Network Datasets
    • Similar to Geometric Networks, but specifically designed to work with Esri’s Network Analyst extension.
    • Also used for finding shortest path between points on a road network.
    • Incorporates local street issues

​

281 of 382

Networks

  • Network Datasets
    • Similar to Geometric Networks, but specifically designed to work with Esri’s Network Analyst extension.
    • Also used for finding shortest path between points on a road network.
    • Incorporates local street issues
      • One-way streets

​

282 of 382

Networks

  • Network Datasets
    • Similar to Geometric Networks, but specifically designed to work with Esri’s Network Analyst extension.
    • Also used for finding shortest path between points on a road network.
    • Incorporates local street issues
      • One-way streets
      • Street on overpass might not intersect lower street

​

283 of 382

Networks

  • Network Datasets
    • Similar to Geometric Networks, but specifically designed to work with Esri’s Network Analyst extension.
    • Also used for finding shortest path between points on a road network.
    • Incorporates local street issues
      • One-way streets
      • Street on overpass might not intersect lower street
      • Local “No Turn” rules

​

284 of 382

Networks

  • Network Datasets
    • Similar to Geometric Networks, but specifically designed to work with Esri’s Network Analyst extension.
    • Also used for finding shortest path between points on a road network.
    • Incorporates local street issues
      • One-way streets
      • Street on overpass might not intersect lower street
      • Local “No Turn” rules
    • Stored in Feature Datasets

​

​

285 of 382

Network Datasets

Resource Allocation

Best Routes

286 of 382

Multi-dimensional Datasets

  • NetCDF (Network Common Data Form), HDF, Cloud Raster Format, “Image Cubes”

Two-dimensions

(Longitude and Latitude)

Add 3rd Dimension

(Altitude)

287 of 382

Multi-dimensional Datasets

  • NetCDF (Network Common Data Form), HDF, Cloud Raster Format, “Image Cubes”
  • Often used for data-intensive scientific applications, like 3D climate or ocean current modeling.

Two-dimensions

(Longitude and Latitude)

Add 3rd Dimension

(Altitude)

288 of 382

Multi-dimensional Datasets

  • NetCDF (Network Common Data Form), HDF, Cloud Raster Format, “Image Cubes”
  • Often used for data-intensive scientific applications, like 3D climate or ocean current modeling.
  • Can be a real pain to work with.

Two-dimensions

(Longitude and Latitude)

Add 3rd Dimension

(Altitude)

289 of 382

Multi-dimensional Datasets

Add 4th Dimension

(Time)

290 of 382

Multi-dimensional Datasets

Add 5th Dimension

(Who knows?)

291 of 382

NetCDF (Network Common Data Form)

  • Very common Multidimensional Format. A lot of global climate and ocean model data come in NetCDF.

292 of 382

NetCDF (Network Common Data Form)

  • Very common Multidimensional Format. A lot of global climate and ocean model data come in NetCDF.

​

​

​

​

​

​

​

​

​

​

​

​

  • Format includes internal query functions, to extract subsets of the full dataset.

293 of 382

NetCDF (Network Common Data Form)

  • Very common Multidimensional Format. A lot of global climate and ocean model data come in NetCDF.

​

​

​

​

​

​

​

​

​

​

​

​

​

  • Format includes internal query functions, to extract subsets of the full dataset.
  • Best tools I’ve found to work with it are in Linux, and intended more for supercomputer or high-end computer cluster analysis.

294 of 382

Terrains

295 of 382

Terrains

  • TIN-based vector datasets optimized for quick analysis, editing and viewing.

296 of 382

Terrains

  • TIN-based vector datasets optimized for quick analysis, editing and viewing.
  • They look like TINs but are not stored the same way. The triangles are created on-the-fly as you view the dataset.

297 of 382

Terrains

  • TIN-based vector datasets optimized for quick analysis, editing and viewing.
  • They look like TINs but are not stored the same way. The triangles are created on-the-fly as you view the dataset.
  • They use Pyramids, which allows them to be drawn at different resolutions when viewed at different scales.

298 of 382

Terrains

  • TIN-based vector datasets optimized for quick analysis, editing and viewing.
  • They look like TINs but are not stored the same way. The triangles are created on-the-fly as you view the dataset.
  • They use Pyramids, which allows them to be drawn at different resolutions when viewed at different scales.
  • Stored in Feature Datasets

299 of 382

LiDAR

300 of 382

LiDAR

  • Like Radar, but with lasers.

301 of 382

LiDAR

  • Like Radar, but with lasers.
  • Produces a point cloud of 3D points.

302 of 382

LiDAR

  • Like Radar, but with lasers.
  • Produces a point cloud of 3D points.
  • Based on the speed of light, and the time it takes to get a return signal from a laser.

303 of 382

LiDAR

  • Like Radar, but with lasers.
  • Produces a point cloud of 3D points.
  • Based on the speed of light, and the time it takes to get a return signal from a laser.
  • Different wavelengths can see different things, like multispectral imagery.

304 of 382

Parcel Fabrics

  • Specifically designed to map Property Boundaries.
  • Stored in a Feature Dataset.

305 of 382

Topology

  • A special type of data structure that tells related vector objects how they are spatially related to each other.

306 of 382

Topology

  • A special type of data structure that tells related vector objects how they are spatially related to each other.
  • For example, suppose you have two adjacent polygons representing timber stands. If you want to move the boundary that separates them, you would like both polygons to incorporate the new boundary.

307 of 382

More on Topology

308 of 382

More on Topology

  • ArcGIS implements topology in many ways.

309 of 382

More on Topology

  • ArcGIS implements topology in many ways.
    • Some datasets have a basic topology built into them (Coverages and TINs, for example).

310 of 382

More on Topology

  • ArcGIS implements topology in many ways.
    • Some datasets have a basic topology built into them (Coverages and TINs, for example).
    • Most datasets have no internal topology defined, but ArcGIS can create a temporary topology when it needs to (as in editing).

311 of 382

More on Topology

  • ArcGIS implements topology in many ways.
    • Some datasets have a basic topology built into them (Coverages and TINs, for example).
    • Most datasets have no internal topology defined, but ArcGIS can create a temporary topology when it needs to (as in editing).
    • ArcGIS also allows you to define complex topological relationships between datasets in geodatabases.

312 of 382

More on Topology

  • ArcGIS implements topology in many ways.
    • Some datasets have a basic topology built into them (Coverages and TINs, for example).
    • Most datasets have no internal topology defined, but ArcGIS can create a temporary topology when it needs to (as in editing).
    • ArcGIS also allows you to define complex topological relationships between datasets in geodatabases.
    • You can add them to feature datasets to help find problems in the data.

313 of 382

More on Topology

  • ArcGIS implements topology in many ways.
    • Some datasets have a basic topology built into them (Coverages and TINs, for example).
    • Most datasets have no internal topology defined, but ArcGIS can create a temporary topology when it needs to (as in editing).
    • ArcGIS also allows you to define complex topological relationships between datasets in geodatabases.
    • You can add them to feature datasets to help find problems in the data.
      • Polylines that almost, but don’t quite, connect.

314 of 382

More on Topology

  • ArcGIS implements topology in many ways.
    • Some datasets have a basic topology built into them (Coverages and TINs, for example).
    • Most datasets have no internal topology defined, but ArcGIS can create a temporary topology when it needs to (as in editing).
    • ArcGIS also allows you to define complex topological relationships between datasets in geodatabases.
    • You can add them to feature datasets to help find problems in the data.
      • Polylines that almost, but don’t quite, connect.
      • Polyline or polygon segments that overshoot.

315 of 382

More on Topology

316 of 382

Pyramids

  • Interesting innovation to speed up drawing time for large rasters and terrains.

317 of 382

Pyramids

  • Interesting innovation to speed up drawing time for large rasters and terrains.
  • Several versions of the data are created at different scales. Depending on the scale of the map, ArcGIS may show a coarser resolution version rather than the actual dataset.

318 of 382

Pyramids

  • Interesting innovation to speed up drawing time for large rasters and terrains.
  • Several versions of the data are created at different scales. Depending on the scale of the map, ArcGIS may show a coarser resolution version rather than the actual dataset.
  • The coarser versions draw a lot faster than the fine versions, and you can’t tell the difference on the screen.

319 of 382

Raster Catalogs

  • Another interesting innovation.
  • A collection of rasters that are treated as a single object, and portrayed as either a vector or raster object depending on your view extent.

320 of 382

Relationship Classes

  • Not actually spatial data in themselves, but sometimes used to define relationships between datasets.

321 of 382

Relationship Classes

  • Not actually spatial data in themselves, but sometimes used to define relationships between datasets.
  • For example, a utility company may have:

322 of 382

Relationship Classes

  • Not actually spatial data in themselves, but sometimes used to define relationships between datasets.
  • For example, a utility company may have:
    • A table of property owners, with names, addresses, etc.

323 of 382

Relationship Classes

  • Not actually spatial data in themselves, but sometimes used to define relationships between datasets.
  • For example, a utility company may have:
    • A table of property owners, with names, addresses, etc.
    • A feature class of electrical distribution lines, with property owner IDs.

324 of 382

Relationship Classes

  • Not actually spatial data in themselves, but sometimes used to define relationships between datasets.
  • For example, a utility company may have:
    • A table of property owners, with names, addresses, etc.
    • A feature class of electrical distribution lines, with property owner IDs.
    • The utility company could create a relationship class that connects the distribution line feature class with the property owner attribute table. Any analysis done on the property lines could then automatically extract property owner information.

325 of 382

Relationship Classes

  • Not actually spatial data in themselves, but sometimes used to define relationships between datasets.
  • For example, a utility company may have:
    • A table of property owners, with names, addresses, etc.
    • A feature class of electrical distribution lines, with property owner IDs.
    • The utility company could create a relationship class that connects the distribution line feature class with the property owner attribute table. Any analysis done on the property lines could then automatically extract property owner information.
  • Creating relationship classes in a Geodatabase requires an ArcGIS Standard or Advanced license.

326 of 382

Data Models

  • For cases where a simple data type is insufficient to describe the complexity.

327 of 382

Data Models

  • For cases where a simple data type is insufficient to describe the complexity.
  • For example, hydrologists study river systems, but a simple polyline feature class is not complex enough.

328 of 382

Data Models

  • For cases where a simple data type is insufficient to describe the complexity.
  • For example, hydrologists study river systems, but a simple polyline feature class is not complex enough.
    • They need to incorporate flow direction, catchment area, surface and subsurface flow rates, etc.

329 of 382

Data Models

  • For cases where a simple data type is insufficient to describe the complexity.
  • For example, hydrologists study river systems, but a simple polyline feature class is not complex enough.
    • They need to incorporate flow direction, catchment area, surface and subsurface flow rates, etc.
  • There is an example of a popular data model (ArcMarine, for marine analysis and management) in your class outline.

330 of 382

ArcMarine Data Model

331 of 382

Mosaic Dataset

  • An example of a Data Model designed to deliver multiple raster datasets as a single unit. It can be analyzed like any other raster dataset.

332 of 382

Voxels (Like Pixels, but with Volume)

333 of 382

3D Models (aka Digital Twins)

334 of 382

Done with Data Types

335 of 382

Done with Data Types

  • A few last words on Catalog:

336 of 382

Done with Data Types

  • A few last words on Catalog:
    • As mentioned before, Catalog is the recommended way to copy, move or delete spatial datasets.

337 of 382

Done with Data Types

  • A few last words on Catalog:
    • As mentioned before, Catalog is the recommended way to copy, move or delete spatial datasets.
    • If you create a new dataset in a workspace (perhaps using one of the geoprocessing tools), you will usually need to refresh Catalog before you will see it (use the F5 key).

338 of 382

Done with Data Types

  • A few last words on Catalog:
    • As mentioned before, Catalog is the recommended way to copy, move or delete spatial datasets.
    • If you create a new dataset in a workspace (perhaps using one of the geoprocessing tools), you will usually need to refresh Catalog before you will see it (use the F5 key).
    • Your class handout has an appendix showing the symbols Catalog uses for different types of datasets.

339 of 382

ArcCatalog Symbols (ArcGIS Pro Catalog symbols are similar)

340 of 382

Metadata

  • Data that describes your data

“I never metadata I didn’t like!

Unknown

341 of 382

Metadata

  • Data that describes your data
    • Who created it

“I never metadata I didn’t like!

Unknown

342 of 382

Metadata

  • Data that describes your data
    • Who created it
    • Purpose and Description

“I never metadata I didn’t like!

Unknown

343 of 382

Metadata

  • Data that describes your data
    • Who created it
    • Purpose and Description
    • Dates it might be valid for

“I never metadata I didn’t like!

Unknown

344 of 382

Metadata

  • Data that describes your data
    • Who created it
    • Purpose and Description
    • Dates it might be valid for
    • Spatial Reference and Extent

“I never metadata I didn’t like!

Unknown

345 of 382

Metadata

  • Data that describes your data
    • Who created it
    • Purpose and Description
    • Dates it might be valid for
    • Spatial Reference and Extent
    • Describe what Attribute Fields mean

“I never metadata I didn’t like!

Unknown

346 of 382

Metadata

  • Data that describes your data
    • Who created it
    • Purpose and Description
    • Dates it might be valid for
    • Spatial Reference and Extent
    • Describe what Attribute Fields mean
    • Processing History (a Slope dataset might list the source elevation dataset, and the parameters used to calculate slope).

“I never metadata I didn’t like!

Unknown

347 of 382

Metadata

  • Data that describes your data
    • Who created it
    • Purpose and Description
    • Dates it might be valid for
    • Spatial Reference and Extent
    • Describe what Attribute Fields mean
    • Processing History (a Slope dataset might list the source elevation dataset, and the parameters used to calculate slope).
    • Lots more! Hundreds of potential attributes

“I never metadata I didn’t like!

Unknown

348 of 382

Metadata

349 of 382

Metadata

  • Metadata can be very important!

350 of 382

Metadata

  • Metadata can be very important!
    • Can tell you whether the data is really valid for your project.

351 of 382

Metadata

  • Metadata can be very important!
    • Can tell you whether the data is really valid for your project.
    • Gives you documentation to back up any conclusions you make from the data.

352 of 382

Metadata

  • Metadata can be very important!
    • Can tell you whether the data is really valid for your project.
    • Gives you documentation to back up any conclusions you make from the data.
  • Not all datasets have metadata!

353 of 382

Metadata

  • Metadata can be very important!
    • Can tell you whether the data is really valid for your project.
    • Gives you documentation to back up any conclusions you make from the data.
  • Not all datasets have metadata!
    • If you make a dataset available to the public, you should add metadata.

354 of 382

Metadata

  • Metadata can be very important!
    • Can tell you whether the data is really valid for your project.
    • Gives you documentation to back up any conclusions you make from the data.
  • Not all datasets have metadata!
    • If you make a dataset available to the public, you should add metadata.
    • If you are just making intermediate datasets in a larger analysis, you probably won’t make metadata.

​

355 of 382

Metadata in ArcGIS Pro View

“Maps are like milk: their information is perishable, and it is wise to check the date.”

Mark Monmonier, How to Lie with Maps

356 of 382

Metadata in Catalog View

357 of 382

Metadata Styles

  • These correspond with various Metadata Standards

358 of 382

Creating and Editing Metadata

You will do this in a lab exercise…

359 of 382

Be warned…

360 of 382

Be warned…

  • ArcGIS tools typically record what you have done into your metadata.

361 of 382

Be warned…

  • ArcGIS tools typically record what you have done into your metadata.
  • This means that often you can see a record of everything that has been done to a particular dataset.

362 of 382

Be warned…

  • ArcGIS tools typically record what you have done into your metadata.
  • This means that often you can see a record of everything that has been done to a particular dataset.
  • This is often a very useful feature, but it might reveal things you didn’t intend to make public.

363 of 382

Be warned…

  • ArcGIS tools typically record what you have done into your metadata.
  • This means that often you can see a record of everything that has been done to a particular dataset.
  • This is often a very useful feature, but it might reveal things you didn’t intend to make public.
  • Your “LeBarronStands_v1_NAD83” feature class has some interesting things in the processing history…

​

364 of 382

Be warned…

  • When you send data to a colleague (or the general public), this kind of information can travel with it:

​

365 of 382

Data Management Strategies

366 of 382

Data Management Strategies

  • It is quite common to use multiple workspaces in a single ArcGIS session.

367 of 382

Data Management Strategies

  • It is quite common to use multiple workspaces in a single ArcGIS session.
  • If you do a lot of analysis, you will probably create a lot of intermediate datasets as you work.

368 of 382

Data Management Strategies

  • It is quite common to use multiple workspaces in a single ArcGIS session.
  • If you do a lot of analysis, you will probably create a lot of intermediate datasets as you work.
  • This quickly leads to cluttered workspaces where you can’t find the data you want.

369 of 382

Data Management Strategies

  • It is quite common to use multiple workspaces in a single ArcGIS session.
  • If you do a lot of analysis, you will probably create a lot of intermediate datasets as you work.
  • This quickly leads to cluttered workspaces where you can’t find the data you want.
  • It is a very good idea to plan where you are going to store your data before you start.

370 of 382

Data Management Strategies

  • It is quite common to use multiple workspaces in a single ArcGIS session.
  • If you do a lot of analysis, you will probably create a lot of intermediate datasets as you work.
  • This quickly leads to cluttered workspaces where you can’t find the data you want.
  • It is a very good idea to plan where you are going to store your data before you start.
    • For example, make several folders or geodatabases where you will store particular datasets. Then be disciplined about storing them in the correct place as you work.

371 of 382

Lab Exercise 1

  • Only if you have not done it already!
  • Connect to your data folder.

372 of 382

Lab Exercise 2

  • Create a new File Geodatabase using Catalog.

373 of 382

Lab Exercise 3

  • Import a feature class into your new file geodatabase.

374 of 382

Lab Exercise 4

  • Import a raster into your new file geodatabase.

375 of 382

Lab Exercise 5

  • Investigate a multiband raster
    • Analyze a typical multiband raster containing images from multiple electromagnetic wavelengths.

376 of 382

Lab Exercise 6

  • Investigate a Layer File
    • Observe the difference between loading a basic feature class into ArcGIS Pro vs. loading a layer file.

377 of 382

Lab Exercise 7

  • Investigate a TIN dataset

378 of 382

Lab Exercise 8

  • Investigate an Attribute Table

379 of 382

Lab Exercise 9

  • Zoom to feature using an attribute table.

380 of 382

Lab Exercise 10

  • Connect to an Online Web service

381 of 382

Lab Exercise 11

  • View and Edit Metadata

382 of 382

Lab Exercise 12

  • Learn how to share spatial data with colleagues.
    • Learn what files make up a shapefile, and how to compress those files into a single file suitable for emailing or posting online.
    • Learn what files make up a file geodatabase workspace, and how to share that workspace with others.