Map client & charts

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

Map client & charts

danji_ma90
Hello,
I have two issues with our SOS map client and wanted to know if anyone encountered the same problems and can provide a solution.

1) Our observations have a high temporal resolution, often with measurements every 10 minutes. We noticed that when viewing the data in the diagram (also when switching to view the values column), depending on the time range chosen, SOS skips a lot of values, lowering temporal resolution. Also when downloading the CSV it will only contain the values demonstrated in the chart view of the client.  Depending on the temporal resolution of the measurements, viewing/downloading complete datasets only works if the time range is very small (e.g. 1-2 days). Is there any way of configuring the SOS so it will always show all values and also enable downloading complete datasets of long time ranges?

2) We also noticed that ALL our measurements have one hour added to their timestamp (measurements at 00:00 show at 01:00) in the map client charts, although the timestamp in the postgres database show the correct time. Any ideas where we might have got the configuration wrong?

Thanks very much for the help,

Daniel
Reply | Threaded
Open this post in threaded view
|

Re: Map client & charts

jansch
Hi Daniel,

I assume that you mean with "SOS map client" our client called
Helgoland? If I am right here are my answers to your questions:

1) It sounds like the client is requesting the data generalized. This
means the API only returns significant values (to optimize the request
bandwidth) to display a diagram which is close to the veritable diagram.
You can deselect this option (called "generalize data") in the client
settings.

2) The client shows the measurements with you local timestamp. Maybe you
are in a neighbour timezone of the location of the measurements?

Best regards,
Jan


On 05.12.2016 16:49, danji_ma90 wrote:

> Hello,
> I have two issues with our SOS map client and wanted to know if anyone
> encountered the same problems and can provide a solution.
>
> 1) Our observations have a high temporal resolution, often with measurements
> every 10 minutes. We noticed that when viewing the data in the diagram (also
> when switching to view the values column), depending on the time range
> chosen, SOS skips a lot of values, lowering temporal resolution. Also when
> downloading the CSV it will only contain the values demonstrated in the
> chart view of the client.  Depending on the temporal resolution of the
> measurements, viewing/downloading complete datasets only works if the time
> range is very small (e.g. 1-2 days). Is there any way of configuring the SOS
> so it will always show all values and also enable downloading complete
> datasets of long time ranges?
>
> 2) We also noticed that ALL our measurements have one hour added to their
> timestamp (measurements at 00:00 show at 01:00) in the map client charts,
> although the timestamp in the postgres database show the correct time. Any
> ideas where we might have got the configuration wrong?
>
> Thanks very much for the help,
>
> Daniel
>
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/Map-client-charts-tp4028764.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: Map client & charts

danji_ma90
Hi Jan,
thank you for your response. Yes I mean the the SOS map client, though I've never come across the term "Helgoland" before.
I had seen and used the "generalize data" operator in the map client, but I must have got something wrong that time, as I can now confirm that was the problem and it is now working fine.
Our data is collected by sensors all located in our province, therefore the timestamp should stay the same. Maybe our settings have to be adjusted somewhere. I checked the admin settings in the SOS client, but can't find any setting for changing time zones. Can you maybe point me in the right direction?

Thanks a lot,

kind regards

Daniel
Reply | Threaded
Open this post in threaded view
|

Re: Map client & charts

Carsten Hollmann
Hi Daniel,

I guess you use the 52N SOS bundle release, right?

Which release version do you use?

As Jan mentioned, the client uses the local time. The SOS, by default,
assumes that the timestamps are contained as UTC values in the database.
But you can define the timezone during the installation process in the
database settings.

In which timezone are the timestamps stored in your database?

It would be great if you could provide two or three examples from the
database and from the client.

Best,
Carsten
_______________________________________________
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: Map client & charts

danji_ma90
Hi Carsten

Thanks again for you quick response.
We use the 52 North SOS version 4.3.7, not the SOS bundle release.

