Skip to content

Datastream and Observation Schema #181

@EricLo-417

Description

@EricLo-417

Hello OGC Connected System People,

I am currently making an implementation of the api and I have a question about datastream and observation schema.

Based on Req 67,

Image

It appears that when creating an observation, the server should get the schema based on the observation (application/json, protobuff, or some custom like application/report+json) then verify the observation follows said schema.

Is that the correct flow, so for example, the result schema seems to follow SWE Common DataComponent (instead of json schema) would be saying the JSON (application/json) needs to adhear that SWE common schema? Asking cause there is an existing application/swe+json format, i would of assumed that uses SWE common result schema and the application/json uses JSON Schema as the resultSchema

Then one last question, in regard to custom schema (let's say application/report+json) if we wanted that to be resolved via json schema we would just upload the json schema to the "resultSchema" field and make our server "know" what how resolve the two.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions