[mapserver-users] Re: Mapserver Projection Errors

[Daniel Morissette]

If you could produce a small testcase that reproduces the issue then it 
may be easier to help. Just a mapfile may be sufficient for testing the 
GetCapabilities.


On 11-10-19 04:06 PM, SixDegrees wrote:
> That's correct. If I use the "init=epsg:4326" form, no error is thrown;
> errors only appear when I use the Proj.4 strings, even if they correspond to
> the same projection.
>
> As I understand things, Mapserver only requires the map-level projection to
> be in epsg format; individual layers can have projections defined in any
> other way Mapserver understands, and when a WMS request is made the layer
> will be reprojected to the projections defined at the map level on the fly.
> In fact, this seems to happen; as noted, the XML for each layer in the
> GetCapabilities response (which produces the errors) contains bounding boxes
> that have all been correctly reprojected into epsg:4326 even when the layer
> itself is in, for example, a UTM projection defined by a Proj.4 string.
>
> So I'm thinking that this is a Mapserver mistake, and the error messages are
> spurious. It certainly seems that way, but it would be nice to have a
> definitive answer.
>
>
>
> --
> View this message in context: http://osgeo-org.1803224.n2.nabble.com/Mapserver-Projection-Errors-tp6908527p6910326.html
> Sent from the Mapserver - User mailing list archive at Nabble.com.
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users


-- 
Daniel Morissette
http://www.mapgears.com/
Provider of Professional MapServer Support since 2000