Sweden phone number data contains contact numbers collected from trusted sources. We define this data by ensuring that all phone numbers come from reliable and verified sources. You can even check source URLs to see where the data is collected from. Being clear makes it easy for you to trust the data. Our team is always available with 24/7 support if you need help or have questions about the data. Also, we focus on opt-in data, meaning that everyone on the list has given permission to be contacted. Sweden number data gives you access to contact information from people in Sweden. We define this data by making sure every number is accurate and useful. If you ever receive an incorrect number, we provide a replacement guarantee. We’ll make sure to fix any mistakes for you. Furthermore, we collect the data on a customer-permission basis. That means each person has agreed to share their contact details. This ensures that you are only getting numbers from people who have given permission. Moreover, we work hard to provide this data from List to Data that you can trust. By offering a replacement guarantee, we make sure that all the phone numbers you get are correct and reliable.

The 2011 Population and Housing Census marks a milestone in census exercises in Europe. For the first time, European legislation defined in detail a set of harmonised high-quality data from the population and housing censuses conducted in the EU Member States. As a result, the data from the 2011 round of censuses offer exceptional flexibility to cross-tabulate different variables and to provide geographically detailed data.

EU Member States have developed different methods to produce these census data. The national differences reflect the specific national situations in terms of data source availability, as well as the administrative practices and traditions of that country.

The EU census legislation respects this diversity. The Regulation of the European Parliament and of the Council on population and housing censuses (Regulation (EC) No 763/2008) is focussed on output harmonisation rather than input harmonisation. Member States are free to assess for themselves how to conduct their 2011 censuses and which data sources, methods and technology should be applied given the national context. This gives the Member States flexibility, in line with the principles of subsidiarity and efficiency, and with the competences of the statistical institutes in the Member States.

However, certain important conditions must be met in order to achieve the objective of comparability of census data from different Member States and to assess the data quality:

Regulation (EC) No 1201/20092 contains definitions and technical specifications for the census topics (variables) and their breakdowns that are required to achieve Europe-wide comparability.

The specifications are based closely on international recommendations and have been designed to provide the best possible information value. The census topics include geographic, demographic, economic and educational characteristics of persons, international and internal migration characteristics as well as household, family and housing characteristics.

Regulation (EU) No 519/2010 requires the data outputs that Member States transmit to the Eurostat to comply with a defined programme of statistical data (tabulation) and with set rules concerning the replacement of statistical data. The content of the EU census programme serves major policy needs of the European Union. Regionally, there is a strong focus on the NUTS 2 level. The data requirements are adapted to the level of regional detail. The Regulation does not require transmission of any data that the Member States consider to be confidential.

The statistical data must be completed by metadata that will facilitate interpretation of the numerical data, including country-specific definitions plus information on the data sources and on methodological issues. This is necessary in order to achieve the transparency that is a condition for valid interpretation of the data.

Users of output-harmonised census data from the EU Member States need to have detailed information on the quality of the censuses and their results.

Regulation (EU) No 1151/2010) therefore requires transmission of a quality report containing a systematic description of the data sources used for census purposes in the Member States and of the quality of the census results produced from these sources. A comparably structured quality report for all EU Member States will support the exchange of experience from the 2011 round and become a reference for future development of census methodology (EU legislation on the 2011 Population and Housing Censuses - Explanatory Notes ).

In order to ensure proper transmission of the data and metadata and provide user-friendly access to this information, a common technical format is set for transmission for all Member States and for the Commission (Eurostat). The Regulation therefore requires the data to be transmitted in a harmonised structure and in the internationally established SDMX format from every Member State. In order to achieve this harmonised transmission, a new system has been developed – the CENSUS HUB.

The Census Hub is a conceptually new system used for the dissemination of the 2011 Census. It is based on the concept of data sharing, where a group of partners (Eurostat on one hand and National Statistical Institutes on the other) agree to provide access to their data according to standard processes, formats and technologies.

The Census Hub is a readily-accessible system that provided the following functions:

• Data providers (the NSIs) can make data available directly from their systems through a querying system. In parallel,
• Data users browse the hub to define a dataset of interest via the above structural metadata and retrieve the dataset from the NSIs.

From the data management point of view, the hub is based on agreed hypercubes (data-sets in the form of multi-dimensional aggregations). The hypercubes are not sent to the central system. Instead the following process operates:

1. a user defines a dataset through the web interface of the central hub and requests it;
2. the central hub translates the user request in one or more queries and sends them to the related NSIs’ systems;
3. NSIs’ systems process the query and send the result to the central hub in a standard format;
4. the central hub puts together all the results sent by the NSI systems and presents them in a user-specified format.

