Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The District boundary definitions are primarily based on the California county boundaries. The Board of Equalization (BOE) County and City Boundary web service is the authoritative source of County boundaries and this was used to digitize the district boundaries based on the data from March 2023. This data is solely for informational purposes. District 9 has been operating independent of the Central Region since November 1, 2015. Kern County remains the only split county in the state, between Districts 6 and 9 respectively. The BOE data was also used to create the district boundary layers along the coastline.
The District boundary definitions are primarily based on the California county boundaries. The Board of Equalization (BOE) County and City Boundary web service is the authoritative source of County boundaries and this was used to digitize the district boundaries based on the data from March 2023. This data is solely for informational purposes. District 9 has been operating independent of the Central Region since November 1, 2015. Kern County remains the only split county in the state, between Districts 6 and 9 respectively. The BOE data was also used to create the district boundary layers along the coastline.
This map delineates CalTRANS district boundaries. It was created for the Governor's Office of the Tribal Advisor by the California Technology Agency/GIS Unit.
The California Department of Transportation (Caltrans) and the California Energy Commission (CEC) are partnering to implement the federal National Electric Vehicle Infrastructure (NEVI) Program, which allocates $5 billion to the states to create a nationwide, interconnected network of DC fast chargers along the National Highway Systems. California's share will be $384 million over 5 years. This map was developed to help prospective applicants and interested parties identify eligible areas for infrastructure deployment.InstructionsViewers can display corridor groups, corridor segments, electric vehicle (EV) charging stations, Justice40 disadvantaged communities, Tribal lands, California-designated low-income or disadvantaged communities, metropolitan planning organizations, regional transportation planning agencies, California state legislative districts, counties, Caltrans districts, utility districts, and congressional districts in this interactive map. The map initially displays corridor groups and their corridor segments included in the Round 2 NEVI solicitation. Viewers can toggle individual layers on and off using the map layers menu located to the right of the map. Some layers are organized into groups; viewers can toggle all layers within a group or select specific ones. The legend to the left of the map will show the layers that have been turned on. There is a search tool to the right of the map that enables viewers to type in an address and locate the address on the map. A basemap selector allows viewers to view road detail. Additional information on the map can be found under the information icon. Viewers can download the map files by clicking on the Data and Supplemental Links icon. Map layers include:A Corridor groups layer that shows designated corridor groups for California's NEVI funding program. Users can click on a corridor segment to view the start and end of each segment within a corridor group. When selected, a pop-up window will appear that identifies the corridor group number, corridor segment, corridor name, minimum number of charging stations required, minimum number of ports required, and needed locations, if applicable, for the corridor segment. Corridor group labels for enhanced accessibility. Note that labels are only visible at certain ranges (zoom in and out to view labels). A NEVI 2 corridors layer shows corridor groups eligible for Round 2 of California's NEVI funding program. NEVI 2 corridor group labels for enhanced accessibility. Note that labels are only visible at certain ranges (zoom in and out to view labels). NEVI 2 corridor segment labels for enhanced accessibility. Note that labels are only visible at certain ranges (zoom in and out to view labels). A Round 1 solicitation corridor groups layer that shows corridor groups eligible for Round 1 of California's NEVI funding program. A layer showing California and Justice40 disadvantaged or low-income communities. A layer showing California-designated disadvantaged or low-income communities. A layer showing Justice40-designated disadvantaged communities. A layer showing California Federally Recognized Tribal Lands. A layer showing Metropolitan Planning Organizations. A layer showing Regional Transportation Planning Agencies. A layer showing California State Senate Districts. A layer showing California State Assembly Districts. A layer showing California Counties. EV charging stations layers (existing DC fast charging stations that are located within one mile of a NEVI-eligible corridor offramp). One layer shows locations of EV charging stations with DC fast charging capabilities that meet the NEVI power level and four-port minimum requirement and could likely become part of the NEVI network if these stations became compliant with other NEVI program requirements such as data reporting. The other layer shows DC fast charging stations that do not meet NEVI power-level or port count requirements but could be upgraded to be NEVI-compliant. Users can click on EV charging stations and a pop-up window will appear with more information on the station (i.e., station address, total port count, minimum NEVI standard, etc.). These data were last updated in March 2024. Please refer to the Department of Energy's Alternative Fuels Data Center and PlugShare for up-to-date existing and planned DC fast charger site information. A layer showing Caltrans Districts. A layer showing Electric Utilities (IOUs and POUs). A layer showing California Congressional Districts. BackgroundThe $5 billion NEVI Program is part of the $1.2 trillion Infrastructure Investment and Jobs Act (IIJA) signed into law by President Biden in November 2021. IIJA commits significant federal funding to clean transportation and energy programs throughout the U.S. to reduce climate changing greenhouse gas emissions. Caltrans is the designated lead agency for NEVI. The CEC is their designated state energy partner. Caltrans and the CEC have partnered to create California's Deployment Plan for the National Electric Vehicle Infrastructure Program that describes how the state plans to allocate its $384 million share of federal NEVI funds to build out a network of modern, high-powered DC fast chargers along federally designated Alternative Fuel Corridors throughout California. California's latest NEVI Deployment Plan was submitted to the Joint Office of Energy and Transportation on August 1, 2023 and approved on September 29, 2023. The Plans must be updated each year over 5 years.NEVI funds must be used initially on federally-designated Alternative Fuel Corridors (shown on the map).Each NEVI-funded DC fast charge station will have a minimum of four 150 kW Combined Charging System (CCS) connectors. Stations will be located no more than 50 miles apart along freeways and highways and no more than 1 mile from a freeway exit or highway roadway. States are required to emphasize equity, with at least 40 percent of NEVI benefits going to disadvantaged, low income, rural and Tribal communities.Data SourcesData are from the Federal Highway Administration's Alternative Fuel Corridors website, the U.S. Department of Energy's Alternative Fuels Data Center Station Data for Alternative Fuel Corridors (as of September 2022), Argonne National Laboratory's Electric Vehicle Charging Justice40 Map, and the California Air Resources Board's Map of California Climate Investments Priority Populations 2022 CES 4.0. ContactPlease submit questions and comments to mediaoffice@energy.ca.gov
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The D12 Park and Ride Map App provides park and ride lots information and other transportation facilities information within Caltrans District 12. Caltrans will continue to explore opportunities to increase the number of Park and Ride facilities through coordination with OCTA, local jurisdictions, and private property owners to identify additional suitable sites.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Bottleneck Mapping is a subproject of the Mobility Performance Report, which is one of the products of the Mobility Performance Reporting and Analysis Program (MPRAP). The Mobility Performance Report is prepared by the California Department of Transportation (Caltrans) and District staff to provide detailed data about highway system performance related to congestion and mobility. Caltrans collects vehicle counts and calculates speeds at all hours of the day and all days of the week in major metropolitan areas throughout California via the Caltrans Performance Measurement System (PeMS--see Data Source tab). This information helps identify congestion bottlenecks and results in more cost-effective investments to improve the performance of the State Highway System.
Caltrans provides Safety Roadside Rest Areas as a part of the State Highway System pursuant to Streets and Highways Code, Sections 218-226.5. Safety Roadside Rest Areas provide opportunities for travelers to safely stop, stretch, take a nap, use the restroom, get water, check maps, place telephone calls, switch drivers, check vehicles and loads, and exercise pets. Rest areas reduce drowsy and distracted driving and provide a safe and convenient alternative to unsafe parking along the roadside. This dataset provides the detail rest area information collected from Right of Way and the Statewide Rest Areas List from Division of Maintenance. The data was last updated on 08-15-2023, Verification Source: CT Public Facilities Inventory List.In some cases, rest areas are closed temporarily for maintenance, the facility web links will help to check the current status of the rest areas.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
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 boundaries 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. 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 Buffers (this dataset)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 BuffersWithout 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".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.
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.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
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.
The bridge inventory data was obtained from Caltrans Structure Maintenance and Investigations (SM&I) Database as of 03/12/2024. Bridge inspectors are responsible for the safety and integrity of 13,261 State Highway bridges by performing inspections in accordance with federal regulations.
High-Occupancy Vehicle (HOV) lane, also known as the carpool or diamond lane, is a traffic management strategy to promote and encourage ridesharing; thereby alleviating congestion and maximizing the people-carrying capacity of California highways. HOV lane is usually located on the inside (left) lane and is identified by signs along the freeway and white diamond symbols painted on the pavement. In Northern California, HOV lanes are only operational on Monday thru Friday during posted peak congestion hours, for example: between 6 a.m. - 10 a.m. and 3 p.m. - 7 p.m. All other vehicles may use the lanes during off-peak hours. This is referred to as "part-time" operation. In Southern California, HOV lanes are generally separated from other lanes by a buffer zone. The HOV lanes are in effect 24-hours a day, 7-days a week, referred to as "full-time" operation. The locations of the HOV system are based on postmiles derived from an excel spreadsheet maintained by Caltrans, Division of Traffic Operations, Office of Traffic Management. High-Occupancy Vehicle Systems Page
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The National Highway System consists of a network of roads important to the economy, defense and mobility. On October 1, 2012 the existing National Highway System (NHS) was expanded to include all existing Principal Arterials (i.e. Functional Classifications 1, 2 and 3) to the new Enhanced NHS.
Under MAP-21, the Enhanced NHS is composed of rural and urban roads nationwide serving major population centers, international border crossings, intermodal transportation facilities, and major travel destinations.The NHS includes:
The Interstate System.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
StateHighways is used to display state highways on a digital map display. Each record represents a segment of California state highway where the county, route, postmile prefix, and postmile suffix are unchanging, and there are no gaps or overlaps in the postmiles.
Each segment is coded with the district, county, route, postmile prefix (if any), begin postmile, end postmile, and postmile suffix (if any). One additional field - AlignCode - should be understood by the user for effective use of this data set (refer to the Entity and Attribute Information section of this metadata).
AlignCode indicates if the state highway segment is on a Right alignment, Left alignment, Right side of an independent alignment or Left side of an independent alignment. Where TSN (Transportation System Network - the source database) considers most state highways to have just a centerline, the underlying LRS (Linear Referencing System) linework that these segments are based upon has a line for each direction.
On undivided highways the right and left lines are identical. On divided highways the right and left are separated, but TSN treats the segment as a single centerline. In the last case where highways are not only divided but also have different lengths (where the right and left carriageway diverge around physical obstacles or are separated onto different one-way streets) the underlying linework has dual carriageways, and TSN treats the segment as an "independent alignment". In some cases (especially for small-scale mapping), it may be appropriate to display linework for just one alignment (e.g. Right alignment), and only for the other side where TSN indicates independent right and left alignments. In other cases (e.g. large-scale mapping), it may be appropriate to display postmiles for both alignments, regardless of how TSN treats the segment.
This is an example of a query string that displays linework only for the right alignment where TSN indicates just a centerline, and on both right and left alignments where TSN indicates independent alignments: "AlignCode" <> 'Left'.
The bOdometer and eOdometer fields represent the actual distance in miles from the start of the highway to the begin and end of each highway section. This is in contrast to the begin and end postmile values, which no longer represent these values as each highway is realigned (and made longer or shorter) over time.
Provide compiled GTFS schedule data in geospatial format. Transit routes associates route information to shapes. Transit stops associates aggregated stop times and route information aggregated for each stops.
The objective is to delineate potential crude by rail routes across California, focusing on a subset of the Caltrans "California Rail Network" dataset. Specifically, this subset comprises Union Pacific and BNSF routes, the primary carriers for crude by rail in the state. For the original dataset, please refer to the Caltrans GIS Data Hub web page.The purpose of the data is to depict the rail network by utilizing available reference data and information from the California Region Timetable 20. Within the Rail feature class, alignment details for passenger and freight railroad lines are included, encompassing commuter rail and heavy rail. This feature class facilitates the selection of various rail alignments in California, covering passenger, commuter, recreational, freight, and shortline rail, excluding BART.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The California Department of Transportation (Caltrans) and California Department of Fish and Game (CDFG) commissioned the California Essential Habitat Connectivity Project because a functional network of connected wildlands is essential to the continued support of California's diverse natural communities in the face of human development and climate change. The Essential Connectivity Map depicts large, relatively natural habitat blocks that support native biodiversity (Natural Landscape Blocks) and areas essential for ecological connectivity between them (Essential Connectivity Areas). This coarse-scale map was based primarily on the concept of ecological integrity, rather than the needs of particular species. Essential Connectivity Areas are placeholder polygons that can inform land-planning efforts, but that should eventually be replaced by more detailed Linkage Designs, developed at finer resolution based on the needs of particular species and ecological processes. It is important to recognize that even areas outside of Natural Landscape Blocks and Essential Connectivity Areas support important ecological values that should not be "written off" as lacking conservation value. Furthermore, because the Essential Habitat Connectivity Map was created at the statewide scale, based on available statewide data layers, and ignored Natural Landscape Blocks smaller than 2,000 acres squared, it has errors of omission that should be addressed at regional and local scales.
Use GTFS schedule trips, stop_times, shapes, and stops to estimate whether corridor segments have scheduled frequencies of 15 minutes or less.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The California Department of Transportation (Caltrans) and California Department of Fish and Game (CDFG) commissioned the California Essential Habitat Connectivity Project because a functional network of connected wildlands is essential to the continued support of Californias diverse natural communities in the face of human development and climate change. The Essential Connectivity Map depicts large, relatively natural habitat blocks that support native biodiversity (Natural Landscape Blocks) and areas essential for ecological connectivity between them (Essential Connectivity Areas). This coarse-scale map was based primarily on the concept of ecological integrity, rather than the needs of particular species. Essential Connectivity Areas are placeholder polygons that can inform land-planning efforts, but that should eventually be replaced by more detailed Linkage Designs, developed at finer resolution based on the needs of particular species and ecological processes. It is important to recognize that even areas outside of Natural Landscape Blocks and Essential Connectivity Areas support important ecological values that should not be "written off" as lacking conservation value. Furthermore, because the Essential Habitat Connectivity Map was created at the statewide scale, based on available statewide data layers, and ignored Natural Landscape Blocks smaller than 2,000 acres squared, it has errors of omission that should be addressed at regional and local scales.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The District boundary definitions are primarily based on the California county boundaries. The Board of Equalization (BOE) County and City Boundary web service is the authoritative source of County boundaries and this was used to digitize the district boundaries based on the data from March 2023. This data is solely for informational purposes. District 9 has been operating independent of the Central Region since November 1, 2015. Kern County remains the only split county in the state, between Districts 6 and 9 respectively. The BOE data was also used to create the district boundary layers along the coastline.