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 dataset is a compilation of available oil and gas pipeline data and is maintained by BSEE. Pipelines are used to transport and monitor oil and/or gas from wells within the outer continental shelf (OCS) to resource collection locations. Currently, pipelines managed by BSEE are found in Gulf of Mexico and southern California waters.

© MarineCadastre.gov This layer is a component of BOEMRE Layers.

This Map Service contains many of the primary data types created by both the Bureau of Ocean Energy Management (BOEM) and the Bureau of Safety and Environmental Enforcement (BSEE) within the Department of Interior (DOI) for the purpose of managing offshore federal real estate leases for oil, gas, minerals, renewable energy, sand and gravel. These data layers are being made available as REST mapping services for the purpose of web viewing and map overlay viewing in GIS systems. Due to re-projection issues which occur when converting multiple UTM zone data to a single national or regional projected space, and line type changes that occur when converting from UTM to geographic projections, these data layers should not be used for official or legal purposes. Only the original data found within BOEM/BSEE’s official internal database, federal register notices or official paper or pdf map products may be considered as the official information or mapping products used by BOEM or BSEE. A variety of data layers are represented within this REST service are described further below. These and other cadastre information the BOEM and BSEE produces are generated in accordance with 30 Code of Federal Regulations (CFR) 256.8 to support Federal land ownership and mineral resource management.

For more information – Contact: Branch Chief, Mapping and Boundary Branch, BOEM, 381 Elden Street, Herndon, VA 20170. Telephone (703) 787-1312; Email: mapping.boundary.branch@boem.gov

The REST services for National Level Data can be found here: http://gis.boemre.gov/arcgis/rest/services/BOEM_BSEE/MMC_Layers/MapServer

REST services for regional level data can be found by clicking on the region of interest from the following URL: http://gis.boemre.gov/arcgis/rest/services/BOEM_BSEE

Individual Regional Data or in depth metadata for download can be obtained in ESRI Shape file format by clicking on the region of interest from the following URL: http://www.boem.gov/Oil-and-Gas-Energy-Program/Mapping-and-Data/Index.aspx

Currently the following layers are available from this REST location:

OCS Drilling Platforms -Locations of structures at and beneath the water surface used for the purpose of exploration and resource extraction. Only platforms in federal Outer Continental Shelf (OCS) waters are included. A database of platforms and rigs is maintained by BSEE.

OCS Oil and Natural Gas Wells -Existing wells drilled for exploration or extraction of oil and/or gas products. Additional information includes the lease number, well name, spud date, the well class, surface area/block number, and statistics on well status summary. Only wells found in federal Outer Continental Shelf (OCS) waters are included. Wells information is updated daily. Additional files are available on well completions and well tests. A database of wells is maintained by BSEE.

OCS Oil & Gas Pipelines -This dataset is a compilation of available oil and gas pipeline data and is maintained by BSEE. Pipelines are used to transport and monitor oil and/or gas from wells within the outer continental shelf (OCS) to resource collection locations. Currently, pipelines managed by BSEE are found in Gulf of Mexico and southern California waters.

Unofficial State Lateral Boundaries - The approximate location of the boundary between two states seaward of the coastline and terminating at the Submerged Lands Act Boundary. Because most State boundary locations have not been officially described beyond the coast, are disputed between states or in some cases the coastal land boundary description is not available, these lines serve as an approximation that was used to determine a starting point for creation of BOEM’s OCS Administrative Boundaries. GIS files are not available for this layer due to its unofficial status.

BOEM OCS Administrative Boundaries - Outer Continental Shelf (OCS) Administrative Boundaries Extending from the Submerged Lands Act Boundary seaward to the Limit of the United States OCS (The U.S. 200 nautical mile Limit, or other marine boundary)For additional details please see the January 3, 2006 Federal Register Notice.

BOEM Limit of OCSLA ‘8(g)’ zone - The Outer Continental Shelf Lands Act '8(g) Zone' lies between the Submerged Lands Act (SLA) boundary line and a line projected 3 nautical miles seaward of the SLA boundary line. Within this zone, oil and gas revenues are shared with the coastal state(s). The official version of the ‘8(g)’ Boundaries can only be found on the BOEM Official Protraction Diagrams (OPDs) or Supplemental Official Protraction described below.

Submerged Lands Act Boundary - The SLA boundary defines the seaward limit of a state's submerged lands and the landward boundary of federally managed OCS lands. The official version of the SLA Boundaries can only be found on the BOEM Official Protraction Diagrams (OPDs) or Supplemental Official Protraction Diagrams described below.

Atlantic Wildlife Survey Tracklines(2005-2012) - These data depict tracklines of wildlife surveys conducted in the Mid-Atlantic region since 2005. The tracklines are comprised of aerial and shipboard surveys. These data are intended to be used as a working compendium to inform the diverse number of groups that conduct surveys in the Mid-Atlantic region.The tracklines as depicted in this dataset have been derived from source tracklines and transects. The tracklines have been simplified (modified from their original form) due to the large size of the Mid-Atlantic region and the limited ability to map all areas simultaneously.The tracklines are to be used as a general reference and should not be considered definitive or authoritative. This data can be downloaded from http://www.boem.gov/uploadedFiles/BOEM/Renewable_Energy_Program/Mapping_and_Data/ATL_WILDLIFE_SURVEYS.zip