We propose a new form of integral which arises from infinite partitions. We use upper and lower series instead of upper and lower Darboux finite sums. We show that every Riemann integrable function, both proper and improper, is integrable in the sense proposed here and both integrals have the same value. We show that the Riemann integral and our integral are equivalent for bounded functions in bounded intervals.

Programmatically generated Data Dictionary document detailing the TxDOT Number of Through Lanes service.

    The PDF contains service metadata and a complete list of data fields.
    For any questions or issues related to the document, please contact the data owner of the service identified in the PDF and Credits of this portal item.


  Related Links
  TxDOT Number of Through Lanes Service URL
  TxDOT Number of Through Lanes Portal Item

The main dataset is a 304 MB file of trajectory data (I90_94_stationary_final.csv) that contains position, speed, and acceleration data for small and large automated (L2) vehicles and non-automated vehicles on a highway in an urban environment. Supporting files include aerial reference images for six distinct data collection “Runs” (I90_94_Stationary_Run_X_ref_image.png, where X equals 1, 2, 3, 4, 5, and 6). Associated centerline files are also provided for each “Run” (I-90-stationary-Run_X-geometry-with-ramps.csv). In each centerline file, x and y coordinates (in meters) marking each lane centerline are provided. The origin point of the reference image is located at the top left corner. Additionally, in each centerline file, an indicator variable is used for each lane to define the following types of road sections: 0=no ramp, 1=on-ramps, 2=off-ramps, and 3=weaving segments. The number attached to each column header is the numerical ID assigned for the specific lane (see “TGSIM – Centerline Data Dictionary – I90_94Stationary.csv” for more details). The dataset defines six northbound lanes using these centerline files. Twelve different numerical IDs are used to define the six northbound lanes (1, 2, 3, 4, 5, 6, 10, 11, 12, 13, 14, and 15) depending on the run. Images that map the lanes of interest to the numerical lane IDs referenced in the trajectory dataset are stored in the folder titled “Annotation on Regions.zip”. Lane IDs are provided in the reference images in red text for each data collection run (I90_94_Stationary_Run_X_ref_image_annotated.jpg, where X equals 1, 2, 3, 4, 5, and 6). This dataset was collected as part of the Third Generation Simulation Data (TGSIM): A Closer Look at the Impacts of Automated Driving Systems on Human Behavior project. During the project, six trajectory datasets capable of characterizing human-automated vehicle interactions under a diverse set of scenarios in highway and city environments were collected and processed. For more information, see the project report found here: https://rosap.ntl.bts.gov/view/dot/74647. This dataset, which is one of the six collected as part of the TGSIM project, contains data collected using the fixed location aerial videography approach with one high-resolution 8K camera mounted on a helicopter hovering over a short segment of I-94 focusing on the merge and diverge points in Chicago, IL. The altitude of the helicopter (approximately 213 meters) enabled the camera to capture 1.3 km of highway driving and a major weaving section in each direction (where I-90 and I-94 diverge in the northbound direction and merge in the southbound direction). The segment has two off-ramps and two on-ramps in the northbound direction. All roads have 88 kph (55 mph) speed limits. The camera captured footage during the evening rush hour (4:00 PM-6:00 PM CT) on a cloudy day. During this period, two SAE Level 2 ADAS-equipped vehicles drove through the segment, entering the northbound direction upstream of the target section, exiting the target section on the right through I-94, and attempting to perform a total of three lane-changing maneuvers (if safe to do so). These vehicles are indicated in the dataset. As part of this dataset, the following files were provided: I90_94_stationary_final.csv contains the numerical data to be used for analysis that includes vehicle level trajectory data at every 0.1 second. Vehicle type, width, and length are provided with instantaneous location, speed, and acceleration data. All distance measurements (width, length, location) were converted from pixels to meters using the following conversion factor: 1 pixel = 0.3-meter conversion. I90_94_Stationary_Run_X_ref_image.png are the aerial reference images that define the geographic region for each run X. I-90-stationary-Run_X-geometry-with-ramps.csv contain the coordinates that define the lane centerlines for each Run X. The "x" and "y" columns represent the horizontal and ve

The 2011 Population and Housing Census marks a milestone in census exercises in Europe. For the first time, European legislation defined in detail a set of harmonised high-quality data from the population and housing censuses conducted in the EU Member States. As a result, the data from the 2011 round of censuses offer exceptional flexibility to cross-tabulate different variables and to provide geographically detailed data.

EU Member States have developed different methods to produce these census data. The national differences reflect the specific national situations in terms of data source availability, as well as the administrative practices and traditions of that country.

