With Versium REACH's Contact Append or Contact Append Plus you can add consumer contact data, including multiple phone numbers or mobile-only to your list of customers or prospects. With Versium REACH you are connected to our proprietary database of over 300+ million consumers, 1 Billion emails, and over 150 million households in the United States. Through either our API or platform you can have contact data appended to your records with any of the following supplied values; Email Address Phone Postal Address, City, State, ZIP First Name, Last Name, City, State First Name, Last Name, ZIP

With Versium REACH's Firmographic Append tool in the Business to Business Direct product suite you unlock the ability to append valuable firmographic data for your customer and prospect contact lists. With only a few available attributes needed you can tap into Versium's industry-leading identity resolution engine and proprietary database to append rich firmographic data. To append data you will only need any of the following: - Email - Business Domain - Business Name, Address, City, State - Business Name, Phone

With Versium REACH's Consumer to Business tool you can unlock the professional data for prospects that are only providing you with their personal email address. Get back business information for your prospects needing only their personal email address. Versium's industry-leading identity resolution engine will locate and append the prospect's business email and/or firmographic data for their business.

With over 60 Million business professionals and 30+ million businesses in Versium's proprietary database, you will greatly increase you ability to identify key contact points and attributes that you were missing before.

This table feeds multiple apps for Tippecanoe County. Columns are the bare minimum details for generating a GRM. When new GRM data points are collected they should be appended here.

Observed linkages between consumer and B2B emails and website domains, categorized into IAB classification codes. Hashed emails can be linked to plain-text emails to append all consumer and B2B data fields for a full view of the individual and their online intent and behavior.

API for www.legislation.gov.uk - launched by The National Archives on 29/07/2010 - giving access to the statute book at various levels, for various times, as reusable html fragments, xml and rdf. The API is RESTful and uses content negotiation, so full access to the data can be achieved using http requests. Alternatively, just append data.xml or data.rdf to any legislation page on the website to return the underlying data. The full API is also available from http://legislation.data.gov.uk.

After May 3, 2024, this dataset and webpage will no longer be updated because hospitals are no longer required to report data on COVID-19 hospital admissions, and hospital capacity and occupancy data, to HHS through CDC’s National Healthcare Safety Network. Data voluntarily reported to NHSN after May 1, 2024, will be available starting May 10, 2024, at COVID Data Tracker Hospitalizations.

The following dataset provides facility-level data for hospital utilization aggregated on a weekly basis (Sunday to Saturday). These are derived from reports with facility-level granularity across two main sources: (1) HHS TeleTracking, and (2) reporting provided directly to HHS Protect by state/territorial health departments on behalf of their healthcare facilities.

The hospital population includes all hospitals registered with Centers for Medicare & Medicaid Services (CMS) as of June 1, 2020. It includes non-CMS hospitals that have reported since July 15, 2020. It does not include psychiatric, rehabilitation, Indian Health Service (IHS) facilities, U.S. Department of Veterans Affairs (VA) facilities, Defense Health Agency (DHA) facilities, and religious non-medical facilities.

For a given entry, the term “collection_week” signifies the start of the period that is aggregated. For example, a “collection_week” of 2020-11-15 means the average/sum/coverage of the elements captured from that given facility starting and including Sunday, November 15, 2020, and ending and including reports for Saturday, November 21, 2020.

Reported elements include an append of either “_coverage”, “_sum”, or “_avg”.

• A “_coverage” append denotes how many times the facility reported that element during that collection week.
• A “_sum” append denotes the sum of the reports provided for that facility for that element during that collection week.
• A “_avg” append is the average of the reports provided for that facility for that element during that collection week.

The file will be updated weekly. No statistical analysis is applied to impute non-response. For averages, calculations are based on the number of values collected for a given hospital in that collection week. Suppression is applied to the file for sums and averages less than four (4). In these cases, the field will be replaced with “-999,999”.

A story page was created to display both corrected and raw datasets and can be accessed at this link: https://healthdata.gov/stories/s/nhgk-5gpv

This data is preliminary and subject to change as more data become available. Data is available starting on July 31, 2020.

Sometimes, reports for a given facility will be provided to both HHS TeleTracking and HHS Protect. When this occurs, to ensure that there are not duplicate reports, deduplication is applied according to prioritization rules within HHS Protect.

For influenza fields listed in the file, the current HHS guidance marks these fields as optional. As a result, coverage of these elements are varied.

For recent updates to the dataset, scroll to the bottom of the dataset description.

On May 3, 2021, the following fields have been added to this data set.

• hhs_ids
• previous_day_admission_adult_covid_confirmed_7_day_coverage
• previous_day_admission_pediatric_covid_confirmed_7_day_coverage
• previous_day_admission_adult_covid_suspected_7_day_coverage
• previous_day_admission_pediatric_covid_suspected_7_day_coverage
• previous_week_personnel_covid_vaccinated_doses_administered_7_day_sum
• total_personnel_covid_vaccinated_doses_none_7_day_sum
• total_personnel_covid_vaccinated_doses_one_7_day_sum
• total_personnel_covid_vaccinated_doses_all_7_day_sum
• previous_week_patients_covid_vaccinated_doses_one_7_day_sum
• previous_week_patients_covid_vaccinated_doses_all_7_day_sum

