The land area of Running Springs, CA was 4 in 2018. The land area of Santa Ynez, CA was 5 in 2018.

Land Area

Water Area

Land area is a measurement providing the size, in square miles, of the land portions of geographic entities for which the Census Bureau tabulates and disseminates data. Area is calculated from the specific boundary recorded for each entity in the Census Bureau's geographic database. Land area is based on current information in the TIGER® data base, calculated for use with Census 2010.

Water Area figures include inland, coastal, Great Lakes, and territorial sea water. Inland water consists of any lake, reservoir, pond, or similar body of water that is recorded in the Census Bureau's geographic database. It also includes any river, creek, canal, stream, or similar feature that is recorded in that database as a two- dimensional feature (rather than as a single line). The portions of the oceans and related large embayments (such as Chesapeake Bay and Puget Sound), the Gulf of Mexico, and the Caribbean Sea that belong to the United States and its territories are classified as coastal and territorial waters; the Great Lakes are treated as a separate water entity. Rivers and bays that empty into these bodies of water are treated as inland water from the point beyond which they are narrower than 1 nautical mile across. Identification of land and inland, coastal, territorial, and Great Lakes waters is for data presentation purposes only and does not necessarily reflect their legal definitions.

Above charts are based on data from the U.S. Census American Community Survey | ODN Dataset | API - Notes:

1. ODN datasets and APIs are subject to change and may differ in format from the original source data in order to provide a user-friendly experience on this site.

2. To build your own apps using this data, see the ODN Dataset and API links.

3. If you use this derived data in an app, we ask that you provide a link somewhere in your applications to the Open Data Network with a citation that states: "Data for this application was provided by the Open Data Network" where "Open Data Network" links to http://opendatanetwork.com. Where an application has a region specific module, we ask that you add an additional line that states: "Data about REGIONX was provided by the Open Data Network." where REGIONX is an HREF with a name for a geographical region like "Seattle, WA" and the link points to this page URL, e.g. http://opendatanetwork.com/region/1600000US5363000/Seattle_WA

Geographic and Area Datasets Involving Santa Ynez, CA or Running Springs, CA

  • API

    Vital Signs: Migration - Bay Area

    data.bayareametro.gov | Last Updated 2019-10-25T20:40:04.000Z

    VITAL SIGNS INDICATOR Migration (EQ4) FULL MEASURE NAME Migration flows LAST UPDATED December 2018 DESCRIPTION Migration refers to the movement of people from one location to another, typically crossing a county or regional boundary. Migration captures both voluntary relocation – for example, moving to another region for a better job or lower home prices – and involuntary relocation as a result of displacement. The dataset includes metropolitan area, regional, and county tables. DATA SOURCE American Community Survey County-to-County Migration Flows 2012-2015 5-year rolling average http://www.census.gov/topics/population/migration/data/tables.All.html CONTACT INFORMATION vitalsigns.info@bayareametro.gov METHODOLOGY NOTES (across all datasets for this indicator) Data for migration comes from the American Community Survey; county-to-county flow datasets experience a longer lag time than other standard datasets available in FactFinder. 5-year rolling average data was used for migration for all geographies, as the Census Bureau does not release 1-year annual data. Data is not available at any geography below the county level; note that flows that are relatively small on the county level are often within the margin of error. The metropolitan area comparison was performed for the nine-county San Francisco Bay Area, in addition to the primary MSAs for the nine other major metropolitan areas, by aggregating county data based on current metropolitan area boundaries. Data prior to 2011 is not available on Vital Signs due to inconsistent Census formats and a lack of net migration statistics for prior years. Only counties with a non-negligible flow are shown in the data; all other pairs can be assumed to have zero migration. Given that the vast majority of migration out of the region was to other counties in California, California counties were bundled into the following regions for simplicity: Bay Area: Alameda, Contra Costa, Marin, Napa, San Francisco, San Mateo, Santa Clara, Solano, Sonoma Central Coast: Monterey, San Benito, San Luis Obispo, Santa Barbara, Santa Cruz Central Valley: Fresno, Kern, Kings, Madera, Merced, Tulare Los Angeles + Inland Empire: Imperial, Los Angeles, Orange, Riverside, San Bernardino, Ventura Sacramento: El Dorado, Placer, Sacramento, Sutter, Yolo, Yuba San Diego: San Diego San Joaquin Valley: San Joaquin, Stanislaus Rural: all other counties (23) One key limitation of the American Community Survey migration data is that it is not able to track emigration (movement of current U.S. residents to other countries). This is despite the fact that it is able to quantify immigration (movement of foreign residents to the U.S.), generally by continent of origin. Thus the Vital Signs analysis focuses primarily on net domestic migration, while still specifically citing in-migration flows from countries abroad based on data availability.

  • API

    Vital Signs: Fatalities From Crashes – by crash

    data.bayareametro.gov | Last Updated 2018-07-06T18:04:12.000Z

    VITAL SIGNS INDICATOR Injuries From Crashes (EN4-6) FULL MEASURE NAME Fatalities from crashes (traffic collisions) LAST UPDATED October 2017 DESCRIPTION Fatalities from crashes refers to deaths as a result of injuries sustained in collisions. The California Highway Patrol includes deaths within 30 days of the collision that are a result of injuries sustained as part of this metric. This total fatalities dataset includes fatality counts for the region and counties, as well as individual collision data and metropolitan area data. DATA SOURCE National Highway Safety Administration: Fatality Analysis Reporting System CONTACT INFORMATION vitalsigns.info@bayareametro.gov METHODOLOGY NOTES (across all datasets for this indicator) The data is reported by the National Highway Safety Administration's Fatalities Analysis Reporting System. 2016 data comes from the California Highway Patrol (CHP) to the Statewide Integrated Traffic Records System (SWITRS), which was accessed via SafeTREC’s Transportation Injury Mapping System (TIMS). The data was tabulated using provided categories specifying injury level, individuals involved, causes of collision, and location/jurisdiction of collision (for more: http://tims.berkeley.edu/help/files/switrs_codebook.doc). Fatalities were normalized over historic population data from the US Census and California Department of Finance and vehicle miles traveled (VMT) data from the Federal Highway Administration. For more regarding reporting procedures and injury classification see the California Highway Patrol Manual (http://www.nhtsa.gov/nhtsa/stateCatalog/states/ca/docs/CA_CHP555_Manual_2_2003_ch1-13.pdf).

  • API

    Wildfire - Fire Risk and Fire Responsibility Areas (HESS)

    data.bayareametro.gov | Last Updated 2023-06-09T19:12:13.000Z

    Wildfire - Fire Risk and Fire Responsibility Areas (CAL FIRE) for development of the Parcel Inventory dataset for the Housing Element Site Selection (HESS) Pre-Screening Tool. ** This data set represents Moderate, High, and Very High Fire Hazard Severity Zones in State Responsibility Areas (SRA) and Very High Fire Hazard Severity Zones in Local Responsibility Areas (LRA) for the San Francisco Bay Region and some of its surrounding counties. The data was assembled by the Metropolitan Transportation Commission from multiple shapefiles provided by the California Department of Forestry and Fire Protection. The SRA data was extracted from a statewide shapefile and the LRA data is a combination of county shapefiles. All source data was downloaded from the Office of the State Fire Marshal's Fire Hazard Severity Zones Maps page (https://osfm.fire.ca.gov/divisions/community-wildfire-preparedness-and-mitigation/wildland-hazards-building-codes/fire-hazard-severity-zones-maps/). ** State Responsibility Areas PRC 4201 - 4204 and Govt. Code 51175-89 direct CAL FIRE to map areas of significant fire hazards based on fuels, terrain, weather, and other relevant factors. These zones, referred to as Fire Hazard Severity Zones (FHSZ), define the application of various mitigation strategies to reduce risk associated with wildland fires. CAL FIRE is remapping FHSZ for SRA and Very High Fire Hazard Severity Zones (VHFHSZ) recommendations in LRA to provide updated map zones, based on new data, science, and technology. Local Responsibility Areas Government Code 51175-89 directs the CAL FIRE to identify areas of very high fire hazard severity zones within LRA. Mapping of the areas, referred to as VHFHSZ, is based on data and models of, potential fuels over a 30-50 year time horizon and their associated expected fire behavior, and expected burn probabilities to quantify the likelihood and nature of vegetation fire exposure (including firebrands) to buildings. Details on the project and specific modeling methodology can be found at https://frap.cdf.ca.gov/projects/hazard/methods.html. Local Responsibility Area VHFHSZ maps were initially developed in the mid-1990s and are now being updated based on improved science, mapping techniques, and data. Local government had 120 days to designate, by ordinance, very high fire hazard severity zones within their jurisdiction after receiving the CAL FIRE recommendations. Local governments were able to add additional VHFHSZs. There was no requirement for local government to report their final action to CAL FIRE when the recommended zones are adopted. Consequently, users are directed to the appropriate local entity (county, city, fire department, or Fire Protection District) to determine the status of the local fire hazard severity zone ordinance. In late 2005, to be effective in 2008, the California Building Commission adopted California Building Code Chapter 7A requiring new buildings in VHFHSZs to use ignition resistant construction methods and materials. These new codes include provisions to improve the ignition resistance of buildings, especially from firebrands. The updated very high fire hazard severity zones will be used by building officials for new building permits in LRA. The updated zones will also be used to identify property whose owners must comply with natural hazards disclosure requirements at time of property sale and 100 foot defensible space clearance. It is likely that the fire hazard severity zones will be used for updates to the safety element of general plans.

  • API

    Vital Signs: Fatalities From Crashes – By Case (2022) DRAFT

    data.bayareametro.gov | Last Updated 2022-12-11T07:45:10.000Z

    VITAL SIGNS INDICATOR Fatalities From Crashes (EN4-6) FULL MEASURE NAME Fatalities from crashes (traffic collisions) LAST UPDATED May 2022 DESCRIPTION Fatalities from crashes refers to deaths as a result of injuries sustained in collisions. The California Highway Patrol includes deaths within 30 days of the collision that are a result of injuries sustained as part of this metric. This total fatalities dataset includes fatality counts for the region and counties, as well as individual collision data and metropolitan area data. DATA SOURCE National Highway Safety Administration: Fatality Analysis Reporting System CONTACT INFORMATION vitalsigns.info@bayareametro.gov METHODOLOGY NOTES (across all datasets for this indicator) The data is reported by the California Highway Patrol (CHP) to the Statewide Integrated Traffic Records System (SWITRS), which was accessed via SafeTREC’s Transportation Injury Mapping System (TIMS). The data was tabulated using provided categories specifying injury level, individuals involved, causes of collision, and location/jurisdiction of collision (for more: http://tims.berkeley.edu/help/files/switrs_codebook.doc). For more regarding reporting procedures and injury classification, see the California Highway Patrol Manual (https://one.nhtsa.gov/nhtsa/stateCatalog/states/ca/docs/CA_CHP555_Manual_2_2003_ch1-13.pdf).

  • API

    CTCAC/HCD Resource Opportunity Areas 2022

    data.bayareametro.gov | Last Updated 2023-06-08T23:15:47.000Z

    In 2017, the California Tax Credit Allocation Committee (CTCAC) and the Department of Housing and Community Development (HCD) created the California Fair Housing Task Force (Task Force). The Task Force was asked to assist CTCAC and HCD in creating evidence-based approaches to increasing access to opportunity for families with children living in housing subsidized by the Low-Income Housing Tax Credit (LIHTC) program. This feature set contains Resource Opportunity Areas (ROAs) that are the results of the Task Force's analysis for the two regions used for the San Francisco Bay Region; one is for the cities and towns (urban) and the other is for the rural areas. The reason for treating urban and rural areas as separate reasons is that using absolute thresholds for place-based opportunity could introduce comparisons between very different areas of the total region that make little sense from a policy perspective — in effect, holding a farming community to the same standard as a dense, urbanized neighborhood. ROA analysis for urban areas is based on census tract data. Since tracts in rural areas of are approximately 37 times larger in land area than tracts in non-rural areas, tract-level data in rural areas may mask over variation in opportunity and resources within these tracts. Assessing opportunity at the census block group level in rural areas reduces this difference by 90 percent (each rural tract contains three block groups), and thus allows for finer-grained analysis. In addition, more consistent standards can be useful for identifying areas of concern from a fair housing perspective — such as high-poverty and racially segregated areas. Assessing these factors based on intraregional comparison could mischaracterize areas in more affluent areas with relatively even and equitable development opportunity patterns as high-poverty, and could generate misleading results in areas with higher shares of objectively poor neighborhoods by holding them to a lower, intraregional standard. To avoid either outcome, the Task Force used a hybrid approach for the CTCAC/HCD ROA analysis — accounting for regional differences in assessing opportunity for most places, while applying more rigid standards for high-poverty, racially segregated areas in all regions. In particular: Filtering for High-Poverty, Racially Segregated Areas The CTCAC/HCD ROA filters areas that meet consistent standards for both poverty (30% of the population below the federal poverty line) and racial segregation (over-representation of people of color relative to the county) into a “High Segregation & Poverty” category. The share of each region that falls into the High Segregation & Poverty category varies from region to region. Calculating Index Scores for Non-Filtered Areas The CTCAC/HCD ROAs process calculates regionally derived opportunity index scores for non-filtered tracts and rural block groups using twenty-one indicators (see Data Quality section of metadata for more information). These index scores make it possible to sort each non-filtered tract or rural block group into opportunity categories according to their rank within the urban or rural areas. To allow CTCAC and HCD to incentivize equitable development patterns in each region to the same degree, the CTCAC/HCD analysis 20 percent of tracts or rural block groups in each urban or rural area, respectively, with the highest relative index scores to the "Highest Resource” designation and the next 20 percent to the “High Resource” designation. The region's urban area thus ends up with 40 percent of its total tracts with reliable data as Highest or High Resource (or 40 percent of block groups in the rural area). The remaining non-filtered tracts or rural block groups are then evenly divided into “Low Resource” and “Moderate Resource” categories. Excluding Tracts or Block Groups The analysis also excludes certain census areas from being categorized. To improve the accuracy of the mapping, tracts and rural bl