Caltrans is responsible for the decennial production of the Adjusted Urban Area Boundaries for the State of California. The CA 2020 adjusted urban area file represents the current Federal Highway Administration (FHWA) approved Caltrans adjusted urban area boundaries.The Urban Area Boundaries are separated into two classifications based on population:Small Urban Areas: population ranging from 5,000 to 49,999Urbanized Areas: population of 50,000 or moreAccording to Title 23 U.S.C. 101(a)(35) and (36), Small Urban and Urbanized Area boundaries are to be adjusted in cooperation by responsible State and local officials, and subject to approval by the Secretary of Transportation. Adjustments may include the addition of significant transportation corridors and areas of growing urbanization.

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

This dataset contains the geographic boundaries of Metropolitan Planning Organizations (MPO) and is intended for metropolitan area multimodal transportation planning applications. MPOs designate the federally mandated and federally funded transportation policy-making organization in the United States. This dataset is for California only and is maintained by the Bureau of Transportation Statistics (BTS), but it has been modified by Caltrans to conform to the California County Boundary dataset. MPO organizations include representatives from local government and governmental transportation authorities and they carry out the metropolitan transportation planning process in that area.

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.

Purpose

County 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 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
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 (this dataset)
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
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

• 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
• Place Name: CDTFA incorporated (city) or county name
• 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.
• Legal 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.
• 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 System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_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.

Accuracy

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. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.This dataset is regularly updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications. PurposeCity boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use. Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal Buffers (this dataset)Counties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The dataset you are currently viewing excludes the coastal buffers for cities and counties that have them in the source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except OFFSHORE and AREA_SQMI to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov Field and Abbreviation DefinitionsCDTFA_CITY: CDTFA incorporated city nameCDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.CENSUS_GEOID: numeric geographic identifiers from the US Census BureauCENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.CDT_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or countyCENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead. Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections.Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor. CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information. CDTFA's source data notes the following about accuracy: City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties. In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose. SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon. Coastline CaveatsSome cities have buffers extending into water bodies

Striping is a Polyline FeatureClass representing the lines on the pavement as detailed by CalTrans. It is primarily used as an inventory layer in Cityworks. The layer is updated as needed by the Public Works Department and QA/QC'd quarterly by the GIS Division. Striping has the following fields:

OBJECTID: Unique identifier automatically generated by Esri type: OID, length: 4, domain: none

AssetID: Cupertino maintained GIS primary key type: String, length: 50, domain: none

Location: Further description of the location type: String, length: 50, domain: none

Status: The active or construction status of the asset in the field type: String, length: 20, domain: pwStatus domain values:['Abandoned', 'Proposed', 'Auction', 'Denied', 'Active', 'Removed', 'Not Connected']

OwnedBy: Organization which owns the asset type: String, length: 50, domain: shdOwnedBy domain values:['Cupertino', 'San Jose Water', 'CalTrans', 'PGE', 'Los Altos', 'Santa Clara', 'Private HOA', 'Saratoga', 'Other Public', 'Santa Clara County', 'San Jose', 'Santa Clara Valley Water District', 'Private', 'California Water Service', 'State Parks', 'Sunnyvale', 'Cupertino Sanitary District', 'CWA']

MaintainedBy: Organization who is responsible for maintenance of asset type: String, length: 50, domain: shdOwnedBy domain values:['Cupertino', 'San Jose Water', 'CalTrans', 'PGE', 'Los Altos', 'Santa Clara', 'Private HOA', 'Saratoga', 'Other Public', 'Santa Clara County', 'San Jose', 'Santa Clara Valley Water District', 'Private', 'California Water Service', 'State Parks', 'Sunnyvale', 'Cupertino Sanitary District', 'CWA']

CreateDate: The date the database row was initially created type: Date, length: 8, domain: none

UpdateDate: The date the database row was last updated type: Date, length: 8, domain: none

Material: Material of the stripping type: String, length: 30, domain: trafMarkingMaterial domain values:['Extruded ThermalPlastic', 'Surface Coating', 'Paint', 'Preform ThermalPlastic', 'Tape', 'RPM']

IsModified:

type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

CalTransDetail: Field containing the Caltrans code for the striping type: String, length: 30, domain: trafStripCalTran domain values:['30', '41A', 'Green Bike Lane', 'Detail (D) YL2R', '21(D)', '39A', '24', '25', '38B', '38C', '21', '22', '23', '28', '29', '40', '41', '1', '2', '22(D)', '4', '7', '6', '9', '5', '40A', '38A', '39', '27B', 'Intersection Green Bike Lane', '27C', '8', '38', 'Detail (D) WT1R', '8-20 City Standard', '11', '10', '13', '12', '15', '14', '16', '19', '32', '31', '25A', '33']

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: none

GlobalID: Unique identifier automatically generated for features in enterprise database type: GlobalID, length: 38, domain: none

RPMInstallDate:

type: Date, length: 8, domain: none

StrippingInstallDate: The date the striping was installed type: Date, length: 8, domain: none

Color: Color associated with the striping type: String, length: 50, domain: shdColor domain values:['Blue', 'White', 'Green', 'Yellow', 'Red']

NumberofReflectors: The number of reflectors along the striping segment type: SmallInteger, length: 2, domain: trafStripNumofReflectors domain values:['1', '2']

