Stephen Woodbridge wrote:
Daniel,
Thanks. What do you think of adding it to the 5.0 plans to add
MAXEXTENTS tag to the MAP object that would do this? This question seems
to come up fairly regularly in one context of another.
I think this would be a good idea, but that would require more
discussion, at least in a bug and maybe in a RFC.
It's more than just adding a parameter, we also need to define the
behavior in various situations where the map would exceed the allowed
extent:
- When panning (fairly trivial: just stop panning at the maxextent limit)
- When zomming out (do you allow zooming out far enough to see data
outside of allowed extent?)
- When doing an explicit call to setExtent() (or setting extent via CGI
or WMS BBOX args), what do you do if requested extent is not inside
MAXEXTENT?
There may be other situations that need to be addressed that I didn't
think of yet.
Daniel
--
Daniel Morissette
http://www.mapgears.com/
