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 <webgisdesarro...@gmail.com> 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 <ijtur...@gmail.com>:
>
>> 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 <webgisdesarro...@gmail.com>
>> 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 <webgisdesarro...@gmail.com>:
>>>
>>>> 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:
>>>>
>>>> <Ogc:Filter xmlns:ogc = "http://www.opengis.net/ogc";>
>>>>         <Ogc:PropertyIsBetween>
>>>>           <Ogc:PropertyName>FH_TIMESTAMP</ogc:PropertyName>
>>>>           <Ogc:LowerBoundary>
>>>>               <Ogc:Literal>2015-06-08 12:00:00</ogc:Literal>
>>>>           </Ogc:LowerBoundary>
>>>>           <Ogc:UpperBoundary>
>>>>               <Ogc:Literal>2015-06-08 13:00:00</ogc:Literal>
>>>>           </Ogc:UpperBoundary>
>>>>         </Ogc:PropertyIsBetween>
>>>> ...
>>>>
>>>> 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:
>>>>
>>>> <Xxx:FH_FECHA>*2015-06-07Z*</xxx:FH_FECHA>
>>>> <xxx:FH_TIMESTAMP>2015-06-08T*10:12:01*Z</xxx:FH_TIMESTAMP>
>>>>
>>>> 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:
>>>>
>>>> <Ogc:PropertyIsBetween>
>>>>          <Ogc:PropertyName>FH_TIMESTAMP</ogc:PropertyName>
>>>>          <Ogc:LowerBoundary>
>>>>              <Ogc:Literal>2015-06-08T10:00:00Z</ogc:Literal>
>>>>          </Ogc:LowerBoundary>
>>>>          <Ogc:UpperBoundary>
>>>>              <Ogc:Literal>2015-06-08T11:00:00Z</ogc:Literal>
>>>>          </Ogc:UpperBoundary>
>>>>        </Ogc:PropertyIsBetween>
>>>>
>>>> Result is the same: hour late and erroneous date:
>>>>
>>>> <Xxx:FH_FECHA>*2015-06-07Z*</xxx:FH_FECHA>
>>>> <xxx:FH_TIMESTAMP>*2015-06-08T10:12:01Z*</xxx:FH_TIMESTAMP>
>>>>
>>>> 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&iu=/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&iu=/4140
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to