The way to access Layers Quickly.

Quick Layers is an Add-In for ArcMap 10.6+ that allows rapid access to the DNR's Geospatial Data Resource Site (GDRS). The GDRS is a data structure that serves core geospatial dataset and applications for not only DNR, but many state agencies, and supports the Minnesota Geospatial Commons. Data added from Quick Layers is pre-symbolized, helping to standardize visualization and map production. Current version: 1.164

To use Quick Layers with the GDRS, there's no need to download QuickLayers from this location. Instead, download a full copy or a custom subset of the public GDRS (including Quick Layers) using GDRS Manager.

Quick Layers also allows users to save and share their own pre-symbolized layers, thus increasing efficiency and consistency across the enterprise.

Installation:

After using GDRS Manager to create a GDRS, including Quick Layers, add the path to the Quick Layers addin to the list of shared folders:
1. Open ArcMap
2. Customize -> Add-In Manager… -> Options
3. Click add folder, and enter the location of the Quick Layers app. For example, if your GDRS is mapped to the V drive, the path would be V:\gdrs\apps\pub\us_mn_state_dnr\quick_layers
4. After you do this, the Quick Layers toolbar will be available. To add it, go to Customize -> Toolbars and select DNR Quick Layers 10

The link below is only for those who are using Quick Layers without a GDRS. To get the most functionality out of Quick Layers, don't install it separately, but instead download it as part of a GDRS build using GDRS Manager.

The way to access Layers Quickly.

Quick Layers is an Add-In for ArcGIS Pro 3 that allows rapid access to the DNR's Geospatial Data Resource Site (GDRS). The GDRS is a data structure that serves core geospatial dataset and applications for not only DNR, but many state agencies, and supports the Minnesota Geospatial Commons. Data added from Quick Layers is pre-symbolized, helping to standardize visualization and map production. Current version: 3.11

To use Quick Layers with the GDRS, there's no need to download QuickLayers from this location. Instead, download a full copy or a custom subset of the public GDRS (including Quick Layers for ArcGIS Pro 3) using GDRS Manager.

Quick Layers also allows users to save and share their own pre-symbolized layers, thus increasing efficiency and consistency across the enterprise.

Installation:

After using GDRS Manager to create a GDRS, including Quick Layers, add the path to the Quick Layers addin to the list of shared folders:
1. Open ArcGIS Pro
2. Project -> Add-In Manager -> Options
3. Click add folder, and enter the location of the Quick Layers Pro app. For example, if your GDRS is mapped to the V drive, the path would be V:\gdrs\apps\pub\us_mn_state_dnr\quick_layers_pro3
4. After you do this, the Quick Layers ribbon will be available. To also add Quick Layers to the Quick Access Toolbar at the top, right click Quick Layers, and select Add to Quick Access Toolbar

The link below is only for those who are using Quick Layers without a GDRS. To get the most functionality out of Quick Layers, don't install it separately, but instead download it as part of a GDRS build using GDRS Manager.

The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses. For more information on the NHDPlus dataset see the NHDPlus v2 User Guide.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territories not including Alaska.Geographic Extent: The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, 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: EPA and USGSUpdate Frequency: There is new new data since this 2019 version, so no updates planned in the futurePublication Date: March 13, 2019Prior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus 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, On or Off Network (flowlines only), Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.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 is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. 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.

A Geospatial Data Resource Site (GDRS) is a structured collection of GIS apps and data used as the data structure that supports the Minnesota Geospatial Commons (MGC) and MNDNR Quick Layers (for ArcGIS Pro and ArcMap). The GDRS Manager application allows anyone to create their own local GDRS, either to be shared on an organization's network drive or to use offline. There is no installation for the GDRSManager. Simply download the application and double-click the executable file to run it. Current version: 1.0.0.44

