Public Data Repository Sample Clauses

Public Data Repository. After the publication of the scientific publication presenting the analyses methods to be developed in URBANFLUXES, the respective data and products become available with free access through the URBANFLUXES in the Public Data Repository (Figure 11). Any potential user of these datasets will have free access, following simple registration instructions given in the respective web-page. The user fills in a dedicated form with minimum information (name, email, etc.), similar to which several projects use (JRC, UN, EEA, etc.) and then grand access to these datasets. The users have the possibility to access, mine, exploit, reproduce and disseminate (free of charge) the data, including associated metadata, needed to validate the results presented in scientific publications. As indicated in the respective metadata field of all URBANFLUXES datasets, the data are protected by Intellectual Property Rights. Thus, the users are obliged to refer to the data source (URBANFLUXES: grant agreement No 637519) when reproducing or using the data in articles or reports. By following this procedure, the URBANFLUXES Consortium will monitor the diffusion of these products, as well as the reuse in other projects, publications, supporting in this way new scientific collaborations. There have been 120 subscriptions to the URBANFLUXES web-site, gaining access to the public data repository during the lifetime of the project. Most of the subscribers are related to the scientific community and only few so far are form public administrations and private companies. Figure 11. The Data Repository section at the URBANLUXES website.
Sample 1
AutoNDA by SimpleDocs

Related to Public Data Repository

  • Electronic Data Interchange (EDI This standard establishes the data contents of the Invoice Transaction Set (810) for use within the context of an EDI environment. This transaction set can be used for invoicing via the AN for catalog and non-catalog goods and services.

  • Electronic Data Interchange If both Parties elect to facilitate business activities hereunder by electronically sending and receiving data in agreed formats (also referred to as Electronic Data Interchange or “EDI”) in substitution for conventional paper-based documents, the terms and conditions of this Agreement shall apply to such EDI activities.

  • EDI - Electronic Data Interchange The exchange of business data in a standardized format between business computer systems.

  • Electronic Data 7.1.1 The parties recognize that Contract Documents, including drawings, specifications and three-dimensional modeling (such as Building Information Models) and other Work Product may be transmitted among Owner, Design-Builder and others in electronic media as an alternative to paper hard copies (collectively “Electronic Data”).

  • ETU Picnic Day In accordance with picnic day provision the Company shall require from an employee proof of picnic day attendance, ie ETU ticket purchase before payment will be made for the day. A ticket purchased in relation to an alternative union picnic day is not sufficient for the purposes of payment. Where possible no work shall be scheduled on the first Monday of December each year which is the Annual Building Industry Picnic Day.

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.

  • Responsibility for Electronic Data The Student is solely responsible for any data stored on the Computer. It is the sole responsibility of the Student to backup such data as necessary.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • Medical Records Medical records relating to Trial Subjects that are not submitted to Sponsor may include some of the same information as is included in Trial Data; however, Sponsor makes no claim of ownership to those documents or the information they contain. c.

  • Joint Funded Project with the Ohio Department of Transportation In the event that the Recipient does not have contracting authority over project engineering, construction, or right-of- way, the Recipient and the OPWC hereby assign certain responsibilities to the Ohio Department of Transportation, an authorized representative of the State of Ohio. Notwithstanding Sections IV, VI.A., VI.B., VI.C., and VII of the Project Agreement, Recipient hereby acknowledges that upon notification by the Ohio Department of Transportation, all payments for eligible project costs will be disbursed by the Grantor directly to the Ohio Department of Transportation. A Memorandum of Funds issued by the Ohio Department of Transportation shall be used to certify the estimated project costs. Upon receipt of a Memorandum of Funds from the Ohio Department of Transportation, the OPWC shall transfer funds directly to the Ohio Department of Transportation via an Intra-State Transfer Voucher. The amount or amounts transferred shall be determined by applying the Participation Percentages defined in Appendix D to those eligible project costs within the Memorandum of Funds. In the event that the Project Scope is for right-of-way only, notwithstanding Appendix D, the OPWC shall pay for 100% of the right-of-way costs not to exceed the total financial assistance provided in Appendix C. APPENDIX D LOCAL SUBDIVISION CONTRIBUTION, PROJECT FINANCING AND EXPENSES SCHEME AND DISBURSEMENT RATIO

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