Feature layer generated from running the Dissolve Boundaries solution.

Land boundary of Marin County

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 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. No modifications to the source data have been made other than to add and calculate the "EIS Name" field. The following EIS boundaries are included in the dataset: 9-Plan, Bighorn Basin, Billings/Pompey's Pillar NM, Buffalo, HiLine, Idaho and SW Montana, Lander, Lewistown, Miles City, NW Colorado, Nevada and NE California, North Dakota, Oregon, South Dakota, Upper Missouri River Breaks NM, and Utah.

State boundaries for Pennsylvania, New Jersey, Delaware, Maryland, New York, Connecticut, and Washington DC. This dataset was compiled from multiple sources. Original Sources: PA - PennDOT NJ - NJOIT DE - DE Geological Survey MD, NY, CT, DC - ESRI Linework has been adjusted using the following methodology. NJ's boundaries overrode PA, since NJ's were highly accurate. PA overrode MD since PennDOT's were more accurate than ESRI's, and DE overrode PA & MD, since the "arc" of northernmost DE was a bit more accurate than PennDOT's or our original county boundaries. Boundaries in the DVRPC region have been adjusted to align with parcel data (where appropriate). This file is the result of a dissolve performed on the county boundary file.

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.

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.

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

Feature Service generated from running the Dissolve Boundaries solution.

This geospatial dataset is a hydrologic unit boundary layer for the Sub-basin (8-digit) level. The dataset is a subset of the 4th level (8-digit) hydrologic unit boundaries of the Watershed Boundary Dataset (WBD) layer for Oregon. It was created by dissolving boundaries from the finer resolution hydrologic units (those of the 5th or 10-digit level) to create these broader boundaries. Boundaries within the this data set were delineated by Pacific Northwest (PNW) Hydrography Framework Partners and Natural Resources Conservation Service (NRCS) to meet state requirements and to contribute to the national WBD repository. To meet these goals, the WBD must adhere to the "Federal Standards for Delineation of Hydrologic Unit Boundaries", dated October, 2004. These boundaries were made from the Oregon and Washington datasets that have been nationally certified by Natural Resources Conservation Service (NRCS) Prior to submission the dataset was subjected to an iterative review and edit process to ensure that the hydrologic boundaries fully satisfy the federal standards. This work was completed under a Memorandum of Understanding between the Pacific Northwest Hydrography Framework Partnership, NRCS and the US Geological Survey (USGS). The current dataset includes the entire 4th level (8-digit) subbasins that fall within or the four county Metro region. This data was originally downloaded from the PNW Hydrography Framework Clearinghouse (http://hydro.reo.gov/hu.html). Date of last data update: 2009-01-31 This is official RLIS data. Contact Person: Christine Rutan christine.rutan@oregonmetro.gov 503-797-1669 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2100 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

This geospatial dataset represents the 2nd level (4-digit) hydrologic unit boundaries of the Watershed Boundary Dataset (WBD) layer for Washington. It was created by dissolving boundaries from the finer resolution hydrologic units to create these broader boundaries. See metadata for the wbd_wa_poly feature class for a more complete description of the WBD.

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. PurposeCity 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 Buffers (this dataset)Counties: 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 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 excludes 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, odsdataservices@state.ca.gov Field and Abbreviation DefinitionsCDTFA_CITY: CDTFA incorporated city nameCDTFA_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_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.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

The California Association Local Agency Formation Commissions defines a sphere of influence (SOI) as "a planning boundary outside of an agency’s legal boundary (such as the city limit line) that designates the agency’s probable future boundary and service area." This feature set represents the SOIs of the incorporated jurisdictions for the San Francisco Bay Region. The Metropolitan Transportation Commission (MTC) updated the feature set in late 2019 as part of the jurisdiction review process for the BASIS data gathering project. Changes were made to the growth boundaries of the following jurisdictions based on BASIS feedback and associated work: Antioch, Brentwood, Campbell, Daly City, Dublin, Fremont, Hayward, Los Gatos, Monte Sereno, Newark, Oakland, Oakley, Pacifica, Petaluma, Pittsburg, Pleasanton, San Bruno, San Francisco (added to reflect other jurisdictions whose SOI is the same as their jurisdiction boundary), San Jose, San Leandro, Santa Clara, Saratoga, and Sunnyvale. Notes: With the exception of San Mateo and Solano Counties, counties included jurisdiction (city/town) areas as part of their SOI boundary data. San Mateo County and Solano County only provided polygons representing the SOI areas outside the jurisdiction areas. To create a consistent, regional feature set, the Metropolitan Transportation Commission (MTC) added the jurisdiction areas to the original, SOI-only features and dissolved the features by name.Because of differences in base data used by the counties and the MTC, edits were made to the San Mateo County and Solano County SOI features that should have been adjacent to their jurisdiction boundary so the dissolve function would create a minimum number of features. Original sphere of influence boundary acquisitions:Alameda County - CityLimits_SOI.shp received as e-mail attachment from Alameda County Community Development Agency on 30 August 2019 Contra Costa County - BND_LAFCO_Cities_SOI.zip downloaded from https://gis.cccounty.us/Downloads/Planning/ on 15 August 2019Marin County - 'Sphere of Influence - City' feature service data downloaded from Marin GeoHub on 15 August 2019Napa County - city_soi.zip downloaded from their GIS Data Catalog on 15 August 2019 City and County of San Francisco - does not have a sphere of influence San Mateo County - 'Sphere of Influence' feature service data downloaded from San Mateo County GIS open data on 15 August 2019 Santa Clara County - 'City Spheres of Influence' feature service data downloaded from Santa Clara County Planning Office GIS Data on 15 August 2019 Solano County - SphereOfInfluence feature service data downloaded from Solano GeoHub on 15 August 2019 Sonoma County - 'SoCo PRMD GIS Spheres Influence.zip' downloaded from County of Sonoma on 15 August 2019

Feature layer generated from running the Dissolve Boundaries solution.

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.