The EU census legislation respects this diversity. The Regulation of the European Parliament and of the Council on population and housing censuses (Regulation (EC) No 763/2008) is focussed on output harmonisation rather than input harmonisation. Member States are free to assess for themselves how to conduct their 2011 censuses and which data sources, methods and technology should be applied given the national context. This gives the Member States flexibility, in line with the principles of subsidiarity and efficiency, and with the competences of the statistical institutes in the Member States.

However, certain important conditions must be met in order to achieve the objective of comparability of census data from different Member States and to assess the data quality:

Regulation (EC) No 1201/20092 contains definitions and technical specifications for the census topics (variables) and their breakdowns that are required to achieve Europe-wide comparability.

The specifications are based closely on international recommendations and have been designed to provide the best possible information value. The census topics include geographic, demographic, economic and educational characteristics of persons, international and internal migration characteristics as well as household, family and housing characteristics.

Regulation (EU) No 519/2010 requires the data outputs that Member States transmit to the Eurostat to comply with a defined programme of statistical data (tabulation) and with set rules concerning the replacement of statistical data. The content of the EU census programme serves major policy needs of the European Union. Regionally, there is a strong focus on the NUTS 2 level. The data requirements are adapted to the level of regional detail. The Regulation does not require transmission of any data that the Member States consider to be confidential.

The statistical data must be completed by metadata that will facilitate interpretation of the numerical data, including country-specific definitions plus information on the data sources and on methodological issues. This is necessary in order to achieve the transparency that is a condition for valid interpretation of the data.

Users of output-harmonised census data from the EU Member States need to have detailed information on the quality of the censuses and their results.

Regulation (EU) No 1151/2010) therefore requires transmission of a quality report containing a systematic description of the data sources used for census purposes in the Member States and of the quality of the census results produced from these sources. A comparably structured quality report for all EU Member States will support the exchange of experience from the 2011 round and become a reference for future development of census methodology (EU legislation on the 2011 Population and Housing Censuses - Explanatory Notes ).

In order to ensure proper transmission of the data and metadata and provide user-friendly access to this information, a common technical format is set for transmission for all Member States and for the Commission (Eurostat). The Regulation therefore requires the data to be transmitted in a harmonised structure and in the internationally established SDMX format from every Member State. In order to achieve this harmonised transmission, a new system has been developed – the CENSUS HUB.

The Census Hub is a conceptually new system used for the dissemination of the 2011 Census. It is based on the concept of data sharing, where a group of partners (Eurostat on one hand and National Statistical Institutes on the other) agree to provide access to their data according to standard processes, formats and technologies.

The Census Hub is a readily-accessible system that provided the following functions:

• Data providers (the NSIs) can make data available directly from their systems through a querying system. In parallel,
• Data users browse the hub to define a dataset of interest via the above structural metadata and retrieve the dataset from the NSIs.

From the data management point of view, the hub is based on agreed hypercubes (data-sets in the form of multi-dimensional aggregations). The hypercubes are not sent to the central system. Instead the following process operates:

1. a user defines a dataset through the web interface of the central hub and requests it;
2. the central hub translates the user request in one or more queries and sends them to the related NSIs’ systems;
3. NSIs’ systems process the query and send the result to the central hub in a standard format;
4. the central hub puts together all the results sent by the NSI systems and presents them in a user-specified format.

Objective: Ambulance patient offload time (APOT) also known colloquially as “Wall time” has been described in various jurisdictions but seems to be highly variable. Any attempt to improve APOT requires the use of common definitions and standard methodology to measure the extent of the problem. Methods: An Ambulance Offload Delay Task Force in California developed a set of standard definitions and methodology to measure APOT for transported 9-1-1 patients. It is defined as the time “interval between the arrival of an ambulance at an emergency department and the time that the patient is transferred to an ED gurney, bed, chair or other acceptable location and the ED assumes responsibility for care of the patient.” Local EMS agencies voluntarily reported data according to the standard methodology to the California EMS Authority (State agency). Results: Data were reported for 9-1-1 transports during 2017 from 9 of 33 local EMS Agencies in California that comprise 37 percent of the state population. These represent 830,637 ambulance transports to 126 hospitals. APOT shows significant variation by EMS agency with half of the agencies demonstrating significant delays. Offload times vary markedly by hospital as well as by region. Three-fourths of hospitals detained EMS crews more than one hour, 40% more than two hours, and one-third delayed EMS return to service by more than three hours. Conclusion: This first step to address offload delays in California consists of standardized definitions for data collection to address the significant variability inherent in obtaining data from 33 local agencies, hundreds of EMS provider agencies, and 320 acute care hospital Emergency Departments that receive 9-1-1 ambulance transports. The first year of standardized data collection of ambulance patient offload times revealed significant ambulance patient offload time delays that are not distributed uniformly, resulting in a substantial financial burden for some EMS providers in California.

Field Name Data Type Description

