Chapter Contents

Previous

Next

Data Set and Catalog Entry Interactions

SAS/GIS software uses SAS catalog entries to store metadata for the spatial database-that is, information about the spatial data values in the spatial data sets. SAS/GIS spatial databases use the following entry types.

Spatial Entries

A spatial entry is a SAS catalog entry of type GISSPA that identifies the spatial data sets for a given spatial database and defines relationships between the variables in those data sets.

SAS/GIS software supports simple spatial entries and merged spatial entries as follows:

Simple spatial entries contain

• References to the chains, nodes, and details data sets that contain spatial information.

• References to any polygonal index data sets that define the boundaries of area features in the spatial data.

• Definitions for composites that specify how the variables in the spatial data sets are used. See Composites for more information on composites.

• The definition for a lattice hierarchy that specifies which area features in the spatial data enclose or are enclosed by other features.

• Parameters for the projection system that is used to interpret the spatial information that is stored in the spatial data sets.

• The accumulated bounding extents of the spatial data coordinates of its underlying child spatial data sets, consisting of the minimum and maximum X and Y coordinate values and the ranges of X and Y values.

Merged spatial entries

• Consist of multiple SAS/GIS spatial databases that are linked together hierarchically in a tree structure.

• Contain logical references to two or more other child spatial entries. A child spatial entry is a dependent spatial entry beneath the merged spatial entry in the hierarchy.

• Contain specifications of how the entries were merged (by overlapping or edgematching).

• Do not have their own spatial data sets.

• Reference the spatial data sets that belong to the child spatial entries beneath them on the hierarchy.

• Do not have references to any polygonal index data sets that define the boundaries of area features in the spatial data.

• Do not have definitions for composites that specify how the variables in the spatial data sets are used. See Composites for more information on composites.

• Do not have the definition for a lattice hierarchy that specifies which area features in the spatial data enclose or are enclosed by other features.

• Do not have parameters for the projection system that is used to interpret the spatial information stored in the spatial data sets.

• Contain the accumulated bounding extents of the spatial data coordinates of their underlying child spatial entries, consisting of the minimum and maximum X and Y coordinate values and the ranges of X and Y values.

For example, you may have two spatial databases that contain the county boundaries of adjoining states. You can build a merged spatial entry that references both states and view a single map that contains both states' counties. Otherwise, you would have to import a new map containing the two states' counties. This new map would double your spatial data storage requirements.

Spatial entries are created and modified using the SPATIAL statement in the GIS procedure.

Note:   You can also create a new spatial entry by selecting the following from the GIS Map window's menu bar:

[File]→[Save As]→[Spatial]  

The following additional statements in the GIS procedure also update the information in the spatial entry:

COMPOSITE statement

Creates or modifies composites that define the relation and function of variables in the spatial data sets. The composite definition is stored in the spatial entry. See COMPOSITE Statement for details about creating or modifying composites.

POLYGONAL INDEX statement

Updates the list of available index names stored in the spatial entry. See POLYGONAL INDEX Statement for details about creating or modifying polygonal indexes.

LATTICE statement

Updates the lattice hierarchy stored in the spatial entry. See LATTICE Statement for details about defining lattice hierarchies.

You can view a formatted report of the contents of a spatial entry by submitting a SPATIAL CONTENTS statement in the GIS procedure.

See SPATIAL Statement for details about using the GIS procedure to create, modify, or view the contents of spatial entries.

Coverage Entries

A coverage entry is a SAS catalog entry of type GISCOVER that defines the subset, or coverage, of the spatial data that are available to a map. SAS/GIS maps refer to coverages rather than directly to the spatial data.

A coverage entry contains the following elements:

• A reference to the root spatial entry.

• A WHERE clause that describes the logical subset of the spatial data that are available for display in a map.

  Note:   The clause WHERE='1' can be used to define a coverage that includes all the data that are in the spatial database. WHERE='1' is called a universal coverage.  
  

  The WHERE clause binds the coverage entry to the spatial data sets that it subsets. The WHERE clause is checked for compatibility with the spatial data when the coverage entry is created and also whenever a map that uses the coverage entry is opened.

• The maximum and minimum X and Y coordinates in the portion of the spatial data that meets the WHERE clause criteria for the coverage.

  These maximum and minimum coordinates are evaluated when the coverage is created. The GIS procedure's COVERAGE CREATE statement reads the matching chains and determines the extents from the chains, the XMIN, YMIN, XMAX, and YMAX variables. If you make changes to the chains, nodes, and details data sets that affect the coverage extents, use the COVERAGE UPDATE statement to update the bounding extent values.

