Non-bounded label priority and priority ordering

[johto]

I would like to use non-bounded priorities for labels. This could be for example a PRIORITYTYPE setting in mapfile which would allow you to choose between the current implementation and between the non-bounded(low overhead) implementation. Also changing between ascending and descending priority ordering would be useful.

[sdlime]

By non-bounded do you mean just rendering the labels in the order they are in the cache with no regards to priority? I believe that's essentially what happens if you don't use priorities, they all end up in one priority level. I believe skipping empty levels is very quick so I don't know what the benefit of the extra complexity would be. Unless I don't understand what you mean by non-bounded.

Steve

[johto]

The priorities are now from 1 (lowest) to 10(highest). By non-bounded I mean that an out-of-bounds priority won't be "clamped to the min/max values at rendering time".

[sdlime]

I'm still missing something, so if there's a priority of 25 what should happen to it?

Steve

[johto]

That would be guaranteed to be rendered before < 25.