AW: [mapserver-users] Mapserver Projection Errors

[SixDegrees]

To summarize the preceding thread contents: Mapfiles are generated using
python, in turn using the GDAL libraries to extract information like the
projection needed in the mapfile. Mapfiles are constructed for use in
response to WMS requests. QGis initially makes a WMS GetCapabilities
request, and this is what is producing the errors in the Mapserver logfile,
one error per layer. This isn't specific to QGis; I get the same errors when
I send my own GetCapabilities request through a browser. The returned XML
does not contain any errors, and layers that have projections that differ
from the top-level mapfile projection - for example, a layer with projection
for UTM Zone 38N, with the mapfile set for epsg:4326 - have bounding boxes
that have been correctly re-projected into the map's projection. If I
replace the layer's Proj.4-style multi-argument string with
"init=epsg:xxxx", where xxxx is the layer's epsg code, no errors are thrown.
Errors only arise when the multi-argument form of the projection string is
used, even when it is equivalent to the epsg code projection.


Eichner, Andreas - SID-NLK wrote:
> 
> I think spaces at the end are not a problem. How is GDAL involved here?
> How do you generate the map files? And how is map file generation
> related to QGIS?
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at .osgeo
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
> 


--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Mapserver-Projection-Errors-tp6908527p6912415.html
Sent from the Mapserver - User mailing list archive at Nabble.com.