Jeremy Fee

I have the same issue, neither the `https` or `secure` options seem to have any effect, but found a work around by using this in your proxy config: ``` protocol:...

You can probably handle this by normalizing the coordinates around the epicenter, so longitudes are consistent. If event longitude is +, normalize all values to be [0,360); if event longitude...

Looking in the event feed: https://earthquake.usgs.gov/fdsnws/event/1/query?eventid=us1000778i&format=geojson The shakemap product reports: ``` "maximum-longitude": "-179.65 "minimum-longitude": "165.633", ``` The image overlay is stretched and reversed because of this. Daniel can probably update...

The main problem is when we use the data in leaflet. It's longitudes continue, but it only wraps at 360 instead of 180. Using coordinates that are close to the...

yes, because those are both close to zero.

@dslosky-usgs : this could be a good issue for the relative time component. I think a shared component for times would be useful. This should take a time input, and...

Currently, text products need to include their own headers when necessary. I agree this isn't ideal. For example, general-text products often include an h2 Tectonic Summary header. At some point,...

For the implementors: This is similar to how focal-mechanism products are supposed to be handled. When there are multiple focal-mechanism products from the same source; they are supposed to be...

Akamai shows this for 503 Service Unavailable responses, we can also configure it to be shown for other 5xx response codes.