gROADS_v1_Dissolve

Feature layer generated from running the Dissolve Boundaries solution.

ownership_poly_dissolve: This theme portrays information related to surface jurisdiction of lands located in the states of Oregon and Washington.

Esri_WorldRoads_Dissolve

This nowCOAST™ time-enabled map service provides maps depicting the geographic coverage of the latest NOAA/National Weather Service (NWS) WATCHES, WARNINGS, ADVISORIES, and STATEMENTS for long-duration hazardous weather, marine weather, hydrological, oceanographic, wildfire, air quality, and ecological conditions which may or are presently affecting inland, coastal, and maritime areas. A few examples include Gale Watch, Gale Warning, High Surf Advisory, High Wind Watch, Areal Flood Warning, Coastal Flood Watch, Winter Storm Warning, Wind Chill Advisory, Frost Advisory, Tropical Storm Watch, Red Flag Warning, Air Stagnation Warning, and Beach Hazards Statement. (A complete list is given in the Background Information section below.) The coverage areas of these products are usually defined by county or sub-county boundaries. The colors used to identify the different watches, advisories, warnings, and statements are the same colors used by the NWS on their map at weather.gov. The NWS products for long-duration hazardous conditions are updated in the nowCOAST map service approximately every 10 minutes. For more detailed information about the update schedule, please see: http://new.nowcoast.noaa.gov/help/#section=updateschedule. The coverage areas of these products are usually defined by county or sub-county boundaries, but for simplicity and performance reasons, adjacent WWAs of the same type, issuance, and expiration are depicted in this service as unified (merged/dissolved) polygons in the layers indicated with the suffix "(Dissolved Polygons)". However, a set of equivalent layers containing the original individual zone geometries are also included for querying purposes, and are indicated with the suffix "(Zone Polygons)". Corresponding zone polygon and dissolved polygon layers are matched together in group layers for each WWA category. The zone polygon layers are included in this service only to support query/identify operations (e.g., in order to retrieve the original zone geometry or other attributes such as a URL to the warning text bulletin) and thus will not be drawn when included in a normal map image request. Thus, the dissolved polygon layers should be used when requesting a map image (e.g. WMS GetMap or ArcGIS REST export operations), while the zone polygon layers should be used when performing a query (e.g. WMS GetFeatureInfo or ArcGIS REST query or identify operations). The colors used to identify the different watches, advisories, warnings, and statements are the same colors used by the NWS on their map at http://www.weather.gov. The NWS products for long-duration hazardous conditions are updated in the nowCOAST™ map service approximately every 10 minutes. For more detailed information about layer update frequency and timing, please reference the nowCOAST™ Dataset Update Schedule. Background Information NWS watches depict the geographic areas where the risk of hazardous weather or hydrologic events has increased significantly, but their occurrence, location, and/or timing is still uncertain. A warning depicts where a hazardous weather or hydrologic event is occurring, is imminent, or has a very high probability of occurring. A warning is used for conditions posing a threat to life or property. Advisories indicate where special weather conditions are occurring, imminent, or have a very high probability of occurring but are less serious than a warning. They are for events that may cause significant inconvenience, and if caution is not exercised, could lead to situations that may threaten life and/or property. Statements usually contain updated information on a warning and are used to let the public know when a warning is no longer in effect. NWS issues over 75 different types of watches, warnings, and advisories (WWAs). WWAs are issued by the NWS regional Weather Forecast Offices (WFOs) and also the NWS Ocean Prediction Center, National Hurricane Center, Central Pacific Hurricane Center, and Storm Prediction Center. The NWS WWAs are organized on the nowCOAST™ map viewer and within this map service by hazardous condition/threat layer groups and then by the geographic area (i.e. coastal & inland, immediate coast or maritime) for which the WWA product is targeted. This was done to allow users to select WWAs for hazardous conditions that are important to their operations or activities. Please note that the Tropical Storm and Hurricane Warnings are provided in both the High Wind Hazards: Maritime Areas and Coastal & Inland Areas layer groups and the Flooding Hazards: Coastal Areas layer group. These warnings are included in the Flooding Hazards/Coastal Areas layer group because the NWS uses those warnings to inform the public that tropical storm or hurricane winds may be accompanied by significant coastal flooding but below the thresholds required for the issuance of a storm surge warning. In addition, a tropical storm or hurricane warning may remain in effect when dangerously high water or a combination of dangerously high water and waves continue, even though the winds may be less than hurricane or tropical storm force. The NWS does not issue a Coastal Flood Warning or Advisory when a tropical storm or hurricane warning is in effect; however that does not mean that there is not a significant coastal flooding threat. High Wind Hazards (Associated with Non-Tropical & Tropical Cyclones) Maritime Areas Brisk Wind Advisory Small Craft Advisory Small Craft Advisory for Winds Gale Watch Gale Warning Storm Watch Storm Warning Hurricane Force Wind Watch Hurricane Force Wind Warning Tropical Storm Watch Tropical Storm Warning Hurricane Watch Hurricane Warning Coastal & Inland Areas High Wind Watch Wind Advisory Lake Wind Advisory High Wind Warning Tropical Storm Watch Tropical Storm Warning Hurricane Watch Hurricane Warning Hazardous Seas, Surf, and Beach Conditions Maritime Areas Small Craft Advisory for Hazardous Seas Small Craft Advisory for Rough Bar Hazardous Seas Watch Hazardous Seas Warning Immediate Coast Beach Hazards Statement High Surf Advisory High Surf Warning Low Water Advisory Rip Current Statement Flooding Hazards Coastal Areas Coastal Flood Statement Coastal Flood Watch Coastal Flood Advisory Coastal Flood Warning Lakeshore Flood Watch Lakeshore Flood Advisory Lakeshore Flood Warning Lakeshore Flood Statement Storm Surge Watch Storm Surge Warning Tsunami Watch Tsunami Warning Tropical Storm Warning Hurricane Warning Inland Areas Flood Watch (Point) (also called River Flood Watch) Flood Watch (Areal) Flood Advisory (Point) (also called River Flood Advisory) Flood Advisory (Areal) Flood Warning (Point) (also called River Flood Warning) Flood Warning (Areal) Hydrologic Outlook Hydrologic Statement Reduced Visibility Hazards Maritime Areas Dense Fog Advisory Coastal & Inland Areas Ashfall Advisory Ashfall Warning Blowing Dust Advisory Blowing Dust Warning Dense Fog Advisory Dense Smoke Advisory Freezing Spray Hazards Maritime Areas Heavy Freezing Spray Watch Freezing Spray Advisory Heavy Freezing Spray Advisory Snow, Sleet, Freezing Rain, and Freezing Fog Hazards Coastal & Inland Areas Blizzard Watch Blizzard Warning Freezing Fog Advisory Freezing Rain Advisory Ice Storm Warning Lake-Effect Snow Watch Lake-Effect Snow Advisory Lake-Effect Snow Warning Winter Storm Watch Winter Weather Advisory Winter Storm Warning Cold and Heat Hazards Coastal & Inland Areas Excessive Cold Watch Excessive Cold Warning Excessive Heat Watch Heat Advisory Excessive Heat Warning Frost Advisory Freeze Watch Freeze Warning Wind Chill Advisory Wind Chill Warning Critical Wildfire Conditions Coastal & Inland Areas Fire Weather Watch Red Flag Warning Unhealthy Air Quality Coastal & Inland Areas Air Stagnation Advisory Air Quality Alerts from states are NOT available For descriptions of individual NWS watches, warnings, and advisories please see Section 2 of the NWS Reference Guide available at http://www.nws.noaa.gov/om/guide/Section2.pdf. Time Information This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component. In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service. This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned. This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency. When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended. Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and

