Virtual Meeting 01. CoP Plenary workshop Forum 5

When: MON and TUE

Description

It seems that the COVID-19 does not want us to meet f2f for a while so this time it has been organized as a long telecon. This is the format:

  • TODAY (Monday): We realized that there are many newcomers registered to this meeting so today we will have a plenary session dedicate to engage with this new people. I'm not sure how many will be interested in our Interoperability experiments. We will see. Do not expect a "normal" interop-CoP meeting as it will be on plenary with the other CoPs. You are welcome to join in to know what the other CoP's are doing and meet the new faces. We will start at 13:00 and end at 16:00 (https://global.gotomeeting.com/join/559511453)

Attendants

Meeting minutes

Attendants: Joan Masó, Andy Cobley, Ester Prat, Andreas Matheus, Lucy Bastin

https://external.ogc.org/twiki_public/CitSciIE/VirtualMeeting01

Diversity of APIs:
Santiago in COS$Cloud is working with several APIs form the different observatories and not with the SensorThings API approach from the Interop-CoP.
Joan: I have found (form George Percival) this resource that I have been told is related with the US department of state. The expose Citizen Science APIs about 4 topics. This is the one about mosquitoes: https://portal-data.cscloud.host/api-details#api=guest-mosquitoes&operation=get-daily. What about showing them to do the same with STA?. Anne knows aobut this one.

Engineering Report:
We can include the Earth Cahllenge experiences
We could agree on reporting about a possible extension for STA

CoPs members continuity:
Andy hasn't any CS project in the near future, but he will keep joining the CoP in the background. It is also uncertain what will happen with UK in the Brexit scenario.

Chapter 8: STA Clients - Andy to describe his client
He shows Python script of COS4Cloud demo. It’s taking the JSON and spreading it out. It creates a CSV file. You read the JSON and manually extract the info you need.

Joan: In a COS4Cloud meeting datastream groups several observation groups?

How to create the list of positions for creating a map? Now you get repeated positions.

One solution would be to build a CSV of observation groups where each observation group is a row and properties are columns.

Observation Groups in COS4Cloud: https://cos4cloud.demo.secure-dimensions.de/sta4cs/v1.0/ObservationGroups?$expand=Observations&$filter=Observations/Datastream/ObservedProperty/name%20eq%20%27Taxon%27 (not working now)

Second Interoperability Engineering Report: https://github.com/opengeospatial/CitSciIE/tree/master/SecondPhase

Section about API proliferation: we discovered in COS4Cloud that some developers don’t care about different existing APIs. With George Percival we have created a repository of APIs. https://portal-data.cscloud.host/apis.
 
Andreas: what we see in COS4Cloud is that every CS initiative is working in silos and love working in silos. No one cares about interoperability. Huge problem in educating datasets owners in sharing databases.

Lucy: maybe GBIF can be a common model for iSpot and Natusfera. But even the taxonomy is not common in those projects, they are not using the GBIF one.

Andreas: Fraunhofer has a FROST server implementing SensorThings API. I implemented an extension and loaded Natusfera data using a 52N data loader. We are trying to prove this by the end of the year.

Challenge: describe the quality of the observation and the semantics in a standardized way (every platform is using a different taxonomy).

Sprint 3 - Interop CoP

Attendants: Andy Cobley, Lucy Bastin, Joan Masó, Ester Prat, Andreas Matheus

COS4Cloud observatories are using different taxonomies. And GBIF is using another API. So in biodiversity field everything is centralised in GBIF and they have an API. But such API is read only, so there is still room for a common API.

But specially in COS4Cloud where work on interoperability is going for one year, it seems easier to adapt to each API rather than building a common one.

Lucy: which is the goal of the use cases? Is it about putting all data together?
It’s also about federating the expert role. Experts can consult, validate and use data in other works.

So the situation in COS4Cloud is a little bit frustrating. We discovered that iSpot has not an API, so it is a good opportunity to have one. 

All this has to be embed in the EOSC portal, which has still an unclear use and future.

We plan to present the 2nd ER in the OGC TC Meeting in December, but this is just a desire. The CoP could continue with the support of COS4Cloud. But we should think on the contents for the next IE, as things are already done or won’t be done anymore.

Andy: is STA a too heavy issue for CS projects? Maybe it’s too complex for a modest CS project looking for data in a local framework.

Lucy: it would be possible to apply STA with a minimal subset or a simplified version?

Andreas: it’s all about reading the documentation: https://developers.sensorup.com/docs/#query-filter

Joan: really it is not trivial to know how to query for information. Standards don’t explain well how they should be applied. Andreas: so this will be part of our best practices recommendations: not to read the standards but the best practices.

Joan: second problem is to make a map from the observations. Feature of Interest is what has the geometry in STA. So you ask for all FoI within a given area. But, what happens where repetitions exist? For example, if I ask for all features of interest, will I get repeated results for the different datastreams in one feature of interest? Andreas: Query should be like that: https://cos4cloud.demo.secure-dimensions.de/sta4cs/v1.0/Observations?$filter=st_within(FeatureOfInterest/feature,geography%27POLYGON((0 0,10 0,10 10,0 10,0 0))%27)

Joan: maybe we can create a section in our ER for recording all these useful queries.

Joan: Maybe the minimum profile for the STA that Lucy was asking could be the sensor and the thing(?). There are many cases where you could forget about the thing.Sometimes the location of the Thing or the Feature of Interest are different.

For the ER: Andy and Andreas to complete their sections about STA implementations. GBIF and iNaturalist APIs Joan will try to investigate. Wilson Center people to complete the Earth Challenge. Lucy is free but ideas are welcome. 

Previous Action points

  • None

Agenda and minutes

Next Action points

GoToMeeting details


https://global.gotomeeting.com/join/321982654


You can also dial in using your phone.
(For supported devices, tap a one-touch number below to join instantly.)

United States: +1 (909) 259-0010
- One-touch: tel:+19092590010,,321982654#

Access Code: 321-982-654


More phone numbers:
(For supported devices, tap a one-touch number below to join instantly.)

Australia: +61 2 8014 4937
- One-touch: tel:+61280144937,,321982654#

Austria: +43 7 2088 1406
- One-touch: tel:+43720881406,,321982654#

Belgium: +32 28 08 4296
- One-touch: tel:+3228084296,,321982654#

Denmark: +45 69 91 89 33
- One-touch: tel:+4569918933,,321982654#

Finland: +358 942 59 9121
- One-touch: tel:+358942599121,,321982654#

France: +33 182 880 462
- One-touch: tel:+33182880462,,321982654#

Germany: +49 898 7806 6465
- One-touch: tel:+4989878066465,,321982654#

Ireland: +353 14 845 982
- One-touch: tel:+35314845982,,321982654#

Italy: +39 0 247 92 12 41
- One-touch: tel:+390247921241,,321982654#

Netherlands: +31 208 080 384
- One-touch: tel:+31208080384,,321982654#

Norway: +47 21 04 29 12
- One-touch: tel:+4721042912,,321982654#

Spain: +34 911 82 9783
- One-touch: tel:+34911829783,,321982654#

Sweden: +46 852 503 473
- One-touch: tel:+46852503473,,321982654#

Switzerland: +41 225 3314 54
- One-touch: tel:+41225331454,,321982654#

United Kingdom: +44 20 3318 4724
- One-touch: tel:+442033184724,,321982654#

Topic attachments
ISorted ascending Attachment Action Size Date Who Comment
ARDDefinitionServer.pngpng ARDDefinitionServer.png manage 33 K 09 Sep 2020 - 11:04 JoanMaso  
STA-CitSci.pngpng STA-CitSci.png manage 170 K 09 Sep 2020 - 11:05 JoanMaso  
Topic revision: r4 - 13 Oct 2020, JoanMaso
This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback