Changes between Initial Version and Version 2 of Ticket #17822


Ignore:
Timestamp:
2019-06-17T21:57:08+02:00 (7 years ago)
Author:
PanierAvide
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17822

    • Property Summary Remove source:geometry -> source:location MapCSS ruleChange source:geometry -> source:position MapCSS rule
  • Ticket #17822 – Description

    initial v2  
    11Hello,
    2 I discovered recently that MapCSS validation rules (geometry.mapcss) contains something to warn user when source:geometry is used on a node, and should be replaced by source:location instead. As now, source:geometry tag is used 1500000 times worldwide, whereas source:location is used 80000 times. It would make sense to keep tagging unified, no matter the kind of geometry we use. If you don't mind, I would like to edit this and change the MapCSS rule, making source:location being changed into source:geometry for any kind of feature.
     2I discovered recently that MapCSS validation rules (geometry.mapcss) contains something to warn user when source:geometry is used on a node, and should be replaced by source:position instead. As now, source:geometry tag is used 1500000 times worldwide, whereas source:position is used 647000 times. It would make sense to keep tagging unified, no matter the kind of geometry we use. If you don't mind, I would like to edit this and change the MapCSS rule, making source:position being changed into source:geometry for any kind of feature.
    33Regards.