[Geoserver-devel] OGC Filter Timezone issue

GeoServer GeoServer Developer
1

Hello,
I’m currently invoking a WFS exposed by geoserver that interrogates a JDBC based layer.

The underlying table has a TIMESTAMP field, and the user interface can call the WFS using a time parameter.

So, if in the invocation we pass something like:

ogc:PropertyIsEqualTo
ogc:PropertyNameMY_TIMESTAMP</ogc:PropertyName>
ogc:Literal2016-04-18T10:00:00Z</ogc:Literal>
</ogc:PropertyIsEqualTo>

I would expect that my db record with MY_TIMESTAMP field set to ‘2016-04-18T10:00:00Z’ is returned, but this is not the case.

But if I pass something like:
ogc:Literal2016-04-18T10:00:00+02:00</ogc:Literal>

the result is returned:

gml:featureMember
<MY_FEATURE fid=“MY_FEATURE.62”>
62
<MY_TIMESTAMP>2016-04-18T10:00:00</MY_TIMESTAMP>
…
</MY_FEATURE>
</gml:featureMember>

It seems that the server does not care about the timezone of the database field but it considers the default timezone of the OS when evaluating an OGC filter.
This is strange, since the filter is in +02:00 TZ and the returned record is in UTC TZ

Now, I found that when launching the Geoserver in standalone mode, if I add the ‘-Duser.timezone=UTC’ to start parameters the problem disappears.
Another solution is to change the timezone on the hosting OS.

This can be a good solution if Geoserver runs in a dedicated VM or as a standalone process.
But how to deal with machines on which I can’t change the timezone because there are other running services?
And also, how to deal geoserver deployed into an Application Server?
Probably I can’t launch the AS with the ‘-Duser.timezone=UTC’ option since there are other services that exposes functionalities that would be compromised by this setting.

Am I facing a known issue or what? Any suggestion?

Thank you and best regards

Francesco Fornari
Java Tech Expert
ACS S.p.A.
Rome - ITALY

2

Hi Francesco,
these questions are better asked on the user list, the dev list hosts discussion between

people actually working on the GeoServer own code (instead of using it).

That said, which version of GeoServer are you using? Some fixes regarding timezones
have been done in the last year, but I believe the only landed on 2.8.x and newer.

Cheers
Andrea

···

On Wed, Apr 20, 2016 at 9:49 AM, Francesco Fornari <fra.fornari@…403…> wrote:

Hello,
I’m currently invoking a WFS exposed by geoserver that interrogates a JDBC based layer.

The underlying table has a TIMESTAMP field, and the user interface can call the WFS using a time parameter.

So, if in the invocation we pass something like:

ogc:PropertyIsEqualTo
ogc:PropertyNameMY_TIMESTAMP</ogc:PropertyName>
ogc:Literal2016-04-18T10:00:00Z</ogc:Literal>
</ogc:PropertyIsEqualTo>

I would expect that my db record with MY_TIMESTAMP field set to ‘2016-04-18T10:00:00Z’ is returned, but this is not the case.

But if I pass something like:
ogc:Literal2016-04-18T10:00:00+02:00</ogc:Literal>

the result is returned:

gml:featureMember
<MY_FEATURE fid=“MY_FEATURE.62”>
62
<MY_TIMESTAMP>2016-04-18T10:00:00</MY_TIMESTAMP>
…
</MY_FEATURE>
</gml:featureMember>

It seems that the server does not care about the timezone of the database field but it considers the default timezone of the OS when evaluating an OGC filter.
This is strange, since the filter is in +02:00 TZ and the returned record is in UTC TZ

Now, I found that when launching the Geoserver in standalone mode, if I add the ‘-Duser.timezone=UTC’ to start parameters the problem disappears.
Another solution is to change the timezone on the hosting OS.

This can be a good solution if Geoserver runs in a dedicated VM or as a standalone process.
But how to deal with machines on which I can’t change the timezone because there are other running services?
And also, how to deal geoserver deployed into an Application Server?
Probably I can’t launch the AS with the ‘-Duser.timezone=UTC’ option since there are other services that exposes functionalities that would be compromised by this setting.

Am I facing a known issue or what? Any suggestion?

Thank you and best regards

Francesco Fornari
Java Tech Expert
ACS S.p.A.
Rome - ITALY

Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313

fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.