Identify Widget 3.1

[GeorgePapamihalakis]

Hi I just added this widget to my Flex - application builder site, and when I click on the icon nothing comes up. Not even an error message. Im sure this is simple, but what could I be missing? Any help would be appreciated. Thanks.

[jjchan]

Hi Robert,

Thanks, I understand, I will take that into mind.  But shouldn't have the <excludebasemaps> tag handled that unsupported issue? I also tried using the <excludelayer> tag to no avail.

Also, interestingly, if at runtime I switched from a previously set 'safe' basemap like Imagery to that 'Imagery with labels' basemap, the Identify widget works as normal. Any further clarification is appreciated and I am very grateful for all the helpful widgets you have contributed to date.

Cheers,

Jj

[RobertScheitlin__GISP]

JJ,

  When you say

(ie, it doesn't do/prompt anything after a selection)

that is strange because the latest version 3.1.4 that I am testing when you click on the map it switches to the results view and state no results found and then a couple of seconds latter switches back to the identify tools view.

The "Imagery with Labels" in my testing does return results identical to the result that the "Imagery" basemap returns.

In my testing it is only the "Terrain with Labels", "Light Gray Canvas", "USA Topo Maps" and "Streets" that produces no results.
The only Basemap that just cause the widget to do nothing is the "OpenStreetMap" as long as I have onlythese set to false?

<layers onlythese="false">

If you set it to true then you need to list each basemap in your layers list for the IdentifyWidget.xml

[jjchan]

Hi Robert,

Thanks for the feedback and taking time to test. Yeah it is strange that it behaves differently on my end as I am also using 3.1.4.

Sorry for being a bit vague though, but my problem wasn't about the basemaps not returning results, actually I don't want them drilled for info by the widget, hence my use of <excludebasemaps> tag to true. My problem was the presence/ absence of a particular basemap somehow affects the functionality of the identify widget across my operational layers regardless if <excludebasemaps>,<onlythese>, <excludelayer> settings were set appropriately (I think). I'll check my config again, thanks.

Cheers,

Janssen

[RobertScheitlin__GISP]

Janssen,

   Strange... The more detailed info you provide the more support I can provide. The use of the excludebasemaps should not have anything to do with operational layers.