SCWG Call 2015/03/13 SZ,PB,EY,PH,PL,VK,DN,AW,RH Next Call: 2015/03/19 at 2PM - Request #147 (P. Bodin): Adding a geographic type attribute. -------------------------- The current field Event.etype encompasses both the physical process involved and the geographic type of an event but only for earthquakes (le,re,ts). PNSN would like the ability to extend this capability to all the other event types and propose to add a new field representing the geographic type of a given event (local,regional,teleseism). Another implementation brought up by the group is to reuse the same Event.etype field and extend its use by prefixing all event types with a possible geographic type. For example: leq (local earthquake), req (regional earthquake), rex (regional explosion), ... The group voted in favor of storing the geographic type into a different field rather than reusing the Event.etype field. One implication resulting from this is that the 3 current event types 'le','re' & 'ts' will have to be merged into one single value 'eq'. The group could not agree on where this new field 'gtype' (L,R,T) should be stored; in the event or in the origin table. It mostly depends on how the RSN's are going to use that field. Currently, all events are declared as 'le' or 'st' in the real-time system. Humans later overwrite them either with Jiggle or the duty review page. If we store the geographic type attribute in the Event table, presumably the same procedure could be kept. Storing the gtype field in the Origin table provides us with a history over time. On the other hand, it requires any application that creates a new Origin row to fetch this value from somewhere; possibly the previous origin? What if the previous origin is of a different type (DD)? If stored in the Origin table, automatic rules based on polygons could be used to set the geographic type attribute.