JS-Client categories and FOI

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

JS-Client categories and FOI

GHillo
This post was updated on .
Hi,
I'm using the JS Client in bundle with the last version of SOS (4.3).
The selection popup with title "Select timeseries by list" seems very useful for the end-users in order to choose timeseries.
But I'm missing the logic of the categorization: category, station, phenomenon, procedure.
I detail, I've not understood the concept of 'category' since it actually shows observable properties which are already listed in the phenomenon category. It would be great if it would be possible to add a different level of categorization (e.g.: some capabilities/characteristics, a 'macroarea' related to the observation like air or water, and so on).
Another question is related to the categories stations  and sensor. In my case a single instrument is composed by many sensors (each providing different measurements). Is it possible (as mentioned before) to organize the data to be inserted in a proper way in order to obtain from the JS Client the possibility of doing a timeseries selection distinguishing by categories like: sensor or instrument, 'category' of the phenomenon (e.g.: if I select 'wind', then I obtein a subset of phenomena like wind-direction or wind-speed), and so on?

Regards
GHillo

Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

Henning Bredel-2

Hey,

I think you seem to be confused about the existence of the field category since you are thinkinh in SOS terms here, which is quite reasonable though.

However, your use case is the exact reason why the category field exists :). The value may appear different from SOS to SOS since each SOS instance is free to model its data diffenrently and choose different identifiers. So it is hard to find a generic case for parsing the catwgory field.

However, here is how it works: by default it is the same as the phenomenon parameter. If for a particular SOS dialect,  a category could add value by organizing parameters it has to be implemented.

I could imagine some user friendly category parsing configuration. If you are interested in implementing such feature let me know!

Best

  Henning

Am 10.07.2015 11:44 schrieb "GHillo" <[hidden email]>:
Hi,
I'm using the JS Client in bundle with the last version of SOS (4.3).
The selection popup with title "Select timeseries by list" seems very useful
for the end-users in order to choose timeseries.
But I'm missing the logic of the categorization: *category, station,
phenomenon, procedure*.
I detail, I've not understood the concept of *'category' *since it actually
shows observable properties which are already listed in the *phenomenon
*category. It would be great if it would be possible to add a different
level of categorization (e.g.: some capabilities/characteristics, a
'macroarea' related to the observation like air or water, and so on).
Another question is related to the categories *stations * and *sensor*. In
my case a single instrument is composed by many sensors (each providing
different measurements). Is it possible (as mentioned before) to organize
the data to be inserted in a proper way in order to obtain from the JS
Client the possibility of doing a timeseries selection distinguishing by
categories like: sensor or instrument, 'category' of the phenomenon (e.g.:
if I select 'wind', then I obteain a subset of phenomena like wind-direction
or wind-speed), and so on?

Regards
GHillo





--
View this message in context: http://sensorweb.forum.52north.org/JS-Client-categories-and-FOI-tp4028118.html
Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines

_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

GHillo
Hi Henning,
thanks a lot, now it is more clear.
I think that in the future (e.g. September) I'll need to implement those features. In this case, I'll contact you in order to apply best practices and do something useful also for the community!

Best
GHillo
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

and.vianello
In reply to this post by Henning Bredel-2
Hi all,
I have some misunderstanding with "category" meaning.
I just see that category and phenomena list the same observable properties and it's not useful.

Is it possible to change the "category filter" input with the offering of the procedures in your opinion?
This would be very great for us.

Let me know if you have some ideas.
Thank you, Andrea.
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

Henning Bredel-5
Hi Andrea,

do you provide your own REST API instance? Does it access data directly from
database or is it a SOS proxy instance?

In case of direct DB access, you should be able to adjust some Hibernate mapping
files. Just change the table mapping within CategoryResource.hbm.xml and adjust
the primary key to match the offeringid.

Also open the DatasetResource.hbm.xml or -- depending for v1.x versions of the
REST API open TimeseriesResource.hbm.xml -- and change the column of
CategoryEntity to offeringid as well.

I think that's it (all untested).

Best

  Henning

On 16.03.2017 17:47, and.vianello wrote:

> Hi all,
> I have some misunderstanding with "category" meaning.
> I just see that category and phenomena list the same observable properties
> and it's not useful.
>
> Is it possible to change the "category filter" input with the offering of
> the procedures in your opinion?
> This would be very great for us.
>
> Let me know if you have some ideas.
> Thank you, Andrea.
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/JS-Client-categories-and-FOI-tp4028118p4028887.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

simonjirka
In reply to this post by and.vianello
Dear Andrea,

The "Categeory" resource is an additional element offered by our
REST-API. In some project, the "Category" attribute is used as a
further approach to help users finding the data they need. However, as
the "Category" attribute is not needed in some scenarios,  it is often
mapped to one of the other SOS filters (e.g. observed property).