InstallDate: The date the striping was installed type: Date, length: 8, domain: none

Rotation: Field used for assigning rotation degree in Maplex Labeling Engine type: Double, length: 8, domain: none

RefreshDate: The date the data was refreshed type: Date, length: 8, domain: none

StripingWidth: The width of the striping type: SmallInteger, length: 2, domain: utilWireSize domain values:['8', '4', '6']

Shape.STLength(): The length of the shape - in feet type: Double, length: 0, domain: none

June 7, 2022 No Longer Updated Proposed Regional Bicycle and Pedestrian FacilitiesIn the past, updates to the Regional Bike Facilities layers were biennial, to coincide with updates of the Bicycle and Pedestrian Master Plan. Going forward, updates will take place annually, though major projects will be added as they are opened, if needed. The Regional Bicycle, Pedestrian, and Trails Master Plan envisions a complete transportation system that supports healthy living and active communities where bicycling and walking are viable and popular travel choices in a comprehensive, safe, and convenient network. The proposed bike facilities layer is a comprehensive layer of bikeways planned by local agencies throughout the region. This data reflects potential bicycle & pedestrian facilities in order to help guide the development of a seamless and integrated regional bikeway network. Since these facilities are in various stages of planning, all may not be eventually built. On-street facilities are aligned to the Regional Centerline; off-street facilities have been added from jurisdiction submissions or digitized using imagery, and final alignments may not have been determined. Line segments represent potential future transportation facilities for pedestrian and/or bicycle use. The "class" field signifies level of use in the design. Class 1 designates a hard-surface multi-use trail suitable for bicycle and foot traffic. It is separate from facilities for motor vehicle traffic and meets CalTrans standards for width, signage, and surface. Class 2 designates an on-street lane for bicycles only. Lanes have striping and other markings to separate them from motor vehicle traffic. There are versions of class 2 lanes that are separated from traffic with painted areas for added security and visibility for riders. Class 3 designates an on-street route for bicycles only. Routes are marked by signage only; cyclists are expected to ride with the flow of traffic.Class 4 designates a buffered bike lane. Buffered bike lanes have have striping and other markings to designate them for bicycle traffic, but also by some form of upright buffer to separate them from motor vehicle traffic. Possible buffers include curbs, planters, parked cars, and pylons. A bike lane separated by paint only is a class 2, not a class 4. Class 0 is a SACOG-created designation to indicate informal trails of local or regional importance. The large majority of these are unpaved trails bridging gaps between other facilities, but some may be paved trails that do not meet the CalTrans width requirements for inclusion as a class 1 facility. Few, if any, informal trails exist in the planning phase. Updates will occur on a rolling basis as we review plans and learn about bike/ped facilities added to plans or removed from consideration.

The California Governor’s Office of Emergency Services’ (Cal OES) CalOES California Webcams is a project to consolidate internet webcams that Cal OES might find useful during an incident. The primary audience is the general public as well as Cal OES response personnel and supporting partners. This Service Contains 2 layers:Camera Locations - This layer contains 4 Types of Cameras (The links to the images or video always point to the last updated image or live video:Fire Cameras - These include ALERTCalifornia and Alert Wildfire (Pan Tilt Zoom) Cameras. These will have their direction updated every minute.Traffic Cameras - These points will update nightly with the status of the camera and will include any new cameras.Tsunami Cameras - These will be included soon from the Tsunami Camera networkOther Cameras - Other camera networks that don't fall into the above categories that will be included as identified and deemed useful.To filter down to a specific type of camera, use the "Camera_Type" field and category names above.To filter down to only video or photos, use the "Display_Type" field and the values of (Picture, Video)Fire Camera Viewsheds - This layer contains the view sheds for the cameras in the ALERTCalifornia and Alert Wildfire Network. These are updated every minute. This layer has the same fields as the locations.The user assumes the entire risk related to their use of this information. Cal OES provides such information "as is," and disclaims any and all warranties, whether express or implied, including (without limitation) any implied warranties of merchantability or fitness for a particular purpose. In no event will Cal OES be liable to you or to any third party for any direct, indirect, incidental, consequential, special or exemplary damages or lost profit resulting from any use or misuse of this data.Cal OES GIS will update as additional webcams are found that have the required information to be put in a GIS and time permits.Sources:ALERTCaliforniaAlert WildfireCalTransHigh Performance Wireless Research & Education Network

IL Coverage of the Gateway camera snapshots. The Gateway provides camera snapshot images throughout its coverage area in the form of camera icons on its maps and images in its camera report. With a free subscription, users can also access the Gateway ftp server which contains the most up to date versions of the images available.ImgPath - this is a link to the travelmidwest.com/lmiga/showCamera.jsp popup window that allows the user to select another direction, if availableCameraLocation - a text description of where the camera is locatedCameraDirection - the direction the camera is facing (NONE, N, E, S, W, NE, NW, SE, or SW)y - latitude in decimal degreesx - longitude in decimal degreesSnapShot - public URL of camera's image file that is suitable for placement in a tag, for instanceWarningAge - "true" if the camera is more than 10 minutes old, false otherwiseTooOld - "true" if more than 30 minutes old, "false" otherwiseAgeInMinutes - integer age of camera image in minutes