On May 8, 2021, this data set has been converted to a corrected data set. The corrections applied to this data set are to smooth out data anomalies caused by keyed in data errors. To help determine which records have had corrections made to it. An additional Boolean field called is_corrected has been added.

On May 13, 2021 Changed vaccination fields from sum to max or min fields. This reflects the maximum or minimum number reported for that metric in a given week.

On June 7, 2021 Changed vaccination fields from max or min fields to Wednesday reported only. This reflects that the number reported for that metric is only reported on Wednesdays in a given week.

On September 20, 2021, the following has been updated: The use of analytic dataset as a source.

On January 19, 2022, the following fields have been added to this dataset:

• inpatient_beds_used_covid_7_day_avg
• inpatient_beds_used_covid_7_day_sum
• inpatient_beds_used_covid_7_day_coverage

On April 28, 2022, the following pediatric fields have been added to this dataset:

• all_pediatric_inpatient_bed_occupied_7_day_avg
• all_pediatric_inpatient_bed_occupied_7_day_coverage
• all_pediatric_inpatient_bed_occupied_7_day_sum
• all_pediatric_inpatient_beds_7_day_avg
• all_pediatric_inpatient_beds_7_day_coverage
• all_pediatric_inpatient_beds_7_day_sum
• previous_day_admission_pediatric_covid_confirmed_0_4_7_day_sum
• previous_day_admission_pediatric_covid_confirmed_12_17_7_day_sum
• previous_day_admission_pediatric_covid_confirmed_5_11_7_day_sum
• previous_day_admission_pediatric_covid_confirmed_unknown_7_day_sum
• staffed_icu_pediatric_patients_confirmed_covid_7_day_avg
• staffed_icu_pediatric_patients_confirmed_covid_7_day_coverage
• staffed_icu_pediatric_patients_confirmed_covid_7_day_sum
• staffed_pediatric_icu_bed_occupancy_7_day_avg
• staffed_pediatric_icu_bed_occupancy_7_day_coverage
• staffed_pediatric_icu_bed_occupancy_7_day_sum
• total_staffed_pediatric_icu_beds_7_day_avg
• total_staffed_pediatric_icu_beds_7_day_coverage
• total_staffed_pediatric_icu_beds_7_day_sum

On October 24, 2022, the data includes more analytical calculations in efforts to provide a cleaner dataset. For a raw version of this dataset, please follow this link: https://healthdata.gov/Hospital/COVID-19-Reported-Patient-Impact-and-Hospital-Capa/uqq2-txqb

Due to changes in reporting requirements, after June 19, 2023, a collection week is defined as starting on a Sunday and ending on the next Saturday.

There are many useful strategies for preparing GIS data for Next Generation 9-1-1. One step of preparation is making sure that all of the required fields exist (and sometimes populated) before loading into the system. While some localities add needed fields to their local data, others use an extract, transform, and load process to transform their local data into a Next Generation 9-1-1 GIS data model, and still others may do a combination of both.There are several strategies and considerations when loading data into a Next Generation 9-1-1 GIS data model. The best place to start is using a GIS data model schema template, or an empty file with the needed data layout to which you can append your data. Here are some resources to help you out. 1) The National Emergency Number Association (NENA) has a GIS template available on the Next Generation 9-1-1 GIS Data Model Page.2) The NENA GIS Data Model template uses a WGS84 coordinate system and pre-builds many domains. The slides from the Virginia NG9-1-1 User Group meeting in May 2021 explain these elements and offer some tips and suggestions for working with them. There are also some tips on using field calculator. Click the "open" button at the top right of this screen or here to view this information.3) VGIN adapted the NENA GIS Data Model into versions for Virginia State Plane North and Virginia State Plane South, as Virginia recommends uploading in your local coordinates and having the upload tools consistently transform your data to the WGS84 (4326) parameters required by the Next Generation 9-1-1 system. These customized versions only include the Site Structure Address Point and Street Centerlines feature classes. Address Point domains are set for address number, state, and country. Street Centerline domains are set for address ranges, parity, one way, state, and country. 4) A sample extract, transform, and load (ETL) for NG9-1-1 Upload script is available here.Additional resources and recommendations on GIS related topics are available on the VGIN 9-1-1 & GIS page.

Test dataset: part a (init) + part b (append) + part c (append) + pending..... review

There are many useful strategies for preparing GIS data for Next Generation 9-1-1. One step of preparation is making sure that all of the required fields exist (and sometimes populated) before loading into the system. While some localities add needed fields to their local data, others use an extract, transform, and load process to transform their local data into a Next Generation 9-1-1 GIS data model, and still others may do a combination of both.There are several strategies and considerations when loading data into a Next Generation 9-1-1 GIS data model. The best place to start is using a GIS data model schema template, or an empty file with the needed data layout to which you can append your data. Here are some resources to help you out. 1) The National Emergency Number Association (NENA) has a GIS template available on the Next Generation 9-1-1 GIS Data Model Page.2) The NENA GIS Data Model template uses a WGS84 coordinate system and pre-builds many domains. The slides from the Virginia NG9-1-1 User Group meeting in May 2021 explain these elements and offer some tips and suggestions for working with them. There are also some tips on using field calculator. Click the "open" button at the top right of this screen or here to view this information.3) VGIN adapted the NENA GIS Data Model into versions for Virginia State Plane North and Virginia State Plane South, as Virginia recommends uploading in your local coordinates and having the upload tools consistently transform your data to the WGS84 (4326) parameters required by the Next Generation 9-1-1 system. These customized versions only include the Site Structure Address Point and Street Centerlines feature classes. Address Point domains are set for address number, state, and country. Street Centerline domains are set for address ranges, parity, one way, state, and country. 4) A sample extract, transform, and load (ETL) for NG9-1-1 Upload script is available here.Additional resources and recommendations on GIS related topics are available on the VGIN 9-1-1 & GIS page.

