Michigan’s environmental remediation program authorizes EGLE to set cleanup standards by considering how the contaminated land will be used in the future. Michigan’s cleanup standards are risk-based and reflect the potential for human health or ecological risks from exposure to hazardous or regulated substances at contaminated sites. A person may use land use or resource use restrictions, as outlined in Part 201 and Part 213, to manage risk by reducing or restricting exposure to environmental contamination left in-place at a property.Land or Resource Use Restrictions may be in various forms including Restrictive Covenant, Notice of Aesthetic Impact, Notice of Corrective Action, Local Public Highway Institutional Control, Michigan Department of Transportation (MDOT) Environmental License Agreement, Local Ordinance, or an Alternative Institutional Control.This dataset shows locations of Land or Resource Use Restrictions that have been used to aid in the closure of a site of environmental contamination. The locations provided are not all-inclusive as they only represent those restrictions that have been sent to EGLE. This polygon dataset must be used along with the available point dataset Land or Resource Use Restrictions (Points) to show all the EGLE-mapped restrictions. Restrictions having proper legal descriptions and/or surveyed restriction area are represented with a polygon, while those having incomplete area and/or location details are represented by a point feature. The data is refreshed from daily from EGLE’s spatial database engine.Restrictions are mapped relative to existing GIS datasets including survey sections and aerial imagery and therefore have inherent inaccuracies. Locations provide a general representation but should not be relied upon for site-specific planning or decision making.The dataset’s field names are described below.

Field Name

Description

OBJECTID

Unique identifier for the GIS

Acres

Area of the restriction (acres)

SquareMiles

Area of the restriction (square miles)

KermitID

Unique identifier used to link to a scan of the restriction

RestrictionType

Numeric Code for the type of restriction

1 = Restrictive Covenant
  (RC)
2 = Notice of Corrective
  Action (NCA)
3 = Notice of Aesthetic
  Impairment (NAI)
4 = Ordinance
5 = Notice of Approved
  Environmental Remediation (NAER)
6 = Notice of Environmental Remediation (NER)
7 = Rescission of a Notice
  of Approved Environmental Remediation
8 (Not used)9 = Michigan Department of Transportation, Environmental License Agreement (MDOT)
0 = Other Institutional
  Control. This includes State Law/Local Health Code (SLHC), Public
  Highway Institutional Control (PHIC), Notice of Contamination (NOC),

RestrictionStatus

Status of the restriction

2 = Filed, Effective,
  Issued, or Recorded

FacilityName

Name of the Part 213 site or Part 201 facility

Address

Physical street address for the site or facility

City

City in which the site or facility is located

ZipCode

Zip code for the site or facility

EgleReferenceNumber

Unique reference number assigned by EGLE to the Land and Resource Use Restriction

Shape

GIS geometry type

Shape.STArea()

Area (square meters)

Shape.STLength()

Perimeter length (meters)

CreatedUser

Username of person who created the feature

CreatedDate

Date of feature creation

LastEditedUser

Username of the person who last edited the feature

LastEditedDate

Date the feature was last updated

LandUseRestrictionType

Text descriptor for the type of restriction

MgEntityCd

Lead EGLE division managing the site when restriction was imposed

ProgramType

Pertinent part of the Natural Resources and Environmental Protection Act

DeedDate

Date of effectiveness and/or recording with the Register of Deeds

LocationId

Unique identifier for the site within RRD’s RIDE database

For questions about this data, please reach out to EGLE-Maps@Michigan.gov.

This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.

This polygon layer contains the boundaries of the 113 block groups in the City of Cambridge for the 2010 US Census. Where appropriate, the boundary lines provided by the U.S. Census were adjusted by City staff to match those lines to such features as the City boundary, street centerlines, and parcel lines.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription BLKGRPCE10 type: Stringwidth: 1precision: 0

GEOID10 type: Stringwidth: 12precision: 0

NAMELSAD10 type: Stringwidth: 13precision: 0

MTFCC10 type: Stringwidth: 5precision: 0

FUNCSTAT10 type: Stringwidth: 1precision: 0

ALAND10 type: Doublewidth: 8precision: 38

AWATER10 type: Doublewidth: 8precision: 38

INTPTLAT10 type: Stringwidth: 11precision: 0

