| Date: | 2002-08-13 13:13:00 | |
| Sender: | Wolfgang Bosch & Wolfgang Seemueller (EDC) <Eurolas Data Center <edc@dgfi.badw-muenchen.de>> | |
| Subject: | [SLR-Mail] No. 967: Onsite normal points from 2-wavelength laser systems | |
| Author: | Wolfgang Bosch | |
| Content: | ******************************************************************************** SLR Electronic Mail 2002-08-13 13:13:00 UTC Message No. 967 ******************************************************************************** Author: Wolfgang Bosch & Wolfgang Seemueller (EDC) Subject: Onsite normal points from 2-wavelength laser systems Subject: Onsite normal points from 2-wavelength laser systems Dear Laser-Mafia! We would like to announce that since Friday, 09th of August, about 15:00 UTC EDC has modified its procedures to handle onsite normal point data for 2-wavelength laser systems. Up to this time passes were identified only by satellite-id, site, date and start time (considering only the seconds modulo 100). From now on we distinguish also with respect to the laser wavelength such that nearly coinciding passes with a second wavelength are no more rejected as ”duplicated” data. In addition we also use the data release field (column 48 of the 1997 data format) as a pass identifier. It seems that only very few site set this flag if they provide an update of the normal points for a pass already delivered. It is very difficult - if not impossible - to identify such updates, if the release flag is not set, because an update may have (nearly) the same start time. We kindly ask the sites to set this release flag properly. An unattended, nearly automatic handling of data with hourly or even shorter redistribution is not possible if the format is not kept! The new EDC-procedure includes also additional data integrity checks: a) number of digits in data record == 54 ? b) seconds < 86400 ? c) surface pressure within < 600 , 1100 > hPa ? d) surface temperature within < 200 , 340 > Kelvin ? e) humidity between < 0 , 100 > percent ? f) any change of release within the pass ? g) is checksum correct or set to ´00´ ? Following this new procedure, data like the following does not pass the validation (it violates checks a), c) and d)): 8606101000221824810153200007328200000005205400021910121 660579115350018216726585000170005558-010006200080000047 660792835970017824494172000200105558-010006200130000050 661342536090017038292816000136505558-010006200140000044 Sometimes we also find non-digit characters in the header record: 860610100106708024195320-000192800000000895463201190381 794490131794014168674157000012507949296300901630000084 794846178817014184705871000011607949296200901470000093 We kindly ask the sites to follow the format definition! A fast and reliable Service requires to keep a few rules! Identification and validation of QL-data at EDC is based on a small C-program. Up to now there is only a german documentation. We will describe the usage in english and place the C-code on the ftp-server of EDC. The program could be used to check the normal point data - before transmission. Best regards Wolfgang Bosch From: Eurolas Data Center ******************************************************************************** |