Re: [Geoserver-users] Problem with timestamps and Oracle datastore

[DGIS Devels]

We had not thought it was a problem related to the time change. We
haveconsidered it and and that Geoserver returns results in GMT, and no
problem with the hour.

However, we still find answers to the date indicated with a day less than
stored in BD.

Thank you very much for your response.

2016-03-16 10:06 GMT+01:00 Ian Turton :

> The quick answer to why there is a 2 hour difference is daylight savings
> (or summer) time. You are actually in GMT+2 in June.
>
> The simple answer is for your client to convert all your timestamps to GMT
> before any interaction with the data base if that is what you have the
> database set to.
>
> Ian
>
> On 16 March 2016 at 08:34, DGIS Devels  wrote:
>
>> Hi,
>>
>> any help on this, please? We fail to understand why the date is sent with
>> a day less than that stored in BD and time to two hours before.
>>
>> Thanks
>>
>> 2016-03-11 12:21 GMT+01:00 DGIS Devels :
>>
>>> Hi all,
>>>
>>> we are having problems retrieving data using WFS from a oracle
>>> datastore, specifically related to dates and timestamps. We have read
>>> other posts in which other people had similar problems, but not found
>>> response.
>>>
>>> Our WFS filters are similar to:
>>>
>>> http://www.opengis.net/ogc;>
>>> 
>>>   FH_TIMESTAMP
>>>   
>>>   2015-06-08 12:00:00
>>>   
>>>   
>>>   2015-06-08 13:00:00
>>>   
>>> 
>>> ...
>>>
>>> Here in Spain, we work in GMT+1. The FH_TIMESTAMP field is defined as
>>> TIMESTAMP in the related table. Tomcat where GeoServer is deployed is
>>> set as defaulta to GMT.
>>> This query must return a single result with date/time 2015-06-08
>>> 12:12:01. Indeed it is recovering, but the response shows 10:12:01
>>> instead of 12:12:01. Also, the date field (Date type in BD ... ), from
>>> which the timestamp is generated, is one day late:
>>>
>>> *2015-06-07Z*
>>> 2015-06-08T*10:12:01*Z
>>>
>>> Geoserver The log shows the following information for this request:
>>>
>>> 03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - SELECT * FROM (?
>>> SELECT FH_FECHA, FH_TIMESTAMP, ..., as GEOM GEOM FROM ... WHERE
>>> (FH_TIMESTAMP BETWEEN ? AND ?)) WHERE ROWNUM <= 2000
>>> 03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 1 = 2015-06-08
>>> 12:00:00.0
>>> 07/03/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 2 = 2015-06-08
>>> 13:00:00.0
>>> 07/03/2016 13: 58: 27.503 DEBUG [geotools.jdbc] - 2015-06-08 12: 12:01.0
>>> is not of type java.sql.Timestamp, attempting conversion
>>>
>>> We have tried to make the same request with "geoserver" format. In this
>>> case, we have to decrease the range of timestamp in two hours in order to
>>> recover the same data:
>>>
>>> 
>>>  FH_TIMESTAMP
>>>  
>>>  2015-06-08T10:00:00Z
>>>  
>>>  
>>>  2015-06-08T11:00:00Z
>>>  
>>>
>>>
>>> Result is the same: hour late and erroneous date:
>>>
>>> *2015-06-07Z*
>>> *2015-06-08T10:12:01Z*
>>>
>>> Same as for the previous query.
>>>
>>> What should we do to show to avoid previous day's date and time with two
>>> hours late?
>>>
>>> Any help is welcome.
>>>
>>> Thank you very much, greetings
>>>
>>
>>
>>
>> --
>> Transform Data into Opportunity.
>> Accelerate data analysis in your applications with
>> Intel Data Analytics Acceleration Library.
>> Click to learn more.
>> http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
>> ___
>> Geoserver-users mailing list
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>
>
> --
> Ian Turton
>
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem with timestamps and Oracle datastore

[Andrea Aime]

On Thu, Mar 17, 2016 at 12:09 PM, DGIS Devels 
wrote:

> We had not thought it was a problem related to the time change. We
> haveconsidered it and and that Geoserver returns results in GMT, and no
> problem with the hour.
>

Dates are also converted to GMT, there is an interesting discussion on the
geotools-devel list for that,
and I believe a new flag is being introduced for those that want dates not
to be considered a concept
related to timezone

I believe it's this one:
http://osgeo-org.1560.x6.nabble.com/GEOT-5329-Proposal-to-avoid-Date-shifting-due-to-Timezones-td5241912.html

Cheers
Andrea

-- 
==
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.

---
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem with timestamps and Oracle datastore

[Ian Turton]

The day change occurs because your time stamp was truncated to a date at
some point and then moved back by an hour (or two) which moves it into the
previous day and then it got truncated again.

Ian

On 17 March 2016 at 11:09, DGIS Devels  wrote:

> We had not thought it was a problem related to the time change. We
> haveconsidered it and and that Geoserver returns results in GMT, and no
> problem with the hour.
>
> However, we still find answers to the date indicated with a day less than
> stored in BD.
>
> Thank you very much for your response.
>
> 2016-03-16 10:06 GMT+01:00 Ian Turton :
>
>> The quick answer to why there is a 2 hour difference is daylight savings
>> (or summer) time. You are actually in GMT+2 in June.
>>
>> The simple answer is for your client to convert all your timestamps to
>> GMT before any interaction with the data base if that is what you have the
>> database set to.
>>
>> Ian
>>
>> On 16 March 2016 at 08:34, DGIS Devels 
>> wrote:
>>
>>> Hi,
>>>
>>> any help on this, please? We fail to understand why the date is sent with
>>> a day less than that stored in BD and time to two hours before.
>>>
>>> Thanks
>>>
>>> 2016-03-11 12:21 GMT+01:00 DGIS Devels :
>>>
 Hi all,

 we are having problems retrieving data using WFS from a oracle
 datastore, specifically related to dates and timestamps. We have read
 other posts in which other people had similar problems, but not found
 response.

 Our WFS filters are similar to:

 http://www.opengis.net/ogc;>
 
   FH_TIMESTAMP
   
   2015-06-08 12:00:00
   
   
   2015-06-08 13:00:00
   
 
 ...

 Here in Spain, we work in GMT+1. The FH_TIMESTAMP field is defined as
 TIMESTAMP in the related table. Tomcat where GeoServer is deployed is
 set as defaulta to GMT.
 This query must return a single result with date/time 2015-06-08
 12:12:01. Indeed it is recovering, but the response shows 10:12:01
 instead of 12:12:01. Also, the date field (Date type in BD ... ), from
 which the timestamp is generated, is one day late:

 *2015-06-07Z*
 2015-06-08T*10:12:01*Z

 Geoserver The log shows the following information for this request:

 03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - SELECT * FROM (?
 SELECT FH_FECHA, FH_TIMESTAMP, ..., as GEOM GEOM FROM ... WHERE
 (FH_TIMESTAMP BETWEEN ? AND ?)) WHERE ROWNUM <= 2000
 03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 1 = 2015-06-08
 12:00:00.0
 07/03/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 2 = 2015-06-08
 13:00:00.0
 07/03/2016 13: 58: 27.503 DEBUG [geotools.jdbc] - 2015-06-08 12:
 12:01.0 is not of type java.sql.Timestamp, attempting conversion

 We have tried to make the same request with "geoserver" format. In
 this case, we have to decrease the range of timestamp in two hours in 
 order to
 recover the same data:

 
  FH_TIMESTAMP
  
  2015-06-08T10:00:00Z
  
  
  2015-06-08T11:00:00Z
  


 Result is the same: hour late and erroneous date:

 *2015-06-07Z*
 *2015-06-08T10:12:01Z*

 Same as for the previous query.

 What should we do to show to avoid previous day's date and time with
 two hours late?

 Any help is welcome.

 Thank you very much, greetings

>>>
>>>
>>>
>>> --
>>> Transform Data into Opportunity.
>>> Accelerate data analysis in your applications with
>>> Intel Data Analytics Acceleration Library.
>>> Click to learn more.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
>>> ___
>>> Geoserver-users mailing list
>>> Geoserver-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>>
>>
>>
>> --
>> Ian Turton
>>
>
>


-- 
Ian Turton
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem with timestamps and Oracle datastore

[DGIS Devels]

All right! We will consider it when showing the return date field. Thanks
to all, again

2016-03-17 12:25 GMT+01:00 Andrea Aime :

> On Thu, Mar 17, 2016 at 12:09 PM, DGIS Devels 
> wrote:
>
>> We had not thought it was a problem related to the time change. We
>> haveconsidered it and and that Geoserver returns results in GMT, and no
>> problem with the hour.
>>
>
> Dates are also converted to GMT, there is an interesting discussion on the
> geotools-devel list for that,
> and I believe a new flag is being introduced for those that want dates not
> to be considered a concept
> related to timezone
>
> I believe it's this one:
> http://osgeo-org.1560.x6.nabble.com/GEOT-5329-Proposal-to-avoid-Date-shifting-due-to-Timezones-td5241912.html
>
> Cheers
> Andrea
>
> --
> ==
> 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.
>
> ---
>
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem with timestamps and Oracle datastore

[Ian Turton]

The quick answer to why there is a 2 hour difference is daylight savings
(or summer) time. You are actually in GMT+2 in June.