Use https://resources.gisdata.mn.gov/pub/gdrs as the source GDRS to access the full public data from the MGC. Copy everything or select which datasets you want to copy to a local GDRS destination. If you have disk space or download speed limiations, sorting the resources by size and unselecting the largest resources is a quick way to reduce the size of a the GDRS but still have access to most of the resources.

Once you have a GDRS set up, run the application again whenever you want to update existing datasets or add additional datasets. You can even keep your data current by scheduling automatic updates to run gdrsmanager.exe through a bat file. For your reference, a template bat file gdrsmanager_console.bat is included in the application download. Just make sure to update the bat file to include the path to your copy of GDRS Manager, and schedule the bat file to run as desired.

The application download includes a comprehensive help document, which you can also access separately here:
gdrsmanager_quicklayers_Pro_help.pdf
gdrsmanager_quicklayers_help.pdf (ArcMap)

*This dataset is authored by ESRI and is being shared as a direct link to the feature service by Pend Oreille County. NHD is a primary hydrologic reference used by our organization.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 territoriesCoordinate System: Web Mercator Auxiliary Sphere Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American Samoa Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSPublication 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 Feature 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.

Feature service for test editing of points lines and polygon feature class.Data Distribution and Retention:• Data is copied nightly from ArcGIS Online into a GIS Database located on the Skagit County Network. Important Notes:• This data is integrated into automated processes (nightly copy), with dependencies. Changes to the data schema, will affect these processes and dependencies. Any changes to the data schema should be coordinated with the GIS Department.

The Federal Emergency Management Agency (FEMA) produces Flood Insurance Rate maps and identifies Special Flood Hazard Areas as part of the National Flood Insurance Program's floodplain management. Special Flood Hazard Areas have regulations that include the mandatory purchase of flood insurance for holders of federally regulated mortgages. In addition, this layer can help planners and firms avoid areas of flood risk and also avoid additional cost to carry insurance for certain planned activities. Dataset SummaryPhenomenon Mapped: Flood Hazard AreasGeographic Extent: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Mariana Islands and American Samoa.Projection: Web Mercator Auxiliary SphereData Coordinate System: USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WGS 1984 Albers (Alaska), Hawaii Albers Equal Area Conic (Hawaii), Western Pacific Albers Equal Area Conic (Guam, Northern Mariana Islands, and American Samoa)Cell Sizes: 10 meters (default), 30 meters, and 90 metersUnits: NoneSource Type: ThematicPixel Type: Unsigned integerSource: Federal Emergency Management Agency (FEMA)Update Frequency: AnnualPublication Date: May 7, 2025 This layer is derived from the May 7, 2025 version Flood Insurance Rate Map feature class S_FLD_HAZ_AR. The vector data were then flagged with an index of 94 classes, representing a unique combination of values displayed by three renderers. (In three resolutions the three renderers make nine processing templates.) Repair Geometry was run on the set of features, then the features were rasterized using the 94 class index at a resolutions of 10, 30, and 90 meters, using the Polygon to Raster tool and the "MAXIMUM_COMBINED_AREA" option. Not every part of the United States is covered by flood rate maps. This layer compiles all the flood insurance maps available at the time of publication. To make analysis easier, areas that were NOT mapped by FEMA for flood insurance rates no longer are served as NODATA but are filled in with a value of 250, representing any unmapped areas which appear in the US Census boundary of the USA states and territories. The attribute table corresponding to value 250 will indicate that the area was not mapped.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 "flood hazard areas" 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 "flood hazard areas" 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. The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one. Processing TemplatesCartographic Renderer - The default. These are meaningful classes grouped by FEMA which group its own Flood Zone Type and Subtype fields. This renderer uses FEMA's own cartographic interpretations of its flood zone and zone subtype fields to help you identify and assess risk. Flood Zone Type Renderer - Specifically renders FEMA FLD_ZONE (flood zone) attribute, which distinguishes the original, broadest categories of flood zones. This renderer displays high level categories of flood zones, and is less nuanced than the Cartographic Renderer. For example, a fld_zone value of X can either have moderate or low risk depending on location. This renderer will simply render fld_zone X as its own color without identifying "500 year" flood zones within that category.Flood Insurance Requirement Renderer - Shows Special Flood Hazard Area (SFHA) true-false status. This may be helpful if you want to show just the places where flood insurance is required. A value of True means flood insurance is mandatory in a majority of the area covered by each 10m pixel. Each of these three renderers have templates at three different raster resolutions depending on your analysis needs. To include the layer in web maps to serve maps and queries, the 10 meter renderers are the preferred option. These are served with overviews and render at all resolutions. However, when doing analysis of larger areas, we now offer two coarser resolutions of 30 and 90 meters in processing templates for added convenience and time savings.Data DictionaryMaking a copy of your area of interest using copyraster in arcgis pro will copy the layer's attribute table to your network alongside the local output raster. The raster attribute table in the copied raster will contain the flood zone, zone subtype, and special flood hazard area true/false flag which corresponds to each value in the layer for your area of interest. For your convienence, we also included a table in CSV format in the box below as a data dictionary you can use as an index to every value in the layer. Value,FLD_ZONE,ZONE_SUBTY,SFHA_TF 2,A,, 3,A,,F 4,A,,T 5,A,,T 6,A,,T 7,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 8,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 9,A,ADMINISTRATIVE FLOODWAY,T 10,A,COASTAL FLOODPLAIN,T 11,A,FLOWAGE EASEMENT AREA,T 12,A99,,T 13,A99,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 14,AE,,F 15,AE,,T 16,AE,,T 17,AE,,T 18,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 19,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 20,AE,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",T 21,AE,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",T 22,AE,ADMINISTRATIVE FLOODWAY,T 23,AE,AREA OF SPECIAL CONSIDERATION,T 24,AE,COASTAL FLOODPLAIN,T 25,AE,COLORADO RIVER FLOODWAY,T 26,AE,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 27,AE,COMMUNITY ENCROACHMENT,T 28,AE,COMMUNITY ENCROACHMENT AREA,T 29,AE,DENSITY FRINGE AREA,T 30,AE,FLOODWAY,T 31,AE,FLOODWAY CONTAINED IN CHANNEL,T 32,AE,FLOODWAY CONTAINED IN STRUCTURE,T 33,AE,FLOWAGE EASEMENT AREA,T 34,AE,RIVERINE FLOODWAY IN COMBINED RIVERINE AND COASTAL ZONE,T 35,AE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 36,AE,STATE ENCROACHMENT AREA,T 37,AH,,T 38,AH,,T 39,AH,FLOODWAY,T 40,AO,,T 41,AO,COASTAL FLOODPLAIN,T 42,AO,FLOODWAY,T 43,AREA NOT INCLUDED,,F 44,AREA NOT INCLUDED,,T 45,AREA NOT INCLUDED,,U 46,D,,F 47,D,,T 48,D,AREA WITH FLOOD RISK DUE TO LEVEE,F 49,OPEN WATER,,F 50,OPEN WATER,,T 51,OPEN WATER,,U 52,V,,T 53,V,COASTAL FLOODPLAIN,T 54,VE,,T 55,VE,,T 56,VE,COASTAL FLOODPLAIN,T 57,VE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 58,X,,F 59,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,F 60,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,T 61,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,U 62,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,F 63,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,F 64,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COASTAL ZONE,F 65,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COMBINED RIVERINE AND COASTAL ZONE,F 66,X,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",F 67,X,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",F 68,X,1 PCT DEPTH LESS THAN 1 FOOT,F 69,X,1 PCT DRAINAGE AREA LESS THAN 1 SQUARE MILE,F 70,X,1 PCT FUTURE CONDITIONS,F 71,X,1 PCT FUTURE CONDITIONS CONTAINED IN STRUCTURE,F 72,X,"1 PCT FUTURE CONDITIONS, COMMUNITY ENCROACHMENT",F 73,X,"1 PCT FUTURE CONDITIONS, FLOODWAY",F 74,X,"1 PCT FUTURE IN STRUCTURE, COMMUNITY ENCROACHMENT",F 75,X,"1 PCT FUTURE IN STRUCTURE, FLOODWAY",F 76,X,AREA OF MINIMAL FLOOD HAZARD, 77,X,AREA OF MINIMAL FLOOD HAZARD,F 78,X,AREA OF MINIMAL FLOOD HAZARD,T 79,X,AREA OF MINIMAL FLOOD HAZARD,U 80,X,AREA OF SPECIAL CONSIDERATION,F 81,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,F 82,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 83,X,FLOWAGE EASEMENT AREA,F 84,X,1 PCT FUTURE CONDITIONS,T 85,AH,COASTAL FLOODPLAIN,T 86,AE,,U 87,AE,FLOODWAY,F 88,X,AREA WITH REDUCED FLOOD HAZARD DUE TO ACCREDITED LEVEE SYSTEM,F 89,X,530,F 90,VE,100,T 91,AE,100,T 92,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO LEVEE SYSTEM,T 93,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO NON-ACCREDITED LEVEE SYSTEM,T 94,A,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 250,AREA NOT INCLUDED,Not Mapped by FEMA, 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.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal Buffers (this dataset)Without Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.AccuracyCDTFA"s source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

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.

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is regularly updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications. PurposeCounty boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use. Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal Buffers (this dataset)Without Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead. Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections.Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor. CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information. CDTFA's source data notes the following about accuracy: City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties. In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose. SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon. Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these

This database was prepared using a combination of materials that include aerial photographs, topographic maps (1:24,000 and 1:250,000), field notes, and a sample catalog. Our goal was to translate sample collection site locations at Yellowstone National Park and surrounding areas into a GIS database. This was achieved by transferring site locations from aerial photographs and topographic maps into layers in ArcMap. Each field site is located based on field notes describing where a sample was collected. Locations were marked on the photograph or topographic map by a pinhole or dot, respectively, with the corresponding station or site numbers. Station and site numbers were then referenced in the notes to determine the appropriate prefix for the station. Each point on the aerial photograph or topographic map was relocated on the screen in ArcMap, on a digital topographic map, or an aerial photograph. Several samples are present in the field notes and in the catalog but do not correspond to an aerial photograph or could not be found on the topographic maps. These samples are marked with “No” under the LocationFound field and do not have a corresponding point in the SampleSites feature class. Each point represents a field station or collection site with information that was entered into an attributes table (explained in detail in the entity and attribute metadata sections). Tabular information on hand samples, thin sections, and mineral separates were entered by hand. The Samples table includes everything transferred from the paper records and relates to the other tables using the SampleID and to the SampleSites feature class using the SampleSite field.

This layer tracks zoning ordinances in the City of Norman. The layer was developed in 1992, using a hard copy wall map maintained by the Planning Department. It has been continually updated since that time using the zoning ordinances adopted by the City of Norman’s City Council.Link to Norman Zoning Ordinance

This feature layer provides access to OpenStreetMap (OSM) buildings data for Africa, which is updated every 1 minute with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM polygon (closed way) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. This feature layer view includes building features defined as a query against the hosted feature layer (i.e. building is not blank).In OSM, a building is a man-made structure with a roof, standing more or less permanently in one place. These features are identified with a building tag. There are thousands of different tag values for building used in the OSM database. In this feature layer, unique symbols are used for several of the most popular building types, while lesser used types are grouped in an "other" category.Zoom in to large scales (e.g. Streets level or 1:10k scale) to see the building features display. You can click on a feature to get the name of the building (if available). The name of the building will display by default at large scales (e.g. Street level of 1:5k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this buildings layer displaying just one or two building types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. building is apartments), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers (e.g. parks) that are ready to use, but not for every type of building.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.