Suppl. Append. 1DNA sequence data from GenBank.SupplApp1.csvSuppl. Append. 2Scored character states and literature sources.SupplApp2.csvSuppl. Append. 3Biogeographic models and model fit statistics. Results for (A) Gesneriaceae, (B) Gesnerioideae, and (C) Didymocarpoideae. Abbreviations: Par. = free parameters; lnLik = log-likelihood; AIC = Akaike Information Criterion; AICc = Akaike Information Criterion, corrected; ΔAICc = change in AICc; AICw = AIC weights; BIC = Bayesian Information Criterion; ΔBIC = change in BIC; DEC = Dispersal Extinction Cladogenesis model; DIVALIKE = BioGeoBEARS implementation of DIVA model; BAYAREALIKE = BioGeoBEARS implementation of BayArea model; s = subset sympatry; J = founder-event speciation.SupplApp3.pdfSuppl. Append. 4Summary of gene sequences used in the present study.SupplApp4.pdfSuppl. Append. 5Taxonomic comments and conclusions of the revised phylogenetic hypotheses for the Gesneriaceae.SupplApp5.pdfSuppl. Append. 6Stem and crown age estimates for Gesneriaceae clades and outgroups. For comparison, the ages of stems and crowns from Petrova et al. (2015), Perret et al. (2013), Woo et al. (2011), Bell et al. (2010), and Roalson et al. (2008) are provided. Estimation methods are indicated below reference names. Dates are indicated as Mean (Minimum, Maximum). Abbreviations: BEAST, Bayesian Evolutionary Analysis Sampling Trees; PL, penalized likelihood.SupplApp6.pdfSuppl. Append. 7GeoSSE model testing. Results for (A) Africa and Madagascar, (B) Temperate and Tropical Andes, (C) Amazon and Atlantic Brazil, (D) Caribbean and West Indies, and (E) Pacific and Southeast Asia. Gray boxes denote the model with the best-fit. Significance of constrained models versus unconstrained (full) model is assessed as follows: N.S., P>0.1; *, P<0.1; **, P<0.05; ***, P<0.001. Rate categories: λA, speciation in focal area (endemic species); λB, speciation in all other areas combined; λAB, speciation in widespread species; μA, extinction in focal area (endemic species); μB, extinction in all other areas combined; qA, dispersal out of focal area; qB, dispersal out of all other areas into focal area. Abbreviations: Df = degrees of freedom; lnLik = log-likelihood; AIC = Akaike Information Criterion; AICc = Akaike Information Criterion, corrected; ΔAICc = change in AICc; AICw = Akaike weights; LRT = likelihood ratio test; BIC = Bayesian Information Criterion; ΔBIC = change in BIC.SupplApp7.pdfSuppl. Append. 8SIMMAP ancestral character estimations of flower characters. Results for flower color in (A) Gesneriaceae, (B) Gesnerioideae, (C) Didymocarpoideae; corolla shape in (D) Gesneriaceae, (E) Gesnerioideae, (F) Didymocarpoideae; pollination syndrome (G) Gesneriaceae, (H) Gesnerioideae, (I) Didymocarpoideae.SupplApp8.pdfSuppl. Append. 9SIMMAP ancestral character estimations of epiphytism and growth form characters. Results for Gesneriaceae for (A) epiphytism and (B) unifoliate growth form.SupplApp9.pdfSuppl. Append. 10Geiger statistics for phylogenetic signal (λ), trait evolution at speciation (κ), and rate increase over time (δ). Significance of model fit with the addition of λ, κ, and δ parameters against the null model is assessed as follows: N.S., not significant; *, P<0.01; **, P<0.001. Corolla gibbosity is abbreviated "gibb." and epiphytism is abbreviated "epi."SupplApp10.pdfSuppl. Append. 11BiSSE model testing. Results for epiphytism in (A) Gesneriaceae, (B) Gesnerioideae, (C) Didymocarpoideae; ornithophily in (D) Gesneriaceae, (E) Gesnerioideae, (F) Didymocarpoideae; unifoliate growth in (G) Didymocarpoideae. Gray boxes denote the best fitting model. Significance of constrained models versus unconstrained (full) model is assessed as follows: N.S., P>0.1; *, P<0.1; **, P<0.05; ***, P<0.001. Rate categories: λ, speciation; μ, extinction; q, transition rate. In all cases, estimated rates for the characters of interest are indicated by λ1 and μ1, respectively. Abbreviations: Df = degrees of freedom; lnLik = log-likelihood; AIC = Akaike Information Criterion; AICc = Akaike Information Criterion, corrected; ΔAICc = change in AICc; AICw = Akaike weights; LRT = likelihood ratio test; BIC = Bayesian Information Criterion; ΔBIC = change in BIC.SupplApp11.pdfSuppl. Figure 1Gesneriaceae phylogenetic hypothesis. Numbers above branches refer to (A) aLRT and (B) ML bootstrap percentages, respectively. (C) ML phylogram with branch lengths.SupplFig1.pdfSuppl. Figure 2Calibrated Gesneriaceae phylogenetic hypothesis. Bars on branches reflect the 95% confidence interval on the time estimate. Circled numbers at nodes indicate fossil, geologic, and secondary calibration points, respectively.SupplFig2.pdfSuppl. Figure 3Historical biogeographical hypothesis for Gesneriaceae using the best-fit model BAYAREALIKE+s+J. Geographic areas: A, Temperate and Tropical Andes; B = Amazon and Atlantic Brazil; C = Central America...

