Data identified by INTAROS Sample Clauses

Data identified by INTAROS. In the H2020 project INTAROS, a deliverable was made on “Report on present observing capacities and gaps: ocean and sea ice observing system” (INTAROS,2018). An Arctic data survey was carried out in 2017, mainly based on current capacities in INTAROS partners. The survey was made for a much wider purpose than Copernicus Service. Although only monitoring activities with the consortium partners were evaluated, significant amounts of physical and biogeochemical observations have been identified, which potentially can be used for CMEMS applications. It should be noted that these extra amounts of data covering mainly Nordic Seas and entire Barents Sea. Areas with less sampling are the Greenlandic and Icelandic offshore and open waters. INTAROS has got funding to perform some in situ observations – some systems were deployed in 2017 but most during summer 2018: • Moorings in Young Sound data in xxxx://xxxx.x-x-x.xx • Moorings and CTD in Coastal Greenland – data in xxxx://xxxx.x-x-x.xx • Ecological monitoring in Young Sound – data in xxx.xxxxxx.xxx • Moorings north of Svalbard in 2017 and 7 moorings in 2018 – French data in xxx.xxxxxx.xxx, polish data in IOPAN but they do not have a data management system (they consider PANGAEA to get a doi). During cruises other data are collected CTD, biogeochemical variables, turbulence • Acidification mooring in the Fram Strait – data in PANGAEA • Carbonate chemistry in Kongsfjorden at Svalbard • Underwater acoustics in Kongsfjorden • Ice-tethered platforms in Central Arctic – unfortunately only worked for one month. • Snow and Ice mass balance Arrays (SIMBA) central Arctic • Glider lines along Atlantic Water Pathway in Fram Strait – data in xxx.xxxxxx.xxx • Ferrybox lines in Barents Sea – available on NIVA ftp server • BioArgo floats in Baffin Bay – data in Coriolis More details are given from the INTAROS report D2.1 (INTAROS, 2018), summarized as below:
Sample 1
AutoNDA by SimpleDocs

Related to Data identified by INTAROS

  • Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.

  • If Identified If the HSP is Identified it will:

  • Why We Collect Information and For How Long We are collecting your data for several reasons: · To better understand your needs and provide you with the services you have requested; · To fulfill our legitimate interest in improving our services and products; · To send you promotional emails containing information we think you may like when we have your consent to do so; · To contact you to fill out surveys or participate in other types of market research, when we have your consent to do so; · To customize our website according to your online behavior and personal preferences. The data we collect from you will be stored for no longer than necessary. The length of time we retain said information will be determined based upon the following criteria: the length of time your personal information remains relevant; the length of time it is reasonable to keep records to demonstrate that we have fulfilled our duties and obligations; any limitation periods within which claims might be made; any retention periods prescribed by law or recommended by regulators, professional bodies or associations; the type of contract we have with you, the existence of your consent, and our legitimate interest in keeping such information as stated in this Policy.

  • Act Identifier Title Shoulder note Iron Ore (Robe River) Agreement Xxx 0000 First Schedule Iron Ore (Robe River) Agreement Second Schedule First variation agreement Third Schedule Second variation agreement [s. 3B] Fourth Schedule Third variation agreement [s. 2] Fifth Schedule Fourth variation agreement Sixth Schedule Fifth variation agreement

  • Review Procedures for Identifying Entity Accounts With Respect to Which Reporting Is Required For Preexisting Entity Accounts described in paragraph B of this section, the Reporting Finnish Financial Institution must apply the following review procedures to determine whether the account is held by one or more Specified U.S. Persons, by Passive NFFEs with one or more Controlling Persons who are U.S. citizens or residents, or by Nonparticipating Financial Institutions:

  • Data Integrity Contractor shall implement policies and procedures reasonably intended to ensure that Protected Health Information and Personally Identifiable Information in its possession is complete, accurate, and current, to the extent necessary for the Contractor’s intended purposes, and has not been altered or destroyed in an unauthorized manner.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Client identification 9.1. The Company has the right to require the Client to confirm his/her registration information specified when opening a trading account. To do so, the Company may ask the Client at its own discretion and at any time to provide a notarized electronic copy of his/her identification document, bank statement or public utilities xxxx as a proof of residence. In particular cases, the Company may ask the Client to provide a photo of him/her holding his/her ID near his/her face. The detailed client identification requirements are set out in the “AML policies” section on the Company’s official site.

  • User Identification 6.2.5.1 Access to each Party’s corporate resources will be based on identifying and authenticating individual users in order to maintain clear and personal accountability for each user’s actions.

  • DATA PROTECTION AND DATA PROCESSING 6.1 The Company and the Client acknowledge that for the purposes of the Data Protection Xxx 0000 and the GDPR, that the Client and the Company shall be considered separate data controllers in relation to the provision of the Services, save and except that in the case of lead generation services, the Client shall be the data controller and the Company shall be the data processor.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!