Mapbox merges the attributes of TextSymbolizer and IconSymbolizer in a single type symbol, where TextSymbolizer related attributes contain the prefix text- and IconSymbolizer related attributes the prefix icon-. However, since all symbol-type properties are optional, we cannot reason if only a Text or an IconSymbolizer should be created, or if both should be created.
Now is the question on how to handle this problem. Should we simply always create both symbolizers or should we only create those symbolizers where e.g. at least one value is not undefined?
The result of both "solutions" would create a non-bijective parser.
PARSER
MAPBOX
QUESTION
Description:
Mapbox merges the attributes of TextSymbolizer and IconSymbolizer in a single type
symbol
, where TextSymbolizer related attributes contain the prefixtext-
and IconSymbolizer related attributes the prefixicon-
. However, since allsymbol
-type properties are optional, we cannot reason if only a Text or an IconSymbolizer should be created, or if both should be created.Now is the question on how to handle this problem. Should we simply always create both symbolizers or should we only create those symbolizers where e.g. at least one value is not undefined?
The result of both "solutions" would create a non-bijective parser.