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.

The Likely Tables herd contains migrants, but this herd does not migrate between traditional summer and winter seasonal ranges. Instead, much of the herd displays a nomadic tendency, slowly migrating north for the summer using various high use areas as they move. Therefore, annual ranges were modeled using year-round data to demarcate high use areas in lieu modeling specific winter ranges. A high use area being used during winter by many of the collared animals is west of the Warner Mountains, east of U.S. Highway 395, and north of Moon Lake. Some animals live in the agricultural fields west of U.S. Highway 395. There appears to be little if any movement across the highway, which is fenced on both sides in this area. Summer ranges are spread out, with some individuals moving as far north as Goose Lake. A few outliers in the herd moved long distances south toward the Lassen herd or east to Nevada. Drought, increasing fire frequency, invasive annual grasses, and juniper encroachment negatively affect pronghorn habitat. Recent population surveys indicate a declining population (Trausch and others, 2020). Juniper removal on public and private lands have potential to improve habitat quality and potentially reduce predation (Ewanyk, 2020). Fences on public and private lands affect movement corridors and increase crossing and/or migration times. Recent fence modifications on BLM lands have shown potential to ease pronghorn movements (Hudgens, 2022). These mapping layers show the _location of the migration stopovers for pronghorn (Antilocapra americana) in the Likely Tables population in California. They were developed from 29 migration sequences collected from a sample size of 17 animals comprising GPS locations collected every 1-4 hours.

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.

Note: This dataset is no longer being updated due to the end of the COVID-19 Public Health Emergency.

The California Department of Public Health (CDPH) is identifying vaccination status of COVID-19 cases, hospitalizations, and deaths by analyzing the state immunization registry and registry of confirmed COVID-19 cases. Post-vaccination cases are individuals who have a positive SARS-Cov-2 molecular test (e.g. PCR) at least 14 days after they have completed their primary vaccination series.

Tracking cases of COVID-19 that occur after vaccination is important for monitoring the impact of immunization campaigns. While COVID-19 vaccines are safe and effective, some cases are still expected in persons who have been vaccinated, as no vaccine is 100% effective. For more information, please see https://www.cdph.ca.gov/Programs/CID/DCDC/Pages/COVID-19/Post-Vaccine-COVID19-Cases.aspx

Post-vaccination infection data is updated monthly and includes data on cases, hospitalizations, and deaths among the unvaccinated and the vaccinated. Partially vaccinated individuals are excluded. To account for reporting and processing delays, there is at least a one-month lag in provided data (for example data published on 9/9/22 will include data through 7/31/22).

Notes:

• On September 9, 2022, the post-vaccination data has been changed to compare unvaccinated with those with at least a primary series completed for persons age 5+. These data will be updated monthly (first Thursday of the month) and include at least a one month lag.

• On February 2, 2022, the post-vaccination data has been changed to distinguish between vaccination with a primary series only versus vaccinated and boosted. The previous dataset has been uploaded as an archived table. Additionally, the lag on this data has been extended to 14 days.

• On November 29, 2021, the denominator for calculating vaccine coverage has been changed from age 16+ to age 12+ to reflect new vaccine eligibility criteria. The previous dataset based on age 16+ denominators has been uploaded as an archived table.

Note: In these datasets, a person is defined as up to date if they have received at least one dose of an updated COVID-19 vaccine. The Centers for Disease Control and Prevention (CDC) recommends that certain groups, including adults ages 65 years and older, receive additional doses.

Starting on July 13, 2022, the denominator for calculating vaccine coverage has been changed from age 5+ to all ages to reflect new vaccine eligibility criteria. Previously the denominator was changed from age 16+ to age 12+ on May 18, 2021, then changed from age 12+ to age 5+ on November 10, 2021, to reflect previous changes in vaccine eligibility criteria. The previous datasets based on age 12+ and age 5+ denominators have been uploaded as archived tables.

Starting June 30, 2021, the dataset has been reconfigured so that all updates are appended to one dataset to make it easier for API and other interfaces. In addition, historical data has been extended back to January 5, 2021.

This dataset shows full, partial, and at least 1 dose coverage rates by zip code tabulation area (ZCTA) for the state of California. Data sources include the California Immunization Registry and the American Community Survey’s 2015-2019 5-Year data.

This is the data table for the LHJ Vaccine Equity Performance dashboard. However, this data table also includes ZTCAs that do not have a VEM score.

This dataset also includes Vaccine Equity Metric score quartiles (when applicable), which combine the Public Health Alliance of Southern California’s Healthy Places Index (HPI) measure with CDPH-derived scores to estimate factors that impact health, like income, education, and access to health care. ZTCAs range from less healthy community conditions in Quartile 1 to more healthy community conditions in Quartile 4.

The Vaccine Equity Metric is for weekly vaccination allocation and reporting purposes only. CDPH-derived quartiles should not be considered as indicative of the HPI score for these zip codes. CDPH-derived quartiles were assigned to zip codes excluded from the HPI score produced by the Public Health Alliance of Southern California due to concerns with statistical reliability and validity in populations smaller than 1,500 or where more than 50% of the population resides in a group setting.

These data do not include doses administered by the following federal agencies who received vaccine allocated directly from CDC: Indian Health Service, Veterans Health Administration, Department of Defense, and the Federal Bureau of Prisons.

For some ZTCAs, vaccination coverage may exceed 100%. This may be a result of many people from outside the county coming to that ZTCA to get their vaccine and providers reporting the county of administration as the county of residence, and/or the DOF estimates of the population in that ZTCA are too low. Please note that population numbers provided by DOF are projections and so may not be accurate, especially given unprecedented shifts in population as a result of the pandemic.

