again... [mapserver-users] mapext=shapes and projection on the fly.

Bullock, Martha F ERDC-CRREL-NH Martha.F.Bullock at erdc.usace.army.mil
Thu Mar 7 12:56:44 EST 2002


I'm having the same problem - has anyone come up with a solution yet?

Issuing mode, qlayer, (and filter) with mapext=shapes in an application
where the layers and map are NOT projected works just as one would expect
(the feature is highlighted and defines the mapextent). 
However, specifying mode, qlayer, (and filter) and mapext=shapes with a
PROJECTED LAYER does not work.  Instead, the map zooms to the very center of
your map at the web object MINSCALE. (as Debbie explains below).

Is this a bug or are we missing an essential parameter?

I'm sure I could work around it by hard-coding extents, but would rather not
if someone has an alternative way around this.

Thanks so much -- Martha



-----Original Message-----
From: Debbie Pagurek [mailto:pagurekd at em.agr.ca]
Sent: Thursday, January 31, 2002 9:24 AM
To: mapserver-users at lists.gis.umn.edu
Subject: [mapserver-users] mapext=shapes and projection on the fly


Hi all,

I have a question regarding queries: 
I have a map file in which I am using the PROJECTION tag to project
on-the-fly from latlong to lcc.  When I click on a polygon, I want the query
results to zoom to this polygon and hilite it.  However, when I use
mapext=shapes, the coordinates are in latlong, not the projected coordinates
and as a result, the map is zoomed to a tiny area that is NOT where I
clicked.  Is this by design or is this a bug?  Is there a way to force
mapext=shapes to return values in projected coordinates?  I am still using
Mapserver CGI and haven't 'graduated' yet to mapscripting...

Mapserver 3.5 on Linux

Thanks,
D. Pagurek





More information about the mapserver-users mailing list