Instructions on the Open Data Portal process for the Open Data Team.This is a step by step instructional document detailing the following processes:PUBLISH DATA TO ARCGIS SERVER MANAGE WEB LAYERS IN PORTAL CREATE FEATURE LAYER IN ARCGIS ONLINEHOW TO ADD DOCUMENTS AND FILESSHARE STATIC FILES THROUGH THE COLLABORATIONCHANGE ITEMS OWNER TO OPEN_DATA_ADMIN

BIOS is an online map viewer designed to enable the management, visualization, and analysis of biogeographic data collected by the California Department of Fish and Wildlife (CDFW) and partner organizations. BIOS facilitates the sharing of those data within CDFW as well as with the public. BIOS integrates GIS, relational database management, and ESRI's ArcGIS Server technology to create a statewide, integrated information management tool that can be accessed via the Internet. BIOS home page: https://www.wildlife.ca.gov/Data/BIOSBIOS public dataset GIS downloads are available from:ftp://ftp.dfg.ca.gov/BDB/GIS/BIOS/Public_Datasets/

This data set is part of an ongoing project to consolidate interagency fire point data. The incorporation of all available historical data is in progress.The InFORM (Interagency Fire Occurrence Reporting Modules) FODR (Fire Occurrence Data Records) are the official record of fire events. Built on top of IRWIN (Integrated Reporting of Wildland Fire Information), the FODR starts with an IRWIN record and then captures the final incident information upon certification of the record by the appropriate local authority. This service contains all wildland fire incidents from the InFORM FODR incident service that meet the following criteria:Categorized as a Wildfire (WF) or Prescribed Fire (RX) recordIs Valid and not "quarantined" due to potential conflicts with other recordsNo "fall-off" rules are applied to this service.Service is a real time display of data.Warning: Please refrain from repeatedly querying the service using a relative date range. This includes using the “(not) in the last” operators in a Web Map filter and any reference to CURRENT_TIMESTAMP. This type of query puts undue load on the service and may render it temporarily unavailable.Attributes:ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency initial attack fire suppression expenditures. for A, B, C & D size class fires on FS lands.ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.CalculatedAcresA measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire. More specifically, the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands. The minimum size must be 0.1.ContainmentDateTimeThe date and time a wildfire was declared contained. ControlDateTimeThe date and time a wildfire was declared under control.CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.CreatedOnDateTimeDate/time that the Incident record was created.IncidentSizeReported for a fire. The minimum size is 0.1.DiscoveryAcresAn estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.EstimatedCostToDateThe total estimated cost of the incident to date.FinalAcresReported final acreage of incident.FinalFireReportApprovedByTitleThe title of the person that approved the final fire report for the incident.FinalFireReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.FinalFireReportApprovedDateThe date that the final fire report was approved for the incident.FireBehaviorGeneralA general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography. FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. FireOutDateTimeThe date and time when a fire is declared out. FSJobCodeA code use to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode.FSOverrideCodeA code used to indicate the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.GACCA code that identifies one of the wildland fire geographic area coordination center at the point of origin for the incident.A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.IncidentNameThe name assigned to an incident.IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category further breaks down the Event Kind into more specific event categories.IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.InitialLatitudeThe latitude location of the initial reported point of origin specified in decimal degrees.InitialLongitudeThe longitude location of the initial reported point of origin specified in decimal degrees.InitialResponseDateTimeThe date/time of the initial response to the incident. More specifically when the IC arrives and performs initial size up. IsFireCauseInvestigatedIndicates if an investigation is underway or was completed to determine the cause of a fire.IsFSAssistedIndicates if the Forest Service provided assistance on an incident outside their jurisdiction.IsReimbursableIndicates the cost of an incident may be another agency’s responsibility.IsTrespassIndicates if the incident is a trespass claim or if a bill will be pursued.LocalIncidentIdentifierA number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year.ModifiedBySystemArcGIS Server username of system that last modified the IRWIN Incident record.ModifiedOnDateTimeDate/time that the Incident record was last modified.PercentContainedIndicates the percent of incident area that is no longer active. Reference definition in fire line handbook when developing standard.POOCityThe closest city to the incident point of origin.POOCountyThe County Name identifying the county or equivalent entity at point of origin designated at the time of collection.POODispatchCenterIDA unique identifier for the dispatch center that intersects with the incident point of origin. POOFipsThe code which uniquely identifies counties and county equivalents. The first two digits are the FIPS State code and the last three are the county code within the state.POOJurisdictionalAgencyThe agency having land and resource management responsibility for a incident as provided by federal, state or local law. POOJurisdictionalUnitNWCG Unit Identifier to identify the unit with jurisdiction for the land where the point of origin of a fire falls. POOJurisdictionalUnitParentUnitThe unit ID for the parent entity, such as a BLM State Office or USFS Regional Office, that resides over the Jurisdictional Unit.POOLandownerCategoryMore specific classification of land ownership within land owner kinds identifying the deeded owner at the point of origin at the time of the incident.POOLandownerKindBroad classification of land ownership identifying the deeded owner at the point of origin at the time of the incident.POOProtectingAgencyIndicates the agency that has protection responsibility at the point of origin.POOProtectingUnitNWCG Unit responsible for providing direct incident management and services to a an incident pursuant to its jurisdictional responsibility or as specified by law, contract or agreement. Definition Extension: - Protection can be re-assigned by agreement. - The nature and extent of the incident determines protection (for example Wildfire vs. All Hazard.)POOStateThe State alpha code identifying the state or equivalent entity at point of origin.PredominantFuelGroupThe fuel majority fuel model type that best represents fire behavior in the incident area, grouped into one of seven categories.PredominantFuelModelDescribes the type of fuels found within the majority of the incident area. UniqueFireIdentifierUnique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = POO protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters) FORIDUnique identifier assigned to each incident record in the FODR database.

