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 March 2025. 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 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 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.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)Working with Coastal BuffersThe 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.govField 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

This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's 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 jurisdictions. The boundaries are continuously being revised 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 and should not be used to determine precise city or county boundary line locations.The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.*Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; 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 (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

This feature class is used for cartographic purposes, for generating statistical data, and for clipping data. Ideally, state and federal agencies should be using the same framework data for common themes such as county boundaries. This layer provides an initial offering as "best available" at 1:24,000 scale for counties.Incorporated cities were merged from the Board of Equalization's 11/16/2021 City and County boundaries dataset. The Cal Fire FRAP County boundaries v 19_1 were maintained for consistency with other use in CA Nature.

This feature service includes change areas for city boundaries and county line adjustments filed in accordance with Government Code 54900. The boundaries in this map are based on the State Board of Equalization's tax rate area maps for the assessment roll year specified in the COFILE field. The information is updated regularly within 10 business days of the most recent BOE acknowledgement date. Some differences may occur between actual recorded boundaries and boundary placement in the tax rate area GIS map. Tax rate area boundaries are representations of taxing jurisdictions for the purpose of determining property tax assessments and should not be used to determine precise city or county boundary line locations. BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number; CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance; RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES: additional clarifying information about the action. BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the BOE'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).

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 March 2025. 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 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 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 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)Working with Coastal BuffersThe 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, odsdataservices@state.ca.govField 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

Complete accounting of all incorporated cities, including the boundary and name of each individual city. From 2009 to 2022 CAL FIRE maintained this dataset by processing and digitally capturing annexations sent by the state Board of Equalization (BOE). In 2022 CAL FIRE began sourcing data directly from BOE, in order to allow the authoritative department provide data directly. This data is then adjusted so it resembles the previous formats.Processing includes:• Clipping the dataset to traditional state boundaries• Erasing areas that span the Bay Area (derived from calw221.gdb)• Querying for incorporated areas only• Dissolving each incorporated polygon into a single feature• Calculating the COUNTY field to remove the word 'County'Version 24_1 is based on BOE_CityCounty_20240315, and includes all annexations present in BOE_CityAnx2023_20240315. Note: The Board of Equalization represents incorporated city boundaries as extending significantly into waterways, including beyond coastal boundaries. To see the representation in its original form please reference the datasets listed above.Note: The Board of Equalization represents incorporated city boundaries is extending significantly into waterways, including beyond coastal boundaries. To see the representation in its original form please reference the datasets listed above.

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, coastal buffers are removed, leaving 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 BuffersWithout Coastal Buffers (this dataset)Place 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.

City, town, village, and place boundaries within the 13-county region H-GAC. The cities, towns, and villages include: Alvin, Ames, Anahuac, Angleton, Arcola, Bailey's Prairie, Barrett, Bay City, Bayou Vista, Baytown, Beach City, Beasley, Bellaire, Bellville, Bonney, Brazoria, Brazos Country, Brookshire, Brookside Village, Bunker Hill Village, Clear Lake Shores, Cleveland, Clute, Columbus, Conroe, Cove, Cut and Shoot, Daisetta, Danbury, Dayton, Dayton Lakes, Deer Park, Devers, Dickinson, Eagle Lake, East Bernard, El Campo, El Lago, Fairchilds, Freeport, Friendswood, Fulshear, Galena Park, Galveston, Hardin, Hedwig Village, Hempstead, Hillcrest, Hilshire Village, Hitchcock, Holiday Lakes, Houston, Humble, Hunters Creek Village, Huntsville, Industry, Iowa Colony, Jacinto City, Jamaica Beach, Jersey Village, Jones Creek, Katy, Kemah, Kendleton, Kenefick, La Marque, La Porte, Lake Jackson, League City, Liberty, Liverpool, Magnolia, Manvel, Meadows Place, Missouri City, Mont Belvieu, Montgomery, Morgan's Point, Nassau Bay, Needville, New Waverly, North Cleveland, Oak Ridge North, Old River-Winfree, Orchard, Oyster Creek, Palacios, Panorama Village, Pasadena, Pattison, Patton Village, Pearland, Pine Island, Piney Point Village, Pleak, Plum Grove, Prairie View, Quintana, Richmond, Richwood, Riverside, Roman Forest, Rosenberg, San Felipe, Sandy Point, Santa Fe, Seabrook, Sealy, Shenandoah, Shoreacres, Simonton, Sourh Frydek, South Houston, Southside Place, Splendora, Spring Valley Village, Stafford, Stagecoach, Sugar Land, Surfside Beach, Sweeny, Taylor Lake Village, Texas City, Thompsons, Tiki Island, Tomball, Waller, Wallis, Webster, Weimar, West Columbia, West University Place, Weston Lakes, Wharton, Willis, Woodbranch, Woodloch. The census designated places (CDPs) include: Aldine, Atascocita, Bacliff, Barrett, Big Thicket Lake Estates, Blessing, Boling, Bolivar Peninsula, Channelview, Cinco Ranch, Cloverleaf, Crosby, Cumings, Damon, Deerwood, East Columbia, Fifth Street, Four Corners, Fresno, Garwood, Glidden, Grangerland, Highlands, Hull, Hungerford, Iago, Louise, Markham, Mataforda, Midfield, Mission Bend, Nada, New Ulm, Oak Island, Pecan Grove, Pinehurst, Porter Heights, Rock Island, Rosharon, San Leon, Sargent, Sheldon, Sheridan, Sienna, Spring, Stowell, The Woodlands, Van Vleck, Wadsworth, Wild Peach Village, Winnie.