BOEM OCS Protraction Diagrams & Leasing Maps - This data set contains a national scale spatial footprint of the outer boundaries of the Bureau of Ocean Energy Management’s (BOEM’s) Official Protraction Diagrams (OPDs) and Leasing Maps (LMs). It is updated as needed. OPDs and LMs are mapping products produced and used by the BOEM to delimit areas available for potential offshore mineral leases, determine the State/Federal offshore boundaries, and determine the limits of revenue sharing and other boundaries to be considered for leasing offshore waters. This dataset shows only the outline of the maps that are available from BOEM.Only the most recently published paper or pdf versions of the OPDs or LMs should be used for official or legal purposes. The pdf maps can be found by going to the following link and selecting the appropriate region of interest. http://www.boem.gov/Oil-and-Gas-Energy-Program/Mapping-and-Data/Index.aspx Both OPDs and LMs are further subdivided into individual Outer Continental Shelf(OCS) blocks which are available as a separate layer. Some OCS blocks that also contain other boundary information are known as Supplemental Official Block Diagrams (SOBDs.) Further information on the historic development of OPD's can be found in OCS Report MMS 99-0006: Boundary Development on the Outer Continental Shelf: http://www.boemre.gov/itd/pubs/1999/99-0006.PDF Also see the metadata for each of the individual GIS data layers available for download. The Official Protraction Diagrams (OPDs) and Supplemental Official Block Diagrams (SOBDs), serve as the legal definition for BOEM offshore boundary coordinates and area descriptions.

BOEM OCS Lease Blocks - Outer Continental Shelf (OCS) lease blocks serve as the legal definition for BOEM offshore boundary coordinates used to define small geographic areas within an Official Protraction Diagram (OPD) for leasing and administrative purposes. OCS blocks relate back to individual Official Protraction Diagrams and are not uniquely numbered. Only the most recently published paper or pdf

GIS data files with metadata used to calculate the changes in surface area over a 120 ka period in 10 ka time bins on the volcanically active island of Terceira (Azores). We took into account changes in sea level and subsidence during the analyses, and we did all analyses in ESRI ArcGIS 10.2.2 desktop software in WGS_1984_UTM_Zone_26N Transverse Mercator projection which resulted in minimal area distorations (

The geographic data are built from the Technical Information Management System (TIMS). TIMS consists of two separate databases: an attribute database and a spatial database. The attribute information for offshore activities is stored in the TIMS database. The spatial database is a combination of the ARC/INFO and FINDER databases and contains all the coordinates and topology information for geographic features. The attribute and spatial databases are interconnected through the use of common data elements in both databases, thereby creating the spatial datasets. The data in the mapping files are made up of straight-line segments. If an arc existed in the original data, it has been replaced with a series of straight lines that approximate the arc. The Gulf of America OCS Region stores all its mapping data in longitude and latitude format. All coordinates are in NAD 27. Data can be obtained in three types of digital formats: INTERACTIVE MAP: The ArcGIS web maps are an interactive display of geographic information, containing a basemap, a set of data layers (many of which include interactive pop-up windows with information about the data), an extent, navigation tools to pan and zoom, and additional tools for geospatial analysis. SHP: A Shapefile is a digital vector (non-topological) storage format for storing geometric location and associated attribute information. Shapefiles can support point, line, and area features with attributes held in a dBASE format file. GEODATABASE: An ArcGIS geodatabase is a collection of geographic datasets of various types held in a common file system folder, a Microsoft Access database, or a multiuser relational DBMS (such as Oracle, Microsoft SQL Server, PostgreSQL, Informix, or IBM DB2). The geodatabase is the native data structure for ArcGIS and is the primary data format used for editing and data management.

A major objective of plant ecology research is to determine the underlying processes responsible for the observed spatial distribution patterns of plant species. Plants can be approximated as points in space for this purpose, and thus, spatial point pattern analysis has become increasingly popular in ecological research. The basic piece of data for point pattern analysis is a point location of an ecological object in some study region. Therefore, point pattern analysis can only be performed if data can be collected. However, due to the lack of a convenient sampling method, a few previous studies have used point pattern analysis to examine the spatial patterns of grassland species. This is unfortunate because being able to explore point patterns in grassland systems has widespread implications for population dynamics, community-level patterns and ecological processes. In this study, we develop a new method to measure individual coordinates of species in grassland communities. This method records plant growing positions via digital picture samples that have been sub-blocked within a geographical information system (GIS). Here, we tested out the new method by measuring the individual coordinates of Stipa grandis in grazed and ungrazed S. grandis communities in a temperate steppe ecosystem in China. Furthermore, we analyzed the pattern of S. grandis by using the pair correlation function g(r) with both a homogeneous Poisson process and a heterogeneous Poisson process. Our results showed that individuals of S. grandis were overdispersed according to the homogeneous Poisson process at 0-0.16 m in the ungrazed community, while they were clustered at 0.19 m according to the homogeneous and heterogeneous Poisson processes in the grazed community. These results suggest that competitive interactions dominated the ungrazed community, while facilitative interactions dominated the grazed community. In sum, we successfully executed a new sampling method, using digital photography and a Geographical Information System, to collect experimental data on the spatial point patterns for the populations in this grassland community.

Methods 1. Data collection using digital photographs and GIS

A flat 5 m x 5 m sampling block was chosen in a study grassland community and divided with bamboo chopsticks into 100 sub-blocks of 50 cm x 50 cm (Fig. 1). A digital camera was then mounted to a telescoping stake and positioned in the center of each sub-block to photograph vegetation within a 0.25 m2 area. Pictures were taken 1.75 m above the ground at an approximate downward angle of 90° (Fig. 2). Automatic camera settings were used for focus, lighting and shutter speed. After photographing the plot as a whole, photographs were taken of each individual plant in each sub-block. In order to identify each individual plant from the digital images, each plant was uniquely marked before the pictures were taken (Fig. 2 B).

Digital images were imported into a computer as JPEG files, and the position of each plant in the pictures was determined using GIS. This involved four steps: 1) A reference frame (Fig. 3) was established using R2V software to designate control points, or the four vertexes of each sub-block (Appendix S1), so that all plants in each sub-block were within the same reference frame. The parallax and optical distortion in the raster images was then geometrically corrected based on these selected control points; 2) Maps, or layers in GIS terminology, were set up for each species as PROJECT files (Appendix S2), and all individuals in each sub-block were digitized using R2V software (Appendix S3). For accuracy, the digitization of plant individual locations was performed manually; 3) Each plant species layer was exported from a PROJECT file to a SHAPE file in R2V software (Appendix S4); 4) Finally each species layer was opened in Arc GIS software in the SHAPE file format, and attribute data from each species layer was exported into Arc GIS to obtain the precise coordinates for each species. This last phase involved four steps of its own, from adding the data (Appendix S5), to opening the attribute table (Appendix S6), to adding new x and y coordinate fields (Appendix S7) and to obtaining the x and y coordinates and filling in the new fields (Appendix S8).

1. Data reliability assessment

To determine the accuracy of our new method, we measured the individual locations of Leymus chinensis, a perennial rhizome grass, in representative community blocks 5 m x 5 m in size in typical steppe habitat in the Inner Mongolia Autonomous Region of China in July 2010 (Fig. 4 A). As our standard for comparison, we used a ruler to measure the individual coordinates of L. chinensis. We tested for significant differences between (1) the coordinates of L. chinensis, as measured with our new method and with the ruler, and (2) the pair correlation function g of L. chinensis, as measured with our new method and with the ruler (see section 3.2 Data Analysis). If (1) the coordinates of L. chinensis, as measured with our new method and with the ruler, and (2) the pair correlation function g of L. chinensis, as measured with our new method and with the ruler, did not differ significantly, then we could conclude that our new method of measuring the coordinates of L. chinensis was reliable.

We compared the results using a t-test (Table 1). We found no significant differences in either (1) the coordinates of L. chinensis or (2) the pair correlation function g of L. chinensis. Further, we compared the pattern characteristics of L. chinensis when measured by our new method against the ruler measurements using a null model. We found that the two pattern characteristics of L. chinensis did not differ significantly based on the homogenous Poisson process or complete spatial randomness (Fig. 4 B). Thus, we concluded that the data obtained using our new method was reliable enough to perform point pattern analysis with a null model in grassland communities.

The USDA Long-Term Agroecosystem Research was established to develop national strategies for sustainable intensification of agricultural production. As part of the Agricultural Research Service, the LTAR Network incorporates numerous geographies consisting of experimental areas and locations where data are being gathered. Starting in early 2019, two working groups of the LTAR Network (Remote Sensing and GIS, and Data Management) set a major goal to jointly develop a geodatabase of LTAR Standard GIS Data Layers. The purpose of the geodatabase was to enhance the Network's ability to utilize coordinated, harmonized datasets and reduce redundancy and potential errors associated with multiple copies of similar datasets. Project organizers met at least twice with each of the 18 LTAR sites from September 2019 through December 2020, compiling and editing a set of detailed geospatial data layers comprising a geodatabase, describing essential data collection areas within the LTAR Network. The LTAR Standard GIS Data Layers geodatabase consists of geospatial data that represent locations and areas associated with the LTAR Network as of late 2020, including LTAR site locations, addresses, experimental plots, fields and watersheds, eddy flux towers, and phenocams. There are six data layers in the geodatabase available to the public. This geodatabase was created in 2019-2020 by the LTAR network as a national collaborative effort among working groups and LTAR sites. The creation of the geodatabase began with initial requests to LTAR site leads and data managers for geospatial data, followed by meetings with each LTAR site to review the initial draft. Edits were documented, and the final draft was again reviewed and certified by LTAR site leads or their delegates. Revisions to this geodatabase will occur biennially, with the next revision scheduled to be published in 2023. Resources in this dataset:Resource Title: LTAR Standard GIS Data Layers, 2020 version, File Geodatabase. File Name: LTAR_Standard_GIS_Layers_v2020.zipResource Description: This file geodatabase consists of authoritative GIS data layers of the Long-Term Agroecosystem Research Network. Data layers include: LTAR site locations, LTAR site points of contact and street addresses, LTAR experimental boundaries, LTAR site "legacy region" boundaries, LTAR eddy flux tower locations, and LTAR phenocam locations.Resource Software Recommended: ArcGIS,url: esri.com Resource Title: LTAR Standard GIS Data Layers, 2020 version, GeoJSON files. File Name: LTAR_Standard_GIS_Layers_v2020_GeoJSON_ADC.zipResource Description: The contents of the LTAR Standard GIS Data Layers includes geospatial data that represent locations and areas associated with the LTAR Network as of late 2020. This collection of geojson files includes spatial data describing LTAR site locations, addresses, experimental plots, fields and watersheds, eddy flux towers, and phenocams. There are six data layers in the geodatabase available to the public. This dataset was created in 2019-2020 by the LTAR network as a national collaborative effort among working groups and LTAR sites. Resource Software Recommended: QGIS,url: https://qgis.org/en/site/

Urban Tree Canopy Assessment. This was created using the Urban Tree Canopy Syracuse 2010 (All Layers) file HERE.The data for this map was created using LIDAR and other spatial analysis tools to identify and measure tree canopy in the landscape. This was a collaboration between the US Forest Service Northern Research Station (USFS), the University of Vermont Spatial Laboratory, and SUNY ESF. Because the full map is too large to be viewed in ArcGIS Online, this has been reduced to a vector tile layer to allow it to be viewed online. To download and view the shapefiles and all of the layers, you can download the data HERE and view this in either ArcGIS Pro or QGIS.Data DictionaryDescription source  USDA Forest ServiceList of values  Value 1 Description Tree CanopyValue 2 Description Grass/ShrubValue 3 Description Bare SoilValue 4 Description WaterValue 5 Description BuildingsValue 6 Description Roads/RailroadsValue 7 Description Other PavedField Class Alias Class Data type String Width 20Geometric objects  Feature class name landcover_2010_syracusecity Object type  complex Object count 7ArcGIS Feature Class Properties Feature class name landcover_2010_syracusecity Feature type  Simple Geometry type Polygon Has topology FALSE Feature count 7 Spatial index TRUE Linear referencing  FALSEDistributionAvailable format  Name ShapefileTransfer options  Transfer size 163.805Description Downloadable DataFieldsDetails for object landcover_2010_syracusecityType Feature Class Row count  7 Definition  UTCField FIDAlias FID Data type OID Width  4 Precision 0 Scale 0Field descriptionInternal feature number.Description source ESRIDescription of valueSequential unique whole numbers that are automatically generated.Field ShapeAlias Shape Data type Geometry Width 0 Precision 0 Scale 0Field description Feature geometry.Description source  ESRIDescription of values Coordinates defining the features.Field CodeAlias Code Data type Number Width 4Overview Description  Metadata DetailsMetadata language  English Metadata character set utf8 - 8 bit UCS Transfer FormatScope of the data described by the metadata  dataset Scope name  datasetLast update 2011-06-02ArcGIS metadata properties Metadata format ArcGIS 1.0 Metadata style North American Profile of ISO19115 2003Created in ArcGIS for the item 2011-06-02 16:48:35 Last modified in ArcGIS for the item 2011-06-02 16:44:43Automatic updates Have been performed Yes Last update 2011-06-02 16:44:43Item location history  Item copied or moved 2011-06-02 16:48:35 From T:\TestSites\NY\Syracuse\Temp\landcover_2010_syracusecity To \T7500\F$\Export\LandCover_2010_SyracuseCity\landcover_2010_syracusecity