Statefp Number US Census Bureau unique identifier of the state

Countyfp Number US Census Bureau unique identifier of the county

Countynm Text County name

Tractce Number US Census Bureau unique identifier of the census tract

Geoid Number US Census Bureau unique identifier of the state + county + census tract

Aland Number US Census Bureau defined land area of the census tract

Awater Number US Census Bureau defined water area of the census tract

Asqmi Number Area calculated in square miles from the Aland

MSSAid Text ID of the Medical Service Study Area (MSSA) the census tract belongs to

MSSAnm Text Name of the Medical Service Study Area (MSSA) the census tract belongs to

Definition Text Type of MSSA, possible values are urban, rural and frontier.

TotalPovPop Number US Census Bureau total population for whom poverty status is determined of the census tract, taken from the 2020 ACS 5 YR S1701

The Dictionary of Algorithms and Data Structures (DADS) is an online, publicly accessible dictionary of generally useful algorithms, data structures, algorithmic techniques, archetypal problems, and related definitions. In addition to brief definitions, some entries have links to related entries, links to implementations, and additional information. DADS is meant to be a resource for the practicing programmer, although students and researchers may find it a useful starting point. DADS has fundamental entries in areas such as theory, cryptography and compression, graphs, trees, and searching, for instance, Ackermann's function, quick sort, traveling salesman, big O notation, merge sort, AVL tree, hash table, and Byzantine generals. DADS also has index pages that list entries by area and by type. Currently DADS does not include algorithms particular to business data processing, communications, operating systems or distributed algorithms, programming languages, AI, graphics, or numerical analysis.

Trusted Research Environments (TREs) enable analysis of sensitive data under strict security assertions that protect the data with technical organizational and legal measures from (accidentally) being leaked outside the facility. While many TREs exist in Europe, little information is available publicly on the architecture and descriptions of their building blocks & their slight technical variations. To shine light on these problems, we give an overview of existing, publicly described TREs and a bibliography linking to the system description. We further analyze their technical characteristics, especially in their commonalities & variations and provide insight on their data type characteristics and availability. Our literature study shows that 47 TREs worldwide provide access to sensitive data of which two-thirds provide data themselves, predominantly via secure remote access. Statistical offices make available a majority of available sensitive data records included in this study.

Methodology

We performed a literature study covering 47 TREs worldwide using scholarly databases (Scopus, Web of Science, IEEE Xplore, Science Direct), a computer science library (dblp.org), Google and grey literature focusing on retrieving the following source material:

• Peer-reviewed articles where available,
• TRE websites,
• TRE metadata catalogs.

The goal for this literature study is to discover existing TREs, analyze their characteristics and data availability to give an overview on available infrastructure for sensitive data research as many European initiatives have been emerging in recent months.

Technical details

This dataset consists of five comma-separated values (.csv) files describing our inventory:

• countries.csv: Table of countries with columns id (number), name (text) and code (text, in ISO 3166-A3 encoding, optional)
• tres.csv: Table of TREs with columns id (number), name (text), countryid (number, refering to column id of table countries), structureddata (bool, optional), datalevel (one of [1=de-identified, 2=pseudonomized, 3=anonymized], optional), outputcontrol (bool, optional), inceptionyear (date, optional), records (number, optional), datatype (one of [1=claims, 2=linked records]), optional), statistics_office (bool), size (number, optional), source (text, optional), comment (text, optional)
• access.csv: Table of access modes of TREs with columns id (number), suf (bool, optional), physical_visit (bool, optional), external_physical_visit (bool, optional), remote_visit (bool, optional)
• inclusion.csv: Table of included TREs into the literature study with columns id (number), included (bool), exclusion reason (one of [peer review, environment, duplicate], optional), comment (text, optional)
• major_fields.csv: Table of data categorization into the major research fields with columns id (number), life_sciences (bool, optional), physical_sciences (bool, optional), arts_and_humanities (bool, optional), social_sciences (bool, optional).

Additionally, a MariaDB (10.5 or higher) schema definition .sql file is needed, properly modelling the schema for databases:

• schema.sql: Schema definition file to create the tables and views used in the analysis.

The analysis was done through Jupyter Notebook which can be found in our source code repository: https://gitlab.tuwien.ac.at/martin.weise/tres/-/blob/master/analysis.ipynb

The perfection ratio of a number is a concept that is related to perfect numbers and how closely a given number approximates the ideal perfection ratio, which is 2.0.

Perfect Numbers:

A perfect number is a positive integer that is equal to the sum of its proper divisors, excluding the number itself. For example: • 6 is a perfect number because its divisors are 1, 2, and 3, and 1 + 2 + 3 = 6 . • 28 is another perfect number because its divisors are 1, 2, 4, 7, and 14, and 1 + 2 + 4 + 7 + 14 = 28 .