This data set contains features representing growth boundaries in the San Francisco Bay Region. The data set was developed by Greenbelt Alliance as part of their open space preservation mission. 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 their BASIS feedback: Antioch, Fremont, Livermore, Marin County, Pittsburg, Pleasanton, and San Ramon.The original features were created by referencing the local measures adopted by voters, city councils/boards of supervisors, or both and map images developed by local government. Web links to the measures and images are included in the attribute table. Greenbelt Alliance is responsible for updating the links to that information if their links change or the documents are taken offline. MTC's updates were made to a limited set of features using shapefiles downloaded from jurisdiction websites, hand editing features by referencing map images provided by jurisdictions, and erasing feature areas using base data features where one jurisdiction's growth boundary overlapped another jurisdiction's city limit. The MTC edits were limited, or related, to features receiving comments from jurisdiction reviewers.While commonly known as either Urban Growth Boundaries (UGBs) or Urban Limit Lines (ULLs), there are no standard designations so they are referred to by a number of designations in the attribute table (name). A couple of the alternative designations include Rural Urban Boundary and City Centered Corridor. Regardless of the designation used, growth boundaries are intended to control where development should be encouraged and discouraged. In this case, the polygons represent the areas where development should occur, and development outside the boundary is discouraged. Development proposed for areas outside the boundary is usually allowed based on special review and approval processes designated by the adopting jurisdiction.Jurisdictions are not required to adopt growth boundaries so the development restrictions imposed by them only apply to the cities and counties that create them. In the case of growth boundaries adopted by counties, they are usually developed with the consent and agreement of the cities adjacent to the county growth boundary.

