Hi

Multiple divs with the same id sounds very likely to be a source of problems. I'd be thinking that would cause the javascript a lot of confusion which would only generate errors within the browser. The server processes would have no idea this was happening and would not log any errors.

I'm presuming from your question that you are using the "Reporting page (customisable)".

Inspecting the code I see there is an undocumented option for the map_panel() in client_helpers/map_helper called divId. Setting

@divId=namweb

under the [map] section of the Form Structure does allow us to control the name of the map div. This may allow you to get your maps working. However, they will all appear inside divs with a hard-coded name of 'map-container'. This is not very clever but browsers may be kind enough to overlook this.

To not show the report grid I would have expected just to remove the [report_grid] section from the Form Structure. However, when I do this the map shows no records.

You say

Where do you see this? That option defaults to false and it is not immediately obvious to me that it is being set to true.

A possible workaround would be to use the Report Map form instead as that is designed for outputting a map alone.

Jim Bacon.

Hi Alice,

That makes things lots clearer! I realised you had a panels page but I assumed you were using panels to assemble content from several different Indicia pages created as separate nodes. I've just had a play at doing that, as it would avoid the need for writing any code, but I got lots of JavaScript errors.

The "Reporting page (customisable)" I refer to is called the "Dynamic Report Explorer" in your version of the code. I use the development code from GitHub.

Let's return to your original question then, based upon the code example you are using. To get the data for each map but without the need for a grid, you can replace the call to report_helper::report_grid() with report_helper::report_map().

To wire up each report to each map... ahh... it looks to me like the code has been written in the assumption of there being only one map to a page.

Sorry. I think we are stuck again where you have envisaged something that cannot be built without some development work.

An alternative to multiple maps might be to try multiple layers on one map I suppose.

Jim Bacon.

Hi Alice,

My look at the code yesterday, which is completely new to me and not well commented, left me with the impression that the dynamic report explorer would suffer from the same problem that we were having with the multiple maps; that all of the features from all the reports appear to be added to a single, global, report layer. I'd like to feel more authoritative on the subject but that would take a lot more effort.

There is a Distribution 3 map which supports 3 layers which might be enough to get you round this current difficulty.

Regarding the click to query, see this thread, http://forums.nbn.org.uk/viewtopic.php?id=6059%29

Jim Bacon.