Perfection Ratio:

The perfection ratio of a number n is a measure of how close the sum of its divisors (excluding the number itself) is to the number. It is defined as:

\text{Perfection Ratio} = \frac{\text{Sum of Proper Divisors of } n}{n}

•  If the perfection ratio is 2.0, the number is considered perfect.
•  If the perfection ratio is greater than 2.0, the number is abundant (i.e., the sum of its proper divisors exceeds the number itself).
•  If the perfection ratio is less than 2.0, the number is deficient (i.e., the sum of its proper divisors is less than the number itself).

Examples:

1. Perfect Number Example:
•  For n = 6 :
•  Proper divisors: 1, 2, 3 
•  Sum of proper divisors: 1 + 2 + 3 = 6 
•  Perfection ratio: \frac{6}{6} = 1.0 
•  Since the perfection ratio is 2.0 for a perfect number, we see the idea of perfect numbers where the sum of divisors divides evenly.

1. Near-Perfect Numbers

• Definition: A near-perfect number is a number for which the sum of its proper divisors is close to the number itself but not exactly equal.
• Example: Consider the number 24. Its proper divisors are 1, 2, 3, 4, 6, 8, and 12. The sum is 36, which is larger than 24, making it almost perfect in the sense that the sum of its divisors is significant but not equal to the number.

2. Almost-Perfect Numbers

• Definition: An almost-perfect number is a number where the sum of its proper divisors equals the number minus one.
• Example: The number 16 is an almost-perfect number. Its proper divisors are 1, 2, 4, and 8, which sum to 15 (16 - 1).

3. Abundant Numbers

• Definition: A number is abundant if the sum of its proper divisors is greater than the number itself.
• Example: The number 12 is abundant because its proper divisors (1, 2, 3, 4, and 6) sum to 16, which is greater than 12.

4. Deficient Numbers

• Definition: A number is deficient if the sum of its proper divisors is less than the number itself.
• Example: The number 8 is deficient because its proper divisors (1, 2, and 4) sum to 7, which is less than 8.

5. Semiperfect Numbers

• Definition: A semiperfect number is a number that is equal to the sum of some (or all) of its proper divisors.
• Example: The number 12 is semiperfect because 12 = 6 + 4 + 2 (some of its proper divisors).

Relevance to the Heat Map

• Density Analysis: By analyzing the heat map further, we might observe concentrations at other specific perfection ratios besides 2. These could indicate near-perfect, almost-perfect, abundant, deficient, or semiperfect numbers.
• Patterns and Trends: Identifying where these numbers cluster can help us understand the distribution and frequency of numbers with these properties within your dataset.

Saudi Arabia phone number data is another important collection of phone numbers. These numbers come from trusted sources. We carefully check every number. This means you only get real numbers from reliable places. Furthermore, this data includes source URLs. You can use these URLs to find out where the numbers came from. This adds transparency to the data. If you have questions, you can get help anytime. Support is available 24/7. Moreover, the phone data has an opt-in feature. With customer support always on hand to help, you can feel confident using this data.Saudi Arabia number data is a special collection of phone numbers. Besides, this list includes numbers from people living in Saudi Arabia. Each number in this database has verification for accuracy. If you ever find a number that does not work, there is a replacement guarantee. This means any invalid number gets replaced with a valid one at no extra cost. The data comes from people who have given permission. Thus, this respect for privacy makes it a great tool for businesses. At List to Data, we help you find important phone numbers easily and quickly.

Bangladesh number dataset provides contact information from trusted sources. We only collect phone numbers from reliable sources and define this information. To ensure transparency, we also provide the source URL to show where the information was collected from. In addition, we offer 24/7 support. If you have a question or need help, we’re always here. However, we care about accuracy, so we carefully collect the Bangladesh number dataset from trusted sources. You may rely on this data for business or personal use. With customer support, you’ll never have to wait when you need help or more information. We use opt-in data to respect privacy. This way, we contact only people who want to hear from you. Bangladesh phone data gives you access to contacts in Bangladesh. Here you can filter information by gender, age, and relationship status. This makes it easy to find exactly the people you want to connect with. We define this data by ensuring it follows all GDPR rules to keep it safe and legal. Our system works hard to remove any invalid data so you get only accurate and valid numbers. List to Data is a helpful website for finding important phone numbers quickly. Also, our Bangladesh phone data is suitable for doing business targeting specific groups. You can easily filter your list to focus on specific types of customers. Since we remove invalid data regularly, you don’t have to deal with old or useless numbers. We assure you that all data follows strict GDPR rules, so you can use it without any problems. Bangladesh phone number list is a collection of phone numbers from people in Bangladesh. We define this list by providing 100% correct and valid phone numbers that are ready to use. Also, we offer a replacement guarantee if you ever receive an invalid number. This means you will always have accurate data. We collect phone numbers that we provide based on customer’s permission. Moreover, we work hard to provide the best Bangladesh phone number list for businesses and personal use. We gather data correctly, so you won’t have to worry about getting outdated or incorrect information. Our replacement guarantee means you’ll always have valid numbers, so you can relax and feel confident.

