Hi all,
just a quick note to introduce Ben Caradoc-Davies at CSIRO in Perth, Australia,
who will be working on reference implementations of web services against data
models, especially the GeoSciML and Observations & Measurements standards.
Ben will be working with my support, to address the h
+1000 from us too.
We have a couple of short-term hacks to do on the 2.4 branch to meet a short
term deadline and get Ben familiar with the test-cases I've been setting up.
Migrating these test case to trunk is the first step, then backfilling the
functionality to make them work.
Its been a
> My initial feedback was more about how to advertise what functions are
> available -
allowing only these functions is possibly the higher priority.
> so geoserver can report them as available etc.
>There is one thing to check in the WFS specification; I am under the
impression that server n
OK - I suppose thats a valid sanity check - not enough info to help formulate
the request, since you dont even know what attributes of what feature types it
applies to, but you can reject some dumb ones. Anyway, its such a trivial thing
to advertise them we can do it now. I was just sceptical a
When I get off the road and back to my desk I'll have a look at the "prepared
statement" architecture of H2 and decide how that affects the SQL-view
perspective. We are also thinking about blowing apart the complex-datastore
GroupingFeatureIterator to allow it to map multiple source "back end f
Thanks Chris
These are of course exactly the right sort of questions.
And the good news is that we do indeed have a long term capability and
willingness to support bug fixing, test support and build processes the changes.
The bad news is that testing of such stuff is extremely difficult until w
