Procedure Computation Instance – Django REST framework

Get a list of ProcedureComputation objects. ProcedureComputations have a 1:1 mapping with Observations.

### Available end points:

- `/ProcedureComputations/` - Will list all ProcedureComputations in the database
- `/ProcedureComputations.json` - Will return all ProcedureComputations in json format
- `/ProcedureComputations/<object_id>/` - Returns ProcedureComputations object with that id

### Available Methods:

- `GET`
- `HEAD`

### Available filters:

- `uuid`
- `title`
- `keywords`
- `abstract`

### How to use filters:

These filters can be used like django query filters using __ for related model relationships.

- `/computations/?uuid=d594d53df2612bbd89c2e0e770b5c1a0`
- `/computations/?title__startswith!=DETAILS NEEDED - COMPUTATION CREATED FOR SATELLITE COMPOSITE`
- `/computations/?abstract__contains=HadCM3 model`

GET /api/v2/computations/37709/?format=api

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "ob_id": 37709,
    "uuid": "1092d97568364adfb4ed37293aee99ab",
    "title": "Caption for Figure 2.12 from Chapter 2 of the Working Group I (WGI) Contribution to the Intergovernmental Panel on Climate Change (IPCC) Sixth Assessment Report (AR6)",
    "abstract": "Temperature trends in the upper air. (a) Zonal cross-section of temperature anomaly trends (2007–2016 baseline) for 2002–2019 in the upper troposphere and lower stratosphere region. The climatological tropopause altitude is marked as a grey line. Significance is not indicated due to the short period over which trends are shown, and because the assessment findings associated to this figure relate to difference between trends at different heights, not the absolute trends. (b, c) Trends in temperature at various atmospheric heights for 1980–2019 and 2002–2019 for the near-global (70°N–70°S) domain. (d, e) as for (b, c) but for the tropical (20°N–20°S) region. Further details on data sources and processing are available in the chapter data table (Table 2.SM.1).",
    "keywords": "",
    "inputDescription": null,
    "outputDescription": null,
    "softwareReference": null,
    "identifier_set": []
}