[Mapbender-users] MB 2.5: Erros in modules loadwmc / overview

[Schönhammer, Herbert]

Hi list,

now I'm doing the second sight for loadwmc. I think, i have found some erros and I have some questions too:

1. Error: Positioning of Overview
=================================
Like in earlier versions of MB 2.5, the overview-picture is positioned wrong in the overview after loading a wmc. The picture in the overview is smaller than the picture in the original gui.

2. Error: German Umlauts in WMS- and Layer-Title
================================================
Yes I know, we should avoid them, but we all must "sell" our work to our chiefs too ;-)

Using german umlauts in a mapserver mapfile and loading this wms in mapbpender, the umlauts are displayed correctly. Saving a wmc, (I think) the umlauts are stored correct too.

But after loading the wmc, the umlauts are not displayed correct.

3. Problem/Error: Which content in Overview ?
==========================================================
In a "normal" gui, the overview picture is generated by a wms. The number of the used wms ist stored in attribute SRC of module overview: ../php/mod_mapOV.php?wms=3&....

Therefore the wms must be loaded into the gui AND the wms must be VISIBLE (if the wms is "hidden", no overview picture is displayed in mapbender; this is a different behavior by comparison to earlier MapBender-versions !).

Let's assume, we use wms "Stadtplan" (WMS id = 3) as wms for generating the overview picture.
Let's assume, the user don't want to see the wms "Stadtplan" (the user switches off the checkbox for this wms; this is possible, because the wms must be visible !). The user chooses other wms.
Now the user saves a wmc and loads this wmc.

After loading the wmc no overview picture is generated. The needed wms is not checked !


3. Suggestions for solution
===========================

3.1 Overview with static pixmap (my priority ONE)
-------------------------------
Mapbender should offer another, second possibility for generating overviews. A pixmap should be used (the limits and epsg-code may be given as a var for module overview).

This pixmap will always be used, independent from user's choice of wms.

Another benefit is, that the server has no not to compute wms requests for overviews.


3.2 The "old" MapBender behavior ist restored (my priority TWO)
----------------------------------------------
If a "hidden" wms could be used (again) for generating overviews, a "hidden" wms with id=0 could ALWAYS be loaded into a gui. So always the same overview is used in a gui, independent of the selected wms.


3.3 Mapbender Extensions in WMC-XML-file (my priority THREE)
========================================
MabBender will also save the WMS for generating the overview picture as a mapbender extension in the wmc file.




Is there a possibility to implement solutions 3.1 and/or 3.2 at once ? Or in the next MB version 2.5.1 ?

Or has anybody a tipp for me, how to restore the old mapbender behavior ?

greetings
Schoenhammer Herbert