INTPTLON10 type: Stringwidth: 12precision: 0 Feature geometry.

Shape type: Doublewidth: 0precision: 0 Feature geometry.

More information on sub special areas can be found here. Planning Sub Special Areas is a Polygon FeatureClass representing areas within special centers with more guidelines for development. It is primarily used The layer is updated as needed by the GIS Division. Planning Sub Special Areas has the following fields:

NAME: Name of the planning sub special area type: String, length: 50, domain: none

AssetID: Cupertino maintained GIS primary key type: String, length: 50, domain: none

Location: Further description of the location type: String, length: 50, domain: none

Status: The active or construction status of the asset in the field type: String, length: 50, domain: none

OwnedBy: Organization which owns the asset type: String, length: 50, domain: none

Maintained: Organization who is responsible for maintenance of asset type: String, length: 50, domain: none

PrimaryIma: Hyperlink to photo or DMS type: String, length: 50, domain: none

DataSource: Description of what methods were used for data capture/migration type: String, length: 50, domain: none

UpdateBy: The user who last updated the database row type: String, length: 50, domain: none

UpdateDate: The date the database row was last updated type: Date, length: 8, domain: none

CreateBy: The name of the staff person who created the database row type: String, length: 50, domain: none

CreateDate: The date the database row was initially created type: Date, length: 8, domain: none

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: none

Label: The label associated with the planning sub special area type: String, length: 50, domain: none

Shape.STAr: The area of the shape - in square feet type: Double, length: 0, domain: none

Shape.STLe: The length of the shape - in feet type: Double, length: 0, domain: none

Description: These files contain the gazetteer used to record distinct, repeated sampling sites across the SAFE Project, including locations in the experimental landscape, the converted landscape surrounding SAFE and forest reserves and protected areas. The data files include a geojson file containing the sampling locations and their associated metadata and a CSV file containing recognized aliases for official gazetteer locations. The data in the csv alias file is deliberately not included in this metadata spreadsheet as the data is primarily used in this CSV format by data checking and other processes. The GIS geometries in the geojson file (using WGS84 coordinates) are taken from a wide range of original GIS files collected from researchers at SAFE: the source files are indicated in the geometry metadata and most will also be available in the SAFE Zenodo community. The files also include the R code used to collate the geometry data from the various source files and create the geojson and aliases files.This update adds new LOMBOK river transects (RRSJI1-6, RR8, RR10, RR19, RR20) Project: This dataset was collected as part of the following SAFE research project: SAFE CORE DATA XML metadata: GEMINI compliant metadata for this dataset is available here Files: This dataset consists of 4 files: SAFE_Gazetteer_metadata_v3.xlsx, gazetteer.geojson, location_aliases.csv, gazetteer_sf.R SAFE_Gazetteer_metadata_v3.xlsx This file only contains metadata for the files below gazetteer.geojson Description: A geojson file containing officially recognised SAFE Project sampling locations, along with basic metadata. This file contains 1 data tables:

SAFE Gazetteer (described in worksheet gazetteer.geojson) Description: This worksheet describes the feature data associated with the geometries in the Gazeetteer.geojson file. Number of fields: 15 Number of data rows: Unavailable (table metadata description only). Fields:

location: The primary ID code used for this location (Field type: id) type: Broad categories describing the different sampling types and campaigns that have been included in the gazetteer (Field type: categorical) plot_size: Intended geometry area for area based sampling locations. (Field type: categorical) display_order: Integer value used to control plotting order in displaying gazetteer data (Field type: numeric) parent: ID of parent location, for locations nested within larger sampling areas (Field type: categorical) region: Broad sampling regions within the SAFE Project (Field type: categorical) fractal_order: Fractal nesting level for core SAFE sampling sites (Field type: numeric) transect_order: Position along sampling point transect within blocks (Field type: numeric) centroid_x: Longitudinal centroid of feature geometry, not defined for linear geometries (Field type: numeric) centroid_y: Latitudinal centroid of feature geometry, not defined for linear geometries (Field type: numeric) source: Name of of original GIS source file containing geometry data (Field type: categorical) bbox_xmin: Geographic bound of geometry (Field type: numeric) bbox_ymin: Geographic bound of geometry (Field type: numeric) bbox_xmax: Geographic bound of geometry (Field type: numeric) bbox_ymax: Geographic bound of geometry (Field type: numeric)

location_aliases.csv Description: A CSV file containing pairs of official location names and accepted aliases, with an additional column showing where a location in an published dataset has been accepted as a gazeteer location This file contains 1 data tables:

SAFE Gazetteer location aliases (described in worksheet location_aliases.csv) Description: This file contains pairs of known aliases for locations and the matching official location ID. Aliases can be global or can be tied to a specific dataset ID. Number of fields: 3 Number of data rows: Unavailable (table metadata description only). Fields:

zenodo_record_id: location_aliases.csv (Field type: id) location: An official SAFE gazetteer location name (Field type: id) alias: A commonly used alternative alias for the location (Field type: id)

gazetteer_sf.R Description: The R file used to generate the two gazetteer files from the source files. The source files are not included in this record as they are published under separate records. Date range: 2010-10-01 to 2020-05-19 Latitudinal extent: 4.4121 to 4.9618 Longitudinal extent: 116.9471 to 117.9959

General Plan Land Use is a Polygon FeatureClass representing It is primarily used to indicate the General Plan Land Use designations within the City Limits. Updates to the layer are requested to the GIS Division by Community Development as directed by the City Council. The latest amendment is from September 2018 per resolution 18-055. General Plan Land Use has the following fields:

OBJECTID: Unique identifier automatically generated by Esri type: OID, length: 4, domain: none

LAND_USE: The land use code associated with the feature type: String, length: 16, domain: none

LABEL: The label associated with the feature type: String, length: 80, domain: none

ResolutionNumber: The resolution number type: String, length: 50, domain: none

GlobalID: Unique identifier automatically generated for features in enterprise database type: GlobalID, length: 38, domain: none

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: noneShape.STArea()The area of the geometric featuretype: Double, length: noneShape.STLength() The length of the geometric featuretype: Double, length: none

Summary

Rail Crossings is a spatial file maintained by the Federal Railroad Administration (FRA) for use by States and railroads.

Description

FRA Grade Crossings is a spatial file that originates from the National Highway-Rail Crossing, Inventory Program. The program is to provide information to Federal, State, and local governments, as well as the railroad industry for the improvements of safety at highway-rail crossing.

Credits

Federal Railroad Administration (FRA)

Use limitations

There are no access and use limitations for this item.

Extent

West -79.491008 East -75.178954 North 39.733500 South 38.051719

Scale Range Maximum (zoomed in) 1:5,000 Minimum (zoomed out) 1:150,000,000

ArcGIS Metadata ▼►Topics and Keywords ▼►Themes or categories of the resource  transportation

* Content type  Downloadable Data Export to FGDC CSDGM XML format as Resource Description No

Temporal keywords  2013

Theme keywords  Rail

Theme keywords  Grade Crossing

Theme keywords  Rail Crossings

Citation ▼►Title rr_crossings Creation date 2013-03-15 00:00:00

Presentation formats  * digital map

Citation Contacts ▼►Responsible party  Individual's name Raquel Hunt Organization's name Federal Railroad Administration (FRA) Contact's position GIS Program Manager Contact's role  custodian

Responsible party  Organization's name Research and Innovative Technology Administration/Bureau of Transportation Statistics Individual's name National Transportation Atlas Database (NTAD) 2013 Contact's position Geospatial Information Systems Contact's role  distributor

Contact information  ▼►Phone  Voice 202-366-DATA

Address  Type  Delivery point 1200 New Jersey Ave. SE City Washington Administrative area DC Postal code 20590 e-mail address answers@BTS.gov

Resource Details ▼►Dataset languages  * English (UNITED STATES) Dataset character set  utf8 - 8 bit UCS Transfer Format

Spatial representation type  * vector

* Processing environment Microsoft Windows 7 Version 6.1 (Build 7600) ; Esri ArcGIS 10.2.0.3348

Credits Federal Railroad Administration (FRA)

ArcGIS item properties  * Name USDOT_RRCROSSINGS_MD * Size 0.047 Location withheld * Access protocol Local Area Network

Extents ▼►Extent  Geographic extent  Bounding rectangle  Extent type  Extent used for searching * West longitude -79.491008 * East longitude -75.178954 * North latitude 39.733500 * South latitude 38.051719 * Extent contains the resource Yes

Extent in the item's coordinate system  * West longitude 611522.170675 * East longitude 1824600.445629 * South latitude 149575.449134 * North latitude 752756.624659 * Extent contains the resource Yes

Resource Points of Contact ▼►Point of contact  Individual's name Raquel Hunt Organization's name Federal Railroad Administration (FRA) Contact's position GIS Program Manager Contact's role  custodian

Resource Maintenance ▼►Resource maintenance  Update frequency  annually

Resource Constraints ▼►Constraints  Limitations of use There are no access and use limitations for this item.

Spatial Reference ▼►ArcGIS coordinate system  * Type Projected * Geographic coordinate reference GCS_North_American_1983_HARN * Projection NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet * Coordinate reference details  Projected coordinate system  Well-known identifier 2893 X origin -120561100 Y origin -95444400 XY scale 36953082.294548117 Z origin -100000 Z scale 10000 M origin -100000 M scale 10000 XY tolerance 0.0032808333333333331 Z tolerance 0.001 M tolerance 0.001 High precision true Latest well-known identifier 2893 Well-known text PROJCS["NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1312333.333333333],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-77.0],PARAMETER["Standard_Parallel_1",38.3],PARAMETER["Standard_Parallel_2",39.45],PARAMETER["Latitude_Of_Origin",37.66666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2893]]

Reference system identifier  * Value 2893 * Codespace EPSG * Version 8.1.1

Spatial Data Properties ▼►Vector  ▼►* Level of topology for this dataset  geometry only

Geometric objects  Feature class name USDOT_RRCROSSINGS_MD * Object type  point * Object count 1749

ArcGIS Feature Class Properties  ▼►Feature class name USDOT_RRCROSSINGS_MD * Feature type Simple * Geometry type Point * Has topology FALSE * Feature count 1749 * Spatial index TRUE * Linear referencing FALSE

Data Quality ▼►Scope of quality information  ▼►Resource level  attribute Scope description  Attributes The States and railroads maintain their own file and get updated to the FRA. The information is reported to the FRA on the U.S. DOT-ARR Crossing inventory form.

Attributes The quality of the inventory can vary because a record of grade crossing location is being maintained by each state and railroad that is responsible for maintaining its respective information.

Lineage ▼►Lineage statement The data was downloaded from the HWY-Rail Crossing Inventory Files. All crossings that were closed or abandon were queried out of the data. All of the crossings with a zero within the latitude or longitude were queried out. Any crossing outside a bounding box of box ((Latitude >= 18 & Latitude <= 72) AND (Longitude >= -171 & Longitude <= -63)) were queried out.

Geoprocessing history ▼►Process  Date 2013-08-14 10:41:15 Tool location c:\program files (x86)\arcgis\desktop10.0\ArcToolbox\Toolboxes\Data Management Tools.tbx\Project Command issued Project RR_CROSSINGS_MD_USDOT \shagbfs\gis_projects\Railroad_Crossings_MD\Railroad_Crossings_MD.gdb\RR_CROSSINGS_MD_USDOT_83FTHARN PROJCS['NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet',GEOGCS['GCS_North_American_1983_HARN',DATUM['D_North_American_1983_HARN',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Lambert_Conformal_Conic'],PARAMETER['False_Easting',1312333.333333333],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-77.0],PARAMETER['Standard_Parallel_1',38.3],PARAMETER['Standard_Parallel_2',39.45],PARAMETER['Latitude_Of_Origin',37.66666666666666],UNIT['Foot_US',0.3048006096012192]] WGS_1984_(ITRF00)_To_NAD_1983_HARN GEOGCS['GCS_WGS_1984',DATUM['D_WGS_1984',SPHEROID['WGS_1984',6378137.0,298.25722356]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]] Include in lineage when exporting metadata No

Distribution ▼►Distributor  ▼►Contact information  Individual's name Office of Geospatial Information Systems Organization's name Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) Contact's role  distributor

Contact information  ▼►Phone  Voice 202-366-DATA

Address  Type  Delivery point 1200 New Jersey Ave. SE City Washington Administrative area DC Postal code 20590 Country US e-mail address answers@bts.gov

Available format  Name Shapefile Version 2013 File decompression technique no compression applied

Ordering process  Instructions Call (202-366-DATA), or E-mail (answers@bts.gov) RITA/BTS to request the National Transportation Atlas Databases (NTAD) 2013 DVD. The NTAD DVD can be ordered from the online bookstore at www.bts.gov. Individual datasets from the NTAD can also be downloaded from the Office of Geospatial Information Systems website at http://www.bts.gov/programs/geographic_information_services/

Transfer options  Transfer size 6.645

Medium of distribution  Medium name  DVD

How data is written  iso9660 (CD-ROM) Recording density 650 Density units of measure Megabytes

Transfer options  Online source  Description  National Transportation Atlas Databases (NTAD) 2013

Distribution format  * Name Shapefile Version 2013

Transfer options  * Transfer size 0.047

Online source  Location http://www.bts.gov/programs/geographic_information_services/

Fields ▼►Details for object USDOT_RRCROSSINGS_MD ▼►* Type Feature Class * Row count 1749

Field FID ▼►* Alias FID * Data type OID * Width 4 * Precision 0 * Scale 0 * Field description Internal feature number.

* Description source ESRI

* Description of values Sequential unique whole numbers that are automatically generated.

Field Shape ▼►* Alias Shape * Data type Geometry * Width 0 * Precision 0 * Scale 0 * Field description Feature geometry.

* Description source ESRI

* Description of values Coordinates defining the features.

Field OBJECTID ▼►* Alias OBJECTID * Data type Integer * Width 9 * Precision 9 * Scale 0

Field CROSSING ▼►* Alias CROSSING * Data type String * Width 7 * Precision 0 * Scale 0 Field description US DOT Valid Crossing ID Number

Description source FRA

Field RAILROAD ▼►* Alias RAILROAD * Data type String * Width 4 * Precision 0 * Scale 0 Field description The

Abstract Urban geometry is one of the main factors influencing the development of urban heat islands. The study of urban geometry requires a characterization of urban canyons, which can be usually measured by the H/W ratio (a relationship between the height and the width of a street), a concept applied in a numerical model by Oke in 1981. The aim of this paper is to verify the impact of the canyon geometry on the intensity of the nocturnal urban heat islands. For this purpose, measurements of climate data and urban geometry were conducted in two Brazilian cities. The values of heat island intensity were cross-examined to those generated with the application of the original Oke's model. Therefore, this latter was calibrated and adapted to run in a GIS platform, allowing the incorporation of a geometric parameter other than the H/W ratio - the roughness length. Then, this process produced a new calculation tool, which is called THIS (Tool for Heat Island Simulation). The new model was applied to simulate some hypothetical urban scenarios representing several urban canyons types. The results showed that the urban canyons with the largest roughness reduce the nocturnal heat island intensities in relation to an urban canyon of the same H/W value, but presenting lower roughness rates instead.

The objective of this research project is to design, develop, and test a pilot collaborative environment between two Irrigation Districts and Reclamation within the Missouri Basin (MB Region). The collaborative environment will utilize ArcGIS Online, ArcGIS Pro, and Field Maps. Through robust testing, the design process, procedural standards, and lessons learned in the implementing stages will be documented and shared with all Regions. This catalog record contains the Final S&T Project Report describing the work done in the project, and two shapefiles with point and line geometry types depicting observation wells and canals obtained from field GPS data collection by Frenchman Cambridge Irrigation District.

This polygon layer contains the 1109 census blocks that make up the City of Cambridge for the 2010 Census.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription Complete type: Stringwidth: 1precision: 0

COUNTYFP10 type: Stringwidth: 3precision: 0

TRACTCE10 type: Stringwidth: 6precision: 0

FollowUp type: Textwidth: 1precision: 0

Comments type: Textwidth: 100precision: 0 Additional notes and or comments

TOTALPOP type: Doublewidth: 8precision: 38 Feature geometry.

BLOCKCE10 type: Textwidth: 4precision: 0

GEOID10 type: Textwidth: 15precision: 0

NAME10 type: Textwidth: 10precision: 0

MTFCC10 type: Textwidth: 5precision: 0

UR10 type: Textwidth: 1precision: 0

UACE10 type: Textwidth: 5precision: 0

FUNCSTAT10 type: Textwidth: 1precision: 0

ALAND10 type: Doublewidth: 8precision: 38

AWATER10 type: Doublewidth: 8precision: 38

INTPTLAT10 type: Textwidth: 11precision: 0

INTPTLON10 type: Textwidth: 12precision: 0

This historical dataset consists of a series of permanent 1-m^2 quadrats located on the sagebrush steppe in eastern Idaho, USA. The key aspect of the data is that during each growing season, all individual plants in each quadrat were identified and mapped. The combination of a long time-series with full spatial detail allows analyses of demographic processes and intra- and interspecific interactions among individual plants. This distribution contains the following data and data formats: 1) image files (*.tif) of the original, scanned maps; 2) the digitized maps in shapefile format; 3) a tabular version of the entire dataset (a table with no spatial information except an x,y coordinate for each individual plant record); 4) a species list, containing information on plant growth forms and shapefile geometry type; 5) quadrat information, such as grazing information and original quadrat names (the names as they appear in the original, scanned maps); 6) an inventory of the years each quadrat was sampled; 7) monthly precipitation, temperature, and snowfall records; and 8) counts of annuals in the quadrats.

This layer is a composite of five sublayers with adjacent scale ranges showing the broadband score across the U.S. and outlying areas, at five different geographies – State, County, Tract, Block Group and Block. The broadband score is an index based on the FCC’s minimum standard of broadband of 25 megabits per second (Mbps) download and 3 Mbps upload. A geography with speeds of 25/3 Mbps is awarded 100 points. Each type of geometry contains housing, population, and internet usage data taken from the following sources:US Census Bureau 2010 Census data (2010)USDA Non-Rural Areas (2013)FCC Form 477 Fixed Broadband Deployment Data (January - June 2020)FCC Population, Housing Unit, and Household Estimates (2019). Note that these are derived from Census and other data.BroadbandNow Average Minimum Terrestrial Broadband Plan Prices (2020)Measurement Lab (Jan - Jun 2020)Broadband offering data from each provider for Census Blocks are in a related table Field Names / Record StructureThis layer includes over 150 attributes relating to reported speed and service information. In addition:Each block includes housing unit, household, and population estimates from the FCC.Each block has an attribute named WaterOnly that indicates if it is entirely water (yes/no).Each block has two attributes indicating whether it is urban or rural (CensusUrbanRural and USDAUrbanRural). For units larger than blocks, block count (urban/rural) was used to determine this. Some tracts and block groups have an equal number of urban and rural blocks—so a new coded value was introduced: S (split). All blocks are either U or R, while tracts and block groups can be U, R, or S.Each block has three attributes indicating whether it is part of a Tribal Block Group, is part of an American Indian/Alaska Native/Native Hawaiian Area (AIANNHA) and the AIANNHA name.US Census and USDA Rurality valuesAmalgamated broadband speed measurement categories based on Form 477. These include:99: All Terrestrial Broadband Plus Satellite98: All Terrestrial Broadband97: Cable Modem96: DSL95: All Other (Electric Power Line, Other Copper Wireline, Other)The FCC Speed Values method is applied to all speeds from all data sources within this service. This includes:Geography: State, County, Tract, Block Group, Block,

This historical dataset consists of a series of permanent 1-m^2 quadrats located on the sagebrush steppe in eastern Idaho, USA. The key aspect of the data is that during each growing season, all individual plants in each quadrat were identified and mapped. The combination of a long time-series with full spatial detail allows analyses of demographic processes and intra- and interspecific interactions among individual plants. This distribution contains the following data and data formats: 1) image files (*.tif) of the original, scanned maps; 2) the digitized maps in shapefile format; 4) a tabular version of the entire dataset (a table with no spatial information except an x,y coordinate for each individual plant record); 5) a species list, containing information on plant growth forms and shapefile geometry type; 6) quadrat information, such as grazing information and original quadrat names (the names as they appear in the original, scanned maps); 7) an inventory of the years each quadrat was sampled; 8) monthly precipitation, temperature, and snowfall records; and 9) counts of annuals in the quadrats.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

This Polygon layer contains the boundaries of the five United States Postal Service (USPS) ZIP code areas in the city of Cambridge.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription ZIP_CODE type: Stringwidth: 32precision: 0 5-digit ZIP code

SHAPE type: Stringwidth: 255precision: 0 Feature geometry.

Shape type: Stringwidth: 255precision: 0 Feature geometry.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)