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

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

I’ll let Hylke & Kathi complement but the way I see it is the following

-          ST API 2.0 is OMS compliant

-          My guts feeling is that TSML will end up 90% (or more) OMS compliant

-          There is a high chance ST API covers (dunno for EDR)

-          If the above is correct : I would suggest trying to reduce the entropy for the external world and not add yet another API. Otherwise for those not following all our internal OGC groups discussion, what the API to implement will be more and more complex.

My 2 €
Sylvain



De : Rob Atkinson <ratkinson@ogc.org>
Envoyé : jeudi 13 juin 2024 17:30
À : Blodgett, David L <dblodgett@usgs.gov>
Cc : Hydro.dwg@lists.ogc.org; Simon Cox <scox@ogc.org>; SDW WG (public-sdw-wg@w3.org) <public-sdw-wg@w3.org>
Objet : 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<https://urldefense.com/v3/__https:/github.com/opengeospatial/ogcapi-sosa__;!!KbSiYrE!m10Fc0eL5fJQIQ6s8LmFxL6rrLEQCDf3UEaCq3k510Xw6QJcJI4QtQ8XqLBN9QrTU66zxOeJMW4zK_GorA$>

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<https://urldefense.com/v3/__https:/ogcincubator.github.io/bblocks-examples/bblock/ogc.bbr.examples.observation.vectorObservationFeature__;!!KbSiYrE!m10Fc0eL5fJQIQ6s8LmFxL6rrLEQCDf3UEaCq3k510Xw6QJcJI4QtQ8XqLBN9QrTU66zxOeJMW5FeQQS9w$>


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<mailto:ratkinson@ogc.org> | ogc.org<https://urldefense.com/v3/__http:/ogc.org/__;!!KbSiYrE!m10Fc0eL5fJQIQ6s8LmFxL6rrLEQCDf3UEaCq3k510Xw6QJcJI4QtQ8XqLBN9QrTU66zxOeJMW5K_TD6Ew$> | @opengeospatial


[https://portal.ogc.org/files/?artifact_id=99287]
Sign up for OGC News<https://urldefense.com/v3/__https:/ogc.us4.list-manage.com/subscribe?u=704e02f81107a6caab1568067&id=4e4528fd9d__;!!KbSiYrE!m10Fc0eL5fJQIQ6s8LmFxL6rrLEQCDf3UEaCq3k510Xw6QJcJI4QtQ8XqLBN9QrTU66zxOeJMW6eGMtr4Q$>


On Fri, Jun 14, 2024 at 12:36 AM Blodgett, David L via Hydro.dwg <hydro.dwg@lists.ogc.org<mailto: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<https://urldefense.com/v3/__http:/www.opengeospatial.org/privacy__;!!KbSiYrE!m10Fc0eL5fJQIQ6s8LmFxL6rrLEQCDf3UEaCq3k510Xw6QJcJI4QtQ8XqLBN9QrTU66zxOeJMW6TU6Ow1g$>.
Hydro.dwg mailing list
Hydro.dwg@lists.ogc.org<mailto: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<https://urldefense.com/v3/__https:/lists.ogc.org/mailman/listinfo/hydro.dwg__;!!KbSiYrE!m10Fc0eL5fJQIQ6s8LmFxL6rrLEQCDf3UEaCq3k510Xw6QJcJI4QtQ8XqLBN9QrTU66zxOeJMW6Vdj2VfQ$>