[Mapcss] MapCSS 0.2 finalization

Thomas Davie tom.davie at gmail.com
Tue May 1 12:21:00 BST 2012

Sounds like a plan to me – I have already done a chunk of turning orange boxes into green ones, and am now left with the ones that are really missing features in OSP, so they may take some more time.  Feel free to treat any orange boxes in my column as "green" for the sake of deciding what goes into the standard.

Your proposal to place a MapCSS version in the meta tag sounds entirely sane to me.  The likely best solution for text: "TAG"; vs text: tag("TAG") and text: "text to render" would be something like
  title: "bob's awesome MapCSS Stylesheet";
  mapcss-version: 0.2;
  text-interprettation: {tag | text};

if (*ra4 != 0xffc78948) { return false; }

On 1 May 2012, at 10:14, Komяpa wrote:

> Hi all,
> A couple of questions to discuss:
> 0) schedule.
> Will it be fine for developers to implement some obvious changes in
> their engines till 15th of May, marking respective rows in the table,
> so we'll have less differences before we start discussing other stuff?
> Two weekends during that period :3
> so, proposed schedule:
> may 1-15: trying to fill more details about your renderer into that
> table, showing weaknesses of others and own strenghts, and trying to
> implement the most of things the others do to be compatible.
> may 15-21: re-partitioning of the table into a "green" release-ready
> part and the "proposed" part for future discussion.
> may 20-30: writing text-form spec from green part of table.
> Any objections?
> 1) meta{}.
> That thing was used as josm's standard way to store info about
> stylesheet, like its name and author.
> I think it's worth it - even if most will just ignore its content, it
> can be used to store mapcss revision number and be used by something
> like libmagic to guess that it's mapcss file at all.
> 2) testing stylesheet.
> For now some developers use openstreetmap.by's komap-in-mind
> stylesheet, http://kothic.googlecode.com/hg/src/styles/osmosnimki-maps.mapcss
> It has advantages of being long (so you can check performance),
> beautifully-rendered (if done right), and has something like reference
> rendering, http://openstreetmap.by itself.
> Obvious problems are that it was written being strongly coupled with
> komap - it has a lot of -x-properties in it and even some hardcoded
> hacks to be nice. Also, some problems of mapnik, like inability to
> cascade rules, sneaked into it too.
> I think we need some shorter sheet that will just utilize all the
> stuff that will go to the standard. Maybe we should revisit that after
> 15th of May, if everyone agrees.
> -- 
> Darafei "Komяpa" Praliaskouski
> OSM BY Team - http://openstreetmap.by/
> xmpp:me at komzpa.net mailto:me at komzpa.net
> _______________________________________________
> Mapcss mailing list
> Mapcss at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/mapcss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/mapcss/attachments/20120501/343f740b/attachment.html>

More information about the Mapcss mailing list