That is a very good question that you should take up with OGC. They are
attempting to redefine/ignore the notions of "version" and "release" by
rewriting history.
On 22/06/12 10:23, Brett Walker wrote:
> If there are two versions, how do you distinguish between them? I would have
> thought sch
Hi Ben,
If there are two versions, how do you distinguish between them? I would have
thought schemas would have changed by version number rather than duplicating
Brett
-Original Message-
From: Ben Caradoc-Davies [mailto:[email protected]]
Sent: Friday, 22 June 2012 12:09 PM
I think that is about it.
Even for app-schema, we might just have to update test dependencies
(like rebuilding all the schema-bundle jar artifacts). It might be more
of an impact for GeoServer app-schema users, who will have to purge
their schema caches and catalogs or risk validation inconsist
Hey Brett,
Sounds reasonable to me, feel free to submit a patch for this stuff.
-Justin
On Wed, Jun 20, 2012 at 7:09 PM, Brett Walker
wrote:
> ** **
>
> Hi Justin,
>
> ** **
>
> I’m being a bit picky, but the method PostGISTestSetup.isVersion2() I would
> rename to PostGISTestSetup.isAtlea
Just to chime in that outside of app-schema (who actually needs xlink) i
don't see this as been too far reaching. The latest versions of the cite
tests which we now run against requires the new xlink schemas and we didn't
have to change anything for them.
So I think outside of app-schema all that
Dear all,
I recently chatted to Jody about the vector grids module (gt-grids)
which has been sitting in unsupported for some time. The module is
described here:
http://docs.geotools.org/latest/userguide/unsupported/grid.html
There is an old proposal for it to be promoted here:
http://docs.codeh
>
> Ugh, implemented as you suggest it will affect performance of WPS chaining a
> lot.
>
> This is due to the removal of the subCollection methods, which are the only
> way to have a streaming process
> (one that returns a computing collection) compute less data if a downstream
> process nee