Lebanon Number Data is a list of phone numbers that you can filter in many ways. You can filter by gender, age, or even relationship status. To contact young people, filter the list to show only numbers from that age group. This helps you connect with the right individual quickly. The list also follows GDPR rules, which means it protects people’s privacy. Furthermore, we regularly update the Lebanon Number Data for clarity. It removes invalid numbers, saving time by avoiding outdated contact details. This feature keeps the list fresh and up-to-date and makes your work more efficient. With Lebanon contact data, you can trust accurate, up-to-date details and filter them to meet your needs. Lebanon phone data is a collection of phone numbers that is 100% correct and valid. The companies that provide this data check every number carefully to make sure it works. So, when you use this cellphone data, you don’t have to worry about the wrong numbers. If, for some reason, a number doesn’t work, you get a replacement guarantee. This means, if a number is invalid, they will give you a new dialing number at no extra cost. Moreover, Lebanon phone data comes with all phone number subscribers’ permission. This means the people who own the numbers have agreed to share their information. It’s very important to have this permission because it keeps you out of legal trouble. Using this database without the customer’s permission can be problematic, but this data is safe and secure. Lebanon phone number list is a collection of phone numbers of people living in Lebanon. This list is very helpful for businesses that need to contact people in Lebanon. The information comes from reliable sources, such as government records, websites, and phone service providers. You can even check the URLs where the data came from. This ensures that the phone numbers are accurate. Also, if you need help, 24/7 support is available. Also, the Lebanon phone number list follows the opt-in rule. Number owners know that others use their info, making it safe to use the data. You won’t face any trouble, and it respects people’s privacy. Using the Lebanon contact number list from our List to Data website, you can confidently connect with the right people.

This dataset contains the raw data for our paper "Numerical ferromagnetic resonance experiments in nano-sized elements" published in IEEE Magnetic Letters. It is organized in folders according to the figures in the paper. Each folder contains the experimental and numerical data, together with the MuMax3 definition files and possible scripts used for evaluation.

Numerical phantom data for an MR Fingerprinting reconstruction. Further described in repository and manuscript.

Reporting of Aggregate Case and Death Count data was discontinued on May 11, 2023, with the expiration of the COVID-19 public health emergency declaration. Although these data will continue to be publicly available, this dataset will no longer be updated.

The surveillance case definition for COVID-19, a nationally notifiable disease, was first described in a position statement from the Council for State and Territorial Epidemiologists, which was later revised. However, there is some variation in how jurisdictions implemented these case definitions. More information on how CDC collects COVID-19 case surveillance data can be found at FAQ: COVID-19 Data and Surveillance.

Aggregate Data Collection Process Since the beginning of the COVID-19 pandemic, data were reported from state and local health departments through a robust process with the following steps:

• Aggregate county-level counts were obtained indirectly, via automated overnight web collection, or directly, via a data submission process.
• If more than one official county data source existed, CDC used a comprehensive data selection process comparing each official county data source to retrieve the highest case and death counts, unless otherwise specified by the state.
• A CDC data team reviewed counts for congruency prior to integration and set up alerts to monitor for discrepancies in the data.
• CDC routinely compiled these data and post the finalized information on COVID Data Tracker.
• County level data were aggregated to obtain state- and territory- specific totals.
• Counting of cases and deaths is based on date of report and not on the date of symptom onset. CDC calculates rates in these data by using population estimates provided by the US Census Bureau Population Estimates Program (2019 Vintage).
• COVID-19 aggregate case and death data are organized in a time series that includes cumulative number of cases and deaths as reported by a jurisdiction on a given date. New case and death counts are calculated as the week-to-week change in cumulative counts of cases and deaths reported (i.e., newly reported cases and deaths = cumulative number of cases/deaths reported this week minus the cumulative total reported the prior week.

This process was collaborative, with CDC and jurisdictions working together to ensure the accuracy of COVID-19 case and death numbers. County counts provided the most up-to-date numbers on cases and deaths by report date. Throughout data collection, CDC retrospectively updated counts to correct known data quality issues.

Description This archived public use dataset focuses on the cumulative and weekly case and death rates per 100,000 persons within various sociodemographic factors across all states and their counties. All resulting data are expressed as rates calculated as the number of cases or deaths per 100,000 persons in counties meeting various classification criteria using the US Census Bureau Population Estimates Program (2019 Vintage).

Each county within jurisdictions is classified into multiple categories for each factor. All rates in this dataset are based on classification of counties by the characteristics of their population, not individual-level factors. This applies to each of the available factors observed in this dataset. Specific factors and their corresponding categories are detailed below.

Population-level factors Each unique population factor is detailed below. Please note that the “Classification” column describes each of the 12 factors in the dataset, including a data dictionary describing what each numeric digit means within each classification. The “Category” column uses numeric digits (2-6, depending on the factor) defined in the “Classification” column.

Metro vs. Non-Metro – “Metro_Rural” Metro vs. Non-Metro classification type is an aggregation of the 6 National Center for Health Statistics (NCHS) Urban-Rural classifications, where “Metro” counties include Large Central Metro, Large Fringe Metro, Medium Metro, and Small Metro areas and “Non-Metro” counties include Micropolitan and Non-Core (Rural) areas. 1 – Metro, including “Large Central Metro, Large Fringe Metro, Medium Metro, and Small Metro” areas 2 – Non-Metro, including “Micropolitan, and Non-Core” areas

Urban/rural - “NCHS_Class” Urban/rural classification type is based on the 2013 National Center for Health Statistics Urban-Rural Classification Scheme for Counties. Levels consist of:

1 Large Central Metro
2 Large Fringe Metro 3 Medium Metro 4 Small Metro 5 Micropolitan 6 Non-Core (Rural)

American Community Survey (ACS) data were used to classify counties based on their age, race/ethnicity, household size, poverty level, and health insurance status distributions. Cut points were generated by using tertiles and categorized as High, Moderate, and Low percentages. The classification “Percent non-Hispanic, Native Hawaiian/Pacific Islander” is only available for “Hawaii” due to low numbers in this category for other available locations. This limitation also applies to other race/ethnicity categories within certain jurisdictions, where 0 counties fall into the certain category. The cut points for each ACS category are further detailed below:

Age 65 - “Age65”

1 Low (0-24.4%) 2 Moderate (>24.4%-28.6%) 3 High (>28.6%)

Non-Hispanic, Asian - “NHAA”

1 Low (<=5.7%) 2 Moderate (>5.7%-17.4%) 3 High (>17.4%)

Non-Hispanic, American Indian/Alaskan Native - “NHIA”

1 Low (<=0.7%) 2 Moderate (>0.7%-30.1%) 3 High (>30.1%)

Non-Hispanic, Black - “NHBA”

1 Low (<=2.5%) 2 Moderate (>2.5%-37%) 3 High (>37%)

Hispanic - “HISP”

1 Low (<=18.3%) 2 Moderate (>18.3%-45.5%) 3 High (>45.5%)

Population in Poverty - “Pov”

1 Low (0-12.3%) 2 Moderate (>12.3%-17.3%) 3 High (>17.3%)

Population Uninsured- “Unins”

1 Low (0-7.1%) 2 Moderate (>7.1%-11.4%) 3 High (>11.4%)

Average Household Size - “HH”

1 Low (1-2.4) 2 Moderate (>2.4-2.6) 3 High (>2.6)

Community Vulnerability Index Value - “CCVI” COVID-19 Community Vulnerability Index (CCVI) scores are from Surgo Ventures, which range from 0 to 1, were generated based on tertiles and categorized as:

1 Low Vulnerability (0.0-0.4) 2 Moderate Vulnerability (0.4-0.6) 3 High Vulnerability (0.6-1.0)

Social Vulnerability Index Value – “SVI" Social Vulnerability Index (SVI) scores (vintage 2020), which also range from 0 to 1, are from CDC/ASTDR’s Geospatial Research, Analysis & Service Program. Cut points for CCVI and SVI scores were generated based on tertiles and categorized as:

1 Low Vulnerability (0-0.333) 2 Moderate Vulnerability (0.334-0.666) 3 High Vulnerability (0.667-1)

The 2011 Population and Housing Census marks a milestone in census exercises in Europe. For the first time, European legislation defined in detail a set of harmonised high-quality data from the population and housing censuses conducted in the EU Member States. As a result, the data from the 2011 round of censuses offer exceptional flexibility to cross-tabulate different variables and to provide geographically detailed data.

EU Member States have developed different methods to produce these census data. The national differences reflect the specific national situations in terms of data source availability, as well as the administrative practices and traditions of that country.

The EU census legislation respects this diversity. The Regulation of the European Parliament and of the Council on population and housing censuses (Regulation (EC) No 763/2008) is focussed on output harmonisation rather than input harmonisation. Member States are free to assess for themselves how to conduct their 2011 censuses and which data sources, methods and technology should be applied given the national context. This gives the Member States flexibility, in line with the principles of subsidiarity and efficiency, and with the competences of the statistical institutes in the Member States.

However, certain important conditions must be met in order to achieve the objective of comparability of census data from different Member States and to assess the data quality:

Regulation (EC) No 1201/20092 contains definitions and technical specifications for the census topics (variables) and their breakdowns that are required to achieve Europe-wide comparability.

The specifications are based closely on international recommendations and have been designed to provide the best possible information value. The census topics include geographic, demographic, economic and educational characteristics of persons, international and internal migration characteristics as well as household, family and housing characteristics.

Regulation (EU) No 519/2010 requires the data outputs that Member States transmit to the Eurostat to comply with a defined programme of statistical data (tabulation) and with set rules concerning the replacement of statistical data. The content of the EU census programme serves major policy needs of the European Union. Regionally, there is a strong focus on the NUTS 2 level. The data requirements are adapted to the level of regional detail. The Regulation does not require transmission of any data that the Member States consider to be confidential.

The statistical data must be completed by metadata that will facilitate interpretation of the numerical data, including country-specific definitions plus information on the data sources and on methodological issues. This is necessary in order to achieve the transparency that is a condition for valid interpretation of the data.

Users of output-harmonised census data from the EU Member States need to have detailed information on the quality of the censuses and their results.

Regulation (EU) No 1151/2010) therefore requires transmission of a quality report containing a systematic description of the data sources used for census purposes in the Member States and of the quality of the census results produced from these sources. A comparably structured quality report for all EU Member States will support the exchange of experience from the 2011 round and become a reference for future development of census methodology (EU legislation on the 2011 Population and Housing Censuses - Explanatory Notes ).

