Keith Jenkins

There are (at least) three types of information we might want to consider. 1. DEFINITIONS: Both ISO 19110 and FGDC CSDGM metadata commonly include attribute definitions. Displaying these definitions for...

@KarenMajewicz Yes, I was thinking in terms of improving the display that depends on WMS (or WFS). For datasets lacking such web services, the whole data dictionary could be displayed,...

p.s. The json GeoFeatureInfo response also includes geojson for the feature, which would make it relatively simple to highlight the selected feature on the map. (See also #606)

Just to clarify, I was talking about WMS GetFeatureInfo (not WFS). I looked at the WMS 1.1.1 spec and it says that GetFeatureInfo support is optional, so I guess there...

Yes, the licensing part is an obstacle. I've only started to investigate this, and it's not easy to even find the appropriate terms of service and free usage limits. If...

still need to investigate the imagery options...

I tested this record in our local dev instance, and it looks like it is sending 2 feature requests (not sure why 2, but they have slightly different bounding boxes)...

It looks like the [FeatureServer](https://mapservices.legis.wisconsin.gov/arcgis/rest/services/WLIP/Parcels/FeatureServer) doesn't currently advertise any "Min Scale", although the corresponding [MapServer](https://mapservices.legis.wisconsin.gov/arcgis/rest/services/WLIP/Parcels/MapServer) does. But I also see a 1000 feature limit on the FeatureServer, so maybe the...

Oh, wait, [FeatureServer/0](https://mapservices.legis.wisconsin.gov/arcgis/rest/services/WLIP/Parcels/FeatureServer/0) does have a "Min Scale" -- I didn't have the `/0` at the end.

I think the test record above was to an image in Artstor, which has since moved to IIIF Image API 2.0 so this is no longer an issue for us....