Tim Schaub wrote:
> This gets beyond the initial motivation, but as long as we're talking
> about allowing a client to ask for a filtered set of capabilities, is it
> nuts to think about BBOX and SRS filters?
>
I think the part you are missing here is a catalog right? ie it already
has all th
Tim Schaub ha scritto:
...
>> Since we have a human in the middle (either as the programmer that sets
>> up the connection to a well known server, or as the user that pastes
>> the capabilities) we could provide him with options, profiles, that
>> would generate different capabilities documents. St
Hey-
Andrea Aime wrote:
> Tim Schaub ha scritto:
>> Hey-
>>
>> A small exercise with my results next to each step.
>>
>> 1) Click:
>> http://sigma.openplans.org/geoserver/ows?SERVICE=WMS&REQUEST=GetCapabilities
>>
>> (wait 3 seconds)
>
> Hum, how curious. I've tested the same, and for me it take
Tim Schaub ha scritto:
> Hey-
>
> A small exercise with my results next to each step.
>
> 1) Click:
> http://sigma.openplans.org/geoserver/ows?SERVICE=WMS&REQUEST=GetCapabilities
> (wait 3 seconds)
Hum, how curious. I've tested the same, and for me it takes between 1
and 2. Checked the response
What about allowing the client to limit the number of SRSs?
I'm thinking adding a parameter
1) Specifying a list of projections of interest (GeoServer would return
the intersection)
or
2) A numeric limit?
That way it can have as much cake as it can handle, and not change the
default behavior ;)
Paul Ramsey wrote:
> I think it's a terrible idea! Firefox is not the expected client for a
> OWS capabilities file, and by restricting the SRSs you advertise
> you're restricting the power of your server: a client cannot request
> an SRS it thinks you don't support! You have this wonderful SRS
>
Yeah, I see the point... but then how does a server that supports the
entire epsg database avoid overloading a client? I mean sure maybe the
browser is not the intended client for a WMS capabilities document but
its not absurd to think that a client will be storing the parsed
capabilities docum
I think it's a terrible idea! Firefox is not the expected client for a
OWS capabilities file, and by restricting the SRSs you advertise
you're restricting the power of your server: a client cannot request
an SRS it thinks you don't support! You have this wonderful SRS
engine behind Geoserver, that
Hi Tim;
The OGC model of open web services is in fact very heavy. Some of the
later specifications include a number so you can tell if your local
cache is any good you will actually find that GeoServer is one of
the faster WMS servers out there; Ionic servers are much much slower and
ofte
Hi Tim,
I think your suggestion makes sense. One thing we could probably do is
on startup check each layer for its SRS and only include those in the
default capabilities document. If the user wants to change it after that
they are free to do so.
It would take a bit of book keeping to manage wh
Hey-
A small exercise with my results next to each step.
1) Click:
http://sigma.openplans.org/geoserver/ows?SERVICE=WMS&REQUEST=GetCapabilities
(wait 3 seconds)
2) Save the result to your desktop, call it ows.xml.
3) Drag ows.xml into Firefox (wait 10 seconds).
Granted, the delay in step one is
11 matches
Mail list logo
