Bug 459

Summary: WMSBrowser: Write MINSCALE MAXSCALE values
Product: Chameleon Reporter: Bart van den Eijnden <bartvde@osgis.nl>
Component: WidgetAssignee: chameleon-dev <chameleon-dev@lists.maptools.org>
Status: RESOLVED FIXED    
Severity: enhancement    
Priority: P2    
Version: 1.99   
Target Milestone: FUTURE   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description From 2004-06-21 10:34:15 
Is it possible for layers which get added through the WMSBrowser widget to get
MINSCALE and MAXSCALE values according to the Scalehint values from the WMS
Capabilities?

I notice this behaviour because of the newly developed Legend template widget
keyword which acts upon scale dependent layers which run out of scale. This does
not work with added layers through the WMSBrowser widget, as the MINSCALE and
MAXSCALE values don't get written in the session MAP file.
------- Comment #1 From 2004-06-21 10:46:54 ------- 
I see after a quick research that this is more complex than I thought.

The wmsparse utility does not parse Scalehint values :(

Also, PHP/Mapscript does not yet have a function which takes a Scalehint value
and calculates the MINSCALE or MAXSCALE. Ofcourse, this could be done in PHP
itself, but IMHO it would be best to have this in PHP/Mapscript.

Any thoughts?
------- Comment #2 From 2004-06-23 07:06:10 ------- 
this will likely require changes to wmsparse to capture scalehint, plus to all
the php-based wms code to capture and propogate the new fields.
------- Comment #3 From 2004-07-08 12:57:52 ------- 
Changed target to 2.1.
------- Comment #4 From 2004-08-10 16:03:05 ------- 
Changed Target Milestone to FUTURE. (Enhancements may be moved from this target 
to specific "versioned" targets after product design review cycles.)
------- Comment #5 From 2004-08-11 03:17:52 ------- 
Just sharing another thought on this subject:

When the scalehint values would be parsed by wmsparse this could add additional
handy functionality, i.e. the wmsbrowser could zoom to a value between
minscalehint en maxscalehint, so that scale dependent layers will always be
viewable.
------- Comment #6 From 2005-05-27 08:18:26 ------- 
This has been incorporated into Chameleon on a contract to Geodan.