Hi all,
even though the complex-features branch is history, the functionality is
being ported to the mainstream geotools code base. Currently there are
unsupported modules for geotools 2.4 and geoserver trunk. We are
currently remediating a few issues relating to the recently published
Observations and Measurements, SensorML and SensorWebEnablement (SWE)
schems from the OGC.
Please advise if you need more info at this stage. Sorry I wasdnt
watching gt-users - probably wont do this until the modules are reayd
for supported status.
Regards
Rob Atkinson
Andrea Aime wrote:
Andrea Aime ha scritto:
Lourens Veen ha scritto:
On Wednesday 10 October 2007 09:13:37 Andrea Aime wrote:
Lourens Veen ha scritto:
Hello,
What is the status of the complex-features branch? I've been trying to
get it to build, but I can't even get the Geotools part of it to work.
I've asked about that on the gt2-users mailinglist, but haven't had a
reply yet. I'm hoping there's someone here who is working on cf. I seem
to recall something on the wiki about merging it into mainline soon,
perhaps that is half-done and that is the reason for my problems?
I wasn't involved in the complex feature branch so take what I say with
a grain of salt. Yet, afaik the branch is long dead, any attempt to
merge it as is has failed.
Ouch. That is bad news.
Thanks for your quick reply. Perhaps I should explain a bit more about my
problem then, to see if there is another possible solution.
I have a database with observations, and each observation has a location.
These locations are mostly standardised grid blocks, so that often many
observations share the same location. I have a client that has controls to
build a filter on the observations, and an OpenLayers map to retrieve and
display the relevant observations from a Geoserver WFS.
So far so good, except that I get lots of results (this is a _big_ database)
and drawing them all takes way too much time.
Have you considered using the WMS filters instead? It's a custom
GeoServer extension, you can add a &FILTER=XXX to a WMS call and
get filtered results. That should be much faster than retrieving
data via WFS and draw in OpenLayers.
Oh, the description of the custom params is here:
http://docs.codehaus.org/display/GEOSDOC/WMS+vendor+parameters
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
begin:vcard
fn:Rob Atkinson
n:Atkinson;Rob
org:Social Change Online
email;internet:[EMAIL PROTECTED]
title:Principal Consultant
tel;cell:+61 419 202 973
x-mozilla-html:TRUE
url:http://online.socialchange.net.au
version:2.1
end:vcard
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