California State Lands Commission Offshore Oil Leases in the vicinity of Santa Barbara, Ventura, and Orange County.The polygons in this layer show the position of Offshore Oil Leases as documented by former State Lands Senior Boundary Determination Officer, Cris N. Perez and as reviewed and updated by GIS and Boundary staff.Background: This layer represents active offshore oil and gas agreements in California waters, which are what remain of the more than 60 originally issued. These leases were issued prior to the catastrophic 1969 oil spill from Platform A in federal waters off Santa Barbara County, and some predate the formation of the Commission. Between 2010 and 2014, the bulk of the approximately $300 million generated annually for the state's General Fund from oil and gas agreements was from these offshore leases.In 1921, the Legislature created the first tidelands oil and gas leasing program. Between 1921 and 1929, approximately 100 permits and leases were issued and over 850 wells were drilled in Santa Barbara and Ventura Counties. In 1929, the Legislature prohibited any new leases or permits. In 1933, however, the prohibition was partially lifted in response to an alleged theft of tidelands oil in Huntington Beach. It wasn't until 1938, and again in 1955, that the Legislature would allow new offshore oil and gas leasing. Except for limited circumstances, the Legislature has consistently placed limits on the areas that the Commission may offer for lease and in 1994, placed the entirety of California's coast off-limits to new oil and gas leases. Layer Creation Process:In 1997 Cris N. Perez, Senior Boundary Determination Officer of the Southern California Section of the State Lands Division, prepared a report on the Commission’s Offshore Oil Leases to:A. Show the position of Offshore Oil Leases. B. Produce a hard copy of 1927 NAD Coordinates for each lease. C. Discuss any problems evident after plotting the leases.Below are some of the details Cris included in the report:I have plotted the leases that were supplied to me by the Long Beach Office and computed 1927 NAD California Coordinates for each one. Where the Mean High Tide Line (MHTL) was called for and not described in the deed, I have plotted the California State Lands Commission CB Map Coordinates, from the actual field surveys of the Mean High Water Line and referenced them wherever used. Where the MHTL was called for and not described in the deed and no California State Lands Coordinates were available, I digitized the maps entitled, “Map of the Offshore Ownership Boundary of the State of California Drawn pursuant to the Supplemental Decree of the U.S. Supreme Court in the U.S. V. California, 382 U.S. 448 (1966), Scale 1:10000 Sheets 1-161.” The shore line depicted on these maps is the Mean Lower Low Water (MLLW) Line as shown on the Hydrographic or Topographic Sheets for the coastline. If a better fit is needed, a field survey to position this line will need to be done.The coordinates listed in Cris’ report were retrieved through Optical Character Recognition (OCR) and used to produce GIS polygons using Esri ArcGIS software. Coordinates were checked after the OCR process when producing the polygons in ArcMap to ensure accuracy. Original Coordinate systems (NAD 1927 California State Plane Zones 5 and 6) were used initially, with each zone being reprojected to NAD 83 Teale Albers Meters and merged after the review process.While Cris’ expertise and documentation were relied upon to produce this GIS Layer, certain polygons were reviewed further for any potential updates since Cris’ document and for any unusual geometry. Boundary Determination Officers addressed these issues and plotted leases currently listed as active, but not originally in Cris’ report. On December 24, 2014, the SLA boundary offshore of California was fixed (permanently immobilized) by a decree issued by the U.S. Supreme Court United States v. California, 135 S. Ct. 563 (2014). Offshore leases were clipped so as not to exceed the limits of this fixed boundary. Lease Notes:PRC 1482The “lease area” for this lease is based on the Compensatory Royalty Agreement dated 1-21-1955 as found on the CSLC Insider. The document spells out the distinction between “leased lands” and “state lands”. The leased lands are between two private companies and the agreement only makes a claim to the State’s interest as those lands as identified and surveyed per the map Tract 893, Bk 27 Pg 24. The map shows the State’s interest as being confined to the meanders of three sloughs, one of which is severed from the bay (Anaheim) by a Tideland sale. It should be noted that the actual sovereign tide and or submerged lands for this area is all those historic tide and submerged lands minus and valid tide land sales patents. The three parcels identified were also compared to what the Orange County GIS land records system has for their parcels. Shapefiles were downloaded from that site as well as two centerline monuments for 2 roads covered by the Tract 893. It corresponded well, so their GIS linework was held and clipped or extended to make a parcel.MJF Boundary Determination Officer 12/19/16PRC 3455The “lease area” for this lease is based on the Tract No. 2 Agreement, Long Beach Unit, Wilmington Oil Field, CA dated 4/01/1965 and found on the CSLC insider (also recorded March 12, 1965 in Book M 1799, Page 801).Unit Operating Agreement, Long Beach Unit recorded March 12, 1965 in Book M 1799 page 599.“City’s Portion of the Offshore Area” shall mean the undeveloped portion of the Long Beach tidelands as defined in Section 1(f) of Chapter 138, and includes Tract No. 1”“State’s Portion of the Offshore Area” shall mean that portion of the Alamitos Beach Park Lands, as defined in Chapter 138, included within the Unit Area and includes Tract No. 2.”“Alamitos Beach Park Lands” means those tidelands and submerged lands, whether filled or unfilled, described in that certain Judgment After Remittitur in The People of the State of California v. City of Long Beach, Case No. 683824 in the Superior Court of the State of California for the County of Los Angeles, dated May 8, 1962, and entered on May 15, 1962 in Judgment Book 4481, at Page 76, of the Official Records of the above entitled court”*The description for Tract 2 has an EXCEPTING (statement) “therefrom that portion lying Southerly of the Southerly line of the Boundary of Subsidence Area, as shown on Long Beach Harbor Department {LBHD} Drawing No. D-98. This map could not be found in records nor via a PRA request to the LBHD directly. Some maps were located that show the extents of subsidence in this area being approximately 700 feet waterward of the MHTL as determined by SCC 683824. Although the “EXCEPTING” statement appears to exclude most of what would seem like the offshore area (out to 3 nautical miles from the MHTL which is different than the actual CA offshore boundary measured from MLLW) the 1964, ch 138 grant (pg25) seems to reference the lands lying seaward of that MHTL and ”westerly of the easterly boundary of the undeveloped portion of the Long Beach tidelands, the latter of which is the same boundary (NW) of tract 2. This appears to then indicate that the “EXCEPTING” area is not part of the Lands Granted to City of Long Beach and appears to indicate that this portion might be then the “State’s Portion of the Offshore Area” as referenced in the Grant and the Unit Operating Agreement. Section “f” in the CSLC insider document (pg 9) defines the Contract Lands: means Tract No. 2 as described in Exhibit “A” to the Unit Agreement, and as shown on Exhibit “B” to the Unit Agreement, together with all other lands within the State’s Portion of the Offshore Area.Linework has been plotted in accordance with the methods used to produce this layer, with record lines rotated to those as listed in the descriptions. The main boundaries being the MHTL(north/northeast) that appears to be fixed for most of the area (projected to the city boundary on the east/southeast); 3 nautical miles from said MHTL on the south/southwest; and the prolongation of the NWly line of Block 50 of Alamitos Bay Tract.MJF Boundary Determination Officer 12-27-16PRC 4736The “lease area” for this lease is based on the Oil and Gas Lease and Agreement as found on the CSLC insider and recorded August 17, 1973 in BK 10855 PG 432 Official Records, Orange County. The State’s Mineral Interests are confined to Parcels “B-1” and “B-2” and are referred to as “State Mineral Lands” comprising 70.00 Acres. The lessee each has a right to certain uses including but not limited to usage of utility corridors, 110 foot radius parcels surrounding well-sites and roads. The State also has access to those same roads per this agreement/lease. Those uses are allowed in what are termed “State Lands”-Parcel E and “Leased Lands” which are defined as the “South Bolsa Lease Area”-Parcel C (2 parcels) and “North Bolsa Lease Area”-Parcel D. The “State Lands”-Parcel E are actually 3 parcels, 2 of which are within road right-of-ways. MJF Boundary Determination Officer 12-28-16

