For a WFS FeatureType layer, we should be able to store the maximum features that should be used to query the layer.

A WFS layer can potentially contain a very large dataset that is impractical to download to a client, and/or too large for a client's renderer.

The max number of features may be different for different layers. A point layer may easily handle 1000 features, where a polygon layer may have problems with 100 features. So the context should be able to recommend the MaxFeatures that a WFS query should use.

<FeatureType hidden="0" group="Features">
<ows:Title>roads</ows:Title>

OWS Context and Catalog interfaces don't allow you to associate a WFS Layer with a WMS layer. This would be very useful in a search and discovery interface where a user starts a search using a WMS interface and then changes to WFS when you finally want to download a large dataset.

A context format like the following might work:

<Layer queryable="0" hidden="0">
<Server service="OGC:WMS" version="1.0.0" title="OGC:WMS" default="1">
<OnlineResource xlink:type="simple" xlink:href="http://localhost:8080/wms"/>
</Server>
<Server service="OGC:WFS" version="1.0.0" title="OGC:WFS">

GEO Logo

GEO Header Template

Source: Roger Lott

This is the new Public work page for OWS Context as part of the Mass Market Geo Working Group effort to work with the open source community on areas of interest.

Picture of AI Pilot Capture Workshop participants creating video captures, 10&11 Sept 2007, Washington DC

Group Picture from the GEO AI Pilot Capture Workshop, 10&11 Sept. 2007, Washington, DC

Mosaic of logos from organizations that responded to the GEO AI Pilot Call For Participation, April 2007