I agree with Tom. The idea of joining the 2 services so explicitly in the Context encoding is also limiting or misleading in a way, because there are scenarios where the "navigation" WMS doesn't need to be showing the same data as the "download" WFS.
If the interest is in a general way to signal that two or more services only make sense when used together, maybe a better idea is to allow nested <ResourceList>s, and give that element some metadata, like a title and abstract. --- Raj On Sep 6, 2007, at 8:24 AM, Kralidis,Tom [Burlington] wrote: > > >> -----Original Message----- >> From: Cameron Shorter [mailto:[EMAIL PROTECTED] >> Sent: 05 September, 2007 4:41 PM >> To: [EMAIL PROTECTED]; >> '[email protected]'; Kralidis,Tom [Burlington] >> Subject: Associating WMS and WFS in the same layer >> >> Tom, >> Another OWS Context question. >> In the CGDI Pilot we are working on, there is a requirement >> to find and then download GML from a WFS. >> >> When finding a dataset, a user will generally want to use WMS >> interface to view datasets because it requires less >> bandwidth. Then when the Area Of Interest has been selected, >> the user will download the dataset using WFS. >> >> In order to do this, we need to associate a WMS layer with a >> WFS layer. >> I think this should be done using something like: >> >> <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"> >> <OnlineResource xlink:type="simple" >> xlink:href="http://localhost:8080/wms"/> >> </Server> >> <Name>basic</Name> >> <Title>World Basemap</Title> >> <SRS>EPSG:4326</SRS> >> </Layer> >> >> >> Note, this means that a WFS layer should be inserted inside a >> <Layer> tag instead of a <FeatureType> tag. >> This comment could be extended to showing the same layer as >> KML, Tiled WMS, ... >> >> Tom, what are your thoughts on this? >> > > Isn't this what WMS DescribeLayer is for? What I would do is a WMS > DescribeLayer request, which would tell you if a layer if WFS-able or > not; if it is, then mark as extractable in your client and chain > along. > > Would this be feasible? > > ..Tom > > _______________________________________________ > Context.rwg mailing list > [EMAIL PROTECTED] > https://mail.opengeospatial.org/mailman/listinfo/context.rwg ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