This public GIS dataset comes from the Alaska GAP project, and it is part of the final project report (Gotthard, Pyare, Huettmann et al. 2013). Here we present a copy of the original data set as a value-added product for basic use and training purposes. It consists of 53 environmental layers for all of Alaska in an ArcGIS 10 format and usually with a pixel size of 60m. These layers were compiled from various sources, and authorships should be fully honoured as stated in the details of this metadata. Output maps were clipped using a state of Alaska coastline in the Alaska Albers NAD83 projection; very small islands are excluded.The data layers were initially compiled for ecological niche models of Alaska's terrestrial biodiversity using Maxent and other Machine Learning algorithms. However, they can also be used for many other purposes, e.g. strategic conservation planning and individual information and assessments. The datasets are a snapshot in space and time (2012) but likely remain valid for years to come. It is appreciated that these data layers are 'living products', and it is hoped that this public data publication here will progress and trigger many updates and data quality improvements for Alaska and its public high-quality data over time. The following variables are included in this dataset: Boundaries Coastline, Climate Precipitation January til December Average monthly precipitation (mm), Climate Precipitation Average annual precipitation (mm), Climate Temperature January til December Average monthly temperature (deg C), Climate Temperature annual temperature (dec C), Climate First day of thaw (Julian date), Climate First day of freeze (Julian date), Climate Length of growing season Number of days, Disturbance Insect history (Year), Distance to Disturbance Insect location (m), Disturbance Fire history Year of fire (1942 til 2007), distance to Disturbance Fire location (m), Soils Grid (category), Surfacial Geology Grid values, Glacial Distance (m), Distance(m) to lotic water, Distance (m) to permafrost boundary, Distance(m) to lentic water, Saltwater Presence, Distance (m) to Sea Ice Extent 2003-2007 December, Distance (m) to Sea Ice Extent 2003-2007 July, Distance to Development Infrastructure, Landcover Vegetation (Landfire), Landcover nlcd60, Elevation (m), Slope (%), Aspect (Degrees from due south), Terrain Ruggedness index, Extent nullgrid 9999, Coast raster.

[Metadata] Description: C&C of Honolulu Land Use Zoning Designations as of September 2023.

This is a copy of another layer - see original source: https://www.arcgis.com/home/item.html?id=e02b85c0ea784ce7bd8add7ae3d293d0OverviewThe 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 perimetersFWS -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 emailLayers

Features in the TAZ ranger districts dataset represent individual USFS Ranger Districts or USFS Administrative Forests Boundaries which compose a stumpage market. The schema of this dataset is a copy of S_USA.RangerDistrict (https://data.fs.usda.gov/geodata/edw/edw_resources/meta/S_USA.RangerDistrict.xml) with two additional fields: APPRAISALZONES_FK supports a one-to-many relationship between S_USA.Com_TimberAppraisalZone and S_USA.Com_TimberAppraisalZone_RDs COMMENTS contains information about individual stumpage market. TAZ Ranger Districts Metadata

More MetadataHistoric drainage is used in agricultural and farm plans, stormwater management, comprehensive planning, floodplain management, and facility planning to provide a better understanding of what previous drainage was like for a given area. Soils were originally shown at the scale of 1:15840 and then redrafted to 1:20000; the data were redrafted a final time to fit Loudoun County's base map standard of 1:2400. Although the current data rely heavily on the original soil survey, there have been extensive alterations. The data are updated as field site inspections or interpretation changes occur. This is a copy of the drains layer as it exists on 20010208. It is meant to provide the county with a historical base for drainage.Photogrammetric updates will not occur to this layer. Data are stored in the corporate ArcSDE Geodatabase as a line feature class. The coordinate system is Virginia State Plane (North), Zone 4501, datum NAD83 HARN (vertical datum, if applicable, NAVD88), US Survey foot units.

This ArcGIS Online hosted feature service displays perimeters from the National Incident Feature Service (NIFS) that meet ALL of the following criteria: