At least in my interpretation of MapCSS, the behaviour when two objects are
defined to have the same z-index is undefined. The order of rendering here
should (in my book) be effectively random.
Bob
if (*ra4 != 0xffc78948) { return false; }
On 27 Jan 2012, at 12:24, Peter Wendorff wrote:
> Hi.
> I have to give a short introduction to someone who should implement a mapcss
> renderer and looked into the docs availlable for that.
> For that I especially looked into the sotm-eu presentation done by Maskim
> [1], and I fear there is a small bug on slide 7 (and the following pages).
>
> The stylesheet presented does not contain any z-index or layer definitions.
> To quote the slide, it's defined as:
>
> line[highway] {
> color: orange;
> width: 11;
> }
>
> area[building] {
> fill-color: gray;
> }
>
> line[waterway] {
> color: blue;
> width:3;
> }
>
> The image presented nearby shows a similar image, but the highway is rendered
> on top of the river.
> Shouldn't that be the other way around (according to the mapcss code, not to
> "good maps")?
>
> regards
> Peter
>
> [1] http://sotm-eu.org/slides/10_MaksimGurtovenko_MapCSS.pdf
>
> _______________________________________________
> Mapcss mailing list
> [email protected]
> http://lists.openstreetmap.org/listinfo/mapcss
_______________________________________________
Mapcss mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/mapcss