The simple answer is for your client to convert all your timestamps to GMT
before any interaction with the data base if that is what you have the
database set to.

Ian

On 16 March 2016 at 08:34, DGIS Devels  wrote:

> Hi,
>
> any help on this, please? We fail to understand why the date is sent with
> a day less than that stored in BD and time to two hours before.
>
> Thanks
>
> 2016-03-11 12:21 GMT+01:00 DGIS Devels :
>
>> Hi all,
>>
>> we are having problems retrieving data using WFS from a oracle datastore,
>> specifically related to dates and timestamps. We have read other posts
>> in which other people had similar problems, but not found response.
>>
>> Our WFS filters are similar to:
>>
>> http://www.opengis.net/ogc;>
>> 
>>   FH_TIMESTAMP
>>   
>>   2015-06-08 12:00:00
>>   
>>   
>>   2015-06-08 13:00:00
>>   
>> 
>> ...
>>
>> Here in Spain, we work in GMT+1. The FH_TIMESTAMP field is defined as
>> TIMESTAMP in the related table. Tomcat where GeoServer is deployed is
>> set as defaulta to GMT.
>> This query must return a single result with date/time 2015-06-08 12:12:01.
>> Indeed it is recovering, but the response shows 10:12:01 instead of
>> 12:12:01. Also, the date field (Date type in BD ... ), from which the
>> timestamp is generated, is one day late:
>>
>> *2015-06-07Z*
>> 2015-06-08T*10:12:01*Z
>>
>> Geoserver The log shows the following information for this request:
>>
>> 03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - SELECT * FROM (? SELECT
>> FH_FECHA, FH_TIMESTAMP, ..., as GEOM GEOM FROM ... WHERE (FH_TIMESTAMP
>> BETWEEN ? AND ?)) WHERE ROWNUM <= 2000
>> 03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 1 = 2015-06-08
>> 12:00:00.0
>> 07/03/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 2 = 2015-06-08
>> 13:00:00.0
>> 07/03/2016 13: 58: 27.503 DEBUG [geotools.jdbc] - 2015-06-08 12: 12:01.0
>> is not of type java.sql.Timestamp, attempting conversion
>>
>> We have tried to make the same request with "geoserver" format. In this
>> case, we have to decrease the range of timestamp in two hours in order to
>> recover the same data:
>>
>> 
>>  FH_TIMESTAMP
>>  
>>  2015-06-08T10:00:00Z
>>  
>>  
>>  2015-06-08T11:00:00Z
>>  
>>
>>
>> Result is the same: hour late and erroneous date:
>>
>> *2015-06-07Z*
>> *2015-06-08T10:12:01Z*
>>
>> Same as for the previous query.
>>
>> What should we do to show to avoid previous day's date and time with two
>> hours late?
>>
>> Any help is welcome.
>>
>> Thank you very much, greetings
>>
>
>
>
> --
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>


-- 
Ian Turton
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem with timestamps and Oracle datastore

[DGIS Devels]

Hi,

any help on this, please? We fail to understand why the date is sent with a
day less than that stored in BD and time to two hours before.

Thanks

2016-03-11 12:21 GMT+01:00 DGIS Devels :

> Hi all,
>
> we are having problems retrieving data using WFS from a oracle datastore,
> specifically related to dates and timestamps. We have read other posts in
> which other people had similar problems, but not found response.
>
> Our WFS filters are similar to:
>
> http://www.opengis.net/ogc;>
> 
>   FH_TIMESTAMP
>   
>   2015-06-08 12:00:00
>   
>   
>   2015-06-08 13:00:00
>   
> 
> ...
>
> Here in Spain, we work in GMT+1. The FH_TIMESTAMP field is defined as
> TIMESTAMP in the related table. Tomcat where GeoServer is deployed is set
> as defaulta to GMT.
> This query must return a single result with date/time 2015-06-08 12:12:01.
> Indeed it is recovering, but the response shows 10:12:01 instead of
> 12:12:01. Also, the date field (Date type in BD ... ), from which the
> timestamp is generated, is one day late:
>
> *2015-06-07Z*
> 2015-06-08T*10:12:01*Z
>
> Geoserver The log shows the following information for this request:
>
> 03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - SELECT * FROM (? SELECT
> FH_FECHA, FH_TIMESTAMP, ..., as GEOM GEOM FROM ... WHERE (FH_TIMESTAMP
> BETWEEN ? AND ?)) WHERE ROWNUM <= 2000
> 03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 1 = 2015-06-08 12:00:00.0
> 07/03/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 2 = 2015-06-08 13:00:00.0
> 07/03/2016 13: 58: 27.503 DEBUG [geotools.jdbc] - 2015-06-08 12: 12:01.0
> is not of type java.sql.Timestamp, attempting conversion
>
> We have tried to make the same request with "geoserver" format. In this
> case, we have to decrease the range of timestamp in two hours in order to
> recover the same data:
>
> 
>  FH_TIMESTAMP
>  
>  2015-06-08T10:00:00Z
>  
>  
>  2015-06-08T11:00:00Z
>  
>
>
> Result is the same: hour late and erroneous date:
>
> *2015-06-07Z*
> *2015-06-08T10:12:01Z*
>
> Same as for the previous query.
>
> What should we do to show to avoid previous day's date and time with two
> hours late?
>
> Any help is welcome.
>
> Thank you very much, greetings
>
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Problem with timestamps and Oracle datastore

[DGIS Devels]

Hi all,

we are having problems retrieving data using WFS from a oracle datastore,
specifically related to dates and timestamps. We have read other posts in
which other people had similar problems, but not found response.

Our WFS filters are similar to:

http://www.opengis.net/ogc;>

  FH_TIMESTAMP
  
  2015-06-08 12:00:00
  
  
  2015-06-08 13:00:00
  

...

Here in Spain, we work in GMT+1. The FH_TIMESTAMP field is defined as
TIMESTAMP in the related table. Tomcat where GeoServer is deployed is set
as defaulta to GMT.
This query must return a single result with date/time 2015-06-08
12:12:01. Indeed
it is recovering, but the response shows 10:12:01 instead of 12:12:01.
Also, the date field (Date type in BD ... ), from which the timestamp is
generated, is one day late:

*2015-06-07Z*
2015-06-08T*10:12:01*Z

Geoserver The log shows the following information for this request:

03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - SELECT * FROM (? SELECT
FH_FECHA, FH_TIMESTAMP, ..., as GEOM GEOM FROM ... WHERE (FH_TIMESTAMP
BETWEEN ? AND ?)) WHERE ROWNUM <= 2000
03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 1 = 2015-06-08 12:00:00.0
07/03/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 2 = 2015-06-08 13:00:00.0
07/03/2016 13: 58: 27.503 DEBUG [geotools.jdbc] - 2015-06-08 12: 12:01.0 is
not of type java.sql.Timestamp, attempting conversion

We have tried to make the same request with "geoserver" format. In this
case, we have to decrease the range of timestamp in two hours in order to
recover the same data:


 FH_TIMESTAMP
 
 2015-06-08T10:00:00Z
 
 
 2015-06-08T11:00:00Z
 
   

Result is the same: hour late and erroneous date:

*2015-06-07Z*
*2015-06-08T10:12:01Z*

Same as for the previous query.

What should we do to show to avoid previous day's date and time with two
hours late?

Any help is welcome.

Thank you very much, greetings
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Problem with timestamps and Oracle datastore

[DGIS Devels]

Hi all,

we are having problems retrieving data using WFS from a oracle datastore,
specifically related to dates and timestamps. We have read other posts in
which other people had similar problems, but not found response.

Our WFS filters are similar to:

http://www.opengis.net/ogc;>

  FH_TIMESTAMP
  
  2015-06-08 12:00:00
  
  
  2015-06-08 13:00:00
  

...

Here in Spain, we work in GMT+1. The FH_TIMESTAMP field is defined as
TIMESTAMP in the related table. Tomcat where GeoServer is deployed is set
as defaulta to GMT.
This query must return a single result with date/time 2015-06-08
12:12:01. Indeed
it is recovering, but the response shows 10:12:01 instead of 12:12:01.
Also, the date field (Date type in BD ... ), from which the timestamp is
generated, is one day late:

*2015-06-07Z*
2015-06-08T*10:12:01*Z

Geoserver The log shows the following information for this request:

03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - SELECT * FROM (? SELECT
FH_FECHA, FH_TIMESTAMP, ..., as GEOM GEOM FROM ... WHERE (FH_TIMESTAMP
BETWEEN ? AND ?)) WHERE ROWNUM <= 2000
03/07/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 1 = 2015-06-08 12:00:00.0
07/03/2016 13: 58: 27.468 DEBUG [geotools.jdbc] - 2 = 2015-06-08 13:00:00.0
07/03/2016 13: 58: 27.503 DEBUG [geotools.jdbc] - 2015-06-08 12: 12:01.0 is
not of type java.sql.Timestamp, attempting conversion

We have tried to make the same request with "geoserver" format. In this
case, we have to decrease the range of timestamp in two hours in order to
recover the same data:


 FH_TIMESTAMP
 
 2015-06-08T10:00:00Z
 
 
 2015-06-08T11:00:00Z
 
   

Result is the same: hour late and erroneous date:

*2015-06-07Z*
*2015-06-08T10:12:01Z*

Same as for the previous query.

What should we do to show to avoid previous day's date and time with two
hours late?

Any help is welcome.

Thank you very much, greetings
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users