Hi Angus,
I'm not using PostGIS layers; this is the Itasca demo for mapserver 4.x,
and putting the PROJECTION param fixes it, indeed!
I wonder why it is not put (uncommented, actually) in the vanilla demo
package. Is there a reason?
Thank you very much for the information!
Best regards,
Arnaud
Angus Dickey wrote:
I am having a similar problem. Apparently Mapserver will automatically
calculate the bounding box if you define it using epsg codes in the map file ex:
PROJECTION
"init=epsg:4269"
END
This works for me when I use shapefiles, i.e. it calculates the correct
bounding box in the right coordinates, however all my Postgis layers end up
with a bounding box of:
minx="-2.5e+07" miny="-2.5e+07" maxx="2.5e+07" maxy="2.5e+07"
Are youusing postgis layers? Does anybody know how to get mapserver to
calculate the correct bounding box for postgis layers?
Thanks for any help,
~Angus
-----Original Message-----
From: Arnaud Diederen [mailto:[EMAIL PROTECTED]
Sent: June 15, 2006 7:17 AM
To: [email protected]
Subject: [UMN_MAPSERVER-USERS] WMS Capabilities: LatLonBoundingBox
Hello,
I'm absolutely new to mapserver, so I downloaded the demo for the 4.x
version (I'm using Debian GNU/Linux).
The demo pages work ok, but when I do a GetCapabilities operation
(http://localhost/cgi-bin/mapserv?service=WMS&version=1.3&map=/var/www/workshop/itasca.map&request=GetCapabilities
- local intranet, sorry :( ), I get the attached XML document.
What I'm wondering is why the LatLonBoundingBox tags holds those values,
since they are supposed to be in 4326, if I read the WMS spec right.
Am I doing something wrong?
I looked the archives, and googled the internet, but I couldn't find any
help on this exact topic.
I would definitely appreciate if somebody could provide any kind of
help; would it be just pointers on what I have to do/fix.
Best regards,
Arnaud