We have a simple public demo database with a small subset of our sensor data. Please take a look at:

http://monalisasos.eurac.edu/sos/index

This also brings me to another issue we have had with the map client. As you may notice in our public demo, the map client never loads properly when you click the first time. In Google Chrome it always works after the 2nd or 3rd refresh, while in Firefox we have to copy the link and paste it into a new tab in order for it to work. Are these bugs or does this happen due to bad configuration?

I can provide an example for the timestamp problem:

I added a small subset.csv of our data from our public database. Following this link http://monalisasos.eurac.edu/sos/static/client/jsClient/index.html?ts=687__localhost&span=2015-01-01T00:00:00+01:00/2015-12-31T23:59:59+01:00 and clicking on chart view (+ disabling the "generalize data" function in the settings) you will find the exact same data, but the timestamp has +01:00 (as the link already indicates)

We are located in Italy, so we use the Central European Timezone UTC + 01:00. As you say we would have to set the database timezone to UTC + 01:00 as well. Is it possible to modify the time zone after the  installation process?

thanks

Daniel
Reply | Threaded
Open this post in threaded view
|

Re: Map client & charts

Carsten Hollmann
Hi Daniel,

you use the SOS bundle release because your instance provides the Sensor
Web REST-API directly.

I have tested your map client with Firefox and Chrome and it works
without refreshing.

You can change the timezone in the datasource.properties ([SOS]\WEB-INF)
and you should reload the SOS.
The timezone value should as defined here:

http://docs.oracle.com/javase/8/docs/api/java/util/TimeZone.html

Best,
Carsten
_______________________________________________
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: Map client & charts

danji_ma90
This post was updated on .
Thanks again for all the advice.

It's strange that the map client loads without problems for you. Without refreshing (with the map not loading properly) the developers console in chrome doesn't show any errors. It simply stops loading properly after "phenomenon-entry.html", leaving the following 9 files as "data:image/gif;base..." with type gif and the map stays blurry and freezes or it just shows a grey surface (though the disk with the number of stations always shoes up). When I refresh, it loads these as png files (eg. 90.png) and the map works correctly. Have you maybe had this issue before?

I accessed our datasource_properties.txt in the console, but can't find the part I have to modify in order to adjust the database time zone.

Thanks again



Reply | Threaded
Open this post in threaded view
|

Re: Map client & charts

Carsten Hollmann
Hi,

 > I accessed our  datasource.txt in the
 > console, but can't find the part I have to modify in order to adjust
 > the database time zone.

Which 52N SOS version do you use?

I think this features is only available in the current development version.

As I mentioned in a previous mail, the SOS expects that the timestamps
are in UTC. It your timestamps are in another timezone, an option eould
be to convert an update your timestamps to UTC.

Best,
Carsten
_______________________________________________
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: Map client & charts

danji_ma90
Hi,
Here is our version-info.txt , we use the web-bundle version 4.3.7.

When querying the timezone in postgres, on our db server and on our webapp server, they all use our local timezone (Central European Timezone CET). Would converting all the timestamps to UTC not modify all the result time values? That might correct the timestamps in the webapp map client, but on the other hand might falsify all the timetsamps in the db (e.g. my colleagues using the R-plugin to access the db might get the wrong timestamps). We would need the webapp to query the right timezone from the db, not use the default UTC.

Reply | Threaded
Open this post in threaded view
|

URLs in GetCapabilities-Answer of 52n-SOS-Server

Scholten, Daniel

Dear all,

 

currently the 52n-SOS-Server shows several URLs for one operation in the OperationsMetadata of the GetCapabilities-Answer:

 

As far as I understand the OWS Common Specification (OGC-Document 06-121r3, pdf-page 46-47), this is not correct. There must be at least one mandatory URL Element next to the Get and Post Elements (not as children of Get and Post) and the handling of different content types must not be done by different URLs (though I did not check the possibilities to realize it with constraints). As far as I understand the specification, it has to be one URL (or several for load balancing or backup reasons) which handles different content types via content negotiation.

 

