Mike,
On 7/31/07, Mike Adair <[EMAIL PROTECTED]> wrote:
> As for GetFeatureInfo, mapViewer and OWSExplorer demos use a different
> implementation than lib/widget/GetFeatureInfo because at the time I
> wanted to implement that using the WebServiceRequest tool. This is a
> little more consistent wi
First off, I apologize for missing the meeting this morning, I
completely forgot about it.
The intent of the OWSExplorer demo is to point to a WMS and/or WFS
instance and see what layers and feature types are available and
visualizing them on the map. It is set up by default to look for a
Geo
To clarify another question from today's meeting:
demo/mapViewer/GetFeatureInfo.js can be replaced by
lib/widget/GetFeatureInfo.js. I just tried both in the mapViewer
example, and both work. Only the widget config parameters are
different: demo/mapViewer/GetFeatureInfo.js takes the map in the
targ
Hi,
as discussed in today's team meeting, I fixed a TBD in
lib/widget/GetFeatureInfo.js: infoFormat is now configurable.
Anyway, I have the impression that GetFeatureInfo.js does a lot that
should be done by the WebServiceRequest.js tool. Since I have not
designed or written either of these files