This dataset contains polygon features representing the Chesapeake Bay Preservation Areas.

Data collected and complied by Department of City Planning maintained on as needed basis by the Department of City Planning.

Any land designated by the city pursuant to Part III of the Chesapeake Bay Preservation Area Designation and Management Regulations, 9 VAC 10-20-70, and section 10.1-2107 of the Code of Virginia. A Chesapeake Bay Preservation Area shall consist of a resource protection area and a resource management area.

The Chesapeake Bay and its tributaries constitute an important and productive estuarine system, providing economic and social benefits to the citizens of the City of Norfolk and the Commonwealth of Virginia. The health of the Chesapeake Bay is vital to maintaining the city's economy and the welfare of its citizens. The intent of the city and the purposes of the Overlay District are to: (1) protect existing high quality state waters; (2) restore all other state waters to a condition or quality that will permit all reasonable public uses and will support the propagation and growth of all aquatic life, including game fish, which might reasonably be expected to inhabit them; (3) safeguard the clean waters of the Commonwealth from pollution; (4) prevent any increase in pollution; (5) reduce existing pollution; and (6) promote water resource conservation in order to provide for the health, safety, and welfare of the present and future citizens of the city.

Any and all data sets are for graphical representations only and should not be used for legal purposes. Any determination of topography or contours, or any depiction of physical improvements, property lines or boundaries is for general information only and shall not be used for the design, modification, or construction of improvement to real property or for flood plain determination.

The dataset can be available using the link:https://norfolkgisdata-orf.opendata.arcgis.com/datasets/712ae93509fb4bb6947bab945d30bd77_0/about

This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.

This shapefile (polygon feature) contains the boundary of the July 1, 2022 100-Year Storm Flood Risk Zone, one of the layers of the July 1, 2022 100-Year Storm Flood Risk Map. Areas within this boundary are highly likely to experience “deep and contiguous” flooding during a 100-year storm. A 100-year storm is a storm that has a 1% chance of occurring in a given year. “Deep and contiguous flooding” means flooding at least 6-inches deep spanning an area at least the size of an average City block. The 100-Year Storm Flood Risk Zone does not provide the exact depth of flooding at a given location. It also does not show areas in the City that may experience shallower and/or more localized flooding in a 100-year storm. Finally, the 100-Year Storm Flood Risk Zone shows flood risk from storm runoff only. It does not consider flood risk in San Francisco from other causes such as shoreline overtopping and overland inundation from the San Francisco Bay or Pacific Ocean.

