AASHTO-2023 web service response edits

Please see the tracked changes in the attached Word file.response_1645540965612+tracked_changes.docx

changed due date to February 24, 2022

added AASHTO-2023 label

assigned to @bclayton

changed milestone to %AASHTO Updates

added To Do label

added In Progress label and removed To Do label

@nluco

The 2009 AASHTO service has the response structure as:

 "data": {
    "pga": 0.637,
    "fpga": 1,
    "as": 0.637,
    "ss": 1.512,
    "fa": 1,
    "sds": 1.512,
    "s1": 0.551,
    "fv": 1.3,
    "sd1": 0.716,
    "sdc": "D",
    "ts": 0.474,
    "t0": 0.095,
    "twoPeriodDesignSpectrum": []
}

Where the current new response is:

"data": {
  "xs": [],
  "ys": []
}

Questions:

1. Do we need to worry about the other parameters at this time?
2. Is the new response data good or do we want?

"data": {
  "twoPeriodDesignSpectrum": {
    "xs": [],
    "ys": []
  }
}

or

"data": {
  "twoPeriodDesignSpectrum": []
}

3. In 2009 the PGA X value is 0, do we want that for the new services as well?

As discussed on 3/8/2022, ...

1. Don't need to worry about other parameters (sdc, sd1, sds, as) at this time.
2. The new response data is good as is, at least for now.

Switch PGA to 0

@bclayton , @zkortum

A couple more minor editorial suggestions:

1. Under "request", change the order to latitude, longitude, siteClass.

2. Under "response-metadata", remove siteClass.

mentioned in merge request !108 (merged)

mentioned in commit ebdcd8c2

closed with merge request !108 (merged)

removed In Progress label