| 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: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. |
| | 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: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. |