In addition to the 100-Year Storm Flood Risk Zone, the 100-Year Storm Flood Risk Map shows:

• “Areas not served by the Combined Sewer and Stormwater Collection System” - showing where data for rainfall driven storm runoff is not available, and where flood risk has not been analyzed. • “Historical Shoreline”, “Historical Creeks”, and “Historical Waterbodies” - historical hydrology layers to illustrate the general topography of low-lying areas in the City. The Horizontal Datum used for the GIS layers is “NAD_1983_2011_StatePlane_California_III_FIPS_0403_Ft_US.”

Notes on Usage

At a minimum, the 100-Year Storm Flood Risk Map is updated by the San Francisco Public Utilities Commission (SFPUC) on an annual basis on or before July 1 to account for any parcel review requests that remove properties from the Flood Zone. To confirm the latest version of the 100-Year Storm Flood Risk Map, check the SFPUC website at https://sfpuc.org/learning/emergency-preparedness/flood-maps to see if the map has been updated since the date of this shapefile or if there have been any parcel review determinations that identify parcels that are no longer part of the 100-Year Flood Risk Zone. The most recent official map, associated documentation, and list of parcels removed from the map from a parcel review process are available at https://sfpuc.org/learning/emergency-preparedness/flood-maps. Please be advised that the parcels listed are no longer considered to be within the 100-Year Flood Risk Zone as a result of the parcel review process. As of July 2022, this list is updated on an ongoing basis. Check the SFPUC website for any changes to this schedule.

The boundaries of this zone align with San Francisco parcel boundaries. The user should confirm proper projection or use of the webmap at https://sfpuc.org/learning/emergency-preparedness/flood-maps to properly identify parcels within the flood zone.

A log of dataset alerts open, monitored or resolved on the open data portal. Alerts can include issues as well as deprecation or discontinuation notices.

This dataset includes boundaries for all Brisbane City Council suburbs. This data is derived from the Queensland Government Digital Cadastral Database (DCDB).What we call suburbs are officially called localities. Localities are the names and boundaries used for addressing. This dataset includes the Brisbane City Local Government Area localities that are Brisbane suburbs, and five localities within Moreton Bay. The five localities in Morton Bay are called:BulwerCowan CowanKooringalMoreton BayMoreton Island The three islands, Green, Mud, and St Helena, have the locality called Moreton Bay.

The map title is Happy Valley-Goose Bay. Tactile map scale. 2 centimetres = 3 kilometres North arrow pointing to the north. Happy Valley-Goose Bay and surrounding area. Goose Bay is shown with a wavy symbol to indicate water. The Churchill River, shown with a wavy symbol to indicate water, flows left to right into Goose Bay. Main road, Trans Labrador Highway. A circle with the shape of an airplane in it indicates Goose Bay Airport to the west of the city. Tactile maps are designed with Braille, large text, and raised features for visually impaired and low vision users. The Tactile Maps of Canada collection includes: (a) Maps for Education: tactile maps showing the general geography of Canada, including the Tactile Atlas of Canada (maps of the provinces and territories showing political boundaries, lakes, rivers and major cities), and the Thematic Tactile Atlas of Canada (maps showing climatic regions, relief, forest types, physiographic regions, rock types, soil types, and vegetation). (b) Maps for Mobility: to help visually impaired persons navigate spaces and routes in major cities by providing information about streets, buildings and other features of a travel route in the downtown area of a city. (c) Maps for Transportation and Tourism: to assist visually impaired persons in planning travel to new destinations in Canada, showing how to get to a city, and streets in the downtown area.

