[mapserver-dev] MapServer 5.6.0-beta3 released

Havard Tveite havard.tveite at umb.no
Tue Oct 13 04:39:31 EDT 2009


Symbology change in 5.6.0?

In the list of changes for 5.6.0, I have not found any mention of
changes to symbol rendering.  However, from 5.4.2 to 5.6.0 beta3,
many of my vector symbols (polygon fills, points, "decorated"
lines) have been screwed up both for AGG and GD.

Something must have changed regarding how the "bounding box" of a
vector symbols is calculated when using it as tiles in a polygon
fill, and when placing point symbols.  It used to always use (0,0)
as the upper left corner, and the maximum x and y values as the
lower right corner.  This must be different now.  See the attached
images for an example of the resulting changes in rendering of
polygon fills.

The blue pattern that you see in the images are specified as
follows in the map file (exploiting the use of 0,0 as the upper
left corner):

SYMBOL
   NAME "marsh_isom"
   TYPE vector
   FILLED true
   POINTS
     0 0.6666666
     100 0.666666
     100 1
     0 1
     0 0.66666666
   END
END

SYMBOL
   NAME "indistinctmarsh_isom"
   TYPE vector
   FILLED true
   POINTS
     0 0.2
     0.45 0.2
     0.45 0.3
     0 0.3
     0 0.2
     -99 -99
     0.7 0.2
     1.15 0.2
     1.15 0.3
     0.7 0.3
     0.7 0.2
     -99 -99
     0.125 0.5
     1.025 0.5
     1.025 0.6
     0.125 0.6
     0.125 0.5
   END
END

This is a significant change, in my opinion, and users should
at least be warned.  Perhaps it even should wait to 6.0.
I do not know the exact nature of the change, but it could make
it more difficult to implement advanced vector symbols and
precise vector symbol placement.

In RFC 45, some of the symbology challenges and possible
solutions are discussed.  The introduction of a (SYMBOL)CENTER
tag could help a bit in reducing the consequences of the
current change, but would not address the polygon fill problem.

Should this be filed as a bug?

Håvard


Daniel Morissette wrote:
> MapServer 5.6.0-beta3 has just been released and is available for 
> download at
> 
>    http://mapserver.org/download.html OR
>    http://download.osgeo.org/mapserver/mapserver-5.6.0-beta3.tar.gz
> 
> Please also keep an eye on the 5.4 to 5.6 Migration Guide where we will 
> document migration issues for this release:
> http://trac.osgeo.org/mapserver/browser/trunk/mapserver/MIGRATION_GUIDE.TXT
> 
> Some great progress has been made since beta2 as you can tell from the 
> list of fixes included at the end of this message, but there are a 
> couple of tricky issues that are still being worked on, so we will have 
> at least one other beta next week before we can have a release candidate.
> 
> Once again, we need your help to ensure a high quality product so please 
> help out by testing your applications with this new beta and reporting 
> your results.
> 
> Thanks for your help
> 
> The MapServer development team.
> 
> 
> 
> Version 5.6.0-beta3 (2009-10-07):
> ---------------------------------
> 
> - Fixed SDE layer seg fault (#3152)
> 
> - Fixed placement of labels using ANGLE AUTO which were not always 
> positioned
>    correctly (#3160)
> 
> - Enable output of geometry in GML GetFeatureInfo if wms_geometries and
>    wms_geom_type are specified (#2989)
> 
> - fix URN typo in mapwfs.c for urn:EPSG:geographicCRS:...
> 
> - don't apply scalefactor to label outlines (#3157)
> 
> - update namespaces and schema pointers (#2872)
> 
> - add RFC49 and RFC40 keywords to copy functions (#2865)
> 
> - minor fix to correct numberOfResults when maxfeatures is set in
>    mapfile (#2907)
> 
> - Fixed possible crash with WFS GetFeature when no projection is specified
>    at the map level (#3129)
> 
> - Fixed anchor point of vertically stacked bar graphs
> 
> - Fixed TEXT property that cannot be removed in the CLASS object.
>    PHP/Mapscript (#3063)
> 
> - Fixed use of minfeaturesize auto with curved labels (#3151)
> 
> - Fixed msRemoveHashTable function when 2 keys have the same hash (#3146)
> 
> - Fix raster thread deadlock condition on posix/linux (#3145)
> 
> - Do not route thread debug output through msDebug which requires locking.
> 
> - Fix WCS coverage metadata handling if size/resolution missing (#2683).
> 
> - Fix WCS crash with use of datasets that aren't physical files (#2901).
> 
> - Fix WCS failure with WCS 1.1 OGC URN (urn:ogc:def:crs:OGC::CRS84) (#3161).
> 
> 
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
> 

-- 
Håvard Tveite
Department of Mathematical Sciences and Technology, UMB
Drøbakveien 31, POBox 5003, N-1432 Ås, NORWAY
Phone: +47 64965483 Fax: +47 64965401 http://www.umb.no/imt/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GD5.4.2.png
Type: image/png
Size: 629 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20091013/aea4591c/GD5.4.2.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GD5.6.0.png
Type: image/png
Size: 526 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20091013/aea4591c/GD5.6.0.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: AGG5.4.2.png
Type: image/png
Size: 1160 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20091013/aea4591c/AGG5.4.2.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: AGG5.6.0.png
Type: image/png
Size: 1128 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20091013/aea4591c/AGG5.6.0.png


More information about the mapserver-dev mailing list