File List bathymetry_30s.7z (MD5: dd855211bbcdee7d6862414da23d6da2) biogeo01_07_30s.7z (MD5: 396525db0abd9de2ede3d8fdeb15e8ee) biogeo08_17_30s.7z (MD5: 96c2417eed84e85f9896536b934c53e1) Monthly_Variables_30s.7z (MD5: 89016a8d17e8d8a1dddef0a121a83f5d)

     Additional high resolution raster files:

Sea_Ice_30s.7z (MD5: 547d355294c530f63b9b0a73dedd2f3a)

     Low resolution MARSPEC data files:

MARSPEC_2o5m.7z (MD5: 923c97d185adb0c72f158a84e2981391) MARSPEC_5m.7z (MD5: 95f7c3739c4f2889c2eff18afeffa489) MARSPEC_10m.7z (MD5: d91f3127f46f7004d116f14328bf4b71) Description Ecological niche models are widely used in terrestrial studies to address critical ecological and evolutionary questions related to past and future climate change, local adaptation and speciation, the discovery of rare endemics, and biological invasions. However the application of niche models to similar questions in marine ecosystems has lagged behind, in part due to the lack of a centralized high-resolution spatial data set representing both benthic and pelagic marine environments. Here we describe the creation of MARSPEC, a high-resolution GIS database of ocean climate layers intended for marine ecological niche modeling and other applications in marine spatial ecology. MARSPEC combines information related to topographic complexity of the seafloor with bioclimatic measures of sea surface temperature and salinity for the world ocean. We derived seven geophysical variables from a high-resolution raster grid representing depth of the seafloor (bathymetry) to characterize six facets of topographic complexity (east-west and north-south components of aspect, slope, concavity of the seafloor, and plan and profile curvature) and distance from shore. We further derived 10 bioclimatic variables describing the annual mean, range, variance and extreme values for temperature and salinity from long-term monthly climatological means obtained from remotely sensed and in situ oceanographic observations. All variables were clipped to a common land mask, interpolated to a nominal 1-km (30 arc-second) grid, and converted to an ESRI raster grid file format compatible with popular GIS programs. MARSPEC is a 10-fold improvement in spatial resolution over the next-best data set (Bio-ORACLE) and is the only high-resolution global marine data set to combine variables from the benthic and pelagic environments into a single database. Additionally, we provide the monthly climatological layers used to derive the bioclimatic variables, allowing users to calculate equivalent MARSPEC variables from anomaly data for past and future climate scenarios. A detailed description of GIS processing steps required to calculate the MARSPEC variables can be found in the metadata.

      Key words: climate change; ecological niche modeling; GIS; marine spatial ecology; ocean climate; salinity; sea surface temperature; species distribution modeling.

