Most messages currently sent using EIDS are converted automatically into products. CUBE messages are automatically converted to EQXML when sent using EIDS. This page currently describes the mapping from EQXML to product. It will eventually contain the mapping from Quakeml to product.
If the first Origin element in the message has isPreferredFlag=true, it will be converted to a product:
<Origin> … <isPreferredFlag>true</isPreferredFlag> </Origin>
If the Origin also contains Phase elements, it is converted to a
phase-data
type product. Otherwise, it is converted to an origin
type product. The product source is Event/DataSource
(e.g.
"nc"), and the product code is Event/DataSource+Event/EventID
(e.g. "nc12345678").
CUBE "E " messages converted to EQXML contain one origin, with
isPreferredFlag=true, and so are converted to an origin
product.
ProductLinks that use a known Code (see below) are automatically
converted into general-link
, scitech-link
, and
impact-link
type products.
The product source is Event/DataSource
, and the
product code is Event/DataSource+Event/EventID+"-"+ProductLink/Code
lowercased (E.g. nc12345678-focalmech1).
CUBE "LI" messages converted to EQXML use addon type for Code, and "LinkURL" for TypeKey.
To be automatically converted to a product, the Code must start with one of these values, case-insensitively.
Sometimes you may want to send multiple links of the same type, but to be considered a separate product, the addon code must be unique. To do this append a sequence number or other unique id:
NOTE: Products sent directly to PDL are not currently delivered to EIDS clients.
Moment tensors are converted into moment-tensor
type
products.