The Clear Lake herd contains migrants, but this herd does not migrate between traditional summer and winter seasonal ranges. Instead, much of the herd displays a nomadic tendency, slowly migrating north, east, or south for the summer using various high use areas as they move. Therefore, annual ranges were modeled using year-round data to demarcate high use areas in lieu of modeling specific winter ranges. The areas adjacent to Clear Lake Reservoir were heavily used during winter by many of the collared animals. A few collared individuals persisted west of State Route 139 year-round, seemingly separated from the rest of the herd due to this highway barrier. However, some pronghorn cross this road near Cornell and join this subgroup. Summer ranges are spread out, with many individuals moving southeast through protected forests or over the state border into Oregon. A few outliers in the herd moved long distances south, crossing State Route 139 to Oak Ridge, or east into Likely Tables pronghorn herd areas. Drought, increasing fire frequency, invasive annual grasses, and juniper encroachment negatively affect pronghorn habitat. Recent population surveys indicate a declining population (Trausch and others, 2020). Juniper removal on public and private lands has potential to improve habitat quality and potentially reduce predation (Ewanyk, 2020). These mapping layers show the _location of the migration routes for pronghorn (Antilocapra americana) in the Clear Lake population in California. They were developed from 72 migration sequences collected from a sample size of 23 animals comprising GPS locations collected every 1-6 hours.

The project lead for the collection of this data was Richard Shinn. Pronghorn (30 adult females and 1 adult male) were captured and equipped with GPS collars (Sirtrack, Havelock North, NZ) transmitting data from 2014-2020. The Likely Tables herd contains migrants, but this herd does not migrate between traditional summer and winter seasonal ranges. Instead, much of the herd displays a somewhat nomadic migratory tendency, slowly migrating north for the summer using various high use areas as they move. Therefore, annual home ranges were modeled using year-round data to demarcate high use areas in lieu of modeling the specific winter ranges commonly seen in other ungulate analyses in California. A high use area being used during winter by many of the collared animals is west of the Warner Mountains, east of Highway 395, and north of the Modoc County line. Additionally, a few individuals persist east of Highway 395, seemingly separated from the rest of the herd. Summer ranges are spread out, with some individuals moving into the Modoc National Forest and as far north as Goose Lake. A few outliers in the herd moved long distances south or east. GPS locations were fixed between 1-4 hour intervals in the dataset. To improve the quality of the data set as per Bjørneraas et al. (2010), the GPS data were filtered prior to analysis to remove locations which were: i) further from either the previous point or subsequent point than an individual pronghorn is able to travel in the elapsed time, ii) forming spikes in the movement trajectory based on outgoing and incoming speeds and turning angles sharper than a predefined threshold , or iii) fixed in 2D space and visually assessed as a bad fix by the analyst. The methodology used for this migration analysis allowed for the mapping of the herd''s home range and the identification and prioritization of migration corridors. Brownian Bridge Movement Models (BBMMs; Sawyer et al. 2009) were constructed with GPS collar data from 17 migrating pronghorn, including 29 migration sequences, location, date, time, and average location error as inputs in Migration Mapper. The average migration time and average migration distance for pronghorn was 15.42 days and 38.02 km, respectively. Corridors and stopovers were prioritized based on the number of animals moving through a particular area. BBMMs were produced at a spatial resolution of 50 m using a sequential fix interval of less than 27 hours. Due to varying fix rates in the data, separate models using Brownian bridge movement models (BMMM), with an adaptable variance rate, and fixed motion variances of 1000 were produced per migration sequence and visually compared for the entire dataset, with best models being combined prior to population-level analyses (72% of sequences selected with BBMM). In general, fixed motion variances were used when BBMM variances exceeded 8000. Home range analyses were based on data from 20 pronghorn and 25 year-round sequences using a combination of BBMMs and fixed motion variances of 1000 (84% of sequences selected with BBMM). Home range designations for this herd may expand with a larger sample, filling in some of the gaps between home range polygons in the map. Large water bodies were clipped from the final outputs.Corridors are visualized based on pronghorn use per cell, with greater than or equal to 1 pronghorn and greater than or equal to 3 pronghorn (20% of the sample) representing migration corridors and high use corridors, respectively. Stopovers were calculated as the top 10 percent of the population level utilization distribution during migrations and can be interpreted as high use areas. Stopover polygon areas less than 20,000 m2 were removed, but remaining small stopovers may be interpreted as short-term resting sites, likely based on a small concentration of points from an individual animal. Home range is visualized as the 50th percentile contour of the home range utilization distribution.

Provides data on people moving through space, including total number observed, gender breakdown, group size, and age groups.

The City of Seattle Department of Transportation (SDOT) is providing data from the public life studies it has conducted since 2017. These studies consist of measuring the number of people using public space and the types of activities present on select sidewalks across the city, as well as several parks and plazas. The data set is continually updated as SDOT and other parties conduct public life studies using Gehl Institute’s Public Life Data Protocol.

This dataset consists of four component spreadsheets and a GeoJSON file, which provide public life data as well as information about the study design and study locations:

1 Public Life Study: provides details on the different studies that have been conducted, including project information. https://data.seattle.gov/Transportation/Public-Life-Data-Study/7qru-sdcp

2 Public Life Location: provides details on the sites selected for each study, including various attributes to allow for comparison across sites. https://data.seattle.gov/Transportation/Public-Life-Data-Locations/fg6z-cn3y

3 Public Life People Moving: provides data on people moving through space, including total number observed, gender breakdown, group size, and age groups.

4 Public Life People Staying: provides data on people staying still in the space, including total number observed, demographic data, group size, postures, and activities. https://data.seattle.gov/Transportation/Public-Life-Data-People-Staying/5mzj-4rtf