This data layer is an overview of project locations that were included in the National Centers for Coastal Ocean Science's HABs and Hypoxia Program Review.See the HABs and Hypoxia Program Review website https://experience.arcgis.com/experience/b82102ea67ba4d4f8339baecba2aa29f

This Administration feature is the single most valuable feature maintained by the GIS Services staff. It combines the maintenance of many individual polygon features in one main overall feature.It is part of a ArcGIS Topology class maintained with our parcel and zoning features in the Editing Feature Data Set.We use the shared editing capabilities of this topology class to leverage our maintenance procedures as simply as possible. Weekly, the individual features maintained with our Administration feature are created with ArcGIS dissolve function. These include Jurisdiction boundaries, Public Safety Response areas, Voting Precincts, Schools Attendance Zones, Inspections, Library Service Zones, and more.Generally, maintenance of this feature is controlled thru shared editing performed with our parcel/zoning edits with the use of the Topology features in ArcGIS. Changes to features maintained in the Administration feature are caused by a number of issues. Parcel edits, new Public Safety Stations, changes in Voting Precincts, Police Reporting districts and other changes occur often. Most changes can be facilitated by selecting one or more “Administrative” polygons and changing the appropriate attribute value. Use of the “Cut Polygon” task may be necessary in those cases where part of a polygon must be changed from a district to another. The appropriate attribute can be changed in the affected area as necessary.

Feature layer generated from running the Dissolve Boundaries solution.

scripts.zip

arcgisTools.atbx: terrainDerivatives: make terrain derivatives from digital terrain model (Band 1 = TPI (50 m radius circle), Band 2 = square root of slope, Band 3 = TPI (annulus), Band 4 = hillshade, Band 5 = multidirectional hillshades, Band 6 = slopeshade). rasterizeFeatures: convert vector polygons to raster masks (1 = feature, 0 = background).

makeChips.R: R function to break terrain derivatives and chips into image chips of a defined size. makeTerrainDerivatives.R: R function to generated 6-band terrain derivatives from digital terrain data (same as ArcGIS Pro tool). merge_logs.R: R script to merge training logs into a single file. predictToExtents.ipynb: Python notebook to use trained model to predict to new data. trainExperiments.ipynb: Python notebook used to train semantic segmentation models using PyTorch and the Segmentation Models package. assessmentExperiments.ipynb: Python code to generate assessment metrics using PyTorch and the torchmetrics library. graphs_results.R: R code to make graphs with ggplot2 to summarize results. makeChipsList.R: R code to generate lists of chips in a directory. makeMasks.R: R function to make raster masks from vector data (same as rasterizeFeatures ArcGIS Pro tool).

