[mapserver-users] MapScript WMS request

Mr. Puneet Kishor punk.kish at gmail.com
Thu Sep 8 21:02:33 EDT 2011


On Sep 8, 2011, at 7:43 PM, Daniel Morissette wrote:

> On 11-09-08 08:40 PM, Mr. Puneet Kishor wrote:
>> 
>> On Sep 8, 2011, at 7:16 PM, Mr. Puneet Kishor wrote:
>>> 
>>> PostGIS. lat/lng. SRID 4326
>>> 
>>>> 
> [...]
>> 
>> 
>> I should have also added the following
>> 
>> macromap=# SELECT ST_AsText(the_geom) FROM gmna LIMIT 1;
>> MULTIPOLYGON(((170.095660072181 65.6251237164987,170.158707739831 65.6269635224645,170.173265447057 65.6291258974802,170.2497277762 65.6357072803021,170.257074956711 65.6372005203368,170.267729454865 65.6409199441452,170.283323865029 65.6476938262634,170.301827075555 65.657286936117,170.370058904075 65.6852127397289,170.394158265237 65.6971816353387,170.45719236517 65.7228758026517,170.477794791157 65.7331303689249,170.501440218163 65.7431659781412,170.506165498289 65.745957239196,170.509550359131 65.74948784687,170.517163313193 65.7692852345393,170.523452830315 65.7856156337451,170.527911709329 65.7872471861488,170.564509940928 65.8002968138894,170.605805308438 65.815184809157,17....
>> 
>> 
>> As you can see, everything is in lat/lng.
>> 
>> 
> 
> Thanks. That rules out the possibility of a data problem.
> 
> With PostGIS, the WMS extents reported for a layer cannot be derived from the data. In the shapefile case we use the shapefile's extents, but this is not readily available with postgis, so unless I'm mistaken, MapServer looks up the wms/ows_extent metadata in the layer, and if not found then it falls back on the map's EXTENT for the mandatory BoundingBox and LatLonBoundingBox elements.
> 
> Maybe call $map->save("/tmp/my.map") in your script after the map and layer have been populated and paste the result... that may give us a hint...
> 

wow! this is a super-awesome debugging technique. I have sent you the map file off list to not pollute the entire list serve.

Puneet.


More information about the mapserver-users mailing list