DATA DETAILS > BOUNDARIES

The feature classes below are stored in the project database within the "boundaries" feature dataset.  
Recommended Uses: reference layers on maps; unit of analysis to generate spatial statistics from geoprocessing tools like intersect and dissolve.

sample_boxes

Spatial Information: 14,400 records; each polygon and row = one sample box.  
Format: file geodatabase polygon feature class
Feature Dataset: boundaries
Primary Key: SampleBox_ID
Attributes:
  • County: county name
  • State:  state name
  • Grid_ID: unique 8-digit code for each sample grid  The first 5 digits correspond with the FIPS county code.
  • SampleBoxID: unique 11-digit code for each sample box.  The first 8 digits correspond with the Grid_ID.
  • X_WGS_84: longitude of centroid in decimal degrees; WGS 84.
  • Y_WGS_84: latitude of centroid in decimal degrees; WGS 84.
  • Shape_Length: perimeter of each sample box in meters.
  • Shape_Area: area of each sample box in square meters.
Coded Domains: none.
Scale: unknown.
Source: Custom dataset created for the project for use as the main unit of analysis in spatial/statistical analyses.  Each sample box is ~ 0.5 square miles by 0.5 square miles.  Sub-division of sample boxes, with 36 sample boxes per sample grid.

sample_grids

Spatial Information: 400 records; each polygon and row = one sample grid.  
Format: file geodatabase polygon feature class
Feature Dataset: boundaries
Primary Key: SampleGrid_ID
Attributes:
  • County: county name
  • State:  state name
  • Grid_ID: unique 8-digit code for each sample grid  The first 5 digits correspond with the FIPS county code.
  • Shape_Length: perimeter of each sample grid in meters.
  • Shape_Area: area of each sample grid in square meters.
Coded Domains: none.
Scale: unknown.
Source: Custom dataset created for the project used to delineate sample areas in which we created land use data.  Each sample grid is ~ 3 square miles by 3 square miles.  Boundaries are based on the Public Land Survey System. 

counties

Spatial Information: 50 records; each polygon and row = one county.  
Format: file geodatabase polygon feature class
Feature Dataset: boundaries
Primary Key: OBJECTID
Attributes:
  • State:  two letter abbreviation for the state name
  • County: county name
  • UTM: number of the UTM Zone the majority of the county is located in.  (Some counties are located on UTM Zone boundaries).
  • AdjacentGr: Yes = shares a border with another study area county.  No= does NOT share a border with another study area county.
  • FIPs: Federal Information Processing Standard Code (FIPS 6-4); a unique 5 digit code for each county.
  • Shape_Length: perimeter of each polygon in meters.
  • Shape_Area: area of each polygon in square meters.
Coded Domains: none.
Scale: unknown.
Source: Source unclear.  Only the 50 counties within the study area are included in the file.

states

Spatial Information: 10 records; each polygon and row = one state.  
Format: file geodatabase polygon feature class
Feature Dataset: boundaries
Primary Key: OBJECTID
Attributes:
  • Abrev: two letter abbreviation for the state name
  • State:  state name
  • Shape_Length: perimeter of each state in meters.
  • Shape_Area: area of each state in square meters.
Coded Domains: none.
Scale: unknown.
Source: Source unclear.  Only the 10 states within the study area are included in the file.

utm_zones

Spatial Information: 4 records; each polygon and row = one UTM Zone.  
Format: file geodatabase polygon feature class
Feature Dataset: boundaries
Primary Key: OBJECTID
Attributes:
  • UTM_Zone:  UTM zone number
  • Shape_Length: perimeter of each UTM Zone in meters.
  • Shape_Area: area of each UTM Zone in square meters.
Coded Domains: none.
Scale: unknown.
Source: Source unclear.  Only the 10 states within the study area are included in the file.