terraceDL.zip

dems: LiDAR DTM data partitioned into training, testing, and validation datasets based on HUC8 watershed boundaries. Original DTM data were provided by the Iowa BMP mapping project: https://www.gis.iastate.edu/BMPs. extents: extents of the training, testing, and validation areas as defined by HUC 8 watershed boundaries. vectors: vector features representing agricultural terraces and partitioned into separate training, testing, and validation datasets. Original digitized features were provided by the Iowa BMP Mapping Project: https://www.gis.iastate.edu/BMPs.

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.

This dataset provides locations and values of water quality parameters from a four-day survey conducted between August 23, 2016 and August 26, 2016 using an Autonomous Underwater Vehicle (AUV) in Great South Bay, New York. Measured parameters include bottom dissolved oxygen (DO), salinity, specific conductance, water temperature, and pH. During the four day period, data was collected along 15 transects of the Great South Bay, totaling 60,480 observation points. From these point data, rasters showing the spatial distribution of bottom dissolved oxygen were generated using an interpolator in a GIS. A unique raster is provided for each day of the survey. All data files for download are available within 'Child Items' below. Observation point data are available as shapefiles while DO rasters are available as TIFFs. Both point data and DO rasters are made available as web mapping services. This allows for use in ArcGIS for Desktop, ArcGIS Online, and other web applications. For additional information on how to use web mapping services please visit http://server.arcgis.com/en/server/10.3/publish-services/linux/what-is-a-map-service.htm. Please note that the .sd files included are not meant to be open as standalone files, but rather were uploaded to generate the online web mapping service links provided.

Polygon depicts the Montana/Dakotas merged planning area in the Greater Sage-Grouse EIS RMP Amendment. This feature class represents the product of merge and dissolve operations in ArcGIS with the inputs being the individually submitted EIS boundary datasets. EIS boundaries were developed by each individual EIS in coordination with the Division of Decision Support, Planning and NEPA (WO 210). EIS boundary submissions occurred between Sept. 25th and Sept. 30th, 2013. The following EIS boundaries are included in the dataset: Billings/Pompey's Pillar NM, HiLine, SW Montana, Lewistown, Miles City, North Dakota, South Dakota, and Upper Missouri River Breaks NM.

This data set represents the 2025 elk hunt area, herd unit, and regions boundaries for Wyoming. The layer was originally digitized at a scale of 1:100,000, using USGS 1:100,000 DRGs as a backdrop for heads up digitizing. Updates requested by Wyoming Game and Fish Biological Services were completed by selecting needed features from other layers, including roads, streams, HUCs, NAIP rasters and others. Hunt area boundary descriptions are part of hunting regulations, which are approved and published annually by the Wyoming Game and Fish Commission. When needed, the 2008 edition (1st Edition) of the Wyoming Road and Recreation Atlas (Benchmark Maps) was consulted for road and other information.NOTE: A layer of herd units is derived from this hunt area layer by dissolving on the "HERDUNIT" and "HERDNAME" attributes (Dissolve_Fields), and unchecking the box "Create multipart features (optional)". All of the same metadata is used from the hunt area layer except that the citation title is modified so that "Herd Unit" replaces "Hunt Area". The "Dissolve" tool: ArcToolbox > Data Management Tools > Generalization.NOTE: A layer of nonresident regions is derived from this hunt area layer by dissolving on the "Region" attribute (Dissolve_Field), and unchecking the box "Create multipart features (optional)". All of the same metadata is used from the hunt area layer except that the citation title is modified so that "Nonresident Region" replaces "Hunt Area". The "Dissolve" tool: ArcToolbox > Data Management Tools > Generalization.

The Washington State Land Use coverage was produced from digital county tax parcel layers using Department of Revenue (DOR) two digit land use codes (see; WAC 458-53-030, Stratification of assessment rolls - real property). Land use attribute data has been normalized for all county parcel data to conform to the two digit DOR codes. All county parcel layers are dissolved using the normalized land use code. No county parcel information remains in this data other that what geometry remains from the dissolve process.

World Countries represents the boundaries for the countries of the world.

Feature Service generated from running the Dissolve Boundaries solution.

Feature layer generated from running the Dissolve Boundaries solution.

Feature layer generated from running the Dissolve Boundaries solution.This layer is part of a map that shows vegetation in Grays Harbor National Wildlife Refuge. Bowerman Basin, where Grays Harbor is located, is home to unique habitat types that provide sustenance for a diversity of birds that occupy and come through the Refuge. Grays Harbor provides a unique set of diverse ecosystem that attracts different kinds of birds.This map is part of the storymap, An Incredible Journey. Every year in early May, a tranquil little dot on the Washington coastline transforms into a high-traffic north-south shorebird highway known as the Pacific Flyway. From long-distance fliers to birds that prefer a more scenic route, they all stop there because it has all the amenities that a hungry and tired bird could want. So, where is this place? It’s Grays Harbor National Wildlife Refuge, and it’s nature’s version of Grand Central Station.