Hi Andreas,

On Tue, 2007-12-04 at 01:31 +0100, Andreas Hocevar wrote:
> I know there was already some discussion about this on the list. What
> if we have the following in an OWS Context document:
> 
>     <Layer queryable="1" hidden="0">
>       <Server service="OGC:WMS-C" version="1.0.0" title="OGC:WMS-C">
>         <OnlineResource xlink:type="simple" xlink:href="/geoserver/wms?"/>
>       </Server>

Just curious: do yo refer to WMS-C as a Tile Cache WMS or Component WMS?
We so happen to be working with the latter for a project. I was curious
if you've done something with that.

Hmm, thinking of this: OGC will use the name WMS-C for Component WMS.
This is where a lot of confusing will be introduced. How will we deal
with this?

> By the way, I have extended widget/GetFeatureInfoWSR.js,
> model/OwsContext.js and tool/wfs_GetFeature to provide this simulated
> wms:GetFeatureInfo using wfs:GetFeature, with a tolerance. See the
> attached patch (note that the patch for GetFeatureInfoWSR also
> contains some bugfixes).
> 
> If you think that it is a good idea to do this, I would like to add
> this to the trunk and the 1.5 release.

Sounds like a very good idea. I have my concerns about the patch (and in
fact, the original code in GetFeatureInfoWSR.js) in regards to the use
of layerName... ;-)
Would you like to change that yourself or shall I fix things in the
trunk so you can create a new patch?

Regards, Roald

-- 
Roald de Wit
Software Engineer
[EMAIL PROTECTED]

Commercial Support for Open Source GIS Software
http://lisasoft.com/LISAsoft/SupportedProducts/


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
mapbuilder-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel

Reply via email to