This is a GIS file set of the Gede ruins. The data was generated from laser scans, photogrammetric techniques and GPS data. The data maps the site of the Gede ruins in Kilifi County in Kenya. All data is in either the unprojected Geographic (GCS WGS84) or the projected Universal Transverse Mercator 37 South (UTM37S WGS84) coordinate system.The data is packaged as an ESRI Map Package (.mpk). If you are not an ESRI user and wish to unpack the package please rename the file extension to .zip and use a programme, such as 7-Zip, to unpack the package. The package contains shapefiles and images which are compatible with most GIS software. The ruins of Gede (also Gedi), a traditional Arab-African Swahili town, are located just off Kenya’s coastline, some 90km north of Mombasa. Gede was a small town built entirely from stones and rocks, and most of the original foundations are still visible today. Remaining structures at the site include coral stone buildings, mosques, houses and a palace. The town was abandoned in the early 17th century, and Gede’s buildings date back to the 15th century, although it is believed that the site could have been inhabited as early as the 11th or 12th century. The Zamani Project spatially documented the Gede ruins in 2010. In addition to the three principal structures of the Great Mosque, the Small Mosque and the Palace, remains of other structures in the immediate vicinity were also documented.The Zamani Project seeks to increase awareness and knowledge of tangible cultural heritage in Africa and internationally by creating metrically accurate digital representations of historical sites. Digital spatial data of cultural heritage sites can be used for research and education, for restoration and conservation and as a record for future generations. The Zamani Project operates as a non-profit organisation within the University of Cape Town.This text has been adapted from the UNESCO website (https://whc.unesco.org/en/tentativelists/5501/).The Zamani Project received funding from the Andrew W Mellon Foundation at the time of the project.

This dataset is a modified version of the FWS developed data depicting “Highly Important Landscapes”, as outlined in Memorandum FWS/AES/058711 and provided to the Wildlife Habitat Spatial analysis Lab on October 29th 2014. Other names and acronyms used to refer to this dataset have included: Areas of Significance (AoSs - name of GIS data set provided by FWS), Strongholds (FWS), and Sagebrush Focal Areas (SFAs - BLM). The BLM will refer to these data as Sagebrush Focal Areas (SFAs). Data were provided as a series of ArcGIS map packages which, when extracted, contained several datasets each. Based on the recommendation of the FWS Geographer/Ecologist (email communication, see data originator for contact information) the dataset called “Outiline_AreasofSignificance” was utilized as the source for subsequent analysis and refinement. Metadata was not provided by the FWS for this dataset. For detailed information regarding the dataset’s creation refer to Memorandum FWS/AES/058711 or contact the FWS directly. Several operations and modifications were made to this source data, as outlined in the “Description” and “Process Step” sections of this metadata file. Generally: The source data was named by the Wildlife Habitat Spatial Analysis Lab to identify polygons as described (but not identified in the GIS) in the FWS memorandum. The Nevada/California EIS modified portions within their decision space in concert with local FWS personnel and provided the modified data back to the Wildlife Habitat Spatial Analysis Lab. Gaps around Nevada State borders, introduced by the NVCA edits, were then closed as was a large gap between the southern Idaho & southeast Oregon present in the original dataset. Features with an area below 40 acres were then identified and, based on FWS guidance, either removed or retained. Finally, guidance from BLM WO resulted in the removal of additional areas, primarily non-habitat with BLM surface or subsurface management authority. Data were then provided to each EIS for use in FEIS development. Based on guidance from WO, SFAs were to be limited to BLM decision space (surface/sub-surface management areas) within PHMA. Each EIS was asked to provide the limited SFA dataset back to the National Operations Center to ensure consistent representation and analysis. Returned SFA data, modified by each individual EIS, was then consolidated at the BLM’s National Operations Center retaining the three standardized fields contained in this dataset.Several Modifications from the original FWS dataset have been made. Below is a summary of each modification.1. The data as received from FWS: 16,514,163 acres & 1 record.2. Edited to name SFAs by Wildlife Habitat Spatial Analysis Lab:Upon receipt of the “Outiline_AreasofSignificance” dataset from the FWS, a copy was made and the one existing & unnamed record was exploded in an edit session within ArcMap. A text field, “AoS_Name”, was added. Using the maps provided with Memorandum FWS/AES/058711, polygons were manually selected and the “AoS_Name” field was calculated to match the names as illustrated. Once all polygons in the exploded dataset were appropriately named, the dataset was dissolved, resulting in one record representing each of the seven SFAs identified in the memorandum.3. The NVCA EIS made modifications in concert with local FWS staff. Metadata and detailed change descriptions were not returned with the modified data. Contact Leisa Wesch, GIS Specialist, BLM Nevada State Office, 775-861-6421, lwesch@blm.gov, for details.4. Once the data was returned to the Wildlife Habitat Spatial Analysis Lab from the NVCA EIS, gaps surrounding the State of NV were closed. These gaps were introduced by the NVCA edits, exacerbated by them, or existed in the data as provided by the FWS. The gap closing was performed in an edit session by either extending each polygon towards each other or by creating a new polygon, which covered the gap, and merging it with the existing features. In addition to the gaps around state boundaries, a large area between the S. Idaho and S.E. Oregon SFAs was filled in. To accomplish this, ADPP habitat (current as of January 2015) and BLM GSSP SMA data were used to create a new polygon representing PHMA and BLM management that connected the two existing SFAs.5. In an effort to simplify the FWS dataset, features whose areas were less than 40 acres were identified and FWS was consulted for guidance on possible removal. To do so, features from #4 above were exploded once again in an ArcMap edit session. Features whose areas were less than forty acres were selected and exported (770 total features). This dataset was provided to the FWS and then returned with specific guidance on inclusion/exclusion via email by Lara Juliusson (lara_juliusson@fws.gov). The specific guidance was:a. Remove all features whose area is less than 10 acresb. Remove features identified as slivers (the thinness ratio was calculated and slivers identified by Lara Juliusson according to https://tereshenkov.wordpress.com/2014/04/08/fighting-sliver-polygons-in-arcgis-thinness-ratio/) and whose area was less than 20 acres.c. Remove features with areas less than 20 acres NOT identified as slivers and NOT adjacent to other features.d. Keep the remainder of features identified as less than 40 acres.To accomplish “a” and “b”, above, a simple selection was applied to the dataset representing features less than 40 acres. The select by location tool was used, set to select identical, to select these features from the dataset created in step 4 above. The records count was confirmed as matching between the two data sets and then these features were deleted. To accomplish “c” above, a field (“AdjacentSH”, added by FWS but not calculated) was calculated to identify features touching or intersecting other features. A series of selections was used: first to select records 6. Based on direction from the BLM Washington Office, the portion of the Upper Missouri River Breaks National Monument (UMRBNM) that was included in the FWS SFA dataset was removed. The BLM NOC GSSP NLCS dataset was used to erase these areas from #5 above. Resulting sliver polygons were also removed and geometry was repaired.7. In addition to removing UMRBNM, the BLM Washington Office also directed the removal of Non-ADPP habitat within the SFAs, on BLM managed lands, falling outside of Designated Wilderness’ & Wilderness Study Areas. An exception was the retention of the Donkey Hills ACEC and adjacent BLM lands. The BLM NOC GSSP NLCS datasets were used in conjunction with a dataset containing all ADPP habitat, BLM SMA and BLM sub-surface management unioned into one file to identify and delete these areas.8. The resulting dataset, after steps 2 – 8 above were completed, was dissolved to the SFA name field yielding this feature class with one record per SFA area.9. Data were provided to each EIS for use in FEIS allocation decision data development.10. Data were subset to BLM decision space (surface/sub-surface) within PHMA by each EIS and returned to the NOC.11. Due to variations in field names and values, three standardized fields were created and calculated by the NOC:a. SFA Name – The name of the SFA.b. Subsurface – Binary “Yes” or “No” to indicated federal subsurface estate.c. SMA – Represents BLM, USFS, other federal and non-federal surface management 12. The consolidated data (with standardized field names and values) were dissolved on the three fields illustrated above and geometry was repaired, resulting in this dataset.

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"

Polygon dataset characterizing bottom type designations determined by Md DNR's Acoustic Bay Bottom Survey conducted from 1974 to 1983. Bottom type designations include cultch, mud, sand, leased bottom, hard bottom, mud with cultch and sand with cultch. Note: The data in this file is up to 30 years old and areas designated as "cultch bottom" when this survey was conducted have likely degraded. For this reason, it is very likely that many of the areas shown as cultch in the dataset are no longer valiid. The data in this file should only be used as a general guide.The Department of Natural Resources makes no warranty, expressed or implied, as to the use or appropriateness of Spatial Data, and there are no warranties of merchantability or fitness for a particular purpose or use. The information contained in Spatial Data is from publicly available sources, but no representation is made as to the accuracy or completeness of Spatial Data. The Department of Natural Resources shall not be subject to liability for human error, error due to software conversion, defect, or failure of machines, or any material used in the connection with the machines, including tapes, disks, CD-ROM’s or DVD-ROM’s and energy. The Department of Natural Resources shall not be liable for any lost profits, consequential damages, or claims against the Department of Natural Resources by third parties. The liability of the Department of Natural Resources for damage regardless of the form of the action shall not exceed any distribution fees that may have been paid in obtaining Spatial Data.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/Geoscientific/MD_Soils/MapServer/11

FOR non-AGOL ACCOUNT HOLDERS, DOWNLOAD THIS GEOSPATIAL DATA HERE: https://gis-fws.opendata.arcgis.com/search?tags=lmvjvPolygon shapefile of the various state game agency managed lands (typically known as WMAs or Wildlife Management Areas) of the West Gulf Coastal Plain & Ouachitas ecological region, as compiled by the Lower Mississippi Valley Joint Venture partnership. Data was pulled from PAD US database aggregated by USGS and selected by location for inclusion in the region and includes data from Mississippi, Arkansas, Oklahoma and Texas. Units are considered areas that are actively managed for game and wildlife species.The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public land and voluntarily provided private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastre Theme ( https://communities.geoplatform.gov/ngda-cadastre/ ). The PAD-US is an ongoing project with several published versions of a spatial database including areas dedicated to the preservation of biological diversity, and other natural (including extraction), recreational, or cultural uses, managed for these purposes through legal or other effective means. The database was originally designed to support biodiversity assessments; however, its scope expanded in recent years to include all open space public and nonprofit lands and waters. Most are public lands owned in fee (the owner of the property has full and irrevocable ownership of the land); however, permanent and long-term easements, leases, agreements, Congressional (e.g. 'Wilderness Area'), Executive (e.g. 'National Monument'), and administrative designations (e.g. 'Area of Critical Environmental Concern') documented in agency management plans are also included. The PAD-US strives to be a complete inventory of U.S. public land and other protected areas, compiling “best available” data provided by managing agencies and organizations. The PAD-US geodatabase maps and describes areas using thirty-six attributes and five separate feature classes representing the U.S. protected areas network: Fee (ownership parcels), Designation, Easement, Marine, Proclamation and Other Planning Boundaries. An additional Combined feature class includes the full PAD-US inventory to support data management, queries, web mapping services, and analyses. The Feature Class (FeatClass) field in the Combined layer allows users to extract data types as needed. A Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) facilitates the extraction of authoritative federal data provided or recommended by managing agencies from the Combined PAD-US inventory. This PAD-US Version 3.0 dataset includes a variety of updates from the previous Version 2.1 dataset (USGS, 2020, https://doi.org/10.5066/P92QM3NT ), achieving goals to: 1) Annually update and improve spatial data representing the federal estate for PAD-US applications; 2) Update state and local lands data as state data-steward and PAD-US Team resources allow; and 3) Automate data translation efforts to increase PAD-US update efficiency. The following list summarizes the integration of "best available" spatial data to ensure public lands and other protected areas from all jurisdictions are represented in the PAD-US (other data were transferred from PAD-US 2.1). Federal updates - The USGS remains committed to updating federal fee owned lands data and major designation changes in annual PAD-US updates, where authoritative data provided directly by managing agencies are available or alternative data sources are recommended. The following is a list of updates or revisions associated with the federal estate: 1) Major update of the Federal estate (fee ownership parcels, easement interest, and management designations where available), including authoritative data from 8 agencies: Bureau of Land Management (BLM), U.S. Census Bureau (Census Bureau), Department of Defense (DOD), U.S. Fish and Wildlife Service (FWS), National Park Service (NPS), Natural Resources Conservation Service (NRCS), U.S. Forest Service (USFS), and National Oceanic and Atmospheric Administration (NOAA). The federal theme in PAD-US is developed in close collaboration with the Federal Geographic Data Committee (FGDC) Federal Lands Working Group (FLWG, https://communities.geoplatform.gov/ngda-govunits/federal-lands-workgroup/ ). 2) Improved the representation (boundaries and attributes) of the National Park Service, U.S. Forest Service, Bureau of Land Management, and U.S. Fish and Wildlife Service lands, in collaboration with agency data-stewards, in response to feedback from the PAD-US Team and stakeholders. 3) Added a Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) to the PAD-US 3.0 geodatabase to facilitate the extraction (by Data Provider, Dataset Name, and/or Aggregator Source) of authoritative data provided directly (or recommended) by federal managing agencies from the full PAD-US inventory. A summary of the number of records (Frequency) and calculated GIS Acres (vs Documented Acres) associated with features provided by each Aggregator Source is included; however, the number of records may vary from source data as the "State Name" standard is applied to national files. The Feature Class (FeatClass) field in the table and geodatabase describe the data type to highlight overlapping features in the full inventory (e.g. Designation features often overlap Fee features) and to assist users in building queries for applications as needed. 4) Scripted the translation of the Department of Defense, Census Bureau, and Natural Resource Conservation Service source data into the PAD-US format to increase update efficiency. 5) Revised conservation measures (GAP Status Code, IUCN Category) to more accurately represent protected and conserved areas. For example, Fish and Wildlife Service (FWS) Waterfowl Production Area Wetland Easements changed from GAP Status Code 2 to 4 as spatial data currently represents the complete parcel (about 10.54 million acres primarily in North Dakota and South Dakota). Only aliquot parts of these parcels are documented under wetland easement (1.64 million acres). These acreages are provided by the U.S. Fish and Wildlife Service and are referenced in the PAD-US geodatabase Easement feature class 'Comments' field. State updates - The USGS is committed to building capacity in the state data-steward network and the PAD-US Team to increase the frequency of state land updates, as resources allow. The USGS supported efforts to significantly increase state inventory completeness with the integration of local parks data in the PAD-US 2.1, and developed a state-to-PAD-US data translation script during PAD-US 3.0 development to pilot in future updates. Additional efforts are in progress to support the technical and organizational strategies needed to increase the frequency of state updates. The PAD-US 3.0 included major updates to the following three states: 1) California - added or updated state, regional, local, and nonprofit lands data from the California Protected Areas Database (CPAD), managed by GreenInfo Network, and integrated conservation and recreation measure changes following review coordinated by the data-steward with state managing agencies. Developed a data translation Python script (see Process Step 2 Source Data Documentation) in collaboration with the data-steward to increase the accuracy and efficiency of future PAD-US updates from CPAD. 2) Virginia - added or updated state, local, and nonprofit protected areas data (and removed legacy data) from the Virginia Conservation Lands Database, provided by the Virginia Department of Conservation and Recreation's Natural Heritage Program, and integrated conservation and recreation measure changes following review by the data-steward. 3) West Virginia - added or updated state, local, and nonprofit protected areas data provided by the West Virginia University, GIS Technical Center. For more information regarding the PAD-US dataset please visit, https://www.usgs.gov/gapanalysis/PAD-US/. For more information about data aggregation please review the PAD-US Data Manual available at https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-manual . A version history of PAD-US updates is summarized below (See https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-history for more information): 1) First posted - April 2009 (Version 1.0 - available from the PAD-US: Team pad-us@usgs.gov). 2) Revised - May 2010 (Version 1.1 - available from the PAD-US: Team pad-us@usgs.gov). 3) Revised - April 2011 (Version 1.2 - available from the PAD-US: Team pad-us@usgs.gov). 4) Revised - November 2012 (Version 1.3) https://doi.org/10.5066/F79Z92XD 5) Revised - May 2016 (Version 1.4) https://doi.org/10.5066/F7G73BSZ 6) Revised - September 2018 (Version 2.0) https://doi.org/10.5066/P955KPLE 7) Revised - September 2020 (Version 2.1) https://doi.org/10.5066/P92QM3NT 8) Revised - January 2022 (Version 3.0) https://doi.org/10.5066/P9Q9LQ4B Comparing protected area trends between PAD-US versions is not recommended without consultation with USGS as many changes reflect improvements to agency and organization GIS systems, or conservation and recreation measure classification, rather than actual changes in protected area acquisition on the ground. These lands are commonly known as Wildlife Management Areas (WMAs) but that nomenclature varies by state.

The Digital Geologic-GIS Map of John Muir National Historic Site and Vicinity, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (jomu_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google The Digital Geohazards-GIS Map of John Muir National Historic Site and Vicinity, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (jomu_geohazard.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (jomu_geohazard.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (jomu_geohazard.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (jomu_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (jomu_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (jomu_geohazard_metadata_faq.pdf). Please read the jomu_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: California Department of Conservation, Division of Mines and Geology. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (jomu_geohazard_metadata.txt or jomu_geohazard_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google

Oil and Gas Lease contains spatial and tabular data potraying Competitive and Non-Competitive Oil and Gas Leases, and Oil and Gas Storage Leases issued by the Alaska Department of Natural Resources.

This spatial data set characterizes the geographic representation of land parcels within the State of Alaska contained by the Oil and Gas Lease category. It has been extracted from data sets used to produce the State status plats. This data set includes cases noted on the digital status plats up to one day prior to data extraction.

Each feature has an associated attribute record, including a Land Administration System (LAS) file-type and file-number which serves as an index to related LAS case-file information. Additional LAS case-file and customer information may be obtained at: http://dev.dnr.alaska.gov/projects/las/ Those requiring more information regarding State land records should contact the Alaska Department of Natural Resources Public Information Center directly.

This file (SWSUB8) is a statewide digital watershed file. It depicts the State with 138 separate watersheds each with an 8-digit numeric code. The file was created primarily for State and Federal agency use. The creation of this file goes back many years and involved several State and Federal agencies. This file was derived from a more detailed watershed file (Maryland's Third-Order Watershed). The process used to create this file is consistent with the elevation contour information found on the US Geological Survey's 7.5 minute topographic quadrangle maps and the Maryland Department of the Environment's watershed location and naming conventions. This file is similar, but not identical, to the US Natural Resources Conservation Service's (NRCS) Hydrologic Unit Code (HUC11) watershed file. The watersheds define Strahler (Strahler 1952 p.1120) third order stream drainage by contours on U.S. Geological Survey (USGS) 7.5 minute quadrangle map sheets. Some watershed drainage areas were defined for streams less than third order and some large area Watersheds were split to maintain a maximum size of 15,000 acres.The Department of Natural Resources makes no warranty, expressed or implied, as to the use or appropriateness of Spatial Data, and there are no warranties of merchantability or fitness for a particular purpose or use. The information contained in Spatial Data is from publicly available sources, but no representation is made as to the accuracy or completeness of Spatial Data. The Department of Natural Resources shall not be subject to liability for human error, error due to software conversion, defect, or failure of machines, or any material used in the connection with the machines, including tapes, disks, CD-ROMs or DVD-ROMs and energy. The Department of Natural Resources shall not be liable for any lost profits, consequential damages, or claims against the Department of Natural Resources by third parties. The liability of the Department of Natural Resources for damage regardless of the form of the action shall not exceed any distribution fees that may have been paid in obtaining Spatial Data.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/Hydrology/MD_Watersheds/FeatureServer/1

SSURGO-QA ArcGIS Pro Toolbox1. SetupDownload SSURGO by Areasymbol - Use Soil Data Access and Web Soil Survey download page to get SSURGO datasets. User can a wildcard to query the database by Areasymbol or by age.Download SSURGO by Region - Downloads SSURGO Soil Survey Areas that are owned by a specific region including an approximiate 2 soil survey area buffer.Generate Regional Transactional Geodatabase - Used to create the Regional Transactional Spatial Database (RTSD) for SSURGO.Generate SSO SSURGO Datasets - Create a SSURGO file geodatabase for a selected MLRA Soil Survey Office.Import SSURGO Datasets in FGDB - This tooll will import SSURGO spatial and tabular datasets within a given location into a File Geodatabase and establish the necessary table and feature class relationships to interact with the dataset.Insert NATSYM and MUNAME Value - This tool adds the National Mapunit Symbol (NATMUSYM) and the Mapunit Name (MUNAME) values to the corresponding MUKEY. An MUKEY field is required to execute. A network connection is required in order to submit a query to SDacess.RTSD - Check SDJR Project Out - Designed to work with the RTSD to manage SDJR projects and export data for those projects to be sent to the MLRA SSO.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. To produce the digital map, a combination of 1:12,000-scale color infrared digital ortho-imagery acquired in 2003, 1:12,000-scale true color ortho-rectified imagery acquired in 2005, and all of the GPS referenced ground data were used to interpret the complex patterns of vegetation and land-use. All imagery was acquired from the U.S. Department of Agriculture - Farm Service Agency’s Aerial Photography Field Office and the National Agriculture Imagery Program. In the end, 27 map units (14 vegetated and 13 land-use) were developed and directly cross-walked or matched to corresponding plant associations and land-use classes. All of the interpreted and remotely sensed data were converted to Geographic Information System (GIS) databases using ArcGIS© software. Draft maps were printed, field tested, reviewed, and revised. One hundred and thirty three accuracy assessment (AA) data points were collected in 2006 and used to determine the map’s accuracy. GIS Database 2002-2005: Project Size = 4,600 acres Lyndon B. Johnson National Historical Park = 674 acres Lyndon B. Johnson State Park and Historic Site = 418 acres Base Imagery acquired from the USDA FSA Aerial Photography Field Office acquired through the National Agriculture Imagery Program: 2005 - 1:12,000-scale true color ortho-rectified imagery, compressed county mosaic,2 meter pixel resolution 2003 - 1:12,000-scale color infrared digital ortho-imagery, compressed county mosaic,1 meter pixel resolution 27 Map Classes 14 Vegetated 13 Non-vegetated Minimum Mapping Unit = ½ hectare is the program standard but this was modified at LYJO to ¼ acre. Total Size = 1,080 Polygons Average Polygon Size = 4.3 acres Overall Thematic Accuracy = 92%

Updated for 2013-17: US Census American Community Survey data table for: COMPUTER AND INTERNET USAGE subject area. Provides information about: TYPES OF COMPUTERS IN HOUSEHOLD for the universe of: HOUSEHOLDS. These data are extrapolated estimates only, based on sampling; they are not actual complete counts. The data is based on 2010 Census Tracts. Table ACS_B28001_TYPECOMPUTERHSHLD contains both the Estimate value in the E item for the census topic and an adjacent M item which defines the Margin of Error for the value. The Margin of Error (MOE) is the plus/minus range for the item estimate value, where the range between the Estimate minus the Margin of Error and the Estimate plus the Margin of Error defines the 90% confidence interval of the item value. Many of the Margin of Error values are significant relative to the size of the Estimate value. This table contains 11 item(s) extracted from a larger sequence table. This extracted subset represents that portion of the sequence that is considered high priority. Other portions of this sequence that are not included can be identified in the data dictionary information provided in the Supplemental Information section. This table information is also provided as a customized layer file: B28001_AREA_TYPECOMPUTERHSHLD.lyr where the table information is joined to the 2010 TRACTS_AREA census geography on the GEOID item. Both the table and customized lyr file name do not contain the year descriptor (i.e. 2013-2017) for the current ACS series. This is intentional in order to maintain the same table name in each successive ACS update. The alias of each item's (E)stimate and (M)easure of Error value stores this year date information as beginning YY and ending YY, i.e., 'E1317' and 'M1317' followed by the rest of the alias description. In this way users of the data tables or lyr files that support field aliases can determine which ACS series is being represented by the current table contents. The next 5-year sample of ACS, representing the current year minus 1, becomes available in December of each year. For example, the next series - 2014 through 2018 - will become available at the end of 2019. The new 2017 data will be posted to the Spatial Data Warehouse by January 2019. The previous series of data is retired to the Historical Data Library geodatabase (according to the ACS series end date) from where it can be accessed if needed.

This data set was developed by the US Bureau of the Census, modified by the Missouri Geographic Resource Center (GRC), and currently maintained by the Missouri Department of Elementary and Secondary Education and the Missouri Office of Administration, Information Technology Services Division, Office of Geospatial Information (OGI). January 2022 update.This is a GRC-edited version of the 2010 TIGER school districts to reflect changes for the 2012 year.The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. School Districts are single-purpose administrative units within which local officials provide public educational services for the area's residents. The Census Bureau obtains the boundaries, names, local education agency codes, grade ranges, and school district levels for school districts from State officials for the primary purpose of providing the U.S. Department of Education with estimates of the number of children in poverty within each school district. This information serves as the basis for the Department of Education to determine the annual allocation of Title I funding to States and school districts. TIGER/Line Files include separate shapefiles for elementary, secondary, and unified school districts.Boundaries were updated in 2015 by Missouri OGI to account for two districts that were voluntarily annexed into existing districts.