Medspiration – System Requirements Document - Data User Element

Medspiration MED-SOC-RS-001_1
System Requirements Document Issue F
Page Table, fig. Reference ID Text from reference documents
44 WP1-065 GDS ERROR message:where is defined in Appendix A2.1 and
is defined in Appendix A7. The format of ERRLOG messages is provided in Appendix A7.
SR entry
EXT.CTR.0520
44 WP-ID1.4 Rename data file to GHRSST-PP GDS specification.
44 WP1-066 In order to identify a data file that has been admitted into the GDS system by an RDAC or GDAC, the GDS recommends
ING.0040
that each data file should be renamed by prefixing the processing centre code to the original filename according to the
following filename specification:
44 WP1-067 -GDS- ING.0040
44 WP1-068 where is defined in Appendix A2 Table A2.1. In the example above, JAP-GDS-20010507tm
ING.0040
would refer to a REMSS TMI bmaps_03 data file (20010507tm) that has been checked and admitted into the GDS at the
Japanese RDAC (JAP).
44 WP1-069 Renaming a data file in this way provides a simple method to identify data that have passed the initial data delivery tests
NASR
from those that have not while preserving the original data product filename. Although data files within this part of the GDS
may have no visibility beyond the RDAC processor itself, the purpose of renaming files to a common specification is to
facilitate error analysis and problem solving. If problems are found at a higher level within the GDS processing chain,
accepted GDS files may be differentiated from other data files and traced back to RDAC/GDAC centres by simply noting
the filename.
GDS-WP-ID2
WP-ID2: Generation of GHRSST-PP Level-2 Pre-processed Data files (L2P).
45 To process input data files and produce GHRSST-PP L2P SST data files in a timely manner.
45 Objectives:
45 WP2-001 1. To extract confidence data provided with each input SST data file. QLC.0050
© 2004 SOC Page 132 of 193