5 Public Life Geography: A GeoJSON file with polygons of every location studied. https://data.seattle.gov/Transportation/Public-Life-Data-Geography/v4q3-5hvp

Please download and refer to the Public Life metadata document - in the attachment section below - for comprehensive information about all of the Public Life datasets.

About this dataset

Context

The dataset tabulates the Los Angeles population over the last 20 plus years. It lists the population for each year, along with the year on year change in population, as well as the change in percentage terms for each year. The dataset can be utilized to understand the population change of Los Angeles across the last two decades. For example, using this dataset, we can identify if the population is declining or increasing. If there is a change, when the population peaked, or if it is still growing and has not reached its peak. We can also compare the trend with the overall trend of United States population over the same period of time.

Key observations

In 2023, the population of Los Angeles was 3.82 million, a 0.05% decrease year-by-year from 2022. Previously, in 2022, Los Angeles population was 3.82 million, a decline of 0.26% compared to a population of 3.83 million in 2021. Over the last 20 plus years, between 2000 and 2023, population of Los Angeles increased by 118,340. In this period, the peak population was 3.98 million in the year 2019. The numbers suggest that the population has already reached its peak and is showing a trend of decline. Source: U.S. Census Bureau Population Estimates Program (PEP).

Content

When available, the data consists of estimates from the U.S. Census Bureau Population Estimates Program (PEP).

Data Coverage:

• From 2000 to 2023

Variables / Data Columns

• Year: This column displays the data year (Measured annually and for years 2000 to 2023)
• Population: The population for the specific year for the Los Angeles is shown in this column.
• Year on Year Change: This column displays the change in Los Angeles population for each year compared to the previous year.
• Change in Percent: This column displays the year on year change as a percentage. Please note that the sum of all percentages may not equal one due to rounding of values.

Good to know

Margin of Error

Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.

Custom data

If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.

Inspiration

Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.

Recommended for further research

This dataset is a part of the main dataset for Los Angeles Population by Year. You can refer the same here

Reasons for moving and location of previous dwelling for households that moved in the past five years, and intentions to move in less than five years for all households, Canada, provinces and territories.

Annual number of interprovincial migrants by province of origin and destination, Canada, provinces and territories.

The project lead for the collection of this data was and Richard Shinn. Pronghorn (28 adult females) were captured and equipped with GPS collars (Sirtrack, Havelock North, NZ) transmitting data from 2015-2020. The Clear Lake herd contains migrants, but this herd does not migrate between traditional summer and winter seasonal ranges. Instead, much of the herd displays a somewhat nomadic migratory tendency, slowly migrating north, east, or south for the summer using various high use areas as they move. Therefore, annual home ranges were modeled using year-round data to demarcate high use areas in lieu of modeling the specific winter ranges commonly seen in other ungulate analyses in California. The areas adjacent to both east and west of Clear Lake Reservoir are highly used during winter by many of the collared animals. Additionally, a few individuals persist west of Highway 139 year-round, seemingly separated from the rest of the herd due to this highway barrier. However, other pronghorn cross this road near Cornell and join this subgroup. Summer ranges are spread out, with many individuals moving southeast through Modoc National Forest or as far north as Fremont National Forest in Oregon. A few outliers in the herd moved long distances south, crossing Rt 139 to Oak Ridge, or east into Likely Tables pronghorn herd areas. GPS locations were fixed between 1-6 hour intervals in the dataset. To improve the quality of the data set as per Bjørneraas et al. (2010), the GPS data were filtered prior to analysis to remove locations which were: i) further from either the previous point or subsequent point than an individual pronghorn is able to travel in the elapsed time, ii) forming spikes in the movement trajectory based on outgoing and incoming speeds and turning angles sharper than a predefined threshold , or iii) fixed in 2D space and visually assessed as a bad fix by the analyst. The methodology used for this migration analysis allowed for the mapping of the herd''s home range and the identification and prioritization of migration corridors. Brownian Bridge Movement Models (BBMMs; Sawyer et al. 2009) were constructed with GPS collar data from 23 migrating pronghorn, including 72 migration sequences, location, date, time, and average location error as inputs in Migration Mapper. The average migration time and average migration distance for pronghorn was 12.11 days and 34.18 km, respectively. Corridors and stopovers were prioritized based on the number of animals moving through a particular area. BBMMs were produced at a spatial resolution of 50 m using a sequential fix interval of less than 27 hours. Due to varying fix rates in the data, separate models using Brownian bridge movement models (BMMM), with an adaptable variance rate, and fixed motion variances of 1000 were produced per migration sequence and visually compared for the entire dataset, with best models being combined prior to population-level analyses (68% of sequences selected with BBMM). In general, fixed motion variances were used when BBMM variances exceeded 8000. Home range analyses were based on data from 24 pronghorn and 47 year-round sequences using a fixed motion variance of 1000. Home range designations for this herd may expand with a larger sample, filling in some of the gaps between home range polygons in the map. Large water bodies were clipped from the final outputs.Corridors are visualized based on pronghorn use per cell, with greater than or equal to 1 pronghorn, greater than or equal to 3 pronghorn (10% of the sample), and greater than or equal to 5 pronghorn (20% of the sample) representing migration corridors, medium use corridors, and high use corridors, respectively. Stopovers were calculated as the top 10 percent of the population level utilization distribution during migrations and can be interpreted as high use areas. Stopover polygon areas less than 20,000 m2 were removed, but remaining small stopovers may be interpreted as short-term resting sites, likely based on a small concentration of points from an individual animal. Home range is visualized as the 50th percentile contour of the home range utilization distribution.

