Hi Jukka, Daniel find it :-) This was a problem with the spatial reference file of ECW format. This problem was already identified and well fixed in GDAL 1.8.1.
http://trac.osgeo.org/gdal/ticket/4131 thank's a lot simon mercier 2011/9/29 Daniel Morissette <[email protected]> > On 11-09-28 02:57 PM, Rahkonen Jukka wrote: > >> So gdalinfo with Upper Left ( 0.0, 0.0) etc. means that gdal cannot >> get the correct georeferencing for your images. They are placed at >> coordinates (0,0) instead and then the WMS BBOX does not intersect the image >> area and server is sending a white map for you. >> > > Your analysis is correct, the invalid extents returned by GDAL are likely > the source of the problem for MapServer. I am checking with Simon off-list > to try to understand why this is happening. > > > > And "ERROR 1: Maximum number of characters allowed reached." suggests that >> for some part of the system the file path is too long. I have never seen >> such an error but I would still take it seriously and have a try placing the >> images into a a place like /mnt/pathtest/image_01.ecw >> >> > I did a quick grep on the GDAL source, and it seems that this error message > would be returned by the CPLReadLine2L() function, so I'd think it is > unlikely to be related to the length of the file path. > > > -- > Daniel Morissette > http://www.mapgears.com/ > Provider of Professional MapServer Support since 2000 > > ______________________________**_________________ > mapserver-users mailing list > [email protected].**org <[email protected]> > http://lists.osgeo.org/**mailman/listinfo/mapserver-**users<http://lists.osgeo.org/mailman/listinfo/mapserver-users> >
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
