GeoServer

Allow user to request limited capabilities from a WMS

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.7.0-RC1
  • Fix Version/s: 2.0.x
  • Component/s: WMS
  • Labels:
    None
  • Number of attachments :
    0

Description

Awhile ago we had a discussion about returning a less heavy capabilities document from GeoSErver's WMS. It's great that we support so many projections, but it causes grief on a number of clients not built for it. Like javascript ones and ArcMap which just doesn't seem to be that fast at parsing XML. The full conversation is at http://www.nabble.com/Re%3A-heavy-capabilities-p17532793.html

Andrea suggested we do something like:

http://.../ows?SERVICE=WMS&REQUEST=GetCapabilities&srsProfile=limited

(http://www.nabble.com/heavy-capabilities-td17523886.html)

I think this makes a lot of sense. We could even have clients supply a list of srs's they care about srsProfile=limited,5543,5432 or something. Or even just srs=4326, as many clients will probably already know what projection they want it in?

If we have this in place then we can have ArcMap work much better with our stuff, we just tell those users to supply the extra parameter when they input the geoserver capabilities document in to their desktop client.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

We already added the ability to limit the advertised SRS. Is any more work required for this one?

Show
Andrea Aime added a comment - We already added the ability to limit the advertised SRS. Is any more work required for this one?
Hide
Permalink
Andrea Aime added a comment -

So, shall we add dynamic filtering or is what we have today (static srs list limiting) ok?

Show
Andrea Aime added a comment - So, shall we add dynamic filtering or is what we have today (static srs list limiting) ok?
Hide
Permalink
Andrea Aime added a comment -

So I added namespace based filtering in GEOS-2471.

Should we also add this srsProfile param?

Show
Andrea Aime added a comment - So I added namespace based filtering in GEOS-2471 . Should we also add this srsProfile param?
Hide
Permalink
Andrea Aime added a comment -

Talking with Tim we agreed it would be sufficient to have a single profile, profile=minimum, that only lists 4326, 900913 and the native srs of the layers contained in the capabilities. this is easy to implement as it requres no server side profile configuration.
If everybody agrees this is what we need, I can handle this quickly.

Show
Andrea Aime added a comment - Talking with Tim we agreed it would be sufficient to have a single profile, profile=minimum, that only lists 4326, 900913 and the native srs of the layers contained in the capabilities. this is easy to implement as it requres no server side profile configuration. If everybody agrees this is what we need, I can handle this quickly.
Hide
Permalink
Chris Holmes added a comment -

+1, that seems sufficient to me. Covers a nice majority of the use cases.

Show
Chris Holmes added a comment - +1, that seems sufficient to me. Covers a nice majority of the use cases.
Hide
Permalink
Andrea Aime added a comment -

Since we've agreed to put 1.7.x in "bugfix mode" I'm moving this one on 2.0.x

Show
Andrea Aime added a comment - Since we've agreed to put 1.7.x in "bugfix mode" I'm moving this one on 2.0.x
Hide
Permalink
Andrea Aime added a comment -

Wondering if we should make this one a admin level config or a request param. At Bolsena people kept on complaining that by default we list too many SRS

Show
Andrea Aime added a comment - Wondering if we should make this one a admin level config or a request param. At Bolsena people kept on complaining that by default we list too many SRS

People

  • Assignee:
    Andrea Aime
    Reporter:
    Chris Holmes
Vote (1)
Watch (3)

Dates

  • Created:
    Updated: