MapServer 5.6.0-beta3 released

[Daniel Morissette]

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
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev

[Havard Tveite]

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
> [hidden email]
> 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: [phone] Fax: [phone] http://www.umb.no/imt/





_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev

[Thomas Bonfort-2]

Havard,

can you post your mapfile layer corresponding to those images?

thanks,

thomas



On Tue, Oct 13, 2009 at 10:39, Havard Tveite <[hidden email]> wrote:

> 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
>> [hidden email]
>> 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: [phone] Fax: [phone] http://www.umb.no/imt/
>
> _______________________________________________
> mapserver-dev mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>

_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev

[Havard Tveite]

Thomas Bonfort wrote:
> Havard,
>
> can you post your mapfile layer corresponding to those images?

Dear Thomas,

Here is the complete layer (you will find the two symbols "marsh_isom" and
"indistinctmarsh_isom" down there).

Håvard

*************************************************************
   LAYER  # Kart - Polygons
     NAME o-kartpolygon
     GROUP "poly"
     STATUS OFF
     TYPE POLYGON
     CONNECTION "blabal"
     CONNECTIONTYPE postgis
     DATA "the_geom from (select oid, symbol, the_geom from okartpolygon order by sequence) as okart using unique oid using SRID=-1"
     METADATA
       "layer_title" "O-kart - polygoner"
       "legend_order" "1"
     END
     SYMBOLSCALEDENOM 2650
     PROJECTION
       "init=epsg:32633"
     END
     LABELITEM "symbol"

     CLASS
       NAME "Berg i dagen"
       EXPRESSION ([symbol] = 2120)
       STYLE
         COLOR 204 204 204
       END # style
     END # CLASS
     CLASS
       NAME "Dyrka mark"
       EXPRESSION ([symbol] = 4150)
       STYLE
         COLOR 255 186 54
       END # style
       STYLE
        symbol "dyrkamark"
        SIZE 80
         COLOR 0 0 0
       END # style
     END # CLASS
     CLASS
       NAME "Åpent lettløpt område"
       EXPRESSION ([symbol] = 4010)
       STYLE
         COLOR 255 186 54
       END # style
     END # CLASS
     CLASS
       NAME "Halvåpent lettløpt område"
       EXPRESSION ([symbol] = 4020)
       STYLE
         COLOR 255 186 54
        SIZE 8
       END # style
     END # CLASS
     CLASS
       NAME "Åpent område"
       EXPRESSION ([symbol] = 4030)
       STYLE
         COLOR 255 221 154
       END # style
     END # CLASS
     CLASS
       NAME "Halvåpent område"
       EXPRESSION ([symbol] = 4040)
       STYLE
         COLOR 255 205 114
       END # style
       STYLE
        symbol "halvapent"
        SIZE 100
        COLOR 255 255 255
       END # style
     END # CLASS
     CLASS
       NAME "Vegetasjon, nedsatt løpbarhet"
       EXPRESSION ([symbol] = 4060)
       STYLE
         COLOR 196 255 185
       END # style
     END # CLASS
     CLASS
       NAME "God sikt, nedsatt løpbarhet"
       EXPRESSION ([symbol] = 4070)
       STYLE
        symbol "vertgreen1"
        SIZE 84
         COLOR 61 255 23
       END # style
     END # CLASS
     CLASS
       NAME "Vegetasjon, dårlig løpbarhet"
       EXPRESSION ([symbol] = 4080)
       STYLE
         COLOR 139 255 116
       END # style
     END # CLASS
     CLASS
       NAME "God sikt, dårlig løpbarhet"
       EXPRESSION ([symbol] = 4090)
       STYLE
        symbol "vertgreen2"
        SIZE 42
         COLOR 61 255 23
       END # style
     END # CLASS
     CLASS
       NAME "Vegetasjon, ikke løpbar"
       EXPRESSION ([symbol] = 4100)
       STYLE
         COLOR 61 255 23
       END # style
     END # CLASS
     CLASS
       NAME "Bygning"
       EXPRESSION ([symbol] = 5260)
       STYLE
         COLOR 0 0 0
       END # style
     END # CLASS
     CLASS
       NAME "Forbudt område"
       EXPRESSION ([symbol] = 5270)
       STYLE
         COLOR 158 186 0
       END # style
     END # CLASS
     CLASS
       NAME "Vann"
       EXPRESSION ([symbol] = 3010 or [symbol] = 3020 )
       STYLE
         COLOR 0 0 255
       END # style
     END # CLASS
     CLASS
       NAME "Plass"
       EXPRESSION ([symbol] = 5290)
       STYLE
         COLOR 209 66  0
         #COLOR 230 120 0
         #COLOR 241 198 165
       # COLOR 209 66 0 # Brun
       END # style
     END # CLASS
     CLASS
       NAME "Myr"
       EXPRESSION ([symbol] = 3100)
       STYLE
         COLOR 0 0 255
        SYMBOL "marsh_isom"
         MINSIZE 3
         SIZE 30
         #MAXSIZE 100
       END # style
     END # CLASS
     CLASS
       NAME "Farlig myr"
       EXPRESSION ([symbol] = 3090)
       STYLE
         COLOR 0 0 255
        SYMBOL "farligmyr"
         MINSIZE 3
         SIZE 50
         #MAXSIZE 100
       END # style
     END # CLASS
     CLASS
       NAME "Utydelig myr"
       EXPRESSION ([symbol] = 3110)
       STYLE
         COLOR 0 0 255
        SYMBOL "indistinctmarsh_isom"
         MINSIZE 3
         SIZE 60
         #MAXSIZE 200
       END # style
     END # CLASS
   END # LAYER # kart - polygons
*************************************************************

>
> thanks,
>
> thomas
>
>
>
> On Tue, Oct 13, 2009 at 10:39, Havard Tveite <[hidden email]> wrote:
>> 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
>>> [hidden email]
>>> 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: [phone] Fax: [phone] http://www.umb.no/imt/
>>
>> _______________________________________________
>> mapserver-dev mailing list
>> [hidden email]
>> 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: [phone] Fax: [phone] http://www.umb.no/imt/
_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev

[Thomas Bonfort-2]

There have been a few changes with scaledependant rendering since
beta3. could you try with the trunk version and report back, so we can
get any more fixes in before beta4?

thanks,

thomas

www.camptocamp.com
[phone]



On Tue, Oct 13, 2009 at 11:53, Havard Tveite <[hidden email]> wrote:

> Thomas Bonfort wrote:
>>
>> Havard,
>>
>> can you post your mapfile layer corresponding to those images?
>
> Dear Thomas,
>
> Here is the complete layer (you will find the two symbols "marsh_isom" and
> "indistinctmarsh_isom" down there).
>
> Håvard
>
> *************************************************************
>  LAYER  # Kart - Polygons
>    NAME o-kartpolygon
>    GROUP "poly"
>    STATUS OFF
>    TYPE POLYGON
>    CONNECTION "blabal"
>    CONNECTIONTYPE postgis
>    DATA "the_geom from (select oid, symbol, the_geom from okartpolygon order
> by sequence) as okart using unique oid using SRID=-1"
>    METADATA
>      "layer_title" "O-kart - polygoner"
>      "legend_order" "1"
>    END
>    SYMBOLSCALEDENOM 2650
>    PROJECTION
>      "init=epsg:32633"
>    END
>    LABELITEM "symbol"
>
>    CLASS
>      NAME "Berg i dagen"
>      EXPRESSION ([symbol] = 2120)
>      STYLE
>        COLOR 204 204 204
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Dyrka mark"
>      EXPRESSION ([symbol] = 4150)
>      STYLE
>        COLOR 255 186 54
>      END # style
>      STYLE
>        symbol "dyrkamark"
>        SIZE 80
>        COLOR 0 0 0
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Åpent lettløpt område"
>      EXPRESSION ([symbol] = 4010)
>      STYLE
>        COLOR 255 186 54
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Halvåpent lettløpt område"
>      EXPRESSION ([symbol] = 4020)
>      STYLE
>        COLOR 255 186 54
>        SIZE 8
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Åpent område"
>      EXPRESSION ([symbol] = 4030)
>      STYLE
>        COLOR 255 221 154
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Halvåpent område"
>      EXPRESSION ([symbol] = 4040)
>      STYLE
>        COLOR 255 205 114
>      END # style
>      STYLE
>        symbol "halvapent"
>        SIZE 100
>        COLOR 255 255 255
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Vegetasjon, nedsatt løpbarhet"
>      EXPRESSION ([symbol] = 4060)
>      STYLE
>        COLOR 196 255 185
>      END # style
>    END # CLASS
>    CLASS
>      NAME "God sikt, nedsatt løpbarhet"
>      EXPRESSION ([symbol] = 4070)
>      STYLE
>        symbol "vertgreen1"
>        SIZE 84
>        COLOR 61 255 23
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Vegetasjon, dårlig løpbarhet"
>      EXPRESSION ([symbol] = 4080)
>      STYLE
>        COLOR 139 255 116
>      END # style
>    END # CLASS
>    CLASS
>      NAME "God sikt, dårlig løpbarhet"
>      EXPRESSION ([symbol] = 4090)
>      STYLE
>        symbol "vertgreen2"
>        SIZE 42
>        COLOR 61 255 23
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Vegetasjon, ikke løpbar"
>      EXPRESSION ([symbol] = 4100)
>      STYLE
>        COLOR 61 255 23
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Bygning"
>      EXPRESSION ([symbol] = 5260)
>      STYLE
>        COLOR 0 0 0
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Forbudt område"
>      EXPRESSION ([symbol] = 5270)
>      STYLE
>        COLOR 158 186 0
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Vann"
>      EXPRESSION ([symbol] = 3010 or [symbol] = 3020 )
>      STYLE
>        COLOR 0 0 255
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Plass"
>      EXPRESSION ([symbol] = 5290)
>      STYLE
>        COLOR 209 66  0
>        #COLOR 230 120 0
>        #COLOR 241 198 165
>      # COLOR 209 66 0 # Brun
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Myr"
>      EXPRESSION ([symbol] = 3100)
>      STYLE
>        COLOR 0 0 255
>        SYMBOL "marsh_isom"
>        MINSIZE 3
>        SIZE 30
>        #MAXSIZE 100
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Farlig myr"
>      EXPRESSION ([symbol] = 3090)
>      STYLE
>        COLOR 0 0 255
>        SYMBOL "farligmyr"
>        MINSIZE 3
>        SIZE 50
>        #MAXSIZE 100
>      END # style
>    END # CLASS
>    CLASS
>      NAME "Utydelig myr"
>      EXPRESSION ([symbol] = 3110)
>      STYLE
>        COLOR 0 0 255
>        SYMBOL "indistinctmarsh_isom"
>        MINSIZE 3
>        SIZE 60
>        #MAXSIZE 200
>      END # style
>    END # CLASS
>  END # LAYER # kart - polygons
> *************************************************************
>
>
>>
>> thanks,
>>
>> thomas
>>
>>
>>
>> On Tue, Oct 13, 2009 at 10:39, Havard Tveite <[hidden email]> wrote:
>>>
>>> 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
>>>> [hidden email]
>>>> 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: [phone] Fax: [phone] http://www.umb.no/imt/
>>>
>>> _______________________________________________
>>> mapserver-dev mailing list
>>> [hidden email]
>>> 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: [phone] Fax: [phone] http://www.umb.no/imt/
>

_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev