SCWG Call 2015/03/19 SZ,PB,EY,PH,PL,DN,AW,RH - Request #147 (P. Bodin): Adding a geographic type attribute. -------------------------- * The group approved the request in the following form: - A new field 'gtype' describing the geographic type will be added to the Origin table. The allowed values for this field will be L/R/T respectively for Local/Regional/Teleseism. - The constraint on the field Event.etype will be modified; the 3 current event types 'le','re' & 'ts' will be merged into one single value 'eq'. * The following applications are modifying the Origin table and will need to be updated accordingly: + Event Coordinator: Currently assigns 'le' for 'etype' to all newly created events. Will assign 'eq' to all events and use polygons to set 'gtype'. + Trigger coordinator: Currently assigns 'st' for 'etype'; that won't change. Possibly assign NULL for 'gtype' field. + Moment Tensor code: Will copy over 'gtype' value from input or preferred origin. + Jiggle: Menu for event types need to be modified. Action will update both 'etype' & 'gtype' fields. Also for quarry blasts, jiggle will need to use polygons to find out value of 'gtype'. + Double difference code: For both the base catalog & the real-time catalog, the value for 'gtype' will be copied from its value for the preferred (hypoinverse) origin. * The following applications are querying the Origin table and might need to be updated: + Alarm modules? No changes necessary. + dbselect? Possibly change options and output formats. + qml? Yes. Mapping from 'eq' to QuakeMl equivalent. + stp? Yes. + catalog search? Probably. + Web services? Maybe. FDSN Event uses dbselect though.