Re: [Hydro.dwg] json waterml2 / timeseriesml?

There is a functional OGC Building Block for the Observations and
Measurements model as Features here:

https://github.com/opengeospatial/ogcapi-sosa

This is being co-developed with the SSN/SOSA update to match the new OMS
specification.

can spin up customised profiles of these easily - e.g.

https://ogcincubator.github.io/bblocks-examples/bblock/ogc.bbr.examples.observation.vectorObservationFeature


there are also experiments and activities to explore how common we can make
domain models with different APIs for different packaging of observations,
including OGC API EDR, SensorThingsAPI and ConnectedSystemsAPI.

So I think there may be a number of alternative encodings required,
depending on which API to serve them, but some commonalities we can factor
out as BuildingBlocks.

Does a Timeseries API also make sense - or does STA or EDR cover all
requirements?

Rob Atkinson
*Senior Research Engineer * | Open Geospatial Consortium (OGC)
Mobile: +61 419 202973
ratkinson@ogc.org | ogc.org | @opengeospatial



Sign up for OGC News
<https://ogc.us4.list-manage.com/subscribe?u=704e02f81107a6caab1568067&id=4e4528fd9d>


On Fri, Jun 14, 2024 at 12:36 AM Blodgett, David L via Hydro.dwg <
hydro.dwg@lists.ogc.org> wrote:

> Hi All –
>
>
>
> In conversation today, the topic of a json encoding of WaterML2 or
> TimeseriesML came up. Is anyone aware of progress on such a thing? Seems
> like someone must have done something like that even as an ad-hoc
> experiment. Is there a world where we could establish a json encoding for
> hydrologic timeseries data?
>
>
>
> Thanks.
>
>
>
> Dave
> _______________________________________________
> You may visit our Privacy Policy at http://www.opengeospatial.org/privacy.
> Hydro.dwg mailing list
> Hydro.dwg@lists.ogc.org
> You may also unsubscribe or manage your OGC public list subscriptions at
>  https://lists.ogc.org/mailman/listinfo/hydro.dwg
>