LatLongBoundingBox?

[Russell Nelson]

Bernhard Reiter writes:
 > I am not sure that Thuban can find out precisely what is wrong, but
 > a warning if it finds out that something is wrong seems the right
 > way to me. We could even pop a dialog up which has a longer
 > explanation.
 > 
 > Another idea to work around the problems would to be to have an
 > outline mode that always makes at least one red dot when a layer is
 > outside the current view being to small or so.
 > Otherwise it mark the bounding box.

Well, part of the problem of having an unprojected or misprojected
layer is that "zoom to the full map extent" does the wrong thing
**from the user's point of view**.  For example, if you have data in
one UTM zone, and select a map projection in a different zone, zooming
to the full map extent causes your data to disappear.  Disappearing
data is very disconcerting to a user!

IMHO, if you have a layer which has been selected to be visible, and
its LatLonBoundingBox does not overlap the current map view, the
corner or edge closest to the data should say "LAYERNAME is over
there" with an arrow.  If you don't want to see that, and you *meant*
for the layer to be off the map, turn off its visibility.

Does anybody else think that's a good thing to have?

-- 
--My blog is at angry-economist.russnelson.com  | Freedom means allowing
Crynwr sells support for free software  | PGPok | people to do things the
521 Pleasant Valley Rd. | +1 315-323-1241 cell  | majority thinks are
Potsdam, NY 13676-3213  | +1 212-202-2318 VOIP  | stupid, e.g. take drugs.