The dataset Sample Clauses

The dataset a. The dataset to which the licence relates consists of all the databases, documentation and other data files and documents that form part of this dataset, which have been transferred by the Depositor.
AutoNDA by SimpleDocs
The dataset. The systematic analysis used information from a comprehensive homogeneous segment dataset developed during previous research (van Xxxxxxxxx). Segments located within a rural area (i.e. outside urban boundaries as defined by FHWA) with one through lane per direction were included in the systematic assessment. The original homogeneous data were assembled using geoprocessing in ArcGIS 9.0 and dataset manipulation in the SAS 9.1 environment. The researchers used the ArmCalc module to combine data from different years. The ArmCalc module is necessary since highway milepost may change from year to year, thus requiring changes in the linear referencing system (LRS). The WSDOT Traffic Data Office (TDO) supplied the ArmCalc module. The data development process also accounted for modifications of the highway system over the analysis years. 1997 and 1998 were excluded because complete collision data are not available for these years. Data from 2006 was not included in the report because traffic volumes were not available at the time of completion of the project report. Annual averages were generally calculated for the 1999 to 2005 period. Table 1 provides the distribution of segment lengths in the homogeneous dataset for two-lane rural highways. Table 1: Data Elements in Analysis Dataset DATASET ELEMENTS YEARS SOURCE Traffic volumes 1999 - 2005 WSDOT TDO TRIPS Dataset Geometric features: horizontal curves, vertical curves, grades 1999 – 2005 WSDOT TDO TRIPS Dataset Intersection locations and characteristics 1999 – 2005 WSDOT TDO TRIPS Dataset Lane configuration (lane width, shoulder width, special use lanes, auxiliary lanes) 1999 - 2005 WSDOT TDO TRIPS Dataset Motor vehicle collision data 1993-1996, 1999 - 2005 WSDOT TDO TRIPS Dataset Washington State Route Network for 2005-12-31 2005 WSDOT GIS layers as developed and maintained by the Office of Information Technology at WSDOT (xxxx://xxx.xxxxx.xx.xxx/mapsdata/geodatac atalog/default.htm). Urban boundaries 1999 - 2005 Pavement characteristics 1999 – 2005 The WSDOT Pavement Management System (WSPMS) that contains pavement specific data Annual weather characteristics 1993-1996, 1999 - 2005 Daily weather data from NOAA, providing information regarding rainfall, snow, and observed weather. Socio-demographic characteristics 2000 and, 2006 US Census data for 2000 by block group, using data from both the Summary File 1 and 3 datasets (US Census 2000) K12 school locations 2005 Office of Superintendent of Public Instruction i...
The dataset. Data from all 114 patients was used in tests between demographic factors, treatment groups, and treated versus fellow eyes. Of the 114, 8 patients had EUA’s at the 1 year of age follow up visit where keratometry measurements were not made. Additionally, 1 patient did not have an EUA at the 1 year visit. This left 105 patients with keratometry measurements at 1 year of age. All comparisons and tests for demographic factors, treatment groups, and treated versus fellow eyes at 1 year of age, and the change between baseline and 1 year of age, were based on these 105 patients. Of those 40 patients who had surgeries reviewed by Xx. Xxxxxxxxx, 4 did not have keratometry measurements at 1 year of age; the comparisons and the change variables for all surgical factors excepting treatment were thus among 36 patients.

Related to The dataset

  • Subscriber Data Subscriber will timely supply Netgateway, in a form acceptable to Netgateway, with all data necessary for Netgateway to perform the ongoing services to be provided hereunder. It is the sole responsibility of Subscriber to insure the completeness and accuracy of such data.

  • Invoice Data The Contractor shall report invoice data from each paid or remitted invoice within 30 calendar days after the end of the reporting quarter, including the invoice data on task orders issued through the GSA AAS Business System Portal. (Note: Whatever method the Contractor chooses (e.g., “each paid” or “remitted”) the Contractor must be consistent in their reporting method throughout the term of the OASIS Contract). If no Invoice Data was received during a required reporting period for a specific task order, the Contractor shall report in the “Zero Invoice Data” screen located in the CPRM system for that particular task order. Regardless of contract type, the Contractor shall report the following into the CPRM:

  • Sensitive data Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.

  • Client Data The Subrecipient shall maintain client data demonstrating client eligibility for services provided. Such data shall include, but not be limited to, client name, address, income level or other basis for determining eligibility, and description of service provided. Such information shall be made available to Grantee monitors or their designees for review upon request.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • PAYEE DATA RECORD FORM STD 204: This form must be completed by all contractors that are not another state agency or other governmental entity.

Time is Money Join Law Insider Premium to draft better contracts faster.