The dataset Sample Clauses

The "The dataset" clause defines what constitutes the dataset being referenced in the agreement. It typically specifies the scope, content, and format of the data, such as whether it includes raw data, processed data, or metadata, and may outline any exclusions or limitations. By clearly identifying the dataset, this clause ensures both parties have a mutual understanding of what data is covered, reducing ambiguity and potential disputes over data access or usage.
The dataset a. The dataset to which the license 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. b. The Depositor declares that the dataset corresponds to the specification provided. c. The Depositor declares that the dataset contains no data or other elements that are, either in themselves or in the event of their publication, contrary to Dutch law. d. The Depositor indemnifies the Repository against all claims by third parties relating to the content of the dataset. e. The Depositor will supply the dataset by means of a method and medium deemed acceptable by the Repository.
View SourceView Similar (4)
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. b. The Depositor declares that the dataset corresponds to the specification provided. c. The Depositor declares that the dataset contains no data or other elements that are contrary to Dutch law. d. The Depositor will supply the dataset by means of a method and medium deemed acceptable by the Repository.
View SourceView Similar (2)
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 ▇▇. ▇▇▇▇▇▇▇▇▇, 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.
View Source
The dataset. The systematic analysis used information from a comprehensive homogeneous segment dataset developed during previous research (van ▇▇▇▇▇▇▇▇▇). 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. 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 (▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇.▇▇▇/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 in Washington.(2005) Locations with liquor licenses 2006 Washington State ...
View Source

Related to The dataset

  • Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.

  • 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.

  • 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.

  • Site Data (i) The Contractor shall be deemed to have inspected and examined the Site and its surroundings and to have satisfied himself before entering into the Agreement in all material respects including but not limited to: (a) the form and nature of the Site (including, inter-alia, the surface and sub- surface conditions and geo-technical factors); (b) the hydrological and climatic conditions; (c) the extent and nature of the works already completed and Materials necessary for the execution and completion of the Works and the remedying of any defects that includes already executed part also. (d) the suitability and the adequacy of the Site for the execution of the Works; (e) the means of access to the Site and the accommodation the Contractor may require; (f) arranging permits as required as per [.] of the Agreement. (g) the requirements of operation and maintenance; and (h) all other factors and circumstances affecting the Contractor's rights and obligations under the Agreement, the Contract Price and Time for Completion.

  • 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.