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.

Table related to ADDRESS_POINT that decodes SITETYPE item. SITETYPE item values are somewhat cryptic and this table clarifies the codes. For SDW GDB users, this table is converted to a coded-value domain and associated with this item so the decodes are seamless. Shapefile users of ADDRESS.shp can use the table directly as a look-up table or can join the tables.

The GIS shapefile and summary table provide irrigated agricultural land-use for Hardee County, Florida through a cooperative project between the U.S Geological Survey (USGS) and the Florida Department of Agriculture and Consumer Services (FDACS), Office of Agricultural Water Policy. Information provided in the shapefile includes the location of irrigated land field-verified between November 2017 and September 2018, crop type, irrigation system type, and primary water source used in Hardee County, Florida. A map in pdf format is provided to illustrate shapefile information for the county.

DHSVM configurations require spatial information for each point included as an input time series: elevation (m), latitude (m; UTM), longitude (m, UTM). The steps required to calculate this information are outlined in this HydroShare resource which includes sample scripts to export the point shapefile table from ArcGIS, calculate the UTM values, generate tables of latitude, longitude, and elevation, and convert the tables into DHSVM text format in a list for the model configuration file. The point shapefiles for the 8 Chehalis subbasins are also compressed and available in this resource.

To run the model, the input file lists each grid cell in the following format (example for 1 point in a list).
Station Name 1 = data_46.53125_-123.28125 North Coordinate 1 = 5153114.279000 East Coordinate 1 = 478431.528300 Elevation 1 = 290 Station File 1 = /civil/shared/ecohydrology/christina/forcs_dhsvm/data_46.53125_-123.28125

Table related to ADDRESS_POINT that decodes SITETYPE item. SITETYPE item values are somewhat cryptic and this table clarifies the codes. For SDW GDB users, this table is converted to a coded-value domain and associated with this item so the decodes are seamless. Shapefile users of ADDRESS.shp can use the table directly as a look-up table or can join the tables.

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)

description: The Digital Geologic Map of the Island of Hawaii is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcMap 9.1 layer (.LYR) files. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.4. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.1 personal geodatabase (havo_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 5N. That data is within the area of interest of Hawaii Volcanoes National Park.; abstract: The Digital Geologic Map of the Island of Hawaii is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcMap 9.1 layer (.LYR) files. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.4. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.1 personal geodatabase (havo_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 5N. That data is within the area of interest of Hawaii Volcanoes National Park.

description: The Digital Geologic Map of Hubbell Trading Post National Historic Site and Vicinity, Arizona is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcMap 9.1 layer (.LYR) files. The data were completed as a component of the Geologic Resource Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.4. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.1 personal geodatabase (hutr_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 12N. That data is within the area of interest of Hubbell Trading Post National Historic Site.; abstract: The Digital Geologic Map of Hubbell Trading Post National Historic Site and Vicinity, Arizona is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcMap 9.1 layer (.LYR) files. The data were completed as a component of the Geologic Resource Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.4. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.1 personal geodatabase (hutr_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 12N. That data is within the area of interest of Hubbell Trading Post National Historic Site.

description: The Digital Geologic Map (Surficial Map) of the Mount Hancock Quadrangle, Yellowstone National Park and adjoining area, Wyoming is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcMap 9.1 layer (.LYR) files. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.4. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.1 personal geodatabase (mtha_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 12N. That data is within the area of interest of Yellowstone National Park.; abstract: The Digital Geologic Map (Surficial Map) of the Mount Hancock Quadrangle, Yellowstone National Park and adjoining area, Wyoming is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcMap 9.1 layer (.LYR) files. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.4. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.1 personal geodatabase (mtha_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 12N. That data is within the area of interest of Yellowstone National Park.

description: The Digital Geologic Map of the Fort Laramie Area, Wyoming is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcView 3.X legend (.AVL) files. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GIS-Geology Coverage/Shapefile Data Model (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 13N. That data is within the area of interest of Fort Laramie National Historic Site.; abstract: The Digital Geologic Map of the Fort Laramie Area, Wyoming is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcView 3.X legend (.AVL) files. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GIS-Geology Coverage/Shapefile Data Model (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 13N. That data is within the area of interest of Fort Laramie National Historic Site.

description: The Digital Geologic Map of Theodore Roosevelt National Park, North Dakota is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcView 3.X legend (.AVL) files. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GIS-Geology Coverage/Shapefile Data Model (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 13N. That data is within the area of interest of Theodore Roosevelt National Park.; abstract: The Digital Geologic Map of Theodore Roosevelt National Park, North Dakota is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcView 3.X legend (.AVL) files. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GIS-Geology Coverage/Shapefile Data Model (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 13N. That data is within the area of interest of Theodore Roosevelt National Park.

description: The Digital Geologic Map (Surficial Map) of the Norris Junction Quadrangle, Yellowstone National Park, Wyoming is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcMap 9.1 layer (.LYR) files. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.4. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.1 personal geodatabase (nrju_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 12N. That data is within the area of interest of Yellowstone National Park.; abstract: The Digital Geologic Map (Surficial Map) of the Norris Junction Quadrangle, Yellowstone National Park, Wyoming is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcMap 9.1 layer (.LYR) files. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.4. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.1 personal geodatabase (nrju_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 12N. That data is within the area of interest of Yellowstone National Park.

The South Florida Water Management District (SFWMD) and the U.S. Geological Survey have developed projected future change factors for precipitation depth-duration-frequency (DDF) curves at 174 NOAA Atlas 14 stations in central and south Florida. The change factors were computed as the ratio of projected future to historical extreme precipitation depths fitted to extreme precipitation data from various downscaled climate datasets using a constrained maximum likelihood (CML) approach. The change factors correspond to the period 2050-2089 (centered in the year 2070) as compared to the 1966-2005 historical period. Geospatial data provided in an ArcGIS shapefile are described herein. The shapefile shows the locations of NOAA Atlas 14 stations in central and south Florida for which depth-duration-frequency curves and change factors of precipitation depths were developed as part of this project. For more information about the stations, see Table 1 of Datasets_station_information.xlsx.