Hi Andrea,
The Geoserver in question is not under my control (I am accessing it using our
client service, based on geotools). I am trying to provide feedback to the
provider on how to better structure the data. Currently, the time information
is a string of type "first half of 2009" etc, relating to the collection of the
information. The geometries are stored with each record coming in in those
regular intervals, generating a huge number of responses. I know that in
reality there are only <100 geometries. The WFS which is out of our control
seems to have a limit of maxFeatures set to 100 – fair enough, but the way the
data are store means that I cannot filter, and thus cannot access, all the
records I need. I want to provide a guidance for them how better to store
timestamped datasets relating to the same geometries.
Thanks,
Martin
--
Martin Tomko, PhD.
Senior Project Manager, Information Infrastructure Design, AURIN
Level 5, Architecture Building
University of Melbourne VIC 3010
AUSTRALIA
T: +61 3 9035 3298
E: [email protected] <mailto:[email protected]>
W: www.aurin.org.au <www.aurin.org.au>
From: Andrea Aime
<[email protected]<mailto:[email protected]>>
Date: Fri, 30 Sep 2011 08:22:53 +0200
To: Martin Tomko <[email protected]<mailto:[email protected]>>
Cc:
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: Re: [Geoserver-users] Geoserver WFS - Time support
On Fri, Sep 30, 2011 at 5:09 AM, Martin Tomko
<[email protected]<mailto:[email protected]>> wrote:
Dear All,
I am just looking for some pointer and best pracitces on dealing with time
together with Geoserver. In particular, we re confronted with the situation of
a temporal series – data measured for the same features in regular intervals. I
need to be able to assist our data provider with a solution how to serve those
from Geoserver, and enabling temporal filtering. With the current solution, I
rapidly hit the problem with maxFeatures, as each feature is basically
duplicated for each time slot.
WFS allows to filter on whatever attribute you want, can't you filter on a time
span to reduce the number of features?
Btw, what is "the problem with maxFeatures"?
The preview artificially limits the results to 50 to avoid the browsers blowing
up with too much content, but you can remove
that, and the server has a hard limit of one million, but that can be changed
as well (in the wfs configuration panel)
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