A. SUMMARY This archived dataset includes data for population characteristics that are no longer being reported publicly. The date on which each population characteristic type was archived can be found in the field “data_loaded_at”.

B. HOW THE DATASET IS CREATED Data on the population characteristics of COVID-19 cases are from:  * Case interviews  * Laboratories  * Medical providers    These multiple streams of data are merged, deduplicated, and undergo data verification processes.  

Race/ethnicity * We include all race/ethnicity categories that are collected for COVID-19 cases. * The population estimates for the "Other" or “Multi-racial” groups should be considered with caution. The Census definition is likely not exactly aligned with how the City collects this data. For that reason, we do not recommend calculating population rates for these groups.

Gender * The City collects information on gender identity using these guidelines.

Skilled Nursing Facility (SNF) occupancy * A Skilled Nursing Facility (SNF) is a type of long-term care facility that provides care to individuals, generally in their 60s and older, who need functional assistance in their daily lives.  * This dataset includes data for COVID-19 cases reported in Skilled Nursing Facilities (SNFs) through 12/31/2022, archived on 1/5/2023. These data were identified where “Characteristic_Type” = ‘Skilled Nursing Facility Occupancy’.

Sexual orientation * The City began asking adults 18 years old or older for their sexual orientation identification during case interviews as of April 28, 2020. Sexual orientation data prior to this date is unavailable. * The City doesn’t collect or report information about sexual orientation for persons under 12 years of age. * Case investigation interviews transitioned to the California Department of Public Health, Virtual Assistant information gathering beginning December 2021. The Virtual Assistant is only sent to adults who are 18+ years old. https://www.sfdph.org/dph/files/PoliciesProcedures/COM9_SexualOrientationGuidelines.pdf">Learn more about our data collection guidelines pertaining to sexual orientation.

Comorbidities * Underlying conditions are reported when a person has one or more underlying health conditions at the time of diagnosis or death.

Homelessness Persons are identified as homeless based on several data sources: * self-reported living situation * the location at the time of testing * Department of Public Health homelessness and health databases * Residents in Single-Room Occupancy hotels are not included in these figures. These methods serve as an estimate of persons experiencing homelessness. They may not meet other homelessness definitions.

Single Room Occupancy (SRO) tenancy * SRO buildings are defined by the San Francisco Housing Code as having six or more "residential guest rooms" which may be attached to shared bathrooms, kitchens, and living spaces. * The details of a person's living arrangements are verified during case interviews.

Transmission Type * Information on transmission of COVID-19 is based on case interviews with individuals who have a confirmed positive test. Individuals are asked if they have been in close contact with a known COVID-19 case. If they answer yes, transmission category is recorded as contact with a known case. If they report no contact with a known case, transmission category is recorded as community transmission. If the case is not interviewed or was not asked the question, they are counted as unknown.

C. UPDATE PROCESS This dataset has been archived and will no longer update as of 9/11/2023.

D. HOW TO USE THIS DATASET Population estimates are only available for age groups and race/ethnicity categories. San Francisco population estimates for race/ethnicity and age groups can be found in a view based on the San Francisco Population and Demographic Census dataset. These population estimates are from the 2016-2020 5-year American Community Survey (ACS).

This dataset includes many different types of characteristics. Filter the “Characteristic Type” column to explore a topic area. Then, the “Characteristic Group” column shows each group or category within that topic area and the number of cases on each date.

New cases are the count of cases within that characteristic group where the positive tests were collected on that specific specimen collection date. Cumulative cases are the running total of all San Francisco cases in that characteristic group up to the specimen collection date listed.

This data may not be immediately available for recently reported cases. Data updates as more information becomes available.

To explore data on the total number of cases, use the ARCHIVED: COVID-19 Cases Over Time dataset.

E. CHANGE LOG

• 9/11/2023 - data on COVID-19 cases by population characteristics over time are no longer being updated. The date on which each population characteristic type was archived can be found in the field “data_loaded_at”.
• 6/6/2023 - data on cases by transmission type have been removed. See section ARCHIVED DATA for more detail.
• 5/16/2023 - data on cases by sexual orientation, comorbidities, homelessness, and single room occupancy have been removed. See section ARCHIVED DATA for more detail.
• 4/6/2023 - the State implemented system updates to improve the integrity of historical data.
• 2/21/2023 - system updates to improve reliability and accuracy of cases data were implemented.
• 1/31/2023 - updated “population_estimate” column to reflect the 2020 Census Bureau American Community Survey (ACS) San Francisco Population estimates.
• 1/5/2023 - data on SNF cases removed. See section ARCHIVED DATA for more detail.
• 3/23/2022 - ‘Native American’ changed to ‘American Indian or Alaska Native’ to align with the census.
• 1/22/2022 - system updates to improve timeliness and accuracy of cases and deaths data were implemented.
• 7/15/2022 - reinfections added to cases dataset. See section SUMMARY for more information on how reinfections are identified.

UPDATE 1/7/2025: On June 28th 2023, the San Francisco Police Department (SFPD) changed its Stops Data Collection System (SDCS). As a result of this change, record identifiers have changed from the Department of Justice (DOJ) identifier to an internal record numbering system (referred to as "LEA Record ID"). The data that SFPD uploads to the DOJ system will contain the internal record number which can be used for joins with the data available on DataSF. A. SUMMARY The San Francisco Police Department (SFPD) Stop Data was designed to capture information to comply with the Racial and Identity Profiling Act (RIPA), or California Assembly Bill (AB)953. SFPD officers collect specific information on each stop, including elements of the stop, circumstances and the perceived identity characteristics of the individual(s) stopped. The information obtained by officers is reported to the California Department of Justice. This dataset includes data on stops starting on July 1st, 2018, which is when the data collection program went into effect. Read the detailed overview for this dataset here. B. HOW THE DATASET IS CREATED By the end of each shift, officers enter all stop data into the Stop Data Collection System, which is automatically submitted to the California Department of Justice (CA DOJ). Once a quarter the Department receives a stops data file from CA DOJ. The SFPD conducts several transformations of this data to ensure privacy, accuracy and compliance with State law and regulation. For increased usability, text descriptions have also been added for several data fields which include numeric codes (including traffic, suspicion, citation, and custodial arrest offense codes, and actions taken as a result of a stop). See the data dictionaries below for explanations of all coded data fields. Read more about the data collection, and transformation, including geocoding and PII cleaning processes, in the detailed overview of this dataset. C. UPDATE PROCESS Information is updated on a quarterly basis. D. HOW TO USE THIS DATASET This dataset includes information about police stops that occurred, including some details about the person(s) stopped, and what happened during the stop. Each row is a person stopped with a record identifier for the stop and a unique identifier for the person. A single stop may involve multiple people and may produce more than one associated unique identifier for the same record identifier. A certain percentage of stops have stop information that can’t be geocoded. This may be due to errors in data input at the officer level (typos in entry or providing an address that doesn't exist). More often, this is due to officers providing a level of detail that isn't codable to a geographic coordinate - most often at the Airport (ie: Terminal 3, door 22.) In these cases, the _location of the stops is coded as unknown. E. DATA DICTIONARIES CJIS Offense Codes data look up table Look up table for other coded data fields

Background
The Labour Force Survey (LFS) is a unique source of information using international definitions of employment and unemployment and economic inactivity, together with a wide range of related topics such as occupation, training, hours of work and personal characteristics of household members aged 16 years and over. It is used to inform social, economic and employment policy. The LFS was first conducted biennially from 1973-1983. Between 1984 and 1991 the survey was carried out annually and consisted of a quarterly survey conducted throughout the year and a 'boost' survey in the spring quarter (data were then collected seasonally). From 1992 quarterly data were made available, with a quarterly sample size approximately equivalent to that of the previous annual data. The survey then became known as the Quarterly Labour Force Survey (QLFS). From December 1994, data gathering for Northern Ireland moved to a full quarterly cycle to match the rest of the country, so the QLFS then covered the whole of the UK (though some additional annual Northern Ireland LFS datasets are also held at the UK Data Archive). Further information on the background to the QLFS may be found in the documentation.

Longitudinal data
The LFS retains each sample household for five consecutive quarters, with a fifth of the sample replaced each quarter. The main survey was designed to produce cross-sectional data, but the data on each individual have now been linked together to provide longitudinal information. The longitudinal data comprise two types of linked datasets, created using the weighting method to adjust for non-response bias. The two-quarter datasets link data from two consecutive waves, while the five-quarter datasets link across a whole year (for example January 2010 to March 2011 inclusive) and contain data from all five waves. A full series of longitudinal data has been produced, going back to winter 1992. Linking together records to create a longitudinal dimension can, for example, provide information on gross flows over time between different labour force categories (employed, unemployed and economically inactive). This will provide detail about people who have moved between the categories. Also, longitudinal information is useful in monitoring the effects of government policies and can be used to follow the subsequent activities and circumstances of people affected by specific policy initiatives, and to compare them with other groups in the population. There are however methodological problems which could distort the data resulting from this longitudinal linking. The ONS continues to research these issues and advises that the presentation of results should be carefully considered, and warnings should be included with outputs where necessary.

New reweighting policy
Following the new reweighting policy ONS has reviewed the latest population estimates made available during 2019 and have decided not to carry out a 2019 LFS and APS reweighting exercise. Therefore, the next reweighting exercise will take place in 2020. These will incorporate the 2019 Sub-National Population Projection data (published in May 2020) and 2019 Mid-Year Estimates (published in June 2020). It is expected that reweighted Labour Market aggregates and microdata will be published towards the end of 2020/early 2021.

LFS Documentation
The documentation available from the Archive to accompany LFS datasets largely consists of the latest version of each user guide volume alongside the appropriate questionnaire for the year concerned. However, volumes are updated periodically by ONS, so users are advised to check the latest documents on the ONS Labour Force Survey - User Guidance pages before commencing analysis. This is especially important for users of older QLFS studies, where information and guidance in the user guide documents may have changed over time.

Additional data derived from the QLFS
The Archive also holds further QLFS series: End User Licence (EUL) quarterly data; Secure Access datasets; household datasets; quarterly, annual and ad hoc module datasets compiled for Eurostat; and some additional annual Northern Ireland datasets.

Variables DISEA and LNGLST
Dataset A08 (Labour market status of disabled people) which ONS suspended due to an apparent discontinuity between April to June 2017 and July to September 2017 is now available. As a result of this apparent discontinuity and the inconclusive investigations at this stage, comparisons should be made with caution between April to June 2017 and subsequent time periods. However users should note that the estimates are not seasonally adjusted, so some of the change between quarters could be due to seasonality. Further recommendations on historical comparisons of the estimates will be given in November 2018 when ONS are due to publish estimates for July to September 2018.

An article explaining the quality assurance investigations that have been conducted so far is available on the ONS Methodology webpage. For any queries about Dataset A08 please email Labour.Market@ons.gov.uk.

Occupation data for 2021 and 2022 data files

The ONS has identified an issue with the collection of some occupational data in 2021 and 2022 data files in a number of their surveys. While they estimate any impacts will be small overall, this will affect the accuracy of the breakdowns of some detailed (four-digit Standard Occupational Classification (SOC)) occupations, and data derived from them. Further information can be found in the ONS article published on 11 July 2023: https://www.ons.gov.uk/employmentandlabourmarket/peopleinwork/employmentandemployeetypes/articles/revisionofmiscodedoccupationaldataintheonslabourforcesurveyuk/january2021toseptember2022" style="background-color: rgb(255, 255, 255);">Revision of miscoded occupational data in the ONS Labour Force Survey, UK: January 2021 to September 2022.

2022 Weighting

The population totals used for the latest LFS estimates use projected growth rates from Real Time Information (RTI) data for UK, EU and non-EU populations based on 2021 patterns. The total population used for the LFS therefore does not take into account any changes in migration, birth rates, death rates, and so on since June 2021, and hence levels estimates may be under- or over-estimating the true values and should be used with caution. Estimates of rates will, however, be robust.

The Clear Lake herd contains migrants, but this herd does not migrate between traditional summer and winter seasonal ranges. Instead, much of the herd displays a nomadic tendency, slowly migrating north, east, or south for the summer using various high use areas as they move. Therefore, annual ranges were modeled using year-round data to demarcate high use areas in lieu of modeling specific winter ranges. The areas adjacent to Clear Lake Reservoir were heavily used during winter by many of the collared animals. A few collared individuals persisted west of State Route 139 year-round, seemingly separated from the rest of the herd due to this highway barrier. However, some pronghorn cross this road near Cornell and join this subgroup. Summer ranges are spread out, with many individuals moving southeast through protected forests or over the state border into Oregon. A few outliers in the herd moved long distances south, crossing State Route 139 to Oak Ridge, or east into Likely Tables pronghorn herd areas. Drought, increasing fire frequency, invasive annual grasses, and juniper encroachment negatively affect pronghorn habitat. Recent population surveys indicate a declining population (Trausch and others, 2020). Juniper removal on public and private lands has potential to improve habitat quality and potentially reduce predation (Ewanyk, 2020). These mapping layers show the _location of the annual range for pronghorn (Antilocapra americana) in the Clear Lake population in California. They were developed from 47 migration sequences collected from a sample size of 24 animals comprising GPS locations collected every 1-6 hours.

Analysis of ‘Exhausted Claims By County (All Programs)’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/5fbb6ae7-3159-4acc-bbc5-202af8d684f1 on 26 January 2022.

--- Dataset description provided by original source is as follows ---

"∙ The data provided is the number of Unemployment Insurance (UI) claims that have exhausted, regardless of the program. The data includes exhaustion counts for the regular UI and the federal extended programs. The data counts the number of individuals who ran out of benefits in a specific program who may or may not qualify for additional benefits. For example, individuals who have exhausted a regular UI claim may qualify for a federal extension. Individuals who have exhausted all available benefits are also included in the data. The data is representative of those claims that were processed during the month and does not necessarily represent the month the final payment was made in. For example, if a claimant is entitled to benefits for the week-ending January 30, 2010, the claim might not get processed until early February and that count would display in the February data. There are a small percentage of claimants that could go back onto a training extension even after exhausting their FED-ED claim. "
∙ The data by county represents the mailing address given by the claimant at the time of filing for UI. It is possible that an individual can reside in a different county than their mailing address. Also, this information does not represent the county where the individual worked. It is also possible that a claimant could have moved or changed their mailing address after filing for UI which would not be reflected here. Data for claimants residing outside of California but collecting benefits are not included in these figures nor are invalid addresses in California where a county cannot be determined.
∙ Data includes the regular UI program and the federal extended benefit programs. The Federal extended benefit programs are:
∙ Emergency Unemployment Compensation (EUC) Tier 1 - California began paying benefits in July 2008.
∙ Emergency Unemployment Compensation (EUC) Tier 2 - California began paying benefits in January 2009, payments retroactive to November 2008.
∙ Emergency Unemployment Compensation (EUC) Tier 3 - California began paying benefits in December 2009, payments retroactive to November 2009.
∙ Emergency Unemployment Compensation (EUC) Tier 4 - California began paying benefits in January 2010, payments retroactive to December 2009.
∙ FED-ED - California began paying benefits May 2009, payments retroactive to February 2009.
∙ Data may include multiple counts for the same individual. For example, a claimant could have exhausted their Regular UI claim in January and then exhausted their EUC Tier I claim in June.

--- Original source retains full ownership of the source dataset ---

Introduction

The 802.11 standard includes several management features and corresponding frame types. One of them are Probe Requests (PR), which are sent by mobile devices in an unassociated state to scan the nearby area for existing wireless networks. The frame part of PRs consists of variable-length fields, called Information Elements (IE), which represent the capabilities of a mobile device, such as supported data rates.

This dataset contains PRs collected over a seven-day period by four gateway devices in an uncontrolled urban environment in the city of Catania.

It can be used for various use cases, e.g., analyzing MAC randomization, determining the number of people in a given location at a given time or in different time periods, analyzing trends in population movement (streets, shopping malls, etc.) in different time periods, etc.

Related dataset

Same authors also produced the Labeled dataset of IEEE 802.11 probe requests with same data layout and recording equipment.

Measurement setup

The system for collecting PRs consists of a Raspberry Pi 4 (RPi) with an additional WiFi dongle to capture WiFi signal traffic in monitoring mode (gateway device). Passive PR monitoring is performed by listening to 802.11 traffic and filtering out PR packets on a single WiFi channel.

The following information about each received PR is collected: - MAC address - Supported data rates - extended supported rates - HT capabilities - extended capabilities - data under extended tag and vendor specific tag - interworking - VHT capabilities - RSSI - SSID - timestamp when PR was received.

The collected data was forwarded to a remote database via a secure VPN connection. A Python script was written using the Pyshark package to collect, preprocess, and transmit the data.

Data preprocessing

The gateway collects PRs for each successive predefined scan interval (10 seconds). During this interval, the data is preprocessed before being transmitted to the database. For each detected PR in the scan interval, the IEs fields are saved in the following JSON structure:

PR_IE_data = { 'DATA_RTS': {'SUPP': DATA_supp , 'EXT': DATA_ext}, 'HT_CAP': DATA_htcap, 'EXT_CAP': {'length': DATA_len, 'data': DATA_extcap}, 'VHT_CAP': DATA_vhtcap, 'INTERWORKING': DATA_inter, 'EXT_TAG': {'ID_1': DATA_1_ext, 'ID_2': DATA_2_ext ...}, 'VENDOR_SPEC': {VENDOR_1:{ 'ID_1': DATA_1_vendor1, 'ID_2': DATA_2_vendor1 ...}, VENDOR_2:{ 'ID_1': DATA_1_vendor2, 'ID_2': DATA_2_vendor2 ...} ...} }

Supported data rates and extended supported rates are represented as arrays of values that encode information about the rates supported by a mobile device. The rest of the IEs data is represented in hexadecimal format. Vendor Specific Tag is structured differently than the other IEs. This field can contain multiple vendor IDs with multiple data IDs with corresponding data. Similarly, the extended tag can contain multiple data IDs with corresponding data.
Missing IE fields in the captured PR are not included in PR_IE_DATA.

When a new MAC address is detected in the current scan time interval, the data from PR is stored in the following structure:

{'MAC': MAC_address, 'SSIDs': [ SSID ], 'PROBE_REQs': [PR_data] },

where PR_data is structured as follows:

{ 'TIME': [ DATA_time ], 'RSSI': [ DATA_rssi ], 'DATA': PR_IE_data }.

This data structure allows to store only 'TOA' and 'RSSI' for all PRs originating from the same MAC address and containing the same 'PR_IE_data'. All SSIDs from the same MAC address are also stored. The data of the newly detected PR is compared with the already stored data of the same MAC in the current scan time interval. If identical PR's IE data from the same MAC address is already stored, only data for the keys 'TIME' and 'RSSI' are appended. If identical PR's IE data from the same MAC address has not yet been received, then the PR_data structure of the new PR for that MAC address is appended to the 'PROBE_REQs' key. The preprocessing procedure is shown in Figure ./Figures/Preprocessing_procedure.png

At the end of each scan time interval, all processed data is sent to the database along with additional metadata about the collected data, such as the serial number of the wireless gateway and the timestamps for the start and end of the scan. For an example of a single PR capture, see the Single_PR_capture_example.json file.

Folder structure

For ease of processing of the data, the dataset is divided into 7 folders, each containing a 24-hour period. Each folder contains four files, each containing samples from that device.

The folders are named after the start and end time (in UTC). For example, the folder 2022-09-22T22-00-00_2022-09-23T22-00-00 contains samples collected between 23th of September 2022 00:00 local time, until 24th of September 2022 00:00 local time.

Files representing their location via mapping: - 1.json -> location 1 - 2.json -> location 2 - 3.json -> location 3 - 4.json -> location 4

Environments description

The measurements were carried out in the city of Catania, in Piazza Università and Piazza del Duomo The gateway devices (rPIs with WiFi dongle) were set up and gathering data before the start time of this dataset. As of September 23, 2022, the devices were placed in their final configuration and personally checked for correctness of installation and data status of the entire data collection system. Devices were connected either to a nearby Ethernet outlet or via WiFi to the access point provided.

Four Raspbery Pi-s were used: - location 1 -> Piazza del Duomo - Chierici building (balcony near Fontana dell’Amenano) - location 2 -> southernmost window in the building of Via Etnea near Piazza del Duomo - location 3 -> nothernmost window in the building of Via Etnea near Piazza Università - location 4 -> first window top the right of the entrance of the University of Catania

Locations were suggested by the authors and adjusted during deployment based on physical constraints (locations of electrical outlets or internet access) Under ideal circumstances, the locations of the devices and their coverage area would cover both squares and the part of Via Etna between them, with a partial overlap of signal detection. The locations of the gateways are shown in Figure ./Figures/catania.png.

Known dataset shortcomings

Due to technical and physical limitations, the dataset contains some identified deficiencies.

PRs are collected and transmitted in 10-second chunks. Due to the limited capabilites of the recording devices, some time (in the range of seconds) may not be accounted for between chunks if the transmission of the previous packet took too long or an unexpected error occurred.

Every 20 minutes the service is restarted on the recording device. This is a workaround for undefined behavior of the USB WiFi dongle, which can no longer respond. For this reason, up to 20 seconds of data will not be recorded in each 20-minute period.

The devices had a scheduled reboot at 4:00 each day which is shown as missing data of up to a few minutes.

 Location 1 - Piazza del Duomo - Chierici

The gateway device (rPi) is located on the second floor balcony and is hardwired to the Ethernet port. This device appears to function stably throughout the data collection period. Its location is constant and is not disturbed, dataset seems to have complete coverage.

 Location 2 - Via Etnea - Piazza del Duomo

The device is located inside the building. During working hours (approximately 9:00-17:00), the device was placed on the windowsill. However, the movement of the device cannot be confirmed. As the device was moved back and forth, power outages and internet connection issues occurred. The last three days in the record contain no PRs from this location.

 Location 3 - Via Etnea - Piazza Università

Similar to Location 2, the device is placed on the windowsill and moved around by people working in the building. Similar behavior is also observed, e.g., it is placed on the windowsill and moved inside a thick wall when no people are present. This device appears to have been collecting data throughout the whole dataset period.

 Location 4 - Piazza Università

This location is wirelessly connected to the access point. The device was placed statically on a windowsill overlooking the square. Due to physical limitations, the device had lost power several times during the deployment. The internet connection was also interrupted sporadically.

Recognitions

The data was collected within the scope of Resiloc project with the help of City of Catania and project partners.

MCGD_Data_V2.2 contains all the data that we have collected on locations in modern China, plus a number of locations outside of China that we encounter frequently in historical sources on China. All further updates will appear under the name "MCGD_Data" with a time stamp (e.g., MCGD_Data2023-06-21)

You can also have access to this dataset and all the datasets that the ENP-China makes available on GitLab: https://gitlab.com/enpchina/IndexesEnp

Altogether there are 464,970 entries. The data include the name of locations and their variants in Chinese, pinyin, and any recorded transliteration; the name of the province in Chinese and in pinyin; Province ID; the latitude and longitude; the Name ID and Location ID, and NameID_Legacy. The Name IDs all start with H followed by seven digits. This is the internal ID system of MCGD (the NameID_Legacy column records the Name IDs in their original format depending on the source). Locations IDs that start with "DH" are data points extracted from China Historical GIS (Harvard University); those that start with "D" are locations extracted from the data points in Geonames; those that have only digits (8 digits) are data points we have added from various map sources.

One of the main features of the MCGD Main Dataset is the systematic collection and compilation of place names from non-Chinese language historical sources. Locations were designated in transliteration systems that are hardly comprehensible today, which makes it very difficult to find the actual locations they correspond to. This dataset allows for the conversion from these obsolete transliterations to the current names and geocoordinates.

From June 2021 onward, we have adopted a different file naming system to keep track of versions. From MCGD_Data_V1 we have moved to MCGD_Data_V2. In June 2022, we introduced time stamps, which result in the following naming convention: MCGD_Data_YYYY.MM.DD.

UPDATES

MCGD_Data2025_02_28 includes a major change with the duplication of all the locations listed under Beijing, Shanghai, Tianjin, and Chongqing (北京, 上海, 天津, 重慶) and their listing under the name of the provinces to which they belonge origially before the creation of the four special municipalities after 1949. This is meant to facilitate the matching of data from historical sources. Each location has a unique NameID. Altogether there are 472,818 entries

MCGD_Data2025_02_27 inclues an update on locations extracted from Minguo zhengfu ge yuanhui keyuan yishang zhiyuanlu 國民政府各院部會科員以上職員錄 (Directory of staff members and above in the ministries and committees of the National Government). Nanjing: Guomin zhengfu wenguanchu yinzhuju 國民政府文官處印鑄局國民政府文官處印鑄局, 1944). We also made corrections in the Prov_Py and Prov_Zh columns as there were some misalignments between the pinyin name and the name in Chines characters. The file now includes 465,128 entries.

MCGD_Data2024_03_23 includes an update on locations in Taiwan from the Asia Directories. Altogether there are 465,603 entries (of which 187 place names without geocoordinates, labelled in the Lat Long columns as "Unknown").

MCGD_Data2023.12.22 contains all the data that we have collected on locations in China, whatever the period. Altogether there are 465,603 entries (of which 187 place names without geocoordinates, labelled in the Lat Long columns as "Unknown"). The dataset also includes locations outside of China for the purpose of matching such locations to the place names extracted from historical sources. For example, one may need to locate individuals born outside of China. Rather than maintaining two separate files, we made the decision to incorporate all the place names found in historical sources in the gazetteer. Such place names can easily be removed by selecting all the entries where the 'Province' data is missing.

As of 9/12/2024, we will begin reporting on hospitalization data again using a new San Francisco specific dataset. Updated data can be accessed here.

On 5/1/2024, hospitalization data reporting will change from mandatory to optional for all hospitals nationwide. We will be pausing the refresh of the underlying data beginning 5/2/2024.

A. SUMMARY Count of COVID+ patients admitted to the hospital. Patients who are hospitalized and test positive for COVID-19 may be admitted to an acute care bed (a regular hospital bed), or an intensive care unit (ICU) bed. This data shows the daily total count of COVID+ patients in these two bed types, and the data reflects totals from all San Francisco Hospitals.

