WMS layers can be queriable or not (ie: allow GetFeatureInfo calls).
Such support can be fetched by GetCapabilities call.
DOL doesn't perform GetCapabilities, but still we can let administrator specify that manually.
Such option would allow the 'query' tool to avoid prompting for unqueriable layers in the interface
or at least let user know about that if allowing override nonetheless.

Comments

tmcw’s picture

tmcw CreditAttribution: tmcw commented

strk: the ability to query WMS was built up in the Nice Map module and it's decently modular - doesn't require Drupal, etc.

It might be possible to bring that into this module. My main concern is not integration proper, but that the layer addition and editing process isn't currently built to do multi-step forms or ahah forms, which a query would certainly require.

zzolo’s picture

zzolo CreditAttribution: zzolo commented

A multistep form would not really be all that possible, but utilizing some AHAH should be alright in the current architecture.

tmcw’s picture

tmcw CreditAttribution: tmcw commented

Anyway, let's not overcomplicate this: it's okay to add an option to WMS layers indicating that they're queriable, although it might also make sense to simply query all WMS layers and allow those not supporting queries to fail.

zzolo’s picture

zzolo CreditAttribution: zzolo commented

Yeah, although checking if a WMS is queryable may be expensive, I don't think most users are going to know whether it is or not, though most users that need WMS may already have higher level knowledge.

strk’s picture

strk CreditAttribution: strk commented
Status: Active » Closed (works as designed)

Let's forget about this. I've added the checkbox with a form_alter in my dolpp module (the same adding the query behavior).
If you'll like it we'll think about possible integrations.