The National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territoriesGeographic Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSUpdate Frequency: AnnualPublication Date: July 2022This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not. Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map.Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

WSDOT template for Esri file geodatabase polygon feature class. Template has pre-defined attribute schema to help users create data that is more consistent or compliant with agency standards. Metadata has been created using the FGDC metadata style but stored in the ArcGIS format. Content presentation will change upon export to FGDC format.This service is maintained by the WSDOT Transportation Data, GIS & Modeling Office. If you are having trouble viewing the service, please contact Online Map Support at onlinemapsupport@wsdot.wa.gov.

These data are a point feature class that provides the location of Research and Development's offices across the United States.

Download In State Plane Projection Here. ** In addition to the Railroad Centerlines feature class, the hyperlink download above also contains a generalized layer, as well as all tracks including spurs ** This dataset was created as a cartographic backdrop as well as for any analysis that requires railroads locations. The railroads were originally traced off aerial photography taken in April of 2000 using heads up digitizing in ESRI ArcGIS and later revised using photography taken in 2005, 2007, 2010, 2012 and 2013. This dataset should satisfy National Map Accuracy Standards for a 1:1200 product. Update Frequency: This dataset is updated on a weekly basis.

This digital dataset was created as part of a U.S. Geological Survey study, done in cooperation with the Monterey County Water Resource Agency, to conduct a hydrologic resource assessment and develop an integrated numerical hydrologic model of the hydrologic system of Salinas Valley, CA. As part of this larger study, the USGS developed this digital dataset of geologic data and three-dimensional hydrogeologic framework models, referred to here as the Salinas Valley Geological Framework (SVGF), that define the elevation, thickness, extent, and lithology-based texture variations of nine hydrogeologic units in Salinas Valley, CA. The digital dataset includes a geospatial database that contains two main elements as GIS feature datasets: (1) input data to the 3D framework and textural models, within a feature dataset called “ModelInput”; and (2) interpolated elevation, thicknesses, and textural variability of the hydrogeologic units stored as arrays of polygonal cells, within a feature dataset called “ModelGrids”. The model input data in this data release include stratigraphic and lithologic information from water, monitoring, and oil and gas wells, as well as data from selected published cross sections, point data derived from geologic maps and geophysical data, and data sampled from parts of previous framework models. Input surface and subsurface data have been reduced to points that define the elevation of the top of each hydrogeologic units at x,y locations; these point data, stored in a GIS feature class named “ModelInputData”, serve as digital input to the framework models. The location of wells used a sources of subsurface stratigraphic and lithologic information are stored within the GIS feature class “ModelInputData”, but are also provided as separate point feature classes in the geospatial database. Faults that offset hydrogeologic units are provided as a separate line feature class. Borehole data are also released as a set of tables, each of which may be joined or related to well location through a unique well identifier present in each table. Tables are in Excel and ascii comma-separated value (CSV) format and include separate but related tables for well location, stratigraphic information of the depths to top and base of hydrogeologic units intercepted downhole, downhole lithologic information reported at 10-foot intervals, and information on how lithologic descriptors were classed as sediment texture. Two types of geologic frameworks were constructed and released within a GIS feature dataset called “ModelGrids”: a hydrostratigraphic framework where the elevation, thickness, and spatial extent of the nine hydrogeologic units were defined based on interpolation of the input data, and (2) a textural model for each hydrogeologic unit based on interpolation of classed downhole lithologic data. Each framework is stored as an array of polygonal cells: essentially a “flattened”, two-dimensional representation of a digital 3D geologic framework. The elevation and thickness of the hydrogeologic units are contained within a single polygon feature class SVGF_3DHFM, which contains a mesh of polygons that represent model cells that have multiple attributes including XY location, elevation and thickness of each hydrogeologic unit. Textural information for each hydrogeologic unit are stored in a second array of polygonal cells called SVGF_TextureModel. The spatial data are accompanied by non-spatial tables that describe the sources of geologic information, a glossary of terms, a description of model units that describes the nine hydrogeologic units modeled in this study. A data dictionary defines the structure of the dataset, defines all fields in all spatial data attributer tables and all columns in all nonspatial tables, and duplicates the Entity and Attribute information contained in the metadata file. Spatial data are also presented as shapefiles. Downhole data from boreholes are released as a set of tables related by a unique well identifier, tables are in Excel and ascii comma-separated value (CSV) format.