Multiple coverage entries can refer to the same spatial entry to create different subsets of the spatial data for different maps. For example, you could define a series of coverages to subset a county into multiple sales regions according to the block groups that are contained in each of the regions. The spatial data for the entire county would still be in a single spatial database that is represented by the chains, nodes, and details data sets and by the controlling spatial entry.

Coverage entries are created and modified by using the COVERAGE statement in the GIS procedure. You can view a formatted report of the contents of a coverage entry by submitting a COVERAGE CONTENTS statement in the GIS procedure. (The contents report for a coverage entry also includes all the contents information for the root spatial entry as well.)

See COVERAGE Statement for more information about creating, modifying, or viewing the contents of coverage entries.

Layer Entries

A layer entry is a SAS catalog entry of type GISLAYER that defines the set of features that compose a layer in the map. A layer entry contains the following elements:

• A WHERE clause that describes the common characteristic of features in the layer.

  The WHERE clause binds the layer entry to the spatial data even though the WHERE clause is stored in the layer entry. The layer is not bound to a specific spatial entry, just to those entries that represent the same type of data. Therefore, a layer that is created for use with data that are imported from a TIGER file can be used with data that are imported from any TIGER file; however, not all filetypes can take advantage of this behavior. The WHERE clause is checked for compatibility with spatial data when the layer entry is created and also whenever a map that uses the layer entry is opened.

  Note:   When you define area layers, you can specify a composite as an alternative to specifying an explicit WHERE clause. However, the layer entry stores the WHERE clause that is implied by the composite. For example, if you specify STATE as the defining composite for a layer, and the STATE composite specifies the following variables: VAR=(LEFT=STATEL,RIGHT=STATER), then the implied WHERE clause that is stored in the layer entry is 'STATEL NE STATER'.  
  

• Option settings for the layer such as the layer type (point, line, or area), whether the layer is static or thematic, whether it is initially displayed or hidden, whether detail points are drawn for the layer, and the scales at which the layer is automatically turned on or off.

• The graphical attributes that are necessary to draw the layer when it is displayed as a static layer.

• The attribute links, theme range breaks, and graphical attributes if the layer contains themes.

Map Entries

A map entry is a SAS catalog entry of type GISMAP. Map entries are the controlling entries for SAS/GIS maps because they tie together all the information that is needed to display a map. A map entry contains the following elements:

• A reference to the coverage entry that defines the subset of the spatial data that are available to the map. Note that the map entry refers to a particular coverage of the spatial data rather than directly to the spatial entry.

• References to the layer entries for all layers that are included in the map.

• References to any attribute data sets that are associated with the map, for example, the data sets that are used for the map actions, along with definitions of how the attribute data sets are linked to the spatial data.

• A reference to the SAS data set that contains labels for map features.

• Definitions for the actions that can be performed.

• Definitions for map legends.

• Parameters for the projection system that is used to project spatial data coordinates for display.

• Option settings for the map, including the following:
  • The units and mode for the map scale

  • Whether coordinate, distance, and attribute feedback are displayed

  • Whether detail points are read

  • Whether the tool palette is active.

Map entries are created by using the MAP CREATE statement in the GIS procedure. However, much of the information that is stored in the map entry is specified interactively in the GIS Map window.

You can view a formatted report of the contents of a map entry by submitting a MAP CONTENTS statement in the GIS procedure. (The contents report for a map entry includes all the contents information for the spatial, coverage, and layer entries as well.)

See MAP Statement for details on using the MAP statement.

Composites

For most operations that involve the spatial database, you refer to composites of the spatial data variables rather than directly to the variables in the spatial data sets. A composite consists of the following elements:

• A variable association that identifies which variable or variables in the spatial database comprise the association. The variable association can specify a single variable, a pair of variables that define a bilateral (left-right) association, or two pairs of variables that define the start and end of a directional (from-to) bilateral association.

• A class attribute that identifies the role of the composite in the spatial database.

For example, if the chains data set has a variable named FEANAME that contains feature names, you can create a composite for the FEANAME variable that assigns the class attribute NAME to indicate that the association represents feature names. Or, if the chains data set has COUNTYL and COUNTYR variables that contain the codes for the counties on the left and right sides of the chains, you can create a composite named COUNTY. The composite identifies the bilateral relationship between these two variables and assigns the class attribute AREA to indicate that the association defines county areas in the spatial data.

Composites are created and modified using the COMPOSITE statement in the GIS procedure. Composite definitions are stored in the spatial entry.

See COMPOSITE Statement for more information about creating or modifying composites.

Chapter Contents

Previous

Next

Top of Page

Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.