The population density of Combined Locks, WI was 2,094 in 2018.
Population Density
Population Density is computed by dividing the total population by Land Area Per Square Mile.
Above charts are based on data from the U.S. Census American Community Survey | ODN Dataset | API -
Geographic and Population Datasets Involving Combined Locks, WI
- API
Internet Master Plan: Adoption and Infrastructure Data by Neighborhood
data.cityofnewyork.us | Last Updated 2022-09-23T19:23:10.000ZKey indicators of broadband adoption, service and infrastructure in New York City.</p> <b>Data Limitations:</b> Data accuracy is limited as of the date of publication and by the methodology and accuracy of the original sources. The City shall not be liable for any costs related to, or in reliance of, the data contained in these datasets.
- API
Broadband Adoption Basic Indicators
data.cityofnewyork.us | Last Updated 2022-09-23T19:23:10.000ZKey indicators of broadband adoption, service and infrastructure in New York City by NTA.
- API
Bronx 311 Air Quality 3.19.13 (population adjusted)
bronx.lehman.cuny.edu | Last Updated 2019-04-18T20:37:00.000ZThis is a 311 dataset combined with 2010 Census population data. The rate of air-quality complaints were divided by the population to get what is called a "population index" in get a better idea of the nature of the air-quality complaints. The more people there are in a given area, the more likely there will be more complaints. This is an attempt to correct for the population density in each census tract. The data is updated daily, so this is a snapshot of all of the complaints from 1/1/2010 to 3/19/2013.
- API
Energy and Water Data Disclosure for Local Law 84 2014 (Data for Calendar Year 2013)
data.cityofnewyork.us | Last Updated 2024-10-01T19:32:33.000ZData and metrics on water and energy consumption in privately owned buildings over 25,000 ft2 and in City-owned buildings over 10,000 ft2.
- API
DOHMH COVID-19 Antibody-by-Modified ZIP Code Tabulation Area
data.cityofnewyork.us | Last Updated 2024-07-03T04:10:41.000ZThis dataset contains information on antibody testing for COVID-19: the number of people who received a test, the number of people with positive results, the percentage of people tested who tested positive, and the rate of testing per 100,000 people, stratified by modified ZIP Code Tabulation Area (ZCTA) of residence. Modified ZCTA reflects the first non-missing address within NYC for each person reported with an antibody test result. This unit of geography is similar to ZIP codes but combines census blocks with smaller populations to allow more stable estimates of population size for rate calculation. It can be challenging to map data that are reported by ZIP Code. A ZIP Code doesn’t refer to an area, but rather a collection of points that make up a mail delivery route. Furthermore, there are some buildings that have their own ZIP Code, and some non-residential areas with ZIP Codes. To deal with the challenges of ZIP Codes, the Health Department uses ZCTAs which solidify ZIP codes into units of area. Often, data reported by ZIP code are actually mapped by ZCTA. The ZCTA geography was developed by the U.S. Census Bureau. These data can also be accessed here: https://github.com/nychealth/coronavirus-data/blob/master/totals/antibody-by-modzcta.csv Exposure to COVID-19 can be detected by measuring antibodies to the disease in a person’s blood, which can indicate that a person may have had an immune response to the virus. Antibodies are proteins produced by the body’s immune system that can be found in the blood. People can test positive for antibodies after they have been exposed, sometimes when they no longer test positive for the virus itself. It is important to note that the science around COVID-19 antibody tests is evolving rapidly and there is still much uncertainty about what individual antibody test results mean for a single person and what population-level antibody test results mean for understanding the epidemiology of COVID-19 at a population level. </br> These data only provide information on people tested. People receiving an antibody test do not reflect all people in New York City; therefore, these data may not reflect antibody prevalence among all New Yorkers. Increasing instances of screening programs further impact the generalizability of these data, as screening programs influence who and how many people are tested over time. Examples of screening programs in NYC include: employers screening their workers (e.g., hospitals), and long-term care facilities screening their residents. In addition, there may be potential biases toward people receiving an antibody test who have a positive result because people who were previously ill are preferentially seeking testing, in addition to the testing of persons with higher exposure (e.g., health care workers, first responders) Rates were calculated using interpolated intercensal population estimates updated in 2019. These rates differ from previously reported rates based on the 2000 Census or previous versions of population estimates. The Health Department produced these population estimates based on estimates from the U.S. Census Bureau and NYC Department of City Planning. Antibody tests are categorized based on the date of specimen collection and are aggregated by full weeks starting each Sunday and ending on Saturday. For example, a person whose blood was collected for antibody testing on Wednesday, May 6 would be categorized as tested during the week ending May 9. A person tested twice in one week would only be counted once in that week. This dataset includes testing data beginning April 5, 2020. Data are updated daily, and the dataset preserves historical records and source data changes, so each extract date reflects the current copy of the data as of that date. For example, an extract date of 11/04/2020 and extract date of 11/03/2020 will both contain all records as they were as of that extract date. Without filtering or grouping by extract date, an analysis wi
- API
Urban Areas 2020
data.delaware.gov | Last Updated 2024-03-01T14:09:39.000Z<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. After each decennial census, the Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the urban footprint. There are 2,646 Urban Areas (UAs) in this data release with either a minimum population of 5,000 or a housing unit count of 2,000 units. Each urban area is identified by a 5-character numeric census code that may contain leading zeroes.</SPAN></P></DIV></DIV></DIV>
- API
Energy and Water Data Disclosure for Local Law 84 2015 (Data for Calendar Year 2014)
data.cityofnewyork.us | Last Updated 2024-10-01T19:32:47.000ZData and metrics on water and energy consumption in privately owned buildings over 25,000 ft2 and in City-owned buildings over 10,000 ft2.
- API
Tracts 2020
data.delaware.gov | Last Updated 2024-03-01T14:44:49.000Z<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.</SPAN></P><P><SPAN>Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2020 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2010 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area.</SPAN></P></DIV></DIV></DIV>
- API
Census Tracts 2010 Centroids
data.bayareametro.gov | Last Updated 2021-11-19T16:27:25.000ZCentroid of 2010 census tracts. Provides 2010 census tracts for the San Francisco Bay Region, clipped by the Metropolitan Transportation Commission to remove major coastal and bay water areas. 2010 Census tracts for the San Francisco Bay Region, clipped to remove major coastal and bay water areas. Features were extracted from, and clipped using, California 2018 TIGER/Line shapefiles by the Metropolitan Transportation Commission. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and are reviewed and updated by local participants prior to each decennial census as part of the Census Bureau’s Participant Statistical Areas Program (PSAP). The Census Bureau updates census tracts in situations where no local participant existed or where local or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of decennial census data. Census tracts generally have a population size between 1,200 and 8,000 people with an optimum size of 4,000 people. The spatial size of census tracts varies widely depending on the density of settlement. Ideally, census tract boundaries remain stable over time to facilitate statistical comparisons from census to census. However, physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, significant changes in population may result in splitting or combining census tracts. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some states to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. Census Tract Codes and Numbers—Census tract numbers have up to a 4-character basic number and may have an optional 2-character suffix; for example, 1457.02. The census tract numbers (used as names) eliminate any leading zeroes and append a suffix only if required. The 6-character numeric census tract codes, however, include leading zeroes and have an implied decimal point for the suffix. Census tract codes range from 000100 to 998999 and are unique within a county or equivalent area. The Census Bureau assigned a census tract code of 9900 to represent census tracts delineated to cover large bodies of water. In addition, census tract codes in the 9400s represent American Indian Areas and codes in the 9800s represent special land use areas. The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes. Relationship to Other Geographic Entities—Within the standard census geographic hierarchy, census tracts never cross state or county boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian, Alaska Native, and Native Hawaiian areas.
- API
Water Rates Survey Data 2017
data.orcities.org | Last Updated 2018-04-30T21:33:40.000ZThis is the survey results from the 2017 LOC Water Rates Survey. The attached Survey will help you with the coding of the data.