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.

Purpose

City 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 Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_CITY: CDTFA incorporated city name
• CDTFA_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 Bureau
• CENSUS_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 System
• GNIS_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 county
• CENSUS_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

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.

Purpose

County 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 Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers (this dataset)
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)
• 
  

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_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 Bureau
• CENSUS_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 System
• GNIS_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 county
• CENSUS_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.

Crop Boundaries

## Overview

Crop Boundaries is a dataset for instance segmentation tasks - it contains Crop Boundaries annotations for 606 images.

## Getting Started

You can download this dataset for use within your own projects, or fork it into a workspace on Roboflow to create your own model.

  ## License

  This dataset is available under the [CC BY 4.0 license](https://creativecommons.org/licenses/CC BY 4.0).

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

Boundaries

## Overview

Boundaries is a dataset for object detection tasks - it contains Signboard annotations for 504 images.

## Getting Started

You can download this dataset for use within your own projects, or fork it into a workspace on Roboflow to create your own model.

  ## License

  This dataset is available under the [CC BY 4.0 license](https://creativecommons.org/licenses/CC BY 4.0).

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.

Purpose

County 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 layer removes the coastal buffer polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_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 Bureau
• CENSUS_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 System
• GNIS_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 county
• CENSUS_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.

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The Boundary layer consists of lines representing the boundaries of Parcels and Legal Descriptions. (See the metadata for those two layers.) Boundary lines are the places that are surveyed in order to delimit the extent of Parcels and Legal Descriptions. The character and accuracy of Boundary locations is held in the attributes of the Points that are at the ends of Boundary lines. All the boundaries of Parcels and Legal Descriptions are covered by a Boundary line. Currently the Boundary layer has little functionality. The only distinction it makes is between upland boundaries and shorelines. In the future Boundary lines will have a richer set of attributes in order to accommodate cartographic needs to distinguish between types of boundaries.WA Boundaries Metadata

This map contains speed limits for all roads in the National Road Database (NWB).

Description from Rijkswaterstaat: "Since 2022, the features are Trees, Entrances, Bowl Boundaries, Parking Points , Parking spaces, Traffic center, Traffic types, Road width, Road categorization and Road narrowings added as a csv file to the database."

"The possible speeds that can be entered are 5, 15, 20, 30 40, 50, 60, 70, 80, 90, 100, 120, 130 km per hour, N/A and unknown. The speeds only apply to roads that are open to car traffic. On cycle paths , footpaths and other roads that are not open to car traffic, the speed is unknown. This also applies to the ferry connections. The file provides variable maximum speeds with a start time and an end time. These mainly apply to motorways. Outside this period with the indicated start time and end time, an alternative speed applies. So, for example, between 6:00 AM and 7:00 PM the speed limit is 100 km per hour and outside of that the maximum speed is 120 km per hour."

Traffic decisions, via the Knowledge and Operation Center for Official Government Publications (KOOP), are used to detect and process changes in speed limits.

Disclaimer:

A number of roads are currently still listed as "unknown" while the speed limit does not actually apply here (pedestrian paths and cycle paths, for example).

Source:

We keep track of speeds within a tool from the National Road Traffic Data Portal (NDW). You can view the map that the NDW offers via: https:// weghouden.ndw.nu/weghouden/wegvakken/323165013/bedrijven/maximumspeed. You can also download the data in shapefile format via https://opendata.ndw.nu/ .

To unlock the speeds within our Eindhoven Open Data portal we use a service from Rijkswaterstaat: https:// geo.rijkswaterstaat.nl/arcgis/rest/services/GDR/maximum_speeds_roads/FeatureServer/0

You can obtain more information and different publication formats from the Rijkswaterstaat data source via: https://maps.rijkswaterstaat.nl/dataregister-publicatie/srv/eng/catalog.search#/metadata/ d7df2888-0c0d-40f1-9b35-3c1a01234d01

Boundary Box Making

## Overview

Boundary Box Making is a dataset for object detection tasks - it contains Words annotations for 3,181 images.

## Getting Started

You can download this dataset for use within your own projects, or fork it into a workspace on Roboflow to create your own model.

  ## License

  This dataset is available under the [CC BY 4.0 license](https://creativecommons.org/licenses/CC BY 4.0).

Dataset SummaryAbout this data:This is a Feature Layer of the NEW City of Rochester City Council Districts (Beginning 2024). If you are interested in viewing and downloading a PDF version of the Map, please click HERE. East Council DistrictThe East District shall include all the area described within the boundaries as follows;Beginning on the centerline of the Genesee River and its intersection with East Main Street; Thence easterly along the centerline of East Main Street to its intersection with the centerline of North Goodman Street; Thence northerly along the centerline of North Goodman Street to its intersection with the centerline of Clifford Avenue; Thence easterly along the centerline of Clifford Avenue to the easterly boundary of the City; Thence southerly along the easterly line of the City including the area known as Tryon Park to the southerly boundary of the City; Thence westerly along the southerly boundary of the City to it’s intersection with the centerline of Elmwood Avenue; Thence westerly along the centerline of Elmwood Avenue to its intersection with the centerline of South Avenue; Thence northerly along the centerline of South Avenue to its intersection with the centerline of Linden Street; Thence easterly along the centerline of Linden Street to its intersection with the centerline of Mount Vernon Avenue; Thence northerly along the centerline of Mount Vernon Avenue to its intersection with the centerline of Caroline Street; Thence easterly along the centerline of Caroline Street to its intersection with the centerline of Meigs Street; Thence northerly along the centerline of Meigs Street to its intersection with the centerline of Interstate 490; Thence generally northwest along the centerline of Interstate 490 and the Inner Loop to the centerline of the Genesee River; Thence northerly along the centerline of the Genesee River to its intersection with the centerline of the East Main Street and to the place of beginning.Northeast Council DistrictThe Northeast District shall include all the area described within the boundaries as follows:Beginning at the intersection of the centerline of the Genesee River and Marina Drive; Thence southerly along the centerline of the Genesee River to its intersection with the centerline of the East Main Street; Thence easterly along the centerline of East Main Street to its intersection with the centerline of North Goodman Street; Thence northerly along the centerline of North Goodman Street to its intersection with the centerline of Clifford Avenue; Thence easterly along the centerline of Clifford Avenue to the easterly boundary of the City; Thence northerly along the easterly boundary of the City to the northerly boundary of the City; Thence westerly along the northerly boundary of the City to a point 33 feet easterly from the centerline of Culver Road; Thence northerly 33 feet easterly from and parallel to the centerline of Culver Road to a point 33 feet northerly from the centerline of Hoffman Road produced easterly; Thence northwesterly 33 feet northerly from and parallel to the centerline of Hoffman Road to a point 33 feet easterly from the centerline of Wisner Road; Thence northerly 33 feet easterly from and parallel to the centerline of Wisner Road to the southerly boundary of Durand Eastman Park; Thence easterly along the southerly line of Durand Eastman Park to the easterly line of Durand Eastman Park; Thence generally northerly along the easterly boundary of Durand Eastman Park to the shore of Lake Ontario; Thence westerly along the shore of Lake Ontario to the westerly line of Durand Eastman Park; Thence generally southerly along the westerly line of Durand Eastman Park to the southerly line of Durand Eastman Park; Thence generally easterly along the southerly line of Durand Eastman Park to a point 33 feet westerly from the centerline of Wisner Road; Thence southerly 33 feet westerly from and parallel to the centerline of Wisner Road to a point 33 feet south of the centerline of Hoffman Road produced westerly; Thence southeasterly 33 feet southerly from and parallel to the centerline of Hoffman Road to a point 33 feet westerly from the centerline of Culver Road; Thence southerly 33 feet westerly from and parallel to the centerline of Culver Road to the northerly boundary line of the City; Thence westerly along the northerly line of the City to the easterly line of the City; Thence generally northerly along the said easterly City line to the centerline of Marina Drive; Thence westerly along the centerline of Marina drive to the center of the Genesee River and to the point of beginning.Northwest Council DistrictThe Northwest District shall include all the area described within the boundaries as follows:Beginning at the intersection of the centerline of the Genesee River with the centerline of Marina Drive; Thence southerly along the centerline of the Genesee River to its intersection with the centerline of the Inner Loop; Thence southwesterly along the centerline of the Inner Loop to its intersection with the centerline of Interstate 490; Thence northwesterly along the centerline of Interstate 490 to its intersection with the centerline of Brown Street; Thence southwesterly along the centerline of Brown Street to its intersection with the centerline of the CSX Rochester Sub Line Railroad; Thence southwesterly along the centerline of the CSX Rochester Sub Line Railroad to its intersection with the westerly boundary of the City; Thence northerly following the westerly boundary of the City to its intersection with the shore of Lake Ontario; Thence easterly along the shore of Lake Ontario to the easterly boundary of the City; Thence southerly along the easterly boundary of the City to the centerline of Marina Drive; Thence westerly along the centerline of Marina drive to the center of the Genesee River and to the point of beginning.South Council DistrictThe South District shall include all the area described within the boundaries as follows:Beginning at the intersection of the westerly boundary of the City with centerline of the CSX Rochester Sub Line Railroad; Thence easterly along the centerline of the CSX Rochester Sub Line Railroad to its intersection with the centerline of Brown Street; Thence northeasterly along the centerline of Brown Street to its intersection with the centerline of Interstate 490; Thence easterly along the centerline of Interstate 490 to its intersection with the centerline of the Inner Loop; Thence northeasterly along the centerline of the Inner Loop to its intersection with the centerline of the Genesee River; Thence southerly along the centerline of the Genesee River to its intersection with the centerline of Interstate 490; Thence southeasterly along the centerline of Interstate 490 to its intersection with the centerline of Meigs Street; Thence southerly along the centerline of Meigs Street to its intersection with the centerline of Caroline Street; Thence westerly along the centerline of Caroline Street to its intersection with the centerline of Mount Vernon Avenue; Thence southerly along the centerline of Mount Vernon Avenue to its intersection with the centerline of Linden Street; Thence westerly along the centerline of Linden Street to its intersection with the centerline of South Avenue; Thence southerly along the centerline of South Avenue to its intersection with the centerline of Elmwood Avenue; Thence easterly along the centerline of Elmwood Avenue to its intersection with the easterly boundary of the City; Thence generally southerly along the easterly boundary of the City to the southerly boundary of the City; Thence generally westerly along the southerly boundary of the City, including Genesee Valley Park, to the westerly boundary of the City; Thence generally along the westerly boundary of the City, including the Rochester‑Monroe County International Airport, to its intersection with the centerline of CSX Rochester Sub Line Railroad and to the point of beginning.Data Dictionary:District: Quadrant of the City of Rochester where the Neighborhood Service Center (NSC) is located (S, NE, NW, E).Source:This data is maintained by the City of Rochester.

When you build with TomTom Maps APIs and map data sets, you build with a partner that combines three decades of mapping experience with the speed and soul of a start-up. We’re proud of our roots, and we never stop looking ahead – working together with you to bring the best, freshest map data and tech to people all over the world. When change happens in the real world, our transactional mapmaking ecosystem allows us to detect, verify and deliver it to the map fast – ensuring your customers, drivers and users always enjoy the most up-to-date map data. That same speed and flexibility extends to how we help you build your mapping app: You’re in control of your map data, choosing what you want to include in your final product.

Note: These are the Department of Public Works Basemap Parcels, not the Assessor-Recorder's Taxable Parcels. See "How to use this dataset" for more information.

A. SUMMARY Parcels are defined areas of land, demarcated by boundaries to visualize distinct and legal parcels of real property. Occasionally, parcels are divided or combined, and a new parcel can be created. This dataset connects current parcels in San Francisco to historical parcels that are associated with it.

B. HOW THE DATASET IS CREATED This dataset utilizes the parcel change log to find associated parcels through an iterative process.

C. UPDATE PROCESS This dataset will be refreshed daily, though the data may not change every day.

D. HOW TO USE THIS DATASET The City and County of San Francisco has two related but distinct parcel databases. The first is managed by the Department of Public Works, is created by surveyors, and is used in the Department of Public Works basemap. Public Works parcels are used to identify very precisely where private properties end and where public City property begins (e.g. sidewalks, roads, rights of way, etc.). The second is managed by the Assessor-Recorder's Office. Assessor parcels are defined by Revenue and Taxation code and Property Tax law. The Assessor-Recorder uses official maps defined under Revenue and Taxation code section 325 in the creation of assessor parcels and are used to identify taxable property. Each of the Assessor's parcels have an Assessor's Parcel Number (APN) which is used by other departments including but not limited to Tax Collector for tax collection, DBI for permitting, and other use cases.

Though most parcels are the same between Public Works and the Assessor’s Office, they are not a perfect match. APN's are retired and activated within the timeline parameters of tax years (July – June) based on tax roll state requirements, which means there can be a lag between the Public Works parcel changing and the associated APN being updated. Public Works’ City Basemap identifies legal parcels defined by California Code Subdivision Map Act and Assessor-Recorder’s parcels identify taxable parcel boundaries defined by Revenue and Taxation Code.

Use this dataset to identify historical parcels from the Public Works Basemap that are associated with an active Public Works basemap parcel. This dataset is not a history of the Assessor-Recorder's Parcels.

E. RELATED DATASETS