Currently, Location longitudes are required to be between ±180. This is generally ok as there is very little continent, and hence hazard of concern, crossing the int'l date line. However the Aleutians do cross it and the NSHMP Alaska grid extends to 200 (or -160). This needs to be addressed because geometric operations on regions are essential (e.g. contains()). Possible solutions:

• Conversion of values in individual applications based on some user preference
• Split regions that cross ±180 in two
• Adopt a garbage in garbage out policy. Allow longitude values between -180 and 360 and assume user/programmer knows what they're doing.

The 3rd is the simplest to implement and would come with the caveats that a user use the correct distance calculation algorithms if they are going to mix and match.

Comments?

The CyberShake? curve plotter should be able to take multiple run IDs, comma separated, in the --compare-to argument.