B. HOW THE DATASET IS CREATED Hospital information is based on admission data reported to the National Healthcare Safety Network (NHSN) and provided by the California Department of Public Health (CDPH).

C. UPDATE PROCESS Updates automatically every week.

D. HOW TO USE THIS DATASET Each record represents how many people were hospitalized on the date recorded in either an ICU bed or acute care bed (shown as Med/Surg under DPHCategory field).

The dataset shown here includes all San Francisco hospitals and updates weekly with data for the past Sunday-Saturday as information is collected and verified. Data may change as more current information becomes available.

E. CHANGE LOG

• 9/12/2024 -Hospitalization data are now being tracked through a new source and are available here.
• 5/1/2024 - hospitalization data reporting to the National Healthcare Safety Network (NHSN) changed from mandatory to optional for all hospitals nationwide. We will be pausing the refresh of the underlying data beginning 5/2/2024.
• 12/14/2023 – added column “hospitalreportingpct” to indicate the percentage of hospitals who submitted data on each report date.
• 8/7/2023 - In response to the end of the federal public health emergency on 5/11/2023 the California Hospital Association (CHA) stopped the collection and dissemination of COVID-19 hospitalization data. In alignment with the California Department of Public Health (CDPH), hospitalization data from 5/11/2023 onward are being pulled from the National Healthcare Safety Network (NHSN). The NHSN data is updated weekly and does not include information on COVID suspected (PUI) patients.
• 4/9/2021 - dataset updated daily with a four-day data lag.