With Versium REACH Demographic Append you will have access to many different attributes for enriching your data.

Basic, Household and Financial, Lifestyle and Interests, Political and Donor.

Here is a list of what sorts of attributes are available for each output type listed above:

Basic: - Senior in Household - Young Adult in Household - Small Office or Home Office - Online Purchasing Indicator
- Language - Marital Status - Working Woman in Household - Single Parent - Online Education - Occupation - Gender - DOB (MM/YY) - Age Range - Religion - Ethnic Group - Presence of Children - Education Level - Number of Children

Household, Financial and Auto: - Household Income - Dwelling Type - Credit Card Holder Bank - Upscale Card Holder - Estimated Net Worth - Length of Residence - Credit Rating - Home Own or Rent - Home Value - Home Year Built - Number of Credit Lines - Auto Year - Auto Make - Auto Model - Home Purchase Date - Refinance Date - Refinance Amount - Loan to Value - Refinance Loan Type - Home Purchase Price - Mortgage Purchase Amount - Mortgage Purchase Loan Type - Mortgage Purchase Date - 2nd Most Recent Mortgage Amount - 2nd Most Recent Mortgage Loan Type - 2nd Most Recent Mortgage Date - 2nd Most Recent Mortgage Interest Rate Type - Refinance Rate Type - Mortgage Purchase Interest Rate Type - Home Pool

Lifestyle and Interests: - Mail Order Buyer - Pets - Magazines - Reading
- Current Affairs and Politics
- Dieting and Weight Loss - Travel - Music - Consumer Electronics - Arts
- Antiques - Home Improvement - Gardening - Cooking - Exercise
- Sports - Outdoors - Womens Apparel
- Mens Apparel - Investing - Health and Beauty - Decorating and Furnishing

Political and Donor: - Donor Environmental - Donor Animal Welfare - Donor Arts and Culture - Donor Childrens Causes - Donor Environmental or Wildlife - Donor Health - Donor International Aid - Donor Political - Donor Conservative Politics - Donor Liberal Politics - Donor Religious - Donor Veterans - Donor Unspecified - Donor Community - Party Affiliation

Parcel boundary lines in this dataset are published once a year, after the boundary adjustments have been approved by Planning and Zoning and certified through the Assessor's Office. Attribute data is published at different times throughout the year, as detailed below.

*Attribute data excludes ownership and address data in this dataset. If you wish to have these data, please fill out the Public Information request form found in the Download Datasets page of the GIS Portal and email to lfrederick@co.valley.id.us.

ATTRIBUTE DATA - MONTHLY UPDATES

These fields are updated in the dataset monthly. After the public table updates are run by the Assessor's Office, Valley County GIS analyst exports the tables to append/update the new data values.

ATTRIBUTE DATA - ANNUAL UPDATES

These fields are updated annually after certification of parcel boundaries and valuation have been completed.

Trace-metal concentrations in sediment and in the clam Limecola petalum (World Register of Marine Species, 2020; formerly reported as Macoma balthica and M. petalum), clam reproductive activity, and benthic macroinvertebrate community structure were investigated in a mudflat located 1 kilometer south of the discharge of the Palo Alto Regional Water Quality Control Plant (PARWQCP) in south San Francisco Bay, California. This report includes data collected by the U.S. Geological Survey (USGS) starting in January 2019. These data append to long-term datasets extending back to 1974. This dataset supports the City of Palo Alto’s Near-Field Receiving-Water Monitoring Program, initiated in 1994. This data release is presented as two datasets each on its own child page. The first child page contains clam tissue metals data, sediment metals data, percentage fine sediment, total organic carbon, and the salinity of the overlying water. The second child page contains clam reproduction and benthic community data. Please read the metadata file corresponding to each dataset for complete details.

ben-ge/DEM: BigEarthNet Extended with Geographical and Environmental Data/Elevation Data

M. Mommert, N. Kesseli, J. Hanna, L. Scheibenreif, D. Borth, B. Demir, "ben-ge: Extending BigEarthNet with Geographical and Environmental Data", IEEE International Geoscience and Remote Sensing Symposium, Pasadena, USA, 2023.

ben-ge is a multimodal dataset for Earth observation (https://github.com/HSG-AIML/ben-ge) that serves as an extension to the BigEarthNet dataset. ben-ge complements the Sentinel-1/2 data contained in BigEarthNet by providing additional data modalities:

• elevation data extracted from the Copernicus Digital Elevation Model GLO-30;
• land-use/land-cover data extracted from ESA Worldcover;
• climate zone information extracted from Beck et al. 2018;
• environmental data concurrent with the Sentinel-1/2 observations from the ERA-5 global reanalysis;
• a seasonal encoding.

This archive contains the digital elevation model (DEM) data of ben-ge, which were extracted from the Copernicus Digital Elevation Model (GLO-30).

Data

Topographic maps are generated based on the global Copernicus Digital Elevation Model (GLO-30) (https://spacedata.copernicus.eu/collections/copernicus-digital-elevation-model). Relevant GLO-30 map tiles from the 2021 data release were downloaded through AWS (https://registry.opendata.aws/copernicus-dem/), reprojected into the coordinate frame of the corresponding Sentinel-1/2 patches and interpolated with bilinear resampling to 10 m resolution on the ground.

Elevation data are provided in a separate geotiff file for each patch. The naming convention for these files uses the Sentinel-2 patch_id to which we append _dem.tif. Each file contains a single band with 16-bit integer values that refer to the elevation of that pixel over sea level.

Relevant meta data for the ben-ge dataset are compiled in the file ben-ge_meta.csv. This file resides on the root level of this archive and contains the following data for each patch: * patch_id: the Sentinel-2 patch id, which plays a central role for cross-referencing different data modalities for individual patches; * patch_id_s1: the Sentinel-1 patch id for this specific patch; * timestamp_s2: the timestamp for the Sentinel-2 observation; * timestamp_s1: the timestamp for the Sentinel-1 observation; * season_s2: the seasonal encoding (see below) for the time of the Sentinel-2 observation; * season_s1: the seasonal encoding (see below) for the time of the Sentinel-1 observation; * lon: longitude (WGS-84) of the center of the patch [degrees]; * lat: latitude (WGS-84) of the center of the patch [degrees]; * climatezone: integer value indicating the climate zone based on Beck et al. 2018 (see below for details).

File and directory structure

This archive contains the following directory and file structure:

| |--- README (this file) |--- ben-ge_meta.csv (ben-ge meta data) |--- dem/ (digital elevation model data) |--- S2A_MSIL2A_20171208T093351_3_82_dem.tif ...

To properly conserve the file and directory structure of the ben-ge dataset, please place this archive file on the root level of the ben-ge dataset and then unpack it. Once unpacked, ben-ge/DEM requires 17.2 GB of space.

Other data modalities from ben-ge (as well as Sentinel-1/2 data as provided by BigEarthNet, https://bigearth.net/#downloads), may be added as required. For reference, the recommended structure for the full dataset looks as follows:

| |--- ben-ge_meta.csv (ben-ge meta data) |--- ben-ge_era-5.csv (ben-ge environmental data) |--- ben-ge_esaworldcover.csv (patch-wise ben-ge land-use/land-cover data) |--- dem/ (digital elevation model data) | |--- S2A_MSIL2A_20171208T093351_3_82_dem.tif | ... |--- esaworldcover/ (land-use/land-cover data) | |--- S2B_MSIL2A_20170914T93030_26_83_esaworldcover.tif | ... |--- sentinel-1/ (Sentinel-1 SAR data) | |--- S1A_IW_GRDH_1SDV_20180219T063851_29UPV_70_43/ | |--- S1A_IW_GRDH_1SDV_20180219T063851_29UPV_70_43_labels_metadata.json (BigEarthNet label file) | |--- S1A_IW_GRDH_1SDV_20180219T063851_29UPV_70_43_VH.tif (BigEarthNet/Sentinel-1 VH polarization data) | |--- S1A_IW_GRDH_1SDV_20180219T063851_29UPV_70_43_VV.tif (BigEarthNet/Sentinel-1 VV polarization data) | ... |--- sentinel-2/ (Sentinel-2 multispectral data) | |--- S2B_MSIL2A_20170818T112109_31_83/ | |--- S2B_MSIL2A_20170818T112109_31_83_B01.tif (BigEarthNet/Sentinel-2 Band 1 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B02.tif (BigEarthNet/Sentinel-2 Band 2 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B03.tif (BigEarthNet/Sentinel-2 Band 3 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B04.tif (BigEarthNet/Sentinel-2 Band 4 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B05.tif (BigEarthNet/Sentinel-2 Band 5 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B06.tif (BigEarthNet/Sentinel-2 Band 6 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B07.tif (BigEarthNet/Sentinel-2 Band 7 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B08.tif (BigEarthNet/Sentinel-2 Band 8 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B09.tif (BigEarthNet/Sentinel-2 Band 9 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B11.tif (BigEarthNet/Sentinel-2 Band 11 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B12.tif (BigEarthNet/Sentinel-2 Band 12 data) | |--- S2B_MSIL2A_20170818T112109_31_83_B8A.tif (BigEarthNet/Sentinel-2 Band 8A data) | |--- S2B_MSIL2A_20170818T112109_31_83_labels_metadata.json (BigEarthNet label file) ...

More Information

For more information, please refer to https://github.com/HSG-AIML/ben-ge.

Citing ben-ge If you use data contained in this archive, please cite the following paper:

M. Mommert, N. Kesseli, J. Hanna, L. Scheibenreif, D. Borth, B. Demir, "ben-ge: Extending BigEarthNet with Geographical and Environmental Data", IEEE International Geoscience and Remote Sensing Symposium, Pasadena, USA, 2023.

Code and data to reproduce all results and graphs reported in Tannenbaum et al. (2022). This folder contains data files (.dta files) and a Stata do-file (code.do) that stitches together the different data files and executes all analyses and produces all figures reported in the paper. The do-file uses a number of user-written packages, which are listed below. Most of these can be installed using the ssc install command in Stata. Also, users will need to change the current directory path (at the start of the do-file) before executing the code. List of user written packages (descriptions): revrs (reverse-codes variable) ereplace (extends the egen command to permit replacing) grstyle (changes the settings for the overall look of graphs) spmap (used for graphing spatial data) qqvalue (used for obtaining Benjamini-Hochberg corrected p-values) parmby (creates a dataset by calling an estimation command for each by-group) domin (used to perform dominance analyses) coefplot (used for creating coefficient plots) grc1leg (combine graphs with a single common legend) xframeappend (append data frames to the end of the current data frame)

Analysis of ‘COVID-19 Reported Patient Impact and Hospital Capacity by Facility’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/e6ff9332-7a6d-42a7-986b-3deb14475c11 on 13 February 2022.

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

The "COVID-19 Reported Patient Impact and Hospital Capacity by Facility" dataset from the U.S. Department of Health & Human Services, filtered for Connecticut. View the full dataset and detailed metadata here: https://healthdata.gov/Hospital/COVID-19-Reported-Patient-Impact-and-Hospital-Capa/anag-cw7u

The following dataset provides facility-level data for hospital utilization aggregated on a weekly basis (Friday to Thursday). These are derived from reports with facility-level granularity across two main sources: (1) HHS TeleTracking, and (2) reporting provided directly to HHS Protect by state/territorial health departments on behalf of their healthcare facilities.

The hospital population includes all hospitals registered with Centers for Medicare & Medicaid Services (CMS) as of June 1, 2020. It includes non-CMS hospitals that have reported since July 15, 2020. It does not include psychiatric, rehabilitation, Indian Health Service (IHS) facilities, U.S. Department of Veterans Affairs (VA) facilities, Defense Health Agency (DHA) facilities, and religious non-medical facilities.

For a given entry, the term “collection_week” signifies the start of the period that is aggregated. For example, a “collection_week” of 2020-11-20 means the average/sum/coverage of the elements captured from that given facility starting and including Friday, November 20, 2020, and ending and including reports for Thursday, November 26, 2020.

Reported elements include an append of either “_coverage”, “_sum”, or “_avg”.

A “_coverage” append denotes how many times the facility reported that element during that collection week.

A “_sum” append denotes the sum of the reports provided for that facility for that element during that collection week.

A “_avg” append is the average of the reports provided for that facility for that element during that collection week.

The file will be updated weekly. No statistical analysis is applied to impute non-response. For averages, calculations are based on the number of values collected for a given hospital in that collection week. Suppression is applied to the file for sums and averages less than four (4). In these cases, the field will be replaced with “-999,999”.

This data is preliminary and subject to change as more data become available. Data is available starting on July 31, 2020.

Sometimes, reports for a given facility will be provided to both HHS TeleTracking and HHS Protect. When this occurs, to ensure that there are not duplicate reports, deduplication is applied according to prioritization rules within HHS Protect.

For influenza fields listed in the file, the current HHS guidance marks these fields as optional. As a result, coverage of these elements are varied.

On May 3, 2021, the following fields have been added to this data set. hhs_ids previous_day_admission_adult_covid_confirmed_7_day_coverage previous_day_admission_pediatric_covid_confirmed_7_day_coverage previous_day_admission_adult_covid_suspected_7_day_coverage previous_day_admission_pediatric_covid_suspected_7_day_coverage previous_week_personnel_covid_vaccinated_doses_administered_7_day_sum total_personnel_covid_vaccinated_doses_none_7_day_sum total_personnel_covid_vaccinated_doses_one_7_day_sum total_personnel_covid_vaccinated_doses_all_7_day_sum previous_week_patients_covid_vaccinated_doses_one_7_day_sum previous_week_patients_covid_vaccinated_doses_all_7_day_sum

On May 8, 2021, this data set has been converted to a corrected data set. The corrections applied to this data set are to smooth out data anomalies caused by keyed in data errors. To help determine which records have had corrections made to it. An additional Boolean field called is_corrected has been added. To see the numbers as reported by the facilities, go to: https://healthdata.gov/Hospital/COVID-19-Reported-Patient-Impact-and-Hospital-Capa/uqq2-txqb

On May 13, 2021 Changed vaccination fields from sum to max or min fields. This reflects the maximum or minimum number report

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

The following dataset provides facility-level data for hospital utilization aggregated on a weekly basis (Friday to Thursday). These are derived from reports with facility-level granularity across two main sources: (1) HHS TeleTracking, and (2) reporting provided directly to HHS Protect by state/territorial health departments on behalf of their healthcare facilities.

The hospital population includes all hospitals registered with Centers for Medicare & Medicaid Services (CMS) as of June 1, 2020. It includes non-CMS hospitals that have reported since July 15, 2020. It does not include psychiatric, rehabilitation, Indian Health Service (IHS) facilities, U.S. Department of Veterans Affairs (VA) facilities, Defense Health Agency (DHA) facilities, and religious non-medical facilities.

For a given entry, the term “collection_week” signifies the start of the period that is aggregated. For example, a “collection_week” of 2020-11-20 means the average/sum/coverage of the elements captured from that given facility starting and including Friday, November 20, 2020, and ending and including reports for Thursday, November 26, 2020.

Reported elements include an append of either “_coverage”, “_sum”, or “_avg”.

A “_coverage” append denotes how many times the facility reported that element during that collection week. A “_sum” append denotes the sum of the reports provided for that facility for that element during that collection week. A “_avg” append is the average of the reports provided for that facility for that element during that collection week. The file will be updated weekly. No statistical analysis is applied to impute non-response. For averages, calculations are based on the number of values collected for a given hospital in that collection week. Suppression is applied to the file for sums and averages less than four (4). In these cases, the field will be replaced with “-999,999”.

This data is preliminary and subject to change as more data become available. Data is available starting on July 31, 2020.

Sometimes, reports for a given facility will be provided to both HHS TeleTracking and HHS Protect. When this occurs, to ensure that there are not duplicate reports, deduplication is applied according to prioritization rules within HHS Protect.

For influenza fields listed in the file, the current HHS guidance marks these fields as optional. As a result, coverage of these elements are varied.

ben-ge/DEM: BigEarthNet Extended with Geographical and Environmental Data/Elevation Data

M. Mommert, N. Kesseli, J. Hanna, L. Scheibenreif, D. Borth, B. Demir, "ben-ge: Extending BigEarthNet with Geographical and Environmental Data", IEEE International Geoscience and Remote Sensing Symposium, Pasadena, USA, 2023.

ben-ge is a multimodal dataset for Earth observation (https://github.com/HSG-AIML/ben-ge) that serves as an extension to the BigEarthNet dataset. ben-ge complements the Sentinel-1/2 data contained in BigEarthNet by providing additional data modalities:

* elevation data extracted from the Copernicus Digital Elevation Model GLO-30;
* land-use/land-cover data extracted from ESA Worldcover;
* climate zone information extracted from Beck et al. 2018;
* environmental data concurrent with the Sentinel-1/2 observations from the ERA-5 global reanalysis;
* a seasonal encoding.

This archive contains the digital elevation model (DEM) data of ben-ge, which were extracted from the Copernicus Digital Elevation Model (GLO-30).

Data

Topographic maps are generated based on the global Copernicus Digital Elevation Model (GLO-30) (https://spacedata.copernicus.eu/collections/copernicus-digital-elevation-model). Relevant GLO-30 map tiles from the 2021 data release were downloaded through AWS (https://registry.opendata.aws/copernicus-dem/), reprojected into the coordinate frame of the corresponding Sentinel-1/2 patches and interpolated with bilinear resampling to 10 m resolution on the ground.

Elevation data are provided in a separate geotiff file for each patch. The naming convention for these files uses the Sentinel-2 patch_id to which we append _dem.tif. Each file contains a single band with 16-bit integer values that refer to the elevation of that pixel over sea level.

Relevant meta data for the ben-ge dataset are compiled in the file ben-ge_meta.csv. This file resides on the root level of this archive and contains the following data for each patch:
* patch_id: the Sentinel-2 patch id, which plays a central role for cross-referencing different data modalities for individual patches;
* patch_id_s1: the Sentinel-1 patch id for this specific patch;
* timestamp_s2: the timestamp for the Sentinel-2 observation;
* timestamp_s1: the timestamp for the Sentinel-1 observation;
* season_s2: the seasonal encoding (see below) for the time of the Sentinel-2 observation;
* season_s1: the seasonal encoding (see below) for the time of the Sentinel-1 observation;
* lon: longitude (WGS-84) of the center of the patch [degrees];
* lat: latitude (WGS-84) of the center of the patch [degrees];
* climatezone: integer value indicating the climate zone based on Beck et al. 2018 (see below for details).

File and directory structure

This archive contains the following directory and file structure:

|
|--- README (this file)
|--- ben-ge_meta.csv (ben-ge meta data)
|--- dem/ (digital elevation model data)
|--- S2A_MSIL2A_20171208T093351_3_82_dem.tif
...

To properly conserve the file and directory structure of the ben-ge dataset, please place this archive file on the root level of the ben-ge dataset and then unpack it. Once unpacked, ben-ge/DEM requires 17.2 GB of space.

Other data modalities from ben-ge (as well as Sentinel-1/2 data as provided by BigEarthNet, https://bigearth.net/#downloads), may be added as required. For reference, the recommended structure for the full dataset looks as follows:

|
|--- ben-ge_meta.csv (ben-ge meta data)
|--- ben-ge_era-5.csv (ben-ge environmental data)
|--- ben-ge_esaworldcover.csv (patch-wise ben-ge land-use/land-cover data)
|--- dem/ (digital elevation model data)
| |--- S2A_MSIL2A_20171208T093351_3_82_dem.tif
| ...
|--- esaworldcover/ (land-use/land-cover data)
| |--- S2B_MSIL2A_20170914T93030_26_83_esaworldcover.tif
| ...
|--- sentinel-1/ (Sentinel-1 SAR data)
| |--- S1A_IW_GRDH_1SDV_20180219T063851_29UPV_70_43/
| |--- S1A_IW_GRDH_1SDV_20180219T063851_29UPV_70_43_labels_metadata.json (BigEarthNet label file)
| |--- S1A_IW_GRDH_1SDV_20180219T063851_29UPV_70_43_VH.tif (BigEarthNet/Sentinel-1 VH polarization data)
| |--- S1A_IW_GRDH_1SDV_20180219T063851_29UPV_70_43_VV.tif (BigEarthNet/Sentinel-1 VV polarization data)
| ...
|--- sentinel-2/ (Sentinel-2 multispectral data)
| |--- S2B_MSIL2A_20170818T112109_31_83/
| |--- S2B_MSIL2A_20170818T112109_31_83_B01.tif (BigEarthNet/Sentinel-2 Band 1 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B02.tif (BigEarthNet/Sentinel-2 Band 2 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B03.tif (BigEarthNet/Sentinel-2 Band 3 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B04.tif (BigEarthNet/Sentinel-2 Band 4 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B05.tif (BigEarthNet/Sentinel-2 Band 5 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B06.tif (BigEarthNet/Sentinel-2 Band 6 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B07.tif (BigEarthNet/Sentinel-2 Band 7 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B08.tif (BigEarthNet/Sentinel-2 Band 8 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B09.tif (BigEarthNet/Sentinel-2 Band 9 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B11.tif (BigEarthNet/Sentinel-2 Band 11 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B12.tif (BigEarthNet/Sentinel-2 Band 12 data)
| |--- S2B_MSIL2A_20170818T112109_31_83_B8A.tif (BigEarthNet/Sentinel-2 Band 8A data)
| |--- S2B_MSIL2A_20170818T112109_31_83_labels_metadata.json (BigEarthNet label file)
...

More Information

For more information, please refer to https://github.com/HSG-AIML/ben-ge.

Citing ben-ge
If you use data contained in this archive, please cite the following paper:

M. Mommert, N. Kesseli, J. Hanna, L. Scheibenreif, D. Borth, B. Demir, "ben-ge: Extending BigEarthNet with Geographical and Environmental Data", IEEE International Geoscience and Remote Sensing Symposium, Pasadena, USA, 2023.

🇺🇸 미국 English After May 3, 2024, this dataset and webpage will no longer be updated because hospitals are no longer required to report data on COVID-19 hospital admissions, and hospital capacity and occupancy data, to HHS through CDC’s National Healthcare Safety Network. Data voluntarily reported to NHSN after May 1, 2024, will be available starting May 10, 2024, at COVID Data Tracker Hospitalizations. The following dataset provides facility-level data for hospital utilization aggregated on a weekly basis (Sunday to Saturday). These are derived from reports with facility-level granularity across two main sources: (1) HHS TeleTracking, and (2) reporting provided directly to HHS Protect by state/territorial health departments on behalf of their healthcare facilities. The hospital population includes all hospitals registered with Centers for Medicare & Medicaid Services (CMS) as of June 1, 2020. It includes non-CMS hospitals that have reported since July 15, 2020. It does not include psychiatric, rehabilitation, Indian Health Service (IHS) facilities, U.S. Department of Veterans Affairs (VA) facilities, Defense Health Agency (DHA) facilities, and religious non-medical facilities. For a given entry, the term “collection_week” signifies the start of the period that is aggregated. For example, a “collection_week” of 2020-11-15 means the average/sum/coverage of the elements captured from that given facility starting and including Sunday, November 15, 2020, and ending and including reports for Saturday, November 21, 2020. Reported elements include an append of either “_coverage”, “_sum”, or “_avg”. A “_coverage” append denotes how many times the facility reported that element during that collection week. A “_sum” append denotes the sum of the reports provided for that facility for that element during that collection week. A “_avg” append is the average of the reports provided for that facility for that element during that collection week. The file will be updated weekly. No statistical analysis is applied to impute non-response. For averages, calculations are based on the number of values collected for a given hospital in that collection week. Suppression is applied to the file for sums and averages less than four (4). In these cases, the field will be replaced with “-999,999”. A story page was created to display both corrected and raw datasets and can be accessed at this link: https://healthdata.gov/stories/s/nhgk-5gpv This data is preliminary and subject to change as more data become available. Data is available starting on July 31, 2020. Sometimes, reports for a given facility will be provided to both HHS TeleTracking and HHS Protect. When this occurs, to ensure that there are not duplicate reports, deduplication is applied according to prioritization rules within HHS Protect. For influenza fields listed in the file, the current HHS guidance marks these fields as optional. As a result, coverage of these elements are varied. For recent updates to the dataset, scroll to the bottom of the dataset description. On May 3, 2021, the following fields have been added to this data set.