Ah ok, many thanks!
Bjoern
On 12 May 2017 at 18:26, Aun Johnsen <[email protected]> wrote:
> AFAIK { set: key=value; } have only been discussed, I hope that pgmapcss
> can implement it, though I havn’t been able to test it or discuss it any
> further with the developer.
>
> Aun Johnsen
>
> On May 12, 2017, at 14:18, Bjoern Hassler <[email protected]> wrote:
>
> OK, many thanks - I guess this is a fairly new feature. Do you know where
> this is documented, or what applications support it yet?
>
> Bjoern
>
> On 12 May 2017 at 16:33, Aun Johnsen <[email protected]> wrote:
>
>> Bjørn
>>
>> I don’t know if it will work, but the way I have been thinking is like
>> this:
>>
>> way[highway=residential][!surface] {
>> set: surface=unpaved;
>> }
>> way[highway=motorway][!surface] {
>> set: surface=paved;
>> }
>>
>> This is done so I can assume default values later in the sheet, without
>> having to test explicitly for untagged ways for each test. If it works on
>> the implementation of mapcss, it will come handy on complex stylesheets.
>>
>> Aun Johnsen
>>
>> On May 12, 2017, at 12:08, Bjoern Hassler <[email protected]> wrote:
>>
>> Aun, can you say a little more about "set tag=value"? I assume these are
>> css tags? What's the purpose?
>>
>>
>>
>>
>> _______________________________________________
>> Mapcss mailing list
>> [email protected]
>> https://lists.openstreetmap.org/listinfo/mapcss
>>
>>
> _______________________________________________
> Mapcss mailing list
> [email protected]
> https://lists.openstreetmap.org/listinfo/mapcss
>
>
>
> _______________________________________________
> Mapcss mailing list
> [email protected]
> https://lists.openstreetmap.org/listinfo/mapcss
>
>
_______________________________________________
Mapcss mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/mapcss