This data release contains the analytical results and evaluated source data files of geospatial analyses for identifying areas in Alaska that may be prospective for different types of lode gold deposits, including orogenic, reduced-intrusion-related, epithermal, and gold-bearing porphyry. The spatial analysis is based on queries of statewide source datasets of aeromagnetic surveys, Alaska Geochemical Database (AGDB3), Alaska Resource Data File (ARDF), and Alaska Geologic Map (SIM3340) within areas defined by 12-digit HUCs (subwatersheds) from the National Watershed Boundary dataset. The packages of files available for download are: 1. LodeGold_Results_gdb.zip - The analytical results in geodatabase polygon feature classes which contain the scores for each source dataset layer query, the accumulative score, and a designation for high, medium, or low potential and high, medium, or low certainty for a deposit type within the HUC. The data is described by FGDC metadata. An mxd file, and cartographic feature classes are provided for display of the results in ArcMap. An included README file describes the complete contents of the zip file. 2. LodeGold_Results_shape.zip - Copies of the results from the geodatabase are also provided in shapefile and CSV formats. The included README file describes the complete contents of the zip file. 3. LodeGold_SourceData_gdb.zip - The source datasets in geodatabase and geotiff format. Data layers include aeromagnetic surveys, AGDB3, ARDF, lithology from SIM3340, and HUC subwatersheds. The data is described by FGDC metadata. An mxd file and cartographic feature classes are provided for display of the source data in ArcMap. Also included are the python scripts used to perform the analyses. Users may modify the scripts to design their own analyses. The included README files describe the complete contents of the zip file and explain the usage of the scripts. 4. LodeGold_SourceData_shape.zip - Copies of the geodatabase source dataset derivatives from ARDF and lithology from SIM3340 created for this analysis are also provided in shapefile and CSV formats. The included README file describes the complete contents of the zip file.

The data in this map service is updated every weekend.Note: This data includes all activities regardless of whether there is a spatial feature attached.Note: This is a large dataset. Metadata and Downloads are available at: https://data.fs.usda.gov/geodata/edw/datasets.php?xmlKeyword=FACTS+common+attributesTo download FACTS activities layers, search for the activity types you want, such as timber harvest or hazardous fuels treatments. The Forest Service's Natural Resource Manager (NRM) Forest Activity Tracking System (FACTS) is the agency standard for managing information about activities related to fire/fuels, silviculture, and invasive species. This feature class contains the FACTS attributes most commonly needed to describe FACTS activities.

TransportationThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau, displays primary roads, secondary roads, local roads and railroads in the United States. According to the USCB, "This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways."Interstates 20 and 635Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (TIGERweb/Transportation) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 155 (Series Information for All Roads County-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Transportation - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Census Feature Class Codes (CFCC)For feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

The feature class indicates the specific types of motorized vehicles allowed on the designated routes and their seasons of use. The feature class is designed to be consistent with the MVUM (Motor Vehicle Use Map). It is compiled from the GIS Data Dictionary data and NRM Infra tabular data that the administrative units have prepared for the creation of their MVUMs. Only roads with a SYMBOL attribute value of 1, 2, 3, 4, 11, and 12 are Forest Service System roads and contain data concerning their availability for OHV (Off Highway Vehicle) use. This data is published and refreshed on a unit by unit basis as needed. Data for each individual unit must be verified and proved consistent with the published MVUMs prior to publication.The Forest Service's Natural Resource Manager (NRM) Infrastructure (Infra) is the agency standard for managing and reporting information about inventory of constructed features and land units as well as the permits sold to the general public and to partners. MetadataThis 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 https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_MVUM_01/MapServer/1 Metadata For complete information, please visit https://data.gov.

The Range Vegetation Improvement feature class depicts the area planned and accomplished areas treated as a part of the Range Vegetation Improvement program of work, funded through the budget allocation process and reported through the Forest Service Activity Tracking System (FACTS) database within the Natural Resource Manager (NRM) suite of applications. Activities are self-reported by Forest Service Units. Metadata

NOTE: The IRWM polygons overlap each other. This polygon Feature Class includes IRWM planning regions participating in the State of California Department of Water Resources IRWM grant program. The data will be included as a component of the DWR Atlas of GIS data and be utilized as the feature data set for GIS projects requiring location of IRWM planning regions. This dataset is not to be utilized for survey purpose and is not designed to that accuracy level. Size of initial data set is 622 KB. Including additional attributes, the dataset is not expected to exceed 700 KB in size. Updates to this data will be once a year or as needed in conjunction with the IRWM Regional Boundaries dataset updates. Some IRWM Regions may decide not to participate in the grant program and will be in the attribute table with no spatial reference. An attribute called “Status” may be added to the feature class table. The data steward will be in charge of updating the dataset and responsible for any versioning. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR GIS Spatial Data Standards. DWR makes no warranties or guarantees, either expressed or implied, as to the completeness, accuracy or correctness of the data, nor accepts or assumes any liability arising from or for any incorrect, incomplete or misleading subject data. Comments, problems improvements, updates or suggestions should be forwarded to the official GIS Data Steward as available and appropriate. The Region Acceptance Process (RAP) is a component of the Integrated Regional Water Management (IRWM) Program Guidelines and is used to evaluate and accept an IRWM region into the IRWM grant program. The RAP is not a grant funding application; however, acceptance of the composition of an IRWM region (including the IRWM region’s boundary) is required for DWR IRWM grant funding eligibility. This dataset includes:-the boundaries of the most current IRWM Regions (as submitted to DWR by the respective IRWM planning region)-their RAP status (Accepted or Conditional) as conferred by DWR the year each entity participated in the RAP-a descriptive field noting the date of any subsequent IRWM boundary changes submitted and accepted by DWR.

WDFW cartography staff create map content designed to inform map viewers where certain types of recreation opportunities are promoted on WDFW Wildlife Areas. This layer is created from WDFW parcel data using parcel attributes to define where these targeted recreation opportunities exist. There are currently two focused map content areas, one is to support the GoHunt application where hunting opportunities are promoted. The other is used to identify WDFW lands where a Washington Discover Pass is required. The Recreation Access Code, managed in the WDFW_Lands feature class, is used to define which parcels are dissolved into this feature class. Recreation Access Code values that are brought across as a result of a standard definition query are: 1 - Parcels managed within a designated Wildlife Area and not restricted in any way for being displayed on GoHunt or Discover Pass maps; 4 - Parcels designated by the Wildlife Program for exclusion from GoHunt activities; 5 - Parcels designated by the Wildlife Program for exclusion from the Discover Pass. Users of this feature class can use ArcMap definition queries to appropriately display either GoHunt or Discover Pass map content. This feature class displays the finest scale of the Wildlife Area administrative hierarchy that consists of Widlife Area Complexes, Wildlife Areas and Wildlife Area Units. There are several fields in this data that can be used to label maps with the Wildlife Area Unit name.

Summary

This feature class documents the fire history on CMR from 1964 - present. This is 1 of 2 feature classes, a polygon and a point. This data has a variety of different origins which leads to differing quality of data. Within the polygon feature class, this contains perimeters that were mapped using a GPS, hand digitized, on-screen digitized, and buffered circles to the estimated acreage. These 2 files should be kept together. Within the point feature class, fires with only a location of latitude/longitude, UTM coordinate, TRS and no estimated acreage were mapped using a point location. GPS started being used in 1992 when the technology became available. Records from FMIS (Fire Management Information System) were reviewed and compared to refuge records. Polygon data in FMIS only occurs from 2012 to current and many acreage estimates did not match. This dataset includes ALL fires no matter the size.

This feature class documents the fire history on CMR from 1964 - present. This is 1 of 2 feature classes, a polygon and a point. This data has a variety of different origins which leads to differing quality of data. Within the polygon feature class, this contains perimeters that were mapped using a GPS, hand digitized, on-screen digitized, and buffered circles to the estimated acreage. These 2 files should be kept together. Within the point feature class, fires with only a location of latitude/longitude, UTM coordinate, TRS and no estimated acreage were mapped using a point location. GPS started being used in 1992 when the technology became available. Data origins include: Data origins include: 1) GPS Polygon-data (Best), 2) GPS Lat/Long or UTM, 3)TRS QS, 4)TRS Point, 6)Hand digitized from topo map, 7) Circle buffer, 8)Screen digitized, 9) FMIS Lat/Long. Started compiling fire history of CMR in 2007. This has been a 10 year process.FMIS doesn't include fires polygons that are less than 10 acres. This dataset has been sent to FMIS for FMIS records to be updated with correct information. The spreadsheet contains 10-15 records without spatial information and weren't included in either feature class. Fire information from 1964 - 1980 came from records Larry Eichhorn, BLM, provided to CMR staff. Mike Granger, CMR Fire Management Officer, tracked fires on an 11x17 legal pad and all this information was brought into Excel and ArcGIS. Frequently, other information about the fires were missing which made it difficult to back track and fill in missing data. Time was spent verifiying locations that were occasionally recorded incorrectly (DMS vs DD) and converting TRS into Lat/Long and/or UTM. CMR is divided into 2 different UTM zones, zone 12 and zone 13. This occasionally caused errors in projecting. Naming conventions caused confusion. Fires are frequently names by location and there are several "Soda Creek", "Rock Creek", etc fires. Fire numbers were occasionally missing or incorrect. Fires on BLM were included if they were "Assists". Also, fires on satellite refuges and the district were also included. Acreages from GIS were compared to FMIS acres. Please see documentation in ServCat (URL) to see how these were handled.