Thus, if you want to adjust this behavior, the recommendations by
Henning will help you.

Best regards
Simon

2017-03-16 17:47 GMT+01:00 and.vianello <[hidden email]>:

> Hi all,
> I have some misunderstanding with "category" meaning.
> I just see that category and phenomena list the same observable properties
> and it's not useful.
>
> Is it possible to change the "category filter" input with the offering of
> the procedures in your opinion?
> This would be very great for us.
>
> Let me know if you have some ideas.
> Thank you, Andrea.
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/JS-Client-categories-and-FOI-tp4028118p4028887.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines



--
Dr. Simon Jirka
52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: [hidden email]
Fon: +49-(0)-251-396371-31
Fax: +49-(0)-251-396371-11
http://52north.org/
Twitter: @FiveTwoN
General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

and.vianello
Thank you very much for your detailed explanations.
We did it and it's working perfectly.

Now it's very usefull, so thank you!
Andrea.
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

and.vianello
Hi,
just to inform you, this operation (mapping Category to offering) works only if you updated observation with the new 4.3.8 webapp and not if you updated observation with 4.3.7 and after you updated to 4.38.
Cheers,
Andrea.
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

Henning Bredel-5
Hi,

that's right. I forgot to mention, sorry.

Here's the hint in the release notes:

  https://github.com/52North/SOS/blob/develop/RELEASE-NOTES#L89

Best

  Henning

On 21.03.2017 16:09, and.vianello wrote:

> Hi,
> just to inform you, this operation (mapping Category to offering) works only
> if you updated observation with the new 4.3.8 webapp and not if you updated
> observation with 4.3.7 and after you updated to 4.38.
> Cheers,
> Andrea.
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/JS-Client-categories-and-FOI-tp4028118p4028897.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

and.vianello
Hi again,
We just noticed that in our service that we mapped with your suggestions we have some problems that you can see in the public webapp: http://monalisasos.eurac.edu/MONALISA_data_service/#/map

We tryed to map the category=offering.

If you select the data using the "List selection" only the Station-tab works properly, but the others no (we hid the Category-tab at the moment).

The Phenomenon-tab should work like in Map-view (Phenomena selection), instead if you select one phenomena, you just obtain one of the possible category.

I think the reason is that we have many offering with the same name (but different identifier) but the selection in the tab use the offeringid.

So is there a better solution to solve the problem?
Thank you,
Andrea.

 
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

and.vianello
I correct: it's just the Phenomenon-tab that doesn't work properly.
Thanks,
Andrea.
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

jansch
Hi Andrea,

I took a quick look and see the problem. I hopefully can fix this issue
in the next days and then come back to you. It would be great if you
could create an issue in the github repository:
https://github.com/52North/sensorweb-client-core/issues

Best regards,
Jan

On 09.05.2017 16:08, and.vianello wrote:

> I correct: it's just the Phenomenon-tab that doesn't work properly.
> Thanks,
> Andrea.
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/JS-Client-categories-and-FOI-tp4028118p4028940.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>

--
Jan Schulte
52°North GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
Fon: +49 251 396371 - 37
Fax: +49 251 396371 - 11
Web: http://52north.org

General Managers:
Albert Remke, Andreas Wytzisk
Local Court Münster HRB 10849
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

jansch
In reply to this post by and.vianello
Hi Andrea,

I take a quick look and see the problem. I hopefully can fix this issue
in the next days and then come back to you. It would be great if you
could create an issue in the github repository:
https://github.com/52North/sensorweb-client-core/issues

Best regards,
Jan

On 09.05.2017 16:08, and.vianello wrote:

> I correct: it's just the Phenomenon-tab that doesn't work properly.
> Thanks,
> Andrea.
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/JS-Client-categories-and-FOI-tp4028118p4028940.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>

--
Jan Schulte
52°North GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
Fon: +49 251 396371 - 37
Fax: +49 251 396371 - 11
Web: http://52north.org

General Managers:
Albert Remke, Andreas Wytzisk
Local Court Münster HRB 10849
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

and.vianello
Hi all,
I opened a new issue in GitHub at:

https://github.com/52North/sensorweb-client-core/issues/26

Thanks,
Andrea.
Reply | Threaded
Open this post in threaded view
|

Re: JS-Client categories and FOI

and.vianello
This post was updated on .
Hi all,
I saw many improvements in the 4.4 release, we are really happy.

I need your help now to understand how to set the mapping in the new release.

I need always that when I use the Category entry in the "List selection" (in the helgoland client) tool, I can see the offering list.

I tryed changing the 2 files: CategoryResource.hbm.xml and DatasetResource.hbm.xml
Is it right and enough? Apparently no.
The DB was already filled with the 4.3.14 release.

Thank you for your help.
Andrea.