In 2007, the California Ocean Protection Council initiated the California Seafloor Mapping Program (CSMP), designed to create a comprehensive seafloor map of high-resolution bathymetry, marine benthic habitats, and geology within California’s State Waters. The program supports a large number of coastal-zone- and ocean-management issues, including the California Marine Life Protection Act (MLPA) (California Department of Fish and Wildlife, 2008), which requires information about the distribution of ecosystems as part of the design and proposal process for the establishment of Marine Protected Areas. A focus of CSMP is to map California’s State Waters with consistent methods at a consistent scale. The CSMP approach is to create highly detailed seafloor maps through collection, integration, interpretation, and visualization of swath sonar data (the undersea equivalent of satellite remote-sensing data in terrestrial mapping), acoustic backscatter, seafloor video, seafloor photography, high-resolution seismic-reflection profiles, and bottom-sediment sampling data. The map products display seafloor morphology and character, identify potential marine benthic habitats, and illustrate both the surficial seafloor geology and shallow (to about 100 m) subsurface geology. It is emphasized that the more interpretive habitat and geology data rely on the integration of multiple, new high-resolution datasets and that mapping at small scales would not be possible without such data. This approach and CSMP planning is based in part on recommendations of the Marine Mapping Planning Workshop (Kvitek and others, 2006), attended by coastal and marine managers and scientists from around the state. That workshop established geographic priorities for a coastal mapping project and identified the need for coverage of “lands” from the shore strand line (defined as Mean Higher High Water; MHHW) out to the 3-nautical-mile (5.6-km) limit of California’s State Waters. Unfortunately, surveying the zone from MHHW out to 10-m water depth is not consistently possible using ship-based surveying methods, owing to sea state (for example, waves, wind, or currents), kelp coverage, and shallow rock outcrops. Accordingly, some of the data presented in this series commonly do not cover the zone from the shore out to 10-m depth. This data is part of a series of online U.S. Geological Survey (USGS) publications, each of which includes several map sheets, some explanatory text, and a descriptive pamphlet. Each map sheet is published as a PDF file. Geographic information system (GIS) files that contain both ESRI ArcGIS raster grids (for example, bathymetry, seafloor character) and geotiffs (for example, shaded relief) are also included for each publication. For those who do not own the full suite of ESRI GIS and mapping software, the data can be read using ESRI ArcReader, a free viewer that is available at http://www.esri.com/software/arcgis/arcreader/index.html (last accessed September 20, 2013). The California Seafloor Mapping Program is a collaborative venture between numerous different federal and state agencies, academia, and the private sector. CSMP partners include the California Coastal Conservancy, the California Ocean Protection Council, the California Department of Fish and Wildlife, the California Geological Survey, California State University at Monterey Bay’s Seafloor Mapping Lab, Moss Landing Marine Laboratories Center for Habitat Studies, Fugro Pelagos, Pacific Gas and Electric Company, National Oceanic and Atmospheric Administration (NOAA, including National Ocean Service–Office of Coast Surveys, National Marine Sanctuaries, and National Marine Fisheries Service), U.S. Army Corps of Engineers, the Bureau of Ocean Energy Management, the National Park Service, and the U.S. Geological Survey. These web services for the Offshore of Coal Oil Point map area includes data layers that are associated to GIS and map sheets available from the USGS CSMP web page at https://walrus.wr.usgs.gov/mapping/csmp/index.html. Each published CSMP map area includes a data catalog of geographic information system (GIS) files; map sheets that contain explanatory text; and an associated descriptive pamphlet. This web service represents the available data layers for this map area. Data was combined from different sonar surveys to generate a comprehensive high-resolution bathymetry and acoustic-backscatter coverage of the map area. These data reveal a range of physiographic including exposed bedrock outcrops, large fields of sand waves, as well as many human impacts on the seafloor. To validate geological and biological interpretations of the sonar data, the U.S. Geological Survey towed a camera sled over specific offshore locations, collecting both video and photographic imagery; these “ground-truth” surveying data are available from the CSMP Video and Photograph Portal at https://doi.org/10.5066/F7J1015K. The “seafloor character” data layer shows classifications of the seafloor on the basis of depth, slope, rugosity (ruggedness), and backscatter intensity and which is further informed by the ground-truth-survey imagery. The “potential habitats” polygons are delineated on the basis of substrate type, geomorphology, seafloor process, or other attributes that may provide a habitat for a specific species or assemblage of organisms. Representative seismic-reflection profile data from the map area is also include and provides information on the subsurface stratigraphy and structure of the map area. The distribution and thickness of young sediment (deposited over the past about 21,000 years, during the most recent sea-level rise) is interpreted on the basis of the seismic-reflection data. The geologic polygons merge onshore geologic mapping (compiled from existing maps by the California Geological Survey) and new offshore geologic mapping that is based on integration of high-resolution bathymetry and backscatter imagery seafloor-sediment and rock samplesdigital camera and video imagery, and high-resolution seismic-reflection profiles. The information provided by the map sheets, pamphlet, and data catalog has a broad range of applications. High-resolution bathymetry, acoustic backscatter, ground-truth-surveying imagery, and habitat mapping all contribute to habitat characterization and ecosystem-based management by providing essential data for delineation of marine protected areas and ecosystem restoration. Many of the maps provide high-resolution baselines that will be critical for monitoring environmental change associated with climate change, coastal development, or other forcings. High-resolution bathymetry is a critical component for modeling coastal flooding caused by storms and tsunamis, as well as inundation associated with longer term sea-level rise. Seismic-reflection and bathymetric data help characterize earthquake and tsunami sources, critical for natural-hazard assessments of coastal zones. Information on sediment distribution and thickness is essential to the understanding of local and regional sediment transport, as well as the development of regional sediment-management plans. In addition, siting of any new offshore infrastructure (for example, pipelines, cables, or renewable-energy facilities) will depend on high-resolution mapping. Finally, this mapping will both stimulate and enable new scientific research and also raise public awareness of, and education about, coastal environments and issues. Web services were created using an ArcGIS service definition file. The ArcGIS REST service and OGC WMS service include all Offshore Coal Oil Point map area data layers. Data layers are symbolized as shown on the associated map sheets.

**Suggested to use 'Download' button instead of 'Open in ArcGIS Pro'The REST service page displays all data provided in this layer package: https://arcgis.dnr.alaska.gov/arcgis/rest/services/Mapper/Surface_Classification/FeatureServer

Retirement Notice: This item is in mature support as of June 2024 and will be retired in December 2026. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version.Areas protected from conversion include areas that are permanently protected and managed for biodiversity such as Wilderness Areas and National Parks. In addition to protected lands, portions of areas protected from conversion includes multiple-use lands that are subject to extractive uses such as mining, logging, and off-highway vehicle use. These areas are managed to maintain a mostly undeveloped landscape including many areas managed by the Bureau of Land Management and US Forest Service. The Protected Areas Database of the United States classifies lands into four GAP Status classes. This layer displays lands managed for biodiversity conservation (GAP Status 1 and 2) and multiple-use lands (GAP Status 3). Dataset SummaryPhenomenon Mapped: Protected and multiple-use lands (GAP Status 1, 2, and 3) Units: MetersCell Size: 30.92208102 metersSource Type: ThematicPixel Type: 8-bit unsigned integerData Coordinate System: WGS 1984Mosaic Projection: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, the US Virgin Islands, Guam, Northern Mariana Islands and American Samoa.Source: USGS National Gap Analysis Program PAD-US version 3.0Publication Date: July 2022 ArcGIS Server URL: https://landscape10.arcgis.com/arcgis/ This layer displays protected areas from the Protected Areas Database of the United States version 3.0 created by the USGS National Gap Analysis Program. This layer displays areas managed for biodiversity where natural disturbances are allowed to proceed or are mimicked by management (GAP Status 1), areas managed for biodiversity where natural disturbance is suppressed (GAP Status 2), and multiple-use lands where extract activities are allowed (GAP Status 3). The source data for this layer are available here. A feature layer published from this dataset is also available. The polygon vector layer was converted to raster layers using the Polygon to Raster Tool using the National Elevation Dataset 1 arc second product as a snap raster. The service behind this layer was published with 8 functions allowing the user to select different views of the service. Other layers created from this service using functions include:USA Protected AreasUSA Unprotected AreasUSA Protected Areas - Gap Status 1-4USA Protected Areas - Gap Status 1USA Protected Areas - Gap Status 2USA Protected Areas - Gap Status 3USA Protected Areas - Gap Status 4 What can you do with this layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application. Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "Protected from Land Cover Conversion" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "Protected from Land Cover Conversion" in the search box, browse to the layer then click OK. In ArcGIS Pro you can use the built-in raster functions to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.

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

The California State Water Resources Control Board is currently in the process of improving the functionality and accessibility of information residing in their Water Quality Control Plans (aka Basin Plans). In order to achieve this, the data (i.e. statewide water quality objectives, beneficial uses, applicable TMDLs, etc.), are being transferred to a standardized digital format and linked to applicable surface water features. This dataset is limited to the beneficial uses data, while the water quality objectives, applicable TMDLs, etc. will be released at a later date. Data formats will include GIS data layers and numerous nonspatial data tables. The GIS layers contain hydrography features derived from a 2012 snapshot of the high-resolution (1:24000 scale) National Hydrography Dataset with added attribution. Nonspatial tables will contain various textual and numeric data from the Regional Basin and State Plans. The extent of the dataset covers the state of California and the non-spatial tables reflect the information and elements from the various plans used up to 2020. The GIS layers and associated attribution will enable the future integration of the various elements of the Basin Plans to ensure that all applicable Basin Plan requirements for a particular waterbody can be determined in a quick and precise manner across different modern mediums. The data are being managed and the project implemented by State and Regional Water Board staff using ESRI's ArcGIS Server and ArcSDE technology.The statewide layer is only provided as a map image layer service. The data is available as feature layer services by Regional Board extract. To view all regional board feature layer extracts go to the Basin Plan GIS Data Library Group here.

The Gap Analysis Program (GAP) is an element of the U.S. Geological Survey (USGS). GAP helps to implement the Department of Interior?s goals of inventory, monitoring, research, and information transfer. GAP has three primary goals: 1 Identify conservation gaps that help keep common species common; 2 Provide conservation information to the public so that informed resource management decisions can be made; and 3 Facilitate the application of GAP data and analysis to specific resource management activities. To implement these goals, GAP carries out the following objectives: --Map the land cover of the United States --Map predicted distributions of vertebrate species for the U.S. --Map the location, ownership and stewardship of protected areas --Document the representation of vertebrate species and land cover types in areas managed for the long-term maintenance of biodiversity --Provide this information to the public and those entities charged with land use research, policy, planning, and management --Build institutional cooperation in the application of this information to state and regional management activities. GAP provides the following data and web services: The Protected Areas Database of the United States (PAD-US) is a geodatabase that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The PADUS GAP Status Layer web service can be found at http://gis1.usgs.gov/arcgis/rest/services/gap/PADUS_Status/MapServer . The Land Cover Data creates a seamless data set for the contiguous United States from the four regional Gap Analysis Projects and the LANDFIRE project. The Raster data in both ArcGIS Grid and ERDAS Imagine format is available for download at http://gis1.usgs.gov/csas/gap/viewer/land_cover/Map.aspx . In addition to the raster datasets the data is available in Web Mapping Services (WMS) format for each of the six NVC classification levels (Class, Subclass, Formation, Division, Macrogroup, Ecological System) at the following links. http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Class_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Subclass_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Formation_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Division_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Macrogroup_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_Ecological_Systems_Landuse/MapServer The GAP species range data show a coarse representation of the total areal extent of a species or the geographic limits within which a species can be found (Morrison and Hall 2002). The GAP species distribution models represent the areas where species are predicted to occur based on habitat associations. A full report documenting the parameters used in each species model can be found via: http://gis1.usgs.gov/csas/gap/viewer/species/Map.aspx Web map services for species distribution models can be accessed from: http://gis1.usgs.gov/arcgis/rest/services/NAT_Species_Birds http://gis1.usgs.gov/arcgis/rest/services/NAT_Species_Mammals http://gis1.usgs.gov/arcgis/rest/services/NAT_Species_Amphibians http://gis1.usgs.gov/arcgis/rest/services/NAT_Species_Reptiles A table listing all of GAP's available web map services can be found here: http://gapanalysis.usgs.gov/species/data/web-map-services/

Retirement Notice: This item is in mature support as of June 2024 and will be retired in December 2026. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. In the United States, areas that are protected from development and managed for biodiversity conservation include Wilderness Areas, National Parks, National Wildlife Refuges, and Wild & Scenic Rivers. Understanding the geographic distribution of these protected areas and their level of protection is an important part of landscape-scale planning. The Protected Areas Database of the United States classifies lands into four GAP Status classes. This layer displays the two highest levels of protection GAP Status 1 and 2. These two classes are commonly referred to as protected areas. Dataset SummaryPhenomenon Mapped: Areas protected from development and managed to maintain biodiversity (GAP Status 1 and 2) Units: MetersCell Size: 30.92208102 metersSource Type: ThematicPixel Type: 8-bit unsigned integerData Coordinate System: WGS 1984Mosaic Projection: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, the US Virgin Islands, Guam, Northern Mariana Islands and American Samoa.Source: USGS National Gap Analysis Program PAD-US version 3.0Publication Date: July 2022 ArcGIS Server URL: https://landscape10.arcgis.com/arcgis/ This layer displays protected areas from the Protected Areas Database of the United States version 3.0 created by the USGS National Gap Analysis Program. This layer displays GAP Status 1, areas managed for biodiversity where natural disturbances are allowed to proceed or are mimicked by management, and GAP Status 2, areas managed for biodiversity where natural disturbance is suppressed. The source data for this layer are available here. A feature layer published from this dataset is also available. The polygon vector layer was converted to raster layers using the Polygon to Raster Tool using the National Elevation Dataset 1 arc second product as a snap raster. The service behind this layer was published with 8 functions allowing the user to select different views of the service. Other layers created from this service using functions include:USA Protected from Land Cover ConversionUSA Unprotected AreasUSA Protected Areas - Gap Status 1-4USA Protected Areas - Gap Status 1USA Protected Areas - Gap Status 2USA Protected Areas - Gap Status 3USA Protected Areas - Gap Status 4

The Department of Fish and Game - Division of Wildlife Conservation's game management units and subunits are the most requested of the Division's GIS data. Hunting and trapping regulations and other wildlife management issues often refer geographically to the effected Game Management Unit (GMU). This file gives the user access to the currently available digital representation of the GMU/UCUs. The purpose of the GMU and associated Subunits and Uniform coding units is to give a uniform, geographic based coding system for all State of Alaska wildlife population and habitat management and regulations. This data can be used for mapping or analysis purposes assuming it is used with comparable data.Uniform Coding UnitsPrior to 1982, Alaska Department of Fish and Game - Division of Wildlife Conservation (ADFG-DWC) had a variety of coding schemes (18) relating harvest and management information to geographical areas. This made it difficult when comparing statewide wildlife information gathered across the state. In 1982, a new standardized statewide, geographically-based, hierarchy system of coding was created called the Uniform Coding Unit or UCU system. Game management units (GMUs), Subunits, and uniform coding units (UCUs) are the underlying geographic foundation of the wildlife and habitat management and regulations for ADFG-DWC. The GMU/UCU system consists of five Regions which are divided into twenty-six (26) Game Management Units (GMUs). Many of the GMUs are divided into Subunits (e.g. GMU 15 has three (3) Subunits, 15A, 15B, and 15C). GMUs that are not divided into subunits have a "Z" designation for the subunit. GMUs and Subunits are further divided into Major Drainages, Minor Drainages and Specific Areas. The smallest of these areas (down to the "specific area") is referred to as a Uniform Coding Unit (UCU) and has a unique 10 character code associated with it. (NOTE: UCU layer is for internal and official use only, not for public use or distribution). The UCU code is used for geographically classifying harvest and management information. Data that cannot be tied to a specific code can be generalized to the next higher level of the hierarchy. For example:a location description that is within multiple "specific areas" within a "minor drainage" can be coded to the minor code with a "00" for the specific area. Unknown "minor drainages" can be coded to the "major drainage" level, etc. If the subunit is unknown or the area covers multiple subunits within a unit, the subunit can be specified as a "Z" code (e.g. an area within subunits 15A and 15B could be recorded as 15Z). If a geographic location covers multiple units or the unit is unknown, the most general code (statewide code) is recorded as 27Z-Z00. The original hardcopy master maps were drawn to portray the UCUs fairly accurately geographically, but were not necessarily precisely drawn (i.e. left vs. right bank of a river, or exact ridge line). Each UCU was represented by drawing boundaries on USGS 1:250,000 scale quadrangle maps with a thick magic marker. A list (database) of place-names and their corresponding UCU codes was created and is still used today to assign permit, harvest, and sealing information to one of these geographic areas. In 1988, the UCU boundaries were digitized (traced) from the original maps into a computerized Geographic Information System (ArcInfo). Minor changes were made in 1989. Effective July 1, 2006 - GMU 24 is now divided up into four subunit 24A, 24B, 24C, 24D. - GMU 21A and 21B - - boundary has been modified. Phase I2006-2008 - initial clean-up of boundaries for GMU 6, 9, 10, 12, 16, 19, 20, 25. These modifications have NOT been verified against the UCU master list or by area biologists. -ras Jan 2009 - Priority has shifted to getting the bulk of the updates into the master. Verification and modifications based on the UCU list and the AB corrections will come at a later date. This shift is to attempt to get the master into a permanent SDE GDB, set it up with the GDB topology, make additional clean-up/edits using the GDB tools, set up versioning, make it easier to replicate to area offices, and to take advantage of the tools/features available thru ArcGIS Server with versioned GDBs. June 2009 - initial clean-up of boundaries for Southeast (GMU 1-5), GMU 17, and GMU 18. These have NOT been verified against the UCU master list or by area biologists. -ras July 1 2009 - initial clean-up of boundaries for GMU 7 and 8. Also some adjustments for 25D based on the NHD 2008 version and ArcHydro Tools "raindrop" feature. These have NOT been verified against the UCU master list or by area biologists. -ras Sept 17, 2009 - initial clean-up of boundaries for GMU 13. These modifications have NOT been verified against the UCU master list or by area biologists. -ras Oct 21, 2009 - initial clean-up of boundaries for GMU 14 These modification have NOT been verified against the UCU master list or by area biologists. -rasNov 19, 2009 - initial clean-up of boundaries for GMU 15. These modifications have NOT been verified against the UCU master list or by area biologists. -ras Dec 7, 2009 - initial clean-up of boundaries for GMU 22. These modification have NOT been verified against the UCU master list or by area biologists. -ras March 3, 2010 - initial clean-up of boundaries for GMU 23. These modification have NOT been verified against the UCU master list or by area biologists. -rasApril 10, 2010 - initial clean-up of boundaries for GMU 26. These modification have NOT been verified against the UCU master list or by area biologists. -ras May 2010 - This completes Phase I of refining the UCUs - bulk heads-up re-digitizing of all arcs. Phase II - Converting and establishing procedures for maintaining the master in an Enterprise GDB is underway. Effective July 1, 2010, Region II was split into Region 2 (GMU's 6, 7, 8, 14C, 15) and Region 4 (GMU's 9, 10, 11, 13, 14AB, 16, 17. This version was updated to reflect the change. An archive of the previous version (with Regions I, II, III, and V) is available on request as GMUMaster_063010. -ras2012-present - minor updates continue as needed and time allows, and as newer base maps are used.2014 minor updates continue as needed, including updates to domain listings (not affecting GIS geometry)Effective July 1, 2014- revision to GMU 18/19/21 boundary to clarify/correct previous insufficient boundary description. Passed during Spring 2014 Board of Game.2015 minor changes as needed

Archived WMATA Regional Bus Stops. The dataset includes bus stop identification, location, and inventory information last updated in December 2023 and now retired. On June 29, 2025, Metro launched its new bus network. Bettter Bus is Metro's initiative to improve regional bus service. At the time, it was the first major overhaul in 50 years.Original description: Feed information to Trapeze, Clever, ATIS, Orbital, Cubic (Farebox), Next Bus, WMATA Website, and Metroview (ArcGIS Server Flex Web applications).Data are provided as-is. Questions can be directed to wmata.com/about/contact.

Retirement Notice: This item is in mature support as of June 2024 and will be retired in December 2026. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. The Protected Areas Database of the United States provides a comprehensive map of lands protected by government agencies and private land owners. This database combines federal lands with information on state and local government lands and conservation easements on private lands to create a powerful resource for land-use planning. Dataset SummaryPhenomenon Mapped: Areas mapped in the Protected Areas Data base of the United States (GAP Status 1-4) Units: MetersCell Size: 30.92208102 metersSource Type: ThematicPixel Type: 8-bit unsigned integerData Coordinate System: WGS 1984Mosaic Projection: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, the US Virgin Islands, Guam, Northern Mariana Islands and American Samoa.Source: USGS National Gap Analysis Program PAD-US version 3.0Publication Date: July 2022 ArcGIS Server URL: https://landscape10.arcgis.com/arcgis/ This layer displays lands mapped in Protected Areas Database of the United States version 3.0 created by the USGS National Gap Analysis Program. This layer displays all four GAP Status classes: GAP Status 1 - Areas managed for biodiversity where natural disturbances are allowed to proceedGAP Status 2 - Areas managed for biodiversity where natural disturbance is suppressedGAP Status 3 - Areas protected from land cover conversion but subject to extractive uses such as logging and miningGAP Status 4 - Areas with no known mandate for protection The source data for this layer are available here. A feature layer published from this dataset is also available. The polygon vector layer was converted to raster layers using the Polygon to Raster Tool using the National Elevation Dataset 1 arc second product as a snap raster. The service behind this layer was published with 8 functions allowing the user to select different views of the service. Other layers created from this service using functions include:USA Protected AreasUSA Protected from Land Cover ConversionUSA Unprotected AreasUSA Protected Areas - Gap Status 1USA Protected Areas - Gap Status 2USA Protected Areas - Gap Status 3USA Protected Areas - Gap Status 4

The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service contains all wildland fire incidents from the IRWIN (Integrated Reporting of Wildland Fire Information) integration service that meet the following criteria:Categorized in IRWIN as a Wildfire (WF), Prescribed Fire (RX), or Incident Complex (CX) recordHas not been declared contained, controlled, nor outHas not had fire report record completed (certified)Is Valid and not "quarantined" in IRWIN due to potential conflicts with other records"Fall-off" rules are used to ensure that stale records are not retained. Records are removed from this service under the following conditions:Fire size is less than 10 acres (Size Class A or B), and fire information has not been updated in more than 3 daysFire size is between 10 and 100 acres (Size Class C), and fire information hasn't been updated in more than 8 daysFire size is larger than 100 acres (Size Class D-L), but fire information hasn't been updated in more than 14 days.Fire size used in the fall off rules is from the IncidentSize field.Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed from IRWIN every 5 minutes.Fall-off rules are enforced hourly.Attributes:SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency IA fire suppression on A, B, C & D size class fires on FS lands.ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.ContainmentDateTimeThe date and time a wildfire was declared contained.ControlDateTimeThe date and time a wildfire was declared under control.CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.IncidentSizeReported for a fire. The minimum size is 0.1.DiscoveryAcresAn estimate of acres burning when the fire is first reported by the first person to call in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.EstimatedCostToDateThe total estimated cost of the incident to date.FinalAcresReported final acreage of incident.FinalFireReportApprovedByTitleThe title of the person that approved the final fire report for the incident.FinalFireReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.FinalFireReportApprovedDateThe date that the final fire report was approved for the incident.FireBehaviorGeneralA general category describing how the fire is currently reacting to the influences of fuel, weather, and topography.FireBehaviorGeneral1A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography).FireBehaviorGeneral2A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography). FireBehaviorGeneral3A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography).FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. FireOutDateTimeThe date and time when a fire is declared out. FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.FireStrategyFullSuppPercentIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.FireStrategyPointZonePercentIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.FSJobCodeSpecific to the Forest Service, code use to indicate the FS job accounting code for the incident. Usually displayed as 2 char prefix on FireCode.FSOverrideCodeSpecific to the Forest Service, code used to indicate the FS override code for the incident. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.GACC"A code that identifies the wildland fire geographic area coordination center (GACC) at the point of origin for the incident. A GACC is a facility used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic area."ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.ICS209ReportForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.ICS209ReportForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates and multiple finals (as determined by business rules).IncidentManagementOrganizationThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.IncidentNameThe name assigned to an incident.IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category breaks down the Event Kind into more specific event categories.IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.InitialLatitudeThe latitude of the initial reported point of origin specified in decimal degrees.InitialLongitudeThe longitude of the initial reported point of origin specified in decimal degrees.InitialResponseAcresAn estimate of acres burning at the time of initial response (when the IC arrives and performs initial size up) The minimum size must be 0.1. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.InitialResponseDateTimeThe date/time of the initial response to the incident (when the IC arrives and performs initial size up)IrwinIDUnique identifier assigned to each incident record in IRWIN.IsFireCauseInvestigatedIndicates if an investigation is underway or was completed to determine the cause of a fire.IsFSAssistedIndicates if the Forest Service provided assistance on an incident outside their jurisdiction.IsMultiJurisdictionalIndicates if the incident covers multiple jurisdictions.IsReimbursableIndicates the cost of an incident may be another agency’s responsibility.IsTrespassIndicates if the incident is a trespass claim or if a bill will be pursued.IsUnifiedCommandIndicates whether the incident is being managed under Unified Command. Unified Command is an application of the ICS used when there is more than one agency with incident jurisdiction or when incidents cross political jurisdictions. Under Unified Command, agencies work together through their designated IC at a single incident command post to establish common objectives and issue a single Incident Action Plan.LocalIncidentIdentifierA number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year.ModifiedBySystemArcGIS Server username of system that last modified the IRWIN Incident record.PercentContainedIndicates the percent of incident area that is no longer active. Reference definition in fire line handbook when developing standard.PercentPerimeterToBeContainedIndicates the percent of perimeter left to be completed. This entry is appropriate for full suppression, point/zone protection, and confine fires, or any combination of these strategies. This entry is not used for wildfires managed entirely under a monitor strategy. (Note: Value is not currently being passed by ICS-209)POOCityThe closest city to the incident point of origin.POOCountyThe County Name

IntroductionIRWIN ArcGIS Online GeoPlatform Services The Integrated Reporting of Wildland-Fire Information (IRWIN) Production data is replicated every 60 seconds to the ArcGIS Online GeoPlatform organization so that read-only views can be provided for consumers. This replicated view is called the hosted datastore. The “IRWIN Data” group is a set of Feature Layer views based on the replicated IRWIN layers. These feature layers provide a near real-time feed of all valid IRWIN data. All incidents that have been shared through the integration service since May 20, 2014 are available through this service. The incident data provides the location of existing fires, size, conditions and several other attributes that help classify fires. The IRWIN Data service allows users to create a web map, share it with their organization, or pull it into ArcMap or ArcGIS Pro for more in-depth analysis.InstructionsTo allow the emergency management GIS staff to join the IRWIN Data group, they will need to set up an ArcGIS Online account through our account manager. Please send the response to Samantha Gibbes (Samantha.C.Gibbes@saic.com) and Kayloni Ahtong (kayloni_ahtong@ios.doi.gov). Use the below template and fill in each part as best as possible, where the point of contact (POC) is the person responsible for the account.Reply Email Body: The (name of application) application requests the following user account and access to the IRWIN Data group.POC Name: First name Last name and titlePOC Email: Username: <>_irwin (choose a username, something short, followed by _irwin)Business Justification: Once you are set up with the account, I will coordinate a call to go over any questions.

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.

