Feature: Improved rupture information

[chrisdicaprio]

When downloading a single rupture from the rupture explorer users want more information about a rupture and a json schema that is easier to parse.

NB: the additional fields are not explicity in the GeoJSON specification, but they are not disallowed

https://datatracker.ietf.org/doc/html/rfc7946#page-15

Members not described in this specification ("foreign members") MAY
be used in a GeoJSON document. Note that support for foreign members
can vary across implementations, and no normative processing model
for foreign members is defined. Accordingly, implementations that
rely too heavily on the use of foreign members might experience
reduced interoperability with other implementations.

For example, in the (abridged) Feature object shown below

{
"type": "Feature",
"id": "f1",
"geometry": {...},
"properties": {...},
"title": "Example Feature"
}

the name/value pair of "title": "Example Feature" is a foreign
member. When the value of a foreign member is an object, all the
descendant members of that object are themselves foreign members.

• add the following to the top of the FeatureCollection:

{
    "type": "FeatureCollection",
    "id": "('CRU', 3)",
    "magnitude": 7.238,
    "mean rate (1/yr)": 0.000010125880180567037,
    "area (km^2)": 1090,
    "length (km)": 35,
    "features": [
        {
...

• "mean rate (1/yr)" is the "rate_weighted_mean" (key is changed to make it's meaning obvious to users).

• Units added to aid user.

• remove the id relating to ruptures (e.g., "('CRU', 3)") from the Featuress. Note (as in the example above) it should be added to the top FeatureCollection.