Or maybe I didn’t got the meaning of the specification or missed some good reasons to do it different?

 

There is no need for me to change this right now, I was just stumpling upon this.

 

Best wishes

Daniel

__________________________________________________

Daniel Scholten

 

Niersverband

Stabsstelle Informations- und Modelltechnik (IMT)

Sachbereich Softwaretechnik

Am Niersverband 10

41747 Viersen

 

Tel.: +49 2162 3704 - 460 [(Sekretariat: - 101)]

Fax: +49 2162 3704 - 444

E-Mail: [hidden email]

 

Körperschaft des öffentlichen Rechts, Sitz: Viersen

Vorsitzender des Verbandsrates: Rolf A. Königs, Vorstand: Prof. Dr.-Ing. Dietmar Schitthelm

 


_______________________________________________
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

Unbenannt.PNG (86K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: URLs in GetCapabilities-Answer of 52n-SOS-Server

Carsten Hollmann
Hi Daniel,

thanks for your hint and we will check this.

The current representation with different endpoints for different
content types is because of the backward compatibility of the first 52N
SOS 4.x versions. In future versions of the 52N SOS only one URL
endpoint would be listed with constraints for the supported content types.

Best,
Carsten

Am 04.01.2017 um 15:19 schrieb Scholten, Daniel:

> Dear all,
>
>
>
> currently the 52n-SOS-Server shows several URLs for one operation in the
> OperationsMetadata of the GetCapabilities-Answer:
>
>
>
> As far as I understand the OWS Common Specification (OGC-Document
> 06-121r3, pdf-page 46-47), this is not correct. There must be at least
> one mandatory URL Element _next to_ the Get and Post Elements (not as
> children of Get and Post) and the handling of different content types
> must not be done by different URLs (though I did not check the
> possibilities to realize it with constraints). As far as I understand
> the specification, it has to be one URL (or several for load balancing
> or backup reasons) which handles different content types via content
> negotiation.
>
>
>
> Or maybe I didn’t got the meaning of the specification or missed some
> good reasons to do it different?
>
>
>
> There is no need for me to change this right now, I was just stumpling
> upon this.
>
>
>
> Best wishes
>
> Daniel
>
> __________________________________________________
>
> Daniel Scholten
>
>
>
> Niersverband
>
> Stabsstelle Informations- und Modelltechnik (IMT)
>
> Sachbereich Softwaretechnik
>
> Am Niersverband 10
>
> 41747 Viersen
>
>
>
> Tel.: +49 2162 3704 - 460 [(Sekretariat: - 101)]
>
> Fax: +49 2162 3704 - 444
>
> E-Mail: [hidden email]
> <mailto:[hidden email]>
>
>
>
> Körperschaft des öffentlichen Rechts, Sitz: Viersen
>
> Vorsitzender des Verbandsrates: Rolf A. Königs, Vorstand: Prof. Dr.-Ing.
> Dietmar Schitthelm
>
>
>
>
>
> _______________________________________________
> 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
>

--
Carsten Hollmann

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-35
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: Map client & charts

Carsten Hollmann
In reply to this post by danji_ma90
Hi,

> Would converting all the timestamps to UTC not modify all the result time
> values?

Yes, that would modify the phenomenon times and result time values.

> We would need the webapp to query the right timezone from the
> db, not use the default UTC.

The current development version (4.4.x) [0] supports the definition of
the stored time zone in the database.
If you need this functionality you should use the development version of
the 52N SOS.
This version contains some changes on the database model which might be
updated by the "Force update ..." functionality during the installation
process but this is not yet fully tested (to update the db model from
4.3.x to 4.4.x).

Best,
Carsten

[0] https://github.com/52North/SOS/tree/develop
_______________________________________________
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