search

ROGUE-JCTD / MapLoom

MapLoom is a web mapping client based on OpenLayers 3. It provides full-featured editing capabilities for data stores in GeoServer - including PostGIS and GeoGig. For GeoGig layers, it lets you view history, and sync with other GeoGig repositories
MIT License
70 stars 66 forks source link

No "Identify" feature using remote WMS service #103

Open JJediny opened 10 years ago

JJediny commented 10 years ago

When user adds a new WMS server, clicking on a feature from that remote WMS service does not return GetFeatureInfo

JJediny commented 9 years ago

Dug deeper into this issue; the MapLoom GetFeatureInfo requests the response from any WMS service in JSON format ('application/json' specification). Geoserver only started supporting this response format after version 2.2.4 (See thread: http://sourceforge.net/p/geoserver/mailman/message/30426792/). As a result any WMS service from Geoserver pre 2.2.x, ArcGIS Server, MapServer, etc. aren't able to generate a formatted response.

Related GNIP/Suggestion for consideration - Create a new "External Layer" class in Maploom to separately add and handle external data sources potentially with support for multiple formats so that support for additional services/feeds/formats (ex. WMS 1.1.1, Tile Services - X/Y/Z, KML, GeoJSON, TopoJSON, GPX, CSV, GeoRSS, etc.) can be pulled into OpenLayers3 as overlays without potentially causing compatibility with MapLoom's current usage of JSON/WFS-T for Geogig