Onorbit
POST /udl/geostatus
Changed onService operation to take a single GEOStatus record as a POST body and ingest into the database. This operation is not intended to be used for automated feeds into UDL. Data providers should contact the UDL team for specific role assignments and for instructions on setting up a permanent feed through an alternate mechanism.
Request
- Base URLhttps://unifieddatalibrary.com
- URLhttps://unifieddatalibrary.com/udl/geostatus
- Authnone declared
Request body
Example request
{
"id": "GEOSTATUS-ID",
"classificationMarking": "U",
"idOnOrbit": "REF-ONORBIT-ID",
"origObjectId": "ORIGOBJECT-ID",
"ss": 1.1,
"sc": 1.1,
"relativeEnergy": 1.1,
"longitudeRate": 1.1,
"longitudeMin": 180.1,
"longitudeMax": 1.01,
"confidenceLevel": "Low",
"planeChangeStatus": "Current",
"troughType": "West",
"objectStatus": "Active",
"rawFileURI": "Example URI",
"createdAt": "2018-01-01T16:00:00.123Z",
"createdBy": "some.user",
"source": "Bluestaq",
"origin": "THIRD_PARTY_DATASOURCE",
"dataMode": "TEST",
"satNo": 21,
"origNetwork": "OPS1"
}Response
Success
Changes
- breaking
the
request property's minLength was increased from0to1
- breaking
- breaking
request body became required
- info
api operation id
create_49removed and replaced with - info
the endpoint scheme security
BasicAuthwas removed from the API
- breaking
Some revisions have not been checked yet.