[fusion-trac] #176: Legend widget misbehaves when you set
maxscaledenom to a layer that is outside the web min / maxscale
Fusion
trac_fusion at osgeo.org
Wed Nov 19 14:21:46 EST 2008
#176: Legend widget misbehaves when you set maxscaledenom to a layer that is
outside the web min / maxscale
--------------------------+-------------------------------------------------
Reporter: pdeschamps | Owner: madair
Type: defect | Status: new
Priority: P2 | Milestone: 2.0
Component: Widgets | Version: 1.1.0
Severity: Minor | Keywords:
External_id: | State: New
Browser: All | Os: All
--------------------------+-------------------------------------------------
Using fusion 1.1 rev 1581 also reproducible in trunk rev 1675
Using the "/templates/mapserver/standard/" application
Using gmap.
Steps to reproduce:
set your WEB section to this:
{{{
WEB
MINSCALE 2000000
MAXSCALE 50000000
#
# On Windows systems, /tmp and /tmp/ms_tmp/ should be created at the root
# of the drive where the .MAP file resides.
#
IMAGEPATH "/home/pdeschamps/fgs/tmp/ms_tmp/"
IMAGEURL "/home/pdeschamps/fgs/tmp/ms_tmp/"
END
}}}
add the maxscaledenom to the rail layer
{{{
LAYER
NAME rail
MAXSCALEDENOM 1000000
METADATA
"DESCRIPTION" "Railroads"
END
TYPE LINE
STATUS ON
DATA rail
CLASS
NAME "Railroads"
STYLE
SIZE 1
SYMBOL "circle"
COLOR 168 0 184
END
END
END # Layer
}}}
When you set a layer to have a maxscaledenom of 1,000,000 when your
web->maxscale is set to 2,000,000 the legend misbehaves.
Zoom in the the 1:200,000 and notice that the legend has toggled all the
layers as inactive.
Understandable issue as the user should not specify a maxscale or minscale
that is outside of the web's min / maxscale.
--
Ticket URL: <http://trac.osgeo.org/fusion/ticket/176>
Fusion <http://trac.osgeo.org/fusion>
Fusion is a web-mapping application development framework for MapServer and MapGuide OS.
More information about the fusion-trac
mailing list