[SCT-Workflow]: Create new POST, PUT, GET, DELETE for "/shoreline"

[trietmnj]

• create POST shoreline endpoint
• create POST shorelines endpoint
• create PUT shoreline endpoint
• create GET shorelines endpoint
• create DELETE shoreline endpoint
• create DELETE shorelines endpoint
• edit swagger docs
• append po_statement POST and PUT to take a shoreline reference in body param

[trietmnj]

Using (project_id, code) as the unique key. These two fields are mandatory, plus the geometry.

[trietmnj]

Example shorelines shapefile.

CharlestonShorelines.zip

[trietmnj]

Similar to reaches, the id for each shoreline is obtainable through the GeoJSON properties on GET shorelines

[trietmnj]

e.g. POST and PUT shoreline body

{
  "type": "Feature",
  "properties": {
    "code": "Updated CODE",
    "name": "Updated This is my name",
    "category": "Updated This is my category",
    "otherCategory": "Updated This is my other category",
    "type": "Updated This is my type",
    "otherType": "Updated This is my other type",
    "waveClimate": "Updated This is my waveClimate",
    "otherWaveClimate": "Updated This is my other waveClimate",
    "shorelineLength": 333,
    "erosion": true,
    "waterBody": "Updated Pacific",
    "scs": [
        "GEOJSON scs1",
        "Updated scs2",
        "GEOJSON scs3"
    ]
  },
  "geometry": {
    "type": "LineString",
    "coordinates": [
        [
        12.478129652015241,
        41.9022826549635
        ],
        [
        12.478129652015241,
        41.90136017129154
        ],
        [
        12.479303348926749,
        41.90136017129154
        ],
        [
        12.479303348926749,
        41.9022826549635
        ],
        [
        12.478129652015241,
        41.9022826549635
        ]
    ]
  }
}