[mapserver-dev] Motion: change default POSITION AUTO labelling order for point layers

[Stephen Woodbridge]

The idea that I was trying to get across is the we have the current auto 
position list that is global. You are proposing a change to a new auto 
position list that is also global. So why not support both lists 
globally via a CONFIG keyword to select the old one if the default list 
is the new one, or vica versa.

This is easier than a patch for users that might need the old behavior 
and do not have the ability to compile like on Windows.

I agree that long term this should be done at the label level. I was 
only trying to think of a simple way around the objections.

Thanks,
   -Steve

On 3/18/2012 6:28 AM, thomas bonfort wrote:
> Steve,
>
> Adding this at the global level would not be particularly difficult to
> implement, we'd just need to read these positions at the beginning of
> the labelcache phase. However, I believe that such a customization
> should be done at the label level, as the need to override the
> accepted "best" positioning order would only need to be applied on a
> very specific label layer.
>
> --
> thomas
>
> On Fri, Mar 16, 2012 at 20:34, Stephen Woodbridge
> <woodbri at swoodbridge.com>  wrote:
>> I have no idea what it would take to do something like this, but what do you
>> think about adding a CONFIG "USE_ALT_LABEL_POSITION_AUTO=yes" or something
>> like this in the mapfile as a global switch to an alternate hardcoded list
>> of positions. Then by default you get the current positioning or select this
>> in the mapfile to get the new positioning order. Assuming that it is easy to
>> grab these config values, it is just an if block to reset the order on
>> startup. I'm not sure if "startup" implies, reading the mapfile, or CGI or
>> FastCGI, or apache module startup. Hopefully it is easy to init when the
>> mapfile is read.
>>
>> -Steve W
>>
>>
>> On 3/16/2012 1:42 PM, thomas bonfort wrote:
>>>
>>> Patches graciously accepted :)
>>> I personally have no incentive in implementing configurable positioning
>>> as a hardcoded
>>>
>>> 6 1 5
>>> 4 X 3
>>> 8 2 7
>>>
>>> suits all my needs.
>>>
>>> --
>>> thomas
>>>
>>> On Fri, Mar 16, 2012 at 16:30, Bob Basques<Bob.Basques at ci.stpaul.mn.us
>>> <mailto:Bob.Basques at ci.stpaul.mn.us>>  wrote:
>>>
>>>     All,
>>>
>>>
>>>     I know my vote doesn't count as much.  But I'm thinking the same
>>>     here with regard to changing things.  As an alternative to changing
>>>     things, what's the timeline on just setting up the planned MAPFILE
>>>     controls instead?
>>>
>>>
>>>     bobb
>>>
>>>
>>>
>>>
>>>      >>>  Daniel Morissette<dmorissette at mapgears.com
>>>     <mailto:dmorissette at mapgears.com>>  wrote:
>>>
>>>     I'd say -0 ... I can see in ticket #4249 that the change of order gives
>>>     better results in that case, but I am always hesitant to change a
>>>     built-in behavior that has been around for years as this change could
>>>     cause side-effects for other use cases where the current order is
>>>     better. (I have no such use case in mind, just being overly careful
>>>     because our users don't like when we break backwards compatibility.)
>>>
>>>     BTW, I love the idea of a mechanism to control the order in the
>>> mapfile.
>>>
>>>     Daniel
>>>
>>>
>>>
>>>     On 12-03-16 10:19 AM, thomas bonfort wrote:
>>>      >  Hi devs,
>>>      >
>>>      >  We have tickets 2981, 4242 and 4249 opened to ask for a change in
>>> the
>>>      >  order which labels are placed around a label point, in order to
>>>     obtain
>>>      >  better quality text placement.
>>>      >
>>>      >  http://trac.osgeo.org/mapserver/ticket/2981
>>>      >  http://trac.osgeo.org/mapserver/ticket/4242
>>>      >  http://trac.osgeo.org/mapserver/ticket/4249
>>>      >
>>>      >  While the long-term solution will allow us to configure this order
>>> at
>>>      >  the mapfile level, I motion that we change this order from
>>>      >
>>>      >
>>>      >  1 7 3
>>>      >  6 X 5
>>>      >  4 8 2
>>>      >
>>>      >  to
>>>      >
>>>      >  6 1 5
>>>      >  4 X 3
>>>      >  8 2 7
>>>      >
>>>      >  for the 6.2 release.
>>>      >  I'll start with my +1.
>>>      >
>>>      >  regards,
>>>      >  thomas
>>>      >  _______________________________________________
>>>      >  mapserver-dev mailing list
>>>      >  mapserver-dev at lists.osgeo.org<mailto:mapserver-dev at lists.osgeo.org>
>>>
>>>      >  http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>>>
>>>
>>>     --
>>>     Daniel Morissette
>>>     http://www.mapgears.com/
>>>     Provider of Professional MapServer Support since 2000
>>>
>>>
>>>     _______________________________________________
>>>     mapserver-dev mailing list
>>>     mapserver-dev at lists.osgeo.org<mailto:mapserver-dev at lists.osgeo.org>
>>>
>>>     http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>>>
>>>
>>>     _______________________________________________
>>>     mapserver-dev mailing list
>>>     mapserver-dev at lists.osgeo.org<mailto:mapserver-dev at lists.osgeo.org>
>>>
>>>     http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> mapserver-dev mailing list
>>> mapserver-dev at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>>
>>
>> _______________________________________________
>> mapserver-dev mailing list
>> mapserver-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapserver-dev