[Geoserver-devel] R: [Geotools-devel] Attacking the tiling rendering issues (Geoserver, but uDig too)

GeoServer GeoServer Developer
1

-----Messaggio originale-----
Da: geotools-devel-bounces@lists.sourceforge.net
[mailto:geotools-devel-bounces@lists.sourceforge.net] Per
conto di Andrea Aime
Inviato: giovedì 4 gennaio 2007 8.56
A: Jody Garnett
Cc: Geotools-Devel list
Oggetto: Re: [Geotools-devel] [Geoserver-devel] Attacking the
tiling rendering issues (Geoserver, but uDig too)

Jody Garnett ha scritto:
> I think that the person configuring GeoServer is in a much
> better position to specify this guess then the client making the
> requests. Ie provide you guess once as part of layer configuration
> rather then part of each and every request.

Not possible in Geoserver. Every request can associate each layer with
a different SLD, having a buffer configured on the feature type (==
layer in geoserver) would be inconsistent with the ability to require
whatever SLD you want, or make up yours (getMap with user
provided SLD).

From a user point of view, I'd prefer to configure Geoserver, setting the metabuffer size once for every layer (== feature type). This not only for convenience, but it can happen one is using a third party WMS client library and it could be impossible or at least time-consuming to properly configure in order to have it supply the custom WMS hints (if I understand well, the metabuffer options have to be supplied as part of every WMS request).

I don't understand why this is not possible, at least regarding the metabuffer issue, which is one parameter (extra pixel size for every feature type). The extra pixel size has only the effect to take into consideration for rendering a bigger number of features, but the SLD has to be applied as usual, regardless of its origin (default style, specified in the request, custom SLD).

Am I missing something?

Cheers,

Fabio

2

Fabio Da Soghe ha scritto:

From a user point of view, I'd prefer to configure Geoserver,
setting the metabuffer size once for every layer (== feature type).
This not only for convenience, but it can happen one is using a
third party WMS client library and it could be impossible or at
least time-consuming to properly configure in order to have it
supply the custom WMS hints (if I understand well, the metabuffer
options have to be supplied as part of every WMS request).

Ouch... what clients do you know that make providing custom
WMS parameters hard/impossible?

I don't understand why this is not possible, at least regarding the
metabuffer issue, which is one parameter (extra pixel size for every
feature type). The extra pixel size has only the effect to take into
consideration for rendering a bigger number of features, but the SLD
has to be applied as usual, regardless of its origin (default style,
specified in the request, custom SLD).

What I mean, is that the user provides an SLD, then whatever buffer
you set against the FeatureType (in the geoserver configuration) may
be too small.
My point is, the metabuffer size is related to the SLD you're using.
Since GetMap allows the user to decide whatever SLD he may want, he
has to provide us with a proper metabuffer as well.

Moreover, I don't want to spend another half a day just to add
a single parameter to Geoserver... I may end up to, but the very
idea of putting my hands again in that mess makes me shiver...

Cheers
Andrea