Hi Ben, Thank you, I appreciate your advice, you are right, we should try to keep as much conversation as possible on the list. I thought I would try someone I knew to get a some more immediate responses as it seems so far that no other Geoserver ARCSDE users are responding apart of course from the developer Gabriel (thank you Gabriel!). Maybe I am the first one to try date range filter with an ARCSDE store?
Thanks also for putting the URL for this discussion thread onto the Jira ticket GEOT-3507. Hi Miles, Thanks for your ideas. I tried your suggestion of having a maximum of 2 parameters nested in the 1 <And>, instead of 3, but it made no difference i.e I tried <And> LOCATION=B <And> DATE>=X DATE<=Y </And> </And> I also tried a combination "> OR =" for the operation ">=, but no difference. i.e I tried LOCATION=Bilgola AND (OBS_DATE_TIME > x OR OBS_DATE_TIME == x) AND (OBS_DATE_TIME < y OR OBS_DATE_TIME == y) Hi Gabriel, I am going to raise 2 more tickets on Jira Geotools as follows: 1) This issue i.e 'inclusive date range >= AND <= not working' 2) Addition of random 1/1000 seconds value to DATE in GML and CSV output I have investigated these issues as much as I can for now. I know you are really busy with other stuff but is there any chance that you could look into this further. For us this is an important issue to fix for an upcoming project where we want to do time range queries on time series data. For the Geoserver users list, Judging from the lack of responses so far it seems nobody else has come across these problems. I know a lot of people use PostGIS data stores so I was curious if there was a similar issue with PostGIS. Does anyone have time series data on PostGIS store where they do inclusive date range queries and do they work properly? Andrew ----- Original Message ----- From: "Ben Caradoc-Davies" <[email protected]> To: "andrew walsh" <[email protected]> Cc: "Miles Jordan" <[email protected]>; <[email protected]>; "Gabriel Roldán" <[email protected]> Sent: Monday, April 18, 2011 4:40 PM Subject: Re: Geoserver with OGC filter not working with inclusive range >= AND <= > Andrew, > > I encourage you to persist with the list (I'm copying this mail back onto > it). > No doubt others will run into the same problem sooner or later. This might be > an ArcSDE-specific error, in which case you will find more ArcSDE users on > the > list. If not, it may well be something deep in the SQL generation that will > be > of general interest, and you will need the SQL gurus. > > There is a nasty gotcha in the standard Java libraries that a calendar with > uninitialized fields gets those fields initialized to the local time. The > error you are seeing looks a bit like one of these. > > I see you created a Jira issue: > http://jira.codehaus.org/browse/GEOT-3507 > > Please reply on your original thread to let Gabriel know that you have > created > the Jira issue he requested. Jira-generated email can get lost in the flood. > > Kind regards, > Ben. > > On 18/04/11 14:05, andrew walsh wrote: >> Hi Ben and Miles, >> >> I am getting this bug with Geoserver for which I have had a conversation >> on the geoserver users list but so far no real help. So I thought I'd >> better send to you guys as it may have slipped your attention through >> the hundreds of emails on the list. >> >> We are using Geoserver 2.0.1 with an ARSCDE-Oracle (ESRI) data >> store. I have a simple table (point features) that has a time series of SST >> and >> a column with a Oracle DATE type called OBS_DATE_TIME. I want >> to filter the data by inclusive date range using>= and<= but its >> not working. Seems only> and< operators work which isn't good >> enough. >> >> For example try this URL >> (filter is: Bilgola and>=2010-12-12 08:58:00 and =< 2011-01-06 09:12:00 ) >> and you will 1 feature back in GML but you should get 2 features, 1 at >> 2010-12-12 08:58:00 and >> the other at 2011-01-06 09:12:00 >> >> http://www.metoc.gov.au/geoserver/wfs?&VERSION=1.1.0&SERVICE=WFS&REQUEST=GetFeature&; >> TYPENAME=test:TEST.BEACH_TEMPS&Filter=<Filter><And><PropertyIsEqualTo><PropertyName>LOCATION</PropertyName> >> <Literal>Bilgola</Literal></PropertyIsEqualTo><PropertyIsGreaterThanOrEqualTo><PropertyName>OBS_DATE_TIME</PropertyName><Function >> name="dateParse"><Literal>yyyy-MM-dd HH:mm:ss</Literal><Literal>2010-12-12 >> 08:58:00</Literal></Function></PropertyIsGreaterThanOrEqualTo><PropertyIsLessThanOrEqualTo><PropertyName>OBS_DATE_TIME</PropertyName><Function >> name="dateParse"><Literal>yyyy-MM-dd HH:mm:ss</Literal><Literal>2011-01-06 >> 09:12:00</Literal></Function></PropertyIsLessThanOrEqualTo></And></Filter> >> >> One vague theory I have is that a random 1/1000 second value is being added >> to >> timestamp >> i.e see the GML it says 2010-12-12T08:58:00.567 but database is 2010-12-12 >> 08:58:00 >> which is causing the = comparison operation to return false. Actually I >> think >> it >> shouldn't be adding >> the 1/1000 seconds bit and the GML you get back should be >> '2010-12-12T08:58:00.000' >> >> Any ideas about this would be greatly appreciated. >> Any other time range filters out there with Geoserver out that work? >> >> Andrew Walsh >> Data Facilitator AODN >> >> > > -- > Ben Caradoc-Davies <[email protected]> > Software Engineering Team Leader > CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre > > ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
