Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
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><br />
MED-SOC-RS-001_1<br />
<strong>System</strong> <strong>Requirements</strong> <strong>Document</strong><br />
Issue F<br />
<strong>Data</strong> Set Description (MMR_DSD) record within the GHRSST-PP MMR for each data<br />
stream.<br />
SR.ING.0040/I Ingestion of data streams shall rename the data file by prefixing the<br />
RDAC identification code to the filename, as defined in Appendix 2 of [RD-3].<br />
Comment: A time stamp may be used to avoid ambiguity in original naming.<br />
SR.ING.0050/I The MMR implementation and delivery of MMR_DSD shall be performed<br />
as defined in GDS appendix A6.<br />
SR.ING.0060/I The data file integrity should be evaluated by identifying a data delivery/a<br />
data format problem.<br />
SR.ING.0070/I The ingestion operation shall compute pixel measurement time.<br />
SR.ING.0080/I The time of the earliest SST measurement within this data set should be<br />
coded as a continuous time coordinate specified from 00:00:00 UTC January 1, 1981<br />
(start of the useful AVHRR SST data record).<br />
SR.ING.0090/I The time of SST measurement should be coded as the deviation in<br />
minutes from the time of the earliest SST measurement.<br />
SR.ING.0100/I In case of bad data file integrity, a dialog with the data provider shall be<br />
initiated, by sending error message, to establish a solution as soon as possible.<br />
SR.ING.0110/I Ingestion must evaluate the timeliness of each data file.<br />
SR.ING.0120/I The MMR_DSD records contains the data provider contact details and<br />
point of contact for error reports.<br />
SR.ING.0130/I L2 data will be extracted over the EURDAC and MEDSPIRATION UHR<br />
areas, as appropriate.<br />
3.2.3 Quality Check<br />
SR.QLC.0010/I Generation of L2P shall determine if SST data are suitable for further use<br />
in the GDS. If not inform the data provider and generate an error message for the<br />
GHRSST-PP ERRLOG explaining why these data have not been used in the GDS.<br />
SR.QLC.0020/I A configuration file, that will be revised as required, is used to store all<br />
QC parameter limits and thresholds (see SR.EXT.ING.0040).<br />
© 2004 SOC Page 32 of 193