© 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 versions of the OPDs or LMs or SOBDs should be used for official or legal purposes. The pdf

Historical FiresLast updated on 06/17/2022OverviewThe national fire history perimeter data layer of conglomerated Agency Authoratative perimeters was developed in support of the WFDSS application and wildfire decision support for the 2021 fire season. The layer encompasses the final fire perimeter datasets of the USDA Forest Service, US Department of Interior Bureau of Land Management, Bureau of Indian Affairs, Fish and Wildlife Service, and National Park Service, the Alaska Interagency Fire Center, CalFire, and WFIGS History. Perimeters are included thru the 2021 fire season. Requirements for fire perimeter inclusion, such as minimum acreage requirements, are set by the contributing agencies. WFIGS, NPS and CALFIRE data now include Prescribed Burns. Data InputSeveral data sources were used in the development of this layer:Alaska fire history USDA FS Regional Fire History Data BLM Fire Planning and Fuels National Park Service - Includes Prescribed Burns Fish and Wildlife ServiceBureau of Indian AffairsCalFire FRAS - Includes Prescribed BurnsWFIGS - BLM & BIA and other S&LData LimitationsFire perimeter data are often collected at the local level, and fire management agencies have differing guidelines for submitting fire perimeter data. Often data are collected by agencies only once annually. If you do not see your fire perimeters in this layer, they were not present in the sources used to create the layer at the time the data were submitted. A companion service for perimeters entered into the WFDSS application is also available, if a perimeter is found in the WFDSS service that is missing in this Agency Authoratative service or a perimeter is missing in both services, please contact the appropriate agency Fire GIS Contact listed in the table below.AttributesThis dataset implements the NWCG Wildland Fire Perimeters (polygon) data standard.https://www.nwcg.gov/sites/default/files/stds/WildlandFirePerimeters_definition.pdfIRWINID - Primary key for linking to the IRWIN Incident dataset. The origin of this GUID is the wildland fire locations point data layer. (This unique identifier may NOT replace the GeometryID core attribute)INCIDENT - The name assigned to an incident; assigned by responsible land management unit. (IRWIN required). Officially recorded name.FIRE_YEAR (Alias) - Calendar year in which the fire started. Example: 2013. Value is of type integer (FIRE_YEAR_INT).AGENCY - Agency assigned for this fire - should be based on jurisdiction at origin.SOURCE - System/agency source of record from which the perimeter came.DATE_CUR - The last edit, update, or other valid date of this GIS Record. Example: mm/dd/yyyy.MAP_METHOD - Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality.GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; Digitized-Topo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; OtherGIS_ACRES - GIS calculated acres within the fire perimeter. Not adjusted for unburned areas within the fire perimeter. Total should include 1 decimal place. (ArcGIS: Precision=10; Scale=1). Example: 23.9UNQE_FIRE_ - Unique fire identifier is the Year-Unit Identifier-Local Incident Identifier (yyyy-SSXXX-xxxxxx). SS = State Code or International Code, XXX or XXXX = A code assigned to an organizational unit, xxxxx = Alphanumeric with hyphens or periods. The unit identifier portion corresponds to the POINT OF ORIGIN RESPONSIBLE AGENCY UNIT IDENTIFIER (POOResonsibleUnit) from the responsible unit’s corresponding fire report. Example: 2013-CORMP-000001LOCAL_NUM - Local incident identifier (dispatch number). A number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year. Field is string to allow for leading zeros when the local incident identifier is less than 6 characters. (IRWIN required). Example: 123456.UNIT_ID - NWCG Unit Identifier of landowner/jurisdictional agency unit at the point of origin of a fire. (NFIRS ID should be used only when no NWCG Unit Identifier exists). Example: CORMPCOMMENTS - Additional information describing the feature. Free Text.FEATURE_CA - Type of wildland fire polygon: Wildfire (represents final fire perimeter or last daily fire perimeter available) or Prescribed Fire or UnknownGEO_ID - Primary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature. Globally Unique Identifier (GUID).Cross-Walk from sources (GeoID) and other processing notesAK: GEOID = OBJECT ID of provided file geodatabase (4580 Records thru 2021), other federal sources for AK data removed. CA: GEOID = OBJECT ID of downloaded file geodatabase (12776 Records, federal fires removed, includes RX)FWS: GEOID = OBJECTID of service download combined history 2005-2021 (2052 Records). Handful of WFIGS (11) fires added that were not in FWS record.BIA: GEOID = "FireID" 2017/2018 data (416 records) provided or WFDSS PID (415 records). An additional 917 fires from WFIGS were added, GEOID=GLOBALID in source.NPS: GEOID = EVENT ID (IRWINID or FRM_ID from FOD), 29,943 records includes RX.BLM: GEOID = GUID from BLM FPER and GLOBALID from WFIGS. Date Current = best available modify_date, create_date, fire_cntrl_dt or fire_dscvr_dt to reduce the number of 9999 entries in FireYear. Source FPER (25,389 features), WFIGS (5357 features)USFS: GEOID=GLOBALID in source, 46,574 features. Also fixed Date Current to best available date from perimeterdatetime, revdate, discoverydatetime, dbsourcedate to reduce number of 1899 entries in FireYear.Relevant Websites and ReferencesAlaska Fire Service: https://afs.ak.blm.gov/CALFIRE: https://frap.fire.ca.gov/mapping/gis-dataBIA - data prior to 2017 from WFDSS, 2017-2018 Agency Provided, 2019 and after WFIGSBLM: https://gis.blm.gov/arcgis/rest/services/fire/BLM_Natl_FirePerimeter/MapServerNPS: New data set provided from NPS Fire & Aviation GIS. cross checked against WFIGS for any missing perimeters in 2021.https://nifc.maps.arcgis.com/home/item.html?id=098ebc8e561143389ca3d42be3707caaFWS -https://services.arcgis.com/QVENGdaPbd4LUkLV/arcgis/rest/services/USFWS_Wildfire_History_gdb/FeatureServerUSFS - https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_FireOccurrenceAndPerimeter_01/MapServerAgency Fire GIS ContactsRD&A Data ManagerVACANTSusan McClendonWFM RD&A GIS Specialist208-258-4244send emailJill KuenziUSFS-NIFC208.387.5283send email Joseph KafkaBIA-NIFC208.387.5572send emailCameron TongierUSFWS-NIFC208.387.5712send emailSkip EdelNPS-NIFC303.969.2947send emailJulie OsterkampBLM-NIFC208.258.0083send email Jennifer L. Jenkins Alaska Fire Service 907.356.5587 send email

A data delivery application that provides web-based access to of soil, water, climate, land management, and geospatial data produced by Conservation Effects Assessment Project (CEAP) watershed research sites across the United States. Data access via ArcGIS Server and MS SQL Server Enhanced data searches and summary options in Tools Access to high-resolution imagery in the Map>Table of Contents Enhanced graphing options on the Get Data page Transparency sliders for individual map components in the Map>Table of Contents Resources in this dataset:Resource Title: STEWARDS - A data delivery application for the USDA/ARS Conservation Effects Assessment Project. File Name: Web Page, url: https://www.nrrig.mwa.ars.usda.gov/stewards/stewards.html