In order to ensure proper transmission of the data and metadata and provide user-friendly access to this information, a common technical format is set for transmission for all Member States and for the Commission (Eurostat). The Regulation therefore requires the data to be transmitted in a harmonised structure and in the internationally established SDMX format from every Member State. In order to achieve this harmonised transmission, a new system has been developed – the CENSUS HUB.

The Census Hub is a conceptually new system used for the dissemination of the 2011 Census. It is based on the concept of data sharing, where a group of partners (Eurostat on one hand and National Statistical Institutes on the other) agree to provide access to their data according to standard processes, formats and technologies.

The Census Hub is a readily-accessible system that provided the following functions:

• Data providers (the NSIs) can make data available directly from their systems through a querying system. In parallel,
• Data users browse the hub to define a dataset of interest via the above structural metadata and retrieve the dataset from the NSIs.

From the data management point of view, the hub is based on agreed hypercubes (data-sets in the form of multi-dimensional aggregations). The hypercubes are not sent to the central system. Instead the following process operates:

1. a user defines a dataset through the web interface of the central hub and requests it;
2. the central hub translates the user request in one or more queries and sends them to the related NSIs’ systems;
3. NSIs’ systems process the query and send the result to the central hub in a standard format;
4. the central hub puts together all the results sent by the NSI systems and presents them in a user-specified format.

The number of CYC electric vehicle recharging points in York (updated definition Q4 21/22 to CYC points only)

This paper is concerned with linear time-invariant (LTI) sampled-data systems (by which we mean sampled-data systems with LTI generalised plants and LTI controllers) and studies their H 2 norms from the viewpoint of impulse responses and generalised H 2 norms from the viewpoint of the induced norms from L 2 to L ∞. A new definition of the H 2 norm of LTI sampled-data systems is first introduced through a sort of intermediate standpoint of those for the existing two definitions. We then establish unified treatment of the three definitions of the H 2 norm through a matrix function G(τ) defined on the sampling interval [0, h). This paper next considers the generalised H 2 norms, in which two types of the L ∞ norm of the output are considered as the temporal supremum magnitude under the spatial 2-norm and ∞-norm of a vector-valued function. We further give unified treatment of the generalised H 2 norms through another matrix function F(θ) which is also defined on [0, h). Through a close connection between G(τ) and F(θ), some theoretical relationships between the H 2 and generalised H 2 norms are provided. Furthermore, appropriate extensions associated with the treatment of G(τ) and F(θ) to the closed interval [0, h] are discussed to facilitate numerical computations and comparisons of the H 2 and generalised H 2 norms. Through theoretical and numerical studies, it is shown that the two generalised H 2 norms coincide with neither of the three H 2 norms of LTI sampled-data systems even though all the five definitions coincide with each other when single-output continuous-time LTI systems are considered as a special class of LTI sampled-data systems. To summarise, this paper clarifies that the five control performance measures are mutually related with each other but they are also intrinsically different from each other.