Facebook
TwitterThe 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. We converted the photointerpreted data into a format usable in a geographic information system (GIS) by employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM), Zone 16, using the North American Datum of 1983 (NAD83). Orthorectify: We orthorectified the interpreted overlays by using OrthoMapper, a softcopy photogrammetric software for GIS. One function of OrthoMapper is to create orthorectified imagery from scanned and unrectified imagery (Image Processing Software, Inc., 2002). The software features a method of visual orientation involving a point-and-click operation that uses existing orthorectified horizontal and vertical base maps. Of primary importance to us, OrthoMapper also has the capability to orthorectify the photointerpreted overlays of each photograph based on the reference information provided. Digitize: To produce a polygon vector layer for use in ArcGIS (Environmental Systems Research Institute [ESRI], Redlands, California), we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format by using ArcGIS. In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map-attribute codes (both map-class codes and physiognomic modifier codes) to the polygons and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer. Geodatabase: At this stage, the map layer has only map-attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.
Facebook
TwitterThis Python script (Shape2DJI_Pilot_KML.py) will scan a directory, find all the ESRI shapefiles (.shp), reproject to EPSG 4326 (geographic coordinate system WGS84 ellipsoid), create an output directory and make a new Keyhole Markup Language (.kml) file for every line or polygon found in the files. These new *.kml files are compatible with DJI Pilot 2 on the Smart Controller (e.g., for M300 RTK). The *.kml files created directly by ArcGIS or QGIS are not currently compatible with DJI Pilot.
Facebook
TwitterThis feature collection, UCR Timber Harvest & Veg Management Activities_2022, provides the proposed timber harvest and vegetation management data within the ongoing Upper Cheat River project by the U.S. Forest Service for Monongahela National Forest, West Virginia.Purpose:This data was created by the U.S. Forest Service staff for use in analysis of the project’s likely environmental impacts.Source & Date:The source data was created in 2020 and downloaded in zipped ESRI shapefile format (GIS Shapefiles.zip) from the USFS project page (Analysis folder). The data was downloaded on July 1, 2021, and subsequently updated. The data is current as of March 29, 2022. Processing:ABRA published the source shapefiles from ArcMap as a feature layer. That feature layer was published as a feature collection to allow grouping in Map Viewer Classic. The sub-layers were symbolized using the provided map document as an example (Scoping Information and Maps.pdf).UCR Timber Harvest & Veg Management Activities_2022 contains the following data layers:UCR_TSIUCR_WildlifeHabitatEnhancementsUCR_FireBlocksUCR_ExWLOMaintenanceUCR_PotentialCommericalHarvestUnitsUCR_FireLines Symbology:The list below refers to the data layers above, named as shown in the Upper Cheat Project map provided by ABRA.Timber Stand Improvement Units: Light blue polygonWildlife Habitat Enhancements:Cutback Borders: a purple polygonDaylighting: green polygonWildlife Opening Expansion: yellow polygonBurn Blocks: brown polygonExisting Wildlife Opening Maintenance: red polygonPotential Commercial Harvest Units: Cable Timber Units: green polygonConventional Timber Units: green polygon with dark green outlineHelicopter Timber Units: clear polygon with red outlineFire Handlines: purple polylineMore information can be found on ABRA’s project description page, hosted by the National Forest Integrity Project. Additional detailed information is available on the USFS project page.
Facebook
TwitterThe 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. We converted the photointerpreted data into a GIS-usable format employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 16, using North American Datum of 1983 (NAD83). To produce a polygon vector layer for use in ArcGIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcGIS (Version 9.2, © 2006 Environmental Systems Research Institute, Redlands, California). In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map attribute codes (both map class codes and physiognomic modifier codes) to the polygons, and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer of INDU and immediate environs. At this stage, the map layer has only map attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map class names, physiognomic definitions, link to NVC association and alliance codes), we produced a feature class table along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature class layers produced from this project, including vegetation sample plots, accuracy assessment sites, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset contains files created, digitized, or georeferenced by Chris DeRolph for mapping the pre-urban renewal community within the boundaries of the Riverfront-Willow St. and Mountain View urban renewal projects in Knoxville TN. Detailed occupant information for properties within boundaries of these two urban renewal projects was extracted from the 1953 Knoxville City Directory. The year 1953 was chosen as a representative snapshot of the Black community before urban renewal projects were implemented. The first urban renewal project to be approved was the Riverfront-Willow Street project, which was approved in 1954 according to the University of Richmond Renewing Inequality project titled ‘Family Displacements through Urban Renewal, 1950-1966’ (link below in the 'Other shapefiles' section). For ArcGIS Online users, the shapefile and tiff layers are available in AGOL and can be found by clicking the ellipsis next to the layer name and selecting 'Show item details' for the layers in this webmap https://knoxatlas.maps.arcgis.com/apps/webappviewer/index.html?id=43a66c3cfcde4f5f8e7ab13af9bbcebecityDirectory1953 is a folder that contains:JPG images of 1953 City Directory for street segments within the urban renewal project boundaries; images collected at the McClung Historical CollectionTXT files of extracted text from each image that was used to join occupant information from directory to GIS address datashp is a folder that contains the following shapefiles:Residential:Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and property ownersBlack_rented_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and non-owners of the propertyNon_Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as property owners that were not listed as BlackNon_Black_rented_residential_1953.shp: residential entries in the 1953 City Directory not listed as Black or property ownersResidential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposeslastName: occupant's last namelabelShort: combines the Number and lastName fields for map labeling purposesNon-residential:Black_nonResidential_1953.shp: non-residential entries in the 1953 City Directory listed as Black-occupiedNonBlack_nonResidential_1953.shp: non-residential entries in the 1953 City Directory not listed as Black-occupiedNon-residential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationNAICS6: 2022 North American Industry Classification System (NAICS) six-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS6title: NAICS6 title/short descriptionNAICS3: 2022 North American Industry Classification System (NAICS) three-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS3title: NAICS3 title/short descriptionflag: flags whether the occupant is part of the public sector or an NGO; a flag of '0' indicates the occupant is assumed to be a privately-owned businessrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposesOther shapefiles:razedArea_1972.shp: approximate area that appears to have been razed during urban renewal based on visual overlay of usgsImage_grayscale_1956.tif and usgsImage_colorinfrared_1972.tif; digitized by Chris DeRolphroadNetwork_preUrbanRenewal.shp: road network present in urban renewal area before razing occurred; removed attribute indicates whether road was removed or remains today; historically removed roads were digitized by Chris DeRolph; remaining roads sourced from TDOT GIS roads dataTheBottom.shp: the approximate extent of the razed neighborhood known as The Bottom; digitized by Chris DeRolphUrbanRenewalProjects.shp: boundaries of the East Knoxville urban renewal projects, as mapped by the University of Richmond's Digital Scholarship Lab https://dsl.richmond.edu/panorama/renewal/#view=0/0/1&viz=cartogram&city=knoxvilleTN&loc=15/35.9700/-83.9080tiff is a folder that contains the following images:streetMap_1952.tif: relevant section of 1952 map 'Knoxville Tennessee and Surrounding Area'; copyright by J.U.G. Rich and East Tenn Auto Club; drawn by R.G. Austin; full map accessed at McClung Historical Collection, 601 S Gay St, Knoxville, TN 37902; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphnewsSentinelRdMap_1958.tif: urban renewal area map from 1958 Knox News Sentinel article; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphusgsImage_grayscale_1956.tif: May 18, 1956 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/ARA550590030582/usgsImage_colorinfrared_1972.tif: April 18, 1972 color infrared USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR6197002600096/usgsImage_grayscale_1976.tif: November 8, 1976 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR1VDUT00390010/
Facebook
TwitterThe Digital Geologic-GIS Map of Sagamore Hill National Historic Site and Vicinity, New York 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 (sahi_geology.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 (sahi_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (sahi_geology.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 (sahi_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (sahi_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 (sahi_geology_metadata_faq.pdf). Please read the sahi_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: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (sahi_geology_metadata.txt or sahi_geology_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:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 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 Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
Facebook
TwitterThis feature layer, Upper_Cheat_Project_Boundary, provides the project boundary associated with the Upper Cheat River Project proposed by the U.S. Forest Service within Monongahela National Forest, West Virginia.Purpose:This data was created by the U.S. Forest Service staff for use in analysis of the project’s likely environmental impacts.Source & Date:The source data was created in 2020 and downloaded in zipped ESRI shapefile format (GIS Shapefiles.zip) from the USFS project page (Scoping folder). The data was downloaded on July 1, 2021, and subsequently updated. The data is current as of January 4, 2022.Processing:The source shapefile was symbolized using the provided map document as an example (Scoping Information and Maps.pdf).Symbology:Upper_Cheat_Project_Boundary: clear polygon with black outlineMore information can be found on ABRA’s project description page, hosted by the National Forest Integrity Project. Additional detailed information is available on the USFS project page.
Facebook
TwitterThe Digital Geologic-GIS Map of San Miguel Island, 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 (smis_geology.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 (smis_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (smis_geology.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.) this file (chis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (chis_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 (smis_geology_metadata_faq.pdf). Please read the chis_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: American Association of Petroleum Geologists. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (smis_geology_metadata.txt or smis_geology_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 Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Activity Project Area NEPA represents an area (polygon) within which one or more activities related to the National Environmental Policy Act (NEPA) are aggregated or organized. The data comes from the Forest Service's Natural Resource Manager (NRM) Forest Activity Tracking System (FACTS), which is the agency standard for managing information about activities related to fire/fuels, silviculture, and invasive species. FACTS is an activity tracking application for all levels of the Forest Service.These data are a central source for project area boundaries for use in national information requests and cross unit analysis and makes the project area boundaries and their basic attributes more easily available to field units. It also provides public access to the data during project planning and implementation. Please note that this dataset is not complete and forests continue to improve the quality of the data over time.Metadata and DownloadsThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService CSV Shapefile GeoJSON KML https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_ActivityProjectAreas_01/MapServer/0 https://www.fs.fed.us/emc/nepa/index.htm For complete information, please visit https://data.gov.
Facebook
TwitterThe 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 true color aerial photography, 1:12,000-scale true color ortho-rectified imagery, and 3 years of ground-truthing were used to interpret the complex patterns of vegetation and land-use. In the end, 52 map units 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. 1,122 accuracy assessment data points were collected and used to determine the map’s accuracy. After final revisions, the accuracy assessment revealed an overall thematic accuracy of 82%.
Facebook
TwitterU.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
Populations of many cold-water species are likely to decline this century with global warming, but declines will vary spatially and some populations will persist even under extreme climate change scenarios. Especially cold habitats could provide important refugia from both future environmental change and invasions by non-native species that prefer warmer waters. The Climate Shield website hosts geospatial data and related information that describes specific locations of cold-water refuge streams for native Cutthroat Trout (Oncorhynchus clarkii) and Bull Trout (Salvelinus confluentus) across the American West. Forecasts about the locations of refugia could enable the protection of key watersheds, inform support among multiple stakeholders, and provide a foundation for planning climate-smart conservation networks that improve the odds of preserving native trout populations through the 21st century. The Northern Rockies Adaptation Partnership provided a valuable forum that accelerated this work. The Great Northern and North Pacific Landscape Conservation Cooperatives generously funded the NorWeST project, which serves as the foundation for Climate Shield. The Climate Shield Cutthroat Trout and Bull Trout models were developed from fish surveys conducted at more than 4,500 locations in over 500 streams, as described in the cited peer-reviewed studies and agency reports. Resources in this dataset:Resource Title: Digital Maps and ArcGIS Shapefiles. File Name: Web Page, url: https://www.fs.fed.us/rm/boise/AWAE/projects/ClimateShield/maps.html Information is available here to download as easy-to-use digital maps (.pdf files) and ArcGIS shapefiles for all streams within the historical ranges of native trout across the northwestern U.S. The geographic areas match the NorWeST production units because those stream temperature scenarios are integral to Climate Shield.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Activity Project Area Timber Sale represents an area (polygon) within which one or more Timber Sale related activities are aggregated or organized. The data comes from the Forest Service's Natural Resource Manager (NRM) Forest Activity Tracking System (FACTS), which is the agency standard for managing information about activities related to fire/fuels, silviculture, and invasive species. FACTS is an activity tracking application for all levels of the Forest Service.These data are a central source for project area boundaries for use in national information requests and cross unit analysis and makes the project area boundaries and their basic attributes more easily available to field units. It also provides public access to the data during project planning and implementation. Please note that this dataset is not complete and forests continue to improve the quality of the data over time.Metadata and DownloadsThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService CSV Shapefile GeoJSON KML https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_ActivityProjectAreas_01/MapServer/2 https://www.fs.fed.us/forestmanagement/products/contracts.shtml For complete information, please visit https://data.gov.
Facebook
TwitterThis archive contains a geology map of the general Roosevelt Hot Springs region, both in PDF and ArcGIS geodatabase formats, that was created as part of the Utah FORGE project. This archive contains an ArcGIS geodatabase containing the GIS feature classes and symbology for the geology of the general Roosevelt Hot Springs region in Utah.
Facebook
TwitterThis layer describes the official USFS project boundary for the Greenbrier Southeast forest management project in Pocahontas County, West Virginia.Purpose:This data was created by the U.S. Forest Service staff for use in analysis of the project’s likely environmental impacts.Source & Date:This layer was created from GIS data downloaded in zipped ESRI shapefile format from the project website (https://www.fs.usda.gov/project/?project=55797 - Analysis folder) on 10/15/2021.Processing:ABRA uploaded the shapefile to ArcGIS Online, where it was published as a feature layer.Symbology:GSE Project Boundary: Black
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset displays the approximate location of US Forest Service, Great American Outdoors Act (GAOA) projects. The data is refreshed on a nightly basis from the US Forest Service database of infrastructure projects which is stewarded by the individual National Forests and Grasslands. This dataset is a spatial data layer of points representing the approximate or general location where the project takes place. The point location is intended for use in small scale maps to indicate the general location of the projects across the country. The location data is maintained by staff on the individual National Forest or Grassland using the database of record. Because a project can be made up of many assets distributed across a land area, a single project location point will not always reflect the specific location and extent of the work in the project. The project detail data can be used to display the individual assets that make up the project. For more information about Forest Service GAOA projects visit our website: https://www.fs.usda.gov/managing-land/gaoaMetadata and DownloadsThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService OGC WMS CSV Shapefile GeoJSON KML For complete information, please visit https://data.gov.
Facebook
TwitterThe data is available in two formats: a ZIP file containing GIS shapefiles connected to an Access datafile containing information pertaining to excavation area, finds, object types along with other metadata regarding the archaeological investigation. The second ZIP file consists of corresponding .gml and .xlsx files.
Facebook
TwitterGeographic Extent: SANDY_Restoration_DE_MD_QL2 Area of Interest covers approximately 3.096 square miles. Lot #5 contains the full project area Dataset Description: The SANDY_Restoration_DE_MD_QL2 project called for the Planning, Acquisition, processing and derivative products of LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1. The data was developed based on a horizontal projection/datum of State Plane Zone Maryland (1900), NAD83, feet and vertical datum of NAVD1988 (GEOID12A), feet. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.2 Files formatted to 3842 individual 1500m x 1500m tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 1500m x 1500m schema, and Breaklines in ESRI shapefile format. Ground Conditions: LiDAR was collected in Winter 2013 / Spring 2014, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 78 QA control points and 99 Land Cover control points that were used to calibrate the LiDAR to known ground locations established throughout the SANDY_Restoration_DE_MD_QL2 project area.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Dorchester/MD_dorchester_slope_m/ImageServer
Facebook
TwitterGeostrat Report – The Sequence Stratigraphy and Sandstone Play Fairways of the Late Jurassic Humber Group of the UK Central Graben This non-exclusive report was purchased by the NSTA from Geostrat as part of the Data Purchase tender process (TRN097012017) that was carried out during Q1 2017. The contents do not necessarily reflect the technical view of the NSTA but the report is being published in the interests of making additional sources of data and interpretation available for use by the wider industry and academic communities. The Geostrat report provides stratigraphic analyses and interpretations of data from the Late Jurassic to Early Cretaceous Humber Group across the UK Central Graben and includes a series of depositional sequence maps for eight stratigraphic intervals. Stratigraphic interpretations and tops from 189 wells (up to Release 91) are also included in the report. The outputs as published here include a full PDF report, ODM/IC .dat format sequence maps, and all stratigraphic tops (lithostratigraphy, ages, sequence stratigraphy) in .csv format (for import into different interpretation platforms). In addition, the NSTA has undertaken to provide the well tops, stratigraphic interpretations and sequence maps in an ESRI ArcGIS format that is intended to facilitate the integration of these data into projects and data storage systems held by individual organisations. As part of this process, the Geostrat well names have been matched as far as possible to the NSTA well names from the NSTA Offshore Wells shapefile (as provided on the NSTA’s Open Data website) and the original polygon files have been incorporated into an ArcGIS project. All the files within the GIS folder of this delivery have been created by the NSTA. NSTA web feature services (WFSs) have been included in the map document in this delivery. They replace the use of a shapefile or feature class to represent block, licence and quadrant data. By using a WFS, the data is automatically updated when it becomes available via the NSTA. A version of this delivery containing shapefiles for well tops, stratigraphic interpretations and sequence maps is available on the NSTA’s Open Data website for use in other GIS software packages. All releases included in the Data Purchase tender process that have been made openly available are summarised in a mapping application available from the NSTA website. The application includes an area of interest outline for each of the products and an overview of which wellbores have been included in the products.
Facebook
TwitterGIS-material for the archaeological project: Preliminary investigations at the bypass Vadstena
The data is available in two formats: a ZIP file containing GIS shapefiles connected to an Access datafile containing information pertaining to excavation area, finds, object types along with other metadata regarding the archaeological investigation. The second ZIP file consists of corresponding .gml and .xlsx files.
Facebook
TwitterThis data is associated with the Nevada Play Fairway project and includes excel files containing raw 2-meter temperature data and corrections. GIS shapefiles and layer files contain ing location and attribute information for the data are included. Well data includes both deep and shallow TG holes, GIS shapefiles and layer files. ArcGIS shapefile with location and attribute information
Facebook
TwitterThe 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. We converted the photointerpreted data into a format usable in a geographic information system (GIS) by employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM), Zone 16, using the North American Datum of 1983 (NAD83). Orthorectify: We orthorectified the interpreted overlays by using OrthoMapper, a softcopy photogrammetric software for GIS. One function of OrthoMapper is to create orthorectified imagery from scanned and unrectified imagery (Image Processing Software, Inc., 2002). The software features a method of visual orientation involving a point-and-click operation that uses existing orthorectified horizontal and vertical base maps. Of primary importance to us, OrthoMapper also has the capability to orthorectify the photointerpreted overlays of each photograph based on the reference information provided. Digitize: To produce a polygon vector layer for use in ArcGIS (Environmental Systems Research Institute [ESRI], Redlands, California), we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format by using ArcGIS. In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map-attribute codes (both map-class codes and physiognomic modifier codes) to the polygons and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer. Geodatabase: At this stage, the map layer has only map-attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.