gROADS_v1_Dissolve

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

Feature layer generated from running the Dissolve Boundaries solution.

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 data provides an interpolated raster surface of dissolved oxygen values across a region covered by an August 25, 2016 AUV survey. The raster was generated by using a natural neighbors interpolator within a GIS on the empirical data set. This interpolator was chosen due to the non-normal distribution observed among the data, and its ability to produce smoother approximations than alternative interpolation methods. During the August 24 survey, 13,910 data points were collected. A subset of 4452 (25%) random points were removed prior to interpolation to check for the accuracy of the interpolated surface.

ESRI grids showing dissolved oxygen, linearly interpolated from CARS2000 mean and seasonal fields to 0.1 degree spaced grid, at depths of 0, 150, 500, 1000 and 2000 metres. The loess filter used to …Show full descriptionESRI grids showing dissolved oxygen, linearly interpolated from CARS2000 mean and seasonal fields to 0.1 degree spaced grid, at depths of 0, 150, 500, 1000 and 2000 metres. The loess filter used to create CARS2000 resolves at each point a mean value and a sinusoid with 1 year period (and in some cases a 6 month period sinusoid - the "semi-annual cycle".) The provided "annual amplitude" is simply the magnitude of that annual sinusoid. CARS is a set of seasonal maps of temperature, salinity, dissolved oxygen, nitrate, phosphate and silicate, generated using Loess mapping from all available oceanographic data in the region. It covers the region 100-200E, 50-0S, on a 0.5 degree grid, and on 56 standard depth levels. Higher resolution versions are also available for the Australian continental shelf. The data was obtained from the World Ocean Atlas 98 and CSIRO Marine and NIWA archives. It was designed to improve on the Levitus WOA98 Atlas, in the Australian region. CARS2000 is derived from ocean cast data, which is always measured above the sea floor. However, for properties which do not change rapidly near the sea floor, this would not lead to a significant error. All the limitations of CARS2000 also apply here.

Esri_WorldRoads_Dissolve

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.

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 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.

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

This feature class represents combined 200ft and 1000ft beach buffers derived from Intertidal_PL. The process for creating this combined buffer is as follows: Select from Intertidal_PL where Description in ( 'CHK' , 'INT', 'EST', 'UIT' ) and buffer it 1000 ft, then dissolve all, so it's just a big ol' blob. Use the same selected set from Intertidal_PL and buffer it 200 feet, then dissolve all.Then select from Intertidal_PL where Description in ( 'CHK' , 'SW', 'EST' ) and erase those areas from the big buffered blobs. (I do not erase the INT areas because that might leave gaps and slivers along the shoreline above the water.)Add a field called Buff1000ft to the 1000 foot buffer and populate it with 'Y'. Add a field called Buff200ft to the 200 foot buffer and populate it with 'Y'. Identity the 200 ft buffer onto the 1000 ft buffer.Select where the field Buff200ft is blank and populate it with 'N'. (This would be the area within the 1000 ft buffer that falls outside of the 200 ft buffer.)The resulting buffer polygons can end up being wider than 1000ft or 200ft respectively in some places (beach…etc), but the intent of the polygons is to go landward 1000ft/200ft – the additional width is due to the beach/island/peninsula type stuff. The reason I originally started choosing to buffer CHK, INT, EST, and UIT was because I was concerned that buffering only INT might lead to odd gaps.

The 1885 UK parliamentary constituencies for Ireland were re-created in 2017 as part of a conference paper delivered at the Southern Irish Loyalism in Context conference at Maynooth University. The intial map only included the territory of the Irish Free State and was created by Martin Charlton and Jack Kavanagh. The remaining six counties of Ulster were completed by Eoin McLaughlin in 2018-19, the combined result is a GIS map of all the parliamentary constituecies across the island of Ireland for the period 1885-1918. The map is available in both ESRI Shapefile format and as a GeoPackage (GPKG). The methodology for creating the constituencies is outlined in detail below.

Methodology

A map showing the outlines of the 1855 – 1918 Constituency boundaries can be found on page 401 of Parliamentary Elections in Ireland, 1801-1922 (Dublin, 1978) by Brian Walker. This forms the basis for the creation of a set of digital boundaries which can then be used in a GIS. The general workflow involves allocating an 1885 Constituency identifier to each of the 309 Electoral Divisions present in the boundaries made available for the 2011 Census of Population data release by CSO. The ED boundaries are available in ‘shapefile’ format (a de facto standard for spatial data transfer). Once a Constituency identifier has been given to each ED, the GIS operation known as ‘dissolve’ is used to remove the boundaries between EDs in the same Constituency. To begin with Walker’s map was scanned at 1200 dots per inch in JPEG form. A scanned map cannot be linked to other spatial data without undergoing a process known as georeferencing. The CSO boundaries are available with spatial coordinates in the Irish National Grid system. The goal of georeferencing is to produce a rectified version of the map together with a world file. Rectification refers to the process of recomputing the pixel positions in the scanned map so that they are oriented with the ING coordinate system; the world file contains the extent in both the east-west and north-south directions of each pixel (in metres) and the coordinates of the most north-westerly pixel in the rectified image.

Georeferencing involves the identification of Ground Control Points – these are locations on the scanned map for which the spatial coordinates in ING are known. The Georeferencing option in ArcGIS 10.4 makes this a reasonably pain free task. For this map 36 GCPs were required for a local spline transformation. The Redistribution of Seats Act 1885 provides the legal basis for the constituencies to be used for future elections in England, Wales, Scotland and Ireland. Part III of the Seventh Schedule of the Act defines the Constituencies in terms of Baronies, Parishes (and part Parishes) and Townlands for Ireland. Part III of the Sixth Schedule provides definitions for the Boroughs of Belfast and Dublin.

The CSO boundary collection also includes a shapefile of Barony boundaries. This makes it possible code a barony in two ways: (i) allocated completely to a Division or (ii) split between two Divisions. For the first type, the code is just the division name, and for the second the code includes both (or more) division names. Allocation of these names to the data in the ED shapefile is accomplished by a spatial join operation. Recoding the areas in the split Baronies is done interactively using the GIS software’s editing option. EDs or groups of EDs can be selected on the screen, and the correct Division code updated in the attribute table. There are a handful of cases where an ED is split between divisions, so a simple ‘majority’ rule was used for the allocation. As the maps are to be used at mainly for displaying data at the national level, a misallocation is unlikely to be noticed. The final set of boundaries was created using the dissolve operation mentioned earlier. There were a dozen ED that had initially escaped being allocated a code, but these were quickly updated. Similarly, a few of the EDs in the split divisions had been overlooked; again updating was painless. This meant that the dissolve had to be run a few more times before all the errors have been corrected.

For the Northern Ireland districts, a slightly different methodology was deployed which involved linking parishes and townlands along side baronies, using open data sources from the OSM Townlands.ie project and OpenData NI.

DOC in streams within a subarctic catchmentFinal figures for manuscriptFigures1.zipDOC in streams within a subarctic catchmentFinal tables for manuscriptTables1.zip

Staging for SSA structure for dissolve process.

This feature class was derived from the GIS polygon dataset BLM Grazing Allotments which was downloaded from the Geospatial Gateway in April 2025. Fields were added to the feature classes and calculated as needed to allow the Rangeland Administration System (RAS) tabular data to be joined to the GIS datasets. RAS tabular data for Authorized allotments and pastures (as of April 2025) was provided by BLM Rangeland Management Specialist Josh Robbins in April 2025 and processed as dbfs, with fields added and calculated as needed to match the BLM GIS Grazing Allotments feature class. RAS tables and BLM GIS data for allotments were joined using the State Allotment Number, a concatenation of allotment number and BLM Administrative State for allotments (ST_ALLOT_NUM). RAS records for Authorized Allotments that did not match during a join operation were tracked in a separate excel sheet from the matching records. Matching records were then joined back to the BLM GIS Allotments grazing feature class and Allotment name fields were edited as necessary. A Status field was added to indicate if the data are either Billed or Authorized and a Source field was added to indicate that the data came from Allotments or Trailing Allotments. An additional field, TR_ALLOT_NUM, was added to designate any Trailing Allotments in the data. Trailing allotments were identified and processed separately for Nevada, since these allotments overlap portions of other allotments. Any overlaps in the data were removed via dissolve and Spatial Join.Input BLM GIS Grazing data:BLM Grazing Pastures and BLM Grazing Allotments are areas of land designated and managed for grazing of livestock. It may include private, state, and public lands under the jurisdiction of the Bureau of Land Management and/or other federal agencies. An allotment is derived from its pastures, where the grazing of livestock is occurring. The attributes of the BLM Grazing Allotment features may be duplicated in RAS, but are considered to be minimum information for unique identification and cartographic purposes.Input RAS Data:The Rangeland Administration System (RAS) provides grazing administrative support and management reports for the BLM and the public. The Rangeland Administration system serves as an electronic calendar for issuance of applications and grazing authorizations, including Permits, Leases, and Exchange-of-Use Agreements. The Authorized data is current as of April 2025 and was provided by BLM Rangeland Management Specialist Josh Robbins in April 2025.

Cover types originated from the timber type coverages for each management area. First, all polygons less than five acres were ELIMINATEd, except islands in Prince William Sound. Second, polygons less than 10 acres (except islands in PWS) were ELIMINATEd. FTYP and NFOR were added as separate items and they were REDEFINEd as FTYP-NFOR. TT-CODE and TT-ALPHA were deleted. Individual FTYP and NFOR codes were consolidated to create the cover types. FTYP consolidations were: Hemlock-White Spruce and Hemlock-Sitka Spruce were combined and called Hemlock-Spruce; Aspen-White Spruce, Birch-White Spruce, Cottonwood-Sitka Spruce, Cottonwood-White Spruce, Cottonwood-Birch-White Spruce, Aspen-Hemlock, Birch-Sitka Spruce & Birch-Hemlock were combined and called Mixed Hardwood-Softwood; Cottonwood-Balsam Poplar and Cottonwood-Birch were combined and called Cottonwood; Aspen-Birch was combined with Aspen and called Aspen. NFOR consolidations were: Natural Grassland and Alpine High Meadow were combined and called Grass & Alpine; Icefield or Snowfield and Recurrent Snow Slide Zone were combined and called Ice & Snow; Urban, Agriculture, Other, Mass Wasting, Sand Dunes, Uplifted Beach, River Fill, Other Causes, Borrow Pit were combined and called Other Non-forested. DISSOLVE was done on FTYP-NFOR. The six coverages were then MAPJOINED into the two final coverages. Data available from the United States Department of Agriculture Forest Service.

This data set represents the approximate boundaries of Sales Tax Areas for the State of Utah. Individual Sales Tax Area polygons are formed by each municipality, special sales tax district (in 2006, there were 6 special transit districts) and the unincorporated areas of each county not in a special sales tax district. This dataset also contains an attribute that can be used to dissolve the Sales Tax polygons into the polygons representing tax areas for the proposed Streamlined Sales Tax implementation.Updated Q2 2025