The map title is Toronto-Bay. Tactile map scale. 2.0 centimetres = 100 metres North arrow pointing to the north. The points of interest in the downtown area of Toronto around Bay Street are labelled with type and Braille expanded in the PDF file. Main streets are labelled with type and Braille expanded in the PDF file. Secondary streets are not labelled. Tactile maps are designed with Braille, large text, and raised features for visually impaired and low vision users. The Tactile Maps of Canada collection includes: (a) Maps for Education: tactile maps showing the general geography of Canada, including the Tactile Atlas of Canada (maps of the provinces and territories showing political boundaries, lakes, rivers and major cities), and the Thematic Tactile Atlas of Canada (maps showing climatic regions, relief, forest types, physiographic regions, rock types, soil types, and vegetation). (b) Maps for Mobility: to help visually impaired persons navigate spaces and routes in major cities by providing information about streets, buildings and other features of a travel route in the downtown area of a city. (c) Maps for Transportation and Tourism: to assist visually impaired persons in planning travel to new destinations in Canada, showing how to get to a city, and streets in the downtown area.

This landslide susceptibility mapping study is a requirement of the Bay of Plenty Regional Policy Statement. The methodology of the study is generally based on the “basic” level assessment described in the Australian Geomechanics Society Guideline for Landslide Susceptibility, Hazard and Risk Zoning (AGS, 2007a).The study area consists of the Bay of Plenty regional boundary, excluding the Tauranga City district and five other areas where landslide susceptibility studies have previously been carried out or are currently being undertaken. It also includes the part of the Rotorua Lakes District that lies within the Waikato region. The geology, geomorphology and characteristic mechanisms of landsliding across the study area are described, based on the results of a literature review of available information. Factors that influence slope stability are identified from the results of the literature review, including correlation to an inventory of previous landslides. Assessment of the landslide susceptibility is based on weighting of the influencing factors and combining these in Geographical Information System (GIS) platform using available geospatial datasets. Four categories of landslide susceptibility are described, from Very Low to High, and these are mapped across the region in GIS showing the spatial distribution and extent of the different susceptibility categories. The maps do not present potential areas of regression and runout of landslide debris, which have not been assessed at this stage. The region was mapped at a 1:50,000 scale, except for urban areas identified by BOPRC, which were mapped at 1:25,000. The maps should be used at appropriate scales suggested, and were made available to the public through the Council natural hazards GIS viewer, the scale should be restricted to 1:25,000 for the 12 identified Urban Areas, and 1:50,000 for the remainder of the region.

The map title is Thunder Bay. Tactile map scale. 2 centimetres = 3 kilometres North arrow pointing to the north. Thunder Bay and surrounding area. Lake Superior is shown with a wavy symbol to indicate water. Pie Island is shown in Lake Superior. Loch Lomond, located south of the airport, is shown with a wavy symbol to indicate water. Main roads, Route 102, Route 17/11 and Route 61. A circle with a dot in the middle indicates a bus terminal in the centre of the city. A circle with the shape of an airplane in it indicates Thunder Bay International Airport to the west of the city. Tactile maps are designed with Braille, large text, and raised features for visually impaired and low vision users. The Tactile Maps of Canada collection includes: (a) Maps for Education: tactile maps showing the general geography of Canada, including the Tactile Atlas of Canada (maps of the provinces and territories showing political boundaries, lakes, rivers and major cities), and the Thematic Tactile Atlas of Canada (maps showing climatic regions, relief, forest types, physiographic regions, rock types, soil types, and vegetation). (b) Maps for Mobility: to help visually impaired persons navigate spaces and routes in major cities by providing information about streets, buildings and other features of a travel route in the downtown area of a city. (c) Maps for Transportation and Tourism: to assist visually impaired persons in planning travel to new destinations in Canada, showing how to get to a city, and streets in the downtown area.

The map title is Iqaluit. Tactile map scale. 2.7 centimetres = 10 kilometres North arrow pointing to the north. Iqaluit general area. Main streets. Airport. Frobisher Bay. Tactile maps are designed with Braille, large text, and raised features for visually impaired and low vision users. The Tactile Maps of Canada collection includes: (a) Maps for Education: tactile maps showing the general geography of Canada, including the Tactile Atlas of Canada (maps of the provinces and territories showing political boundaries, lakes, rivers and major cities), and the Thematic Tactile Atlas of Canada (maps showing climatic regions, relief, forest types, physiographic regions, rock types, soil types, and vegetation). (b) Maps for Mobility: to help visually impaired persons navigate spaces and routes in major cities by providing information about streets, buildings and other features of a travel route in the downtown area of a city. (c) Maps for Transportation and Tourism: to assist visually impaired persons in planning travel to new destinations in Canada, showing how to get to a city, and streets in the downtown area.