Changes between Initial Version and Version 1 of Location_Code_Policy

01/19/12 18:21:48 (10 years ago)



  • Location_Code_Policy

    v1 v1  
     3Earthworm Location Code Policy                           2004/03/05:LDD 
     6These rules are based on the SEED and CISN conventions referenced below,  
     7with a nod to current practices and software logic simplification. 
     91. We will follow the SEED convention of allowed characters 
     10   (A-Z, 0-9, space).  In apparent contradiction to the previous  
     11   statement, we will use the character '-' to represent 'space'  
     12   in all Earthworm I/O. Just remember to think 'space' when you 
     13   see '-'. Lower case alphanumerics are not permitted. 
     152. The location code will always contain 2 characters, either 
     16   two alpha-numeric characters or two spaces ('--'). The use  
     17   of a single space (or '-') adjacent to an alpha-numeric is not  
     18   permitted.  
     203. The default location code in SEED is "  " (space-space). 
     21   We'll call this the "blank" location code.  While there are no rules  
     22   on how EW software should represent a blank location code for its own   
     23   internal manipulations, all software must obey the following rules   
     24   for all of its Input/Output, including its log files: 
     25   a. For all ASCII I/O, both column-oriented and whitespace-delimited, 
     26      a blank location code will be written as "--".  We recognize that  
     27      "  " could be interpreted properly by software in column-oriented 
     28      ASCII, but we feel that it is easier for humans reading the data 
     29      to have a single convention for all ASCII information. 
     30      When parsing any ASCII input, software will interpret "-" or "--"  
     31      as the blank location code. 
     32   b. In binary I/O, currently only the Earthworm tracedata messages, 
     33      the blank location code will also be represented by "--". 
     34   c. In the Earthworm DBMS, the blank location code will be represented 
     35      as the string "--". 
     374. When Earthworm data is converted to SEED format, all blank location 
     38   codes will be converted from "--" to "  " (space-space). 
     405. Software should *never* assume that the location code has any 
     41   meaning. It should be used exclusively as a tie-breaker when 
     42   multiple channels of data have the same SCN.  This will allow 
     43   allow each network to use their own convention for assigning  
     44   the location code and to process data from another network whose 
     45   convention is different. 
     48Current Practices 
     50In the EW database, blank location codes are stored as NULLs. Queries 
     51for a blank location code must have extra logic to check the DBMS for a  
     52blank string or a NULL field.  When we switch to storing blank location  
     53codes as "--" everywhere, no extra logic would be required for  
     56In the NCEDC database, blank location codes are stored as "space-space". 
     58In SEED, fields are blank padded, so a blank or NULL location code is  
     59always stored as "space-space".  IRIS DMC software maps a "-" in a  
     60data request to a "space" in the location code.  Therefore, if data  
     61were stored with a "-" in the location code, there would be no way to  
     62request it explicitly.  Therefore, when Earthworm data is converted to 
     63SEED format, we must revert to "space-space". 
     68SEED convention: 
     71CISN convention: