Brent Fraser

You suggestion doesn't work. I've setup a map-source: ``` https://demo.mapserver.org/cgi-bin/wfs? ``` GeoMoose sends ``` https://demo.mapserver.org/cgi-bin/wfs?srsname=EPSG%3A4326&outputFormat=text%2Fxml%3B+subtype%3Dgml%2F2.1.2&service=WFS&version=1.1.0&request=GetFeature&bbox=-10378290.697282547%2C5463768.038048627%2C-10330823.302717453%2C5520255.001951372%2CEPSG%3A3857&cross-origin=anonymous&typename=ms%3Acities ``` Which in general looks OK, except the bbox is in EPSG:3857 (proj is given...

You could set it in the mapsource's param in the mapbook, but the problem is GM does not have the code in place to handle the returned geojson (or the...

Some similar info at #546

TBD: Test on PR #787

GeoJSON would include the geometry useful for highlighting the feature. I had mentioned the WFS code 'cuz it shows how to allow GML or GeoJSON. So a little bit of...

I think the spec is somewhat quiet on the acceptable (and accepted) values of [INFO_FORMAT](https://cite.opengeospatial.org/OGCTestData/wms/1.1.1/spec/wms1.1.1.html#wmsops.getfeatureinfo.params). GeoServer WMS and ArcGIS Server (MapServer-WMS) seem to support GeoJSON. And for the one WMS...

Got caught on this again. Server lists Identify Formats: application/vnd.esri.wms_raw_xml application/vnd.esri.wms_featureinfo_xml application/vnd.ogc.wms_xml application/geojson text/xml text/html text/plain But no gml.

Now that v3 has embraced the concept of an admin writing app.js, and potentially writing other JavaScript (e.g. plugins), perhaps the solution to parsing and rendering Identify results is to...

While a work-around might be to use `query-as` to a corresponding WFS service, there might not be one.

Yes, it can be a pain. Currently all the the map-source types support a `` tag in the map-source to define a legend graphic to be shown in the catalog...