MassGIS Level 3 Parcel Data: Data Fiscal Year: Aquinnah 2019, Chilmark 2020, Edgartown 2021, Gosnold 2015, Oak Bluffs 2021, Tisbury 2021, West Tisbury 2021.Building Info Table: Acquired by MVC from Town Assessors in FY20.Downloaded from MassGIS,, this polygon file represents the parcel bounds for the 7 towns in Dukes County MA (Aquinnah, Chilmark, Edgartown, Godnold, Oak Bluffs, Tisbury, West Tisbury). Each town has their own parcel data consultant and then the data are forwarded to MassGIS for final processing. All data comply with the MassGIS Level 3 Parcel Data Standard. This file geodatabase only includes the TaxPar feature class and Assess table for each town. All TaxPar feature classes were appended into one feature class (Parcels_duk) by the MVC.Each assess table is utilized in that town's respective relationship join (1 to Many) for linking the parcel polygon to the related record(s) in the Assess table. The Assess Table contains info about ownership and assessed values. This is not a detailed building table. If there are multiple owners associated with a property, then the Assess table will have multiple records for that property/parcel (such as for condo parcels).Each building table is utilized in that town's respective relationship join (1 to Many) for linking the parcel polygon to the related record(s) in the Bldg table. The Bldg (building) table contains info about each building on the parcel (such as number of bedrooms, number of bathrooms, the living area square footage, etc.). NOTES of CAUTION: The Living Area Square Footage may not represent the exact same thing in each town. As a generalization, Living Area is interior space that is heated. Regarding West Tisbury, their building table only contains info for one building on the parcel. It is uncertain at this time if the info is the most recent, most primary, or some kind of summarization where multiple buildings on a parcel exist.The field of [assess_mYB] represents the Minimum/Earliest Year Built for any building on the parcel and is appended to the TaxPar feature class based on an analysis of the info provided in the building table. This field [assess_mYB] is utilized in the Historic Structures App found in ArcGIS OnLine.

This Quarter Section feature class depicts PLSS Second Divisions . PLSS townships are subdivided in a spatial hierarchy of first, second, and third division. These divisions are typically aliquot parts ranging in size from 640 acres to 160 to 40 acres, and subsequently all the way down to 2.5 acres. The data in this feature class was translated from the PLSSSecondDiv feature class in the original production data model, which defined the second division for a specific parcel of land. Metadata

This polygon feature class shows the spatial extent and boundaries of Areas of Critical Environmental Concern that have become officially designated by the BLM. These polygon features were previously in a pre-designated status (i.e. being considered as areas to be eventually designated as official ACEC designated polygons). Once these polygon feature left the Pre-Designated phase (transitioned from a Considered to Designated status), they were removed from the ACEC Pre-designated polygon feature class and placed in this ACEC Designated polygon feature class. This dataset is a subset of the official national dataset, containing features and attributes intended for public release and has been optimized for online map service performance. The Implementation Guide represents the official national dataset from which this dataset was derived.

The FinalFirePerimeter polygon layer represents final mapped wildland fire perimeters. This feature class is a subset of the FirePerimeters feature class. Incidents of 10 acres or greater in size are expected. Incidents smaller than 10 acres in size may also be included. Data are maintained at the Forest/District level, or their equivalent, to track the area affected by wildland fire. Records in FirePerimeter include perimeters for wildland fires that have corresponding records in FIRESTAT, which is the authoritative data source for all wildland fire reports. FIRESTAT, the Fire Statistics System computer application, required by the USFS for all wildland fire occurrences on National Forest System Lands or National Forest-protected lands, is used to enter and maintain information from the Individual Fire Report (FS-5100-29).National USFS fire occurrence final fire perimeters where wildland fires have historically occurred on National Forest System Lands and/or where protection is the responsibility of the US Forest Service. Knowing where wildland fire events have happened in the past is critical to land management efforts in the future.This data is utilized by fire & aviation staffs, land managers, land planners, and resource specialists on and around National Forest System Lands.*This data has been updated to match 2021 National GIS Data Dictionary Standards.Metadata and Downloads

LouVelo is a docked bikeshare program owned by Louisville Metro Government and operated by Cyclehop since May of 2017. The System includes Approximately 250 bikes, 25 Docked Stations in Louisville, and an additional 3 stations owned and operated by the City of Jeffersonville in Partnership with Cyclehop. These data will be updated on a monthly basis to show trends in station use. These data are updated and maintained for use in the Louisville Metro Open Data Portal LouVelo Dashboard to show ridership for the entirety of the program. Some stations have been relocated since the programs founding. For up to date information on dock locations please view the system map on the LouVelo website. This dashboard is maintained by Louisville Metro Public Works.For any questions please contact:James GrahamMobility CoordinatorLouisville Metro Public WorksDivision of Transportation444 S. 5th, St, Suite 400Louisville, KY 40202(502) 574-6473james.graham@louisvilleky.govFor more information about the LouVelo bikeshare program please visit their website.