UtahBG {micromapST}R Documentation

UtahBG border group datasets to support creating micromaps for the counties in the state of Utah

Description

The micromapST function has the ability to generate linked micromaps for any geographical area. To specify the geographical area, the bordGrp call parameter is used to specify the border group dataset for the geographical area. The UtahBG border group dataset is contained within this package and supports creating linked micromaps for the 29 counties in the state of Utah. When the bordGrp call parameter is set to UtahBG, the appropriate name table (county names and abbreviations) and the 29 sub-areas (countries) boundary data is loaded in micromapST. The user's data is then linked to the boundary data via the county's name, abbreviation, alternate abbreviation, or ID based on the table below.

Details

The UtahBG border group dataset contains the following data.frames:

areaParms

- contains specific parameters for the border group

areaNamesAbbrsIDs

- containing the names, abbreviations, and numerical identifier for the 29 counties in the state of Utah.

areaVisBorders

- the boundary point lists for each county area in Utah.

L2VisBorders

- the boundaries for an intermediate level. For this border group, this boundary data.frame is not used and set to L3VisBorders as a place holder.

RegVisBorders

- the boundaries for an intermediate level. For this border group, this boundary data.frame is not used and set to L3VisBorders as a place holder.

L3VisBorders

- the boundary of the state of Utah

The Utah county border group contains 29 county sub-areas. Each county has a row in the areaNamesAbbrsIDs data.frame and a set of polygons in the areaVisBorders data.frame datasets. No regions are defined in the Utah county border group, so the L2VisBorders dataset is not used and the regions option is disabled. The L3VisBorders dataset contains the outline of the state of Utah.

The details on each of these data.frame structures can be found in the "bordGrp" section of this document. The areaNamesAbbrsIDs data.frame provides the linkages to the boundary data for each sub-area (county) using the fullname, abbreviation, and numerical identifier for each country to the <statsDFrame> data based on the setting of the rowNames call argument.

A identified column (idCol) or the data.frame row.names must match one of the types of names in the border group's areaNamesAbbrsIDs data.frame name table. If the data row does not match a value in the name table, an warning is issued and the data is ignored. If no data is present for a sub-area (county) in the name table, the sub-area is mapped but not colored.

The following are a list of the names, abbreviations, alternate abbreviations and IDs for each country in the UtahBG border group.

name ab alt_ab id
Beaver BV BEA 49001
Box Elder BE BOX 49003
Cache CH CAC 49005
Carbon CA CAR 49007
Daggett DAG DAG 49009
Davis DAV DAV 49011
Duchesne DU DUC 49013
Emery EM EME 49015
Garfield GA GAR 49017
Grand GR GRA 49019
Iron IR IRO 49021
Juab JB JUA 49023
Kane KN KAN 49025
Millard MI MIL 49027
Morgan MO MOR 49029
Piute PT PIU 49031
Rich RH RIC 49033
Salt Lake SL SAL 49035
San Juan SJ SNJ 49037
Sanpete SP SNP 49039
Sevier SV SEV 49041
Summit SU SUM 49043
Tooele TO TOO 49045
Uintah UI UIN 49047
Utah UT UTA 49049
Wasatch WS WST 49051
Washington WA WSH 49053
Wayne WN WAY 49055
Weber WB WEB 49057

When compiling the information for the UtahBG border group, it was not clear what was the standard accepted abbreviation for each county. Therefore, two sets of abbreviations for each county are included. The first abbreviation set can be referenced by setting the rowNames call parameter to "ab". The second (alternate) abbreviation set can be used by setting the rowNames to "alt_ab".

The id field value is the 5 digit U. S. state and county FIPS code.

The rowNames = "alias" and the regions features are not supported in the UtahBG border group.


[Package micromapST version 3.0.3 Index]