30.01.2015 Views

Medspiration – System Requirements Document - Data User Element

Medspiration – System Requirements Document - Data User Element

Medspiration – System Requirements Document - Data User Element

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Medspiration</strong> MED-SOC-RS-001_1<br />

<strong>System</strong> <strong>Requirements</strong> <strong>Document</strong> Issue F<br />

Page Table, fig. Reference ID Text from reference documents<br />

SR entry<br />

specification set out in Appendix A4.1 (WP-ID3.1.2).<br />

69 WP3-029 in situ observations may be matched to SST measurements derived from different satellite sensors and are thus used<br />

MDB.0250<br />

more than once in the system providing consistency across GHRSST-PP data products<br />

69 WP3-030 only 1 instance of each in situ observation (the nearest in space and time to the satellite data) is used to define a matchup<br />

MDB.0260<br />

record<br />

70 WP3-031 SSES are published on the GHRSST-PP web site as part of the GHRSST-PP <strong>User</strong> Information Service (UIS) and all<br />

NASR<br />

RDAC/GDAC are informed of the latest issue of SSES for use in the generation of GHRSST-PP L2P data products<br />

WP-ID3.1 Generation of Match Up <strong>Data</strong>base (MDB) records<br />

70 WP3-032 The GHRSST-PP MDB system is a relational database containing all GHRSST-PP MDB data records. The GHRSST-PP<br />

NASR<br />

MDB will be implemented and maintained at the JPL PO.DAAC using the MySQL /database system<br />

70 WP3-033 MDB data records should be produced by RDAC and ingested at the MDB in near real time (1-7 days[1]) in order for SSES<br />

MDB.0030<br />

to be generated in a timely manner. [1] Note that the MDB will be used extensively by the GHRSST-PP reanalysis project<br />

so that the time constraints specified here should be interpreted in the broadest possible sense; if a match-up data record<br />

has been established, it should be delivered to the MDB system regardless of the timeliness of the data.<br />

70 WP3-034 Timeliness of MDB data is related to the availability of in situ data. Time penalties are incurred because data centres<br />

MDB.0030<br />

careful quality control and validate in situ measurements<br />

70 WP3-035 Collaboration with operational data centres that are well practiced in the QC of in situ observations must be established<br />

and maintained by RDAC and GDAC especially in the case of data that are made available on the GTS<br />

70 WP3-036 The GHRSST-PP expects to work closely with the CORIOLIS data centre (France), the Japanese Meteorological Agency<br />

MDB.0130<br />

MDB.0110<br />

MDB.0110<br />

(JMA), and the MEDS data centre (Canada) amongst others as described in Appendix A3.4.5 and Appendix A3.4.6<br />

70 WP3-037 the MDB is open to all in situ observations that are deemed of sufficient quality by the RDAC and GDAC teams MDB.0120<br />

MDB.0110<br />

© 2004 SOC Page 161 of 193

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!