forked from MapComplete/MapComplete
Performance: split validation into multiple files, avoid using 'fixImages' and 'exractImages' into well-known themes as it takes a big chunk of data
This commit is contained in:
parent
7d20a1924f
commit
b91b1378d1
16 changed files with 1009 additions and 949 deletions
|
|
@ -93,6 +93,10 @@ export default interface PointRenderingConfigJson {
|
|||
* question: What rotation should be applied on the icon?
|
||||
* This is mostly useful for items that face a specific direction, such as surveillance cameras
|
||||
* This is interpreted as css property for 'rotate', thus has to end with 'deg', e.g. `90deg`, `{direction}deg`, `calc(90deg - {camera:direction}deg)``
|
||||
*
|
||||
* If the icon is shown on the projected centerpoint of a way, one can also use `_direction:centerpoint`
|
||||
*
|
||||
* suggestions: return [{if: "value={_direction:centerpoint}deg", then: "Point north if the icon is pointing up"}, {if: "value=calc( {_direction:centerpoint}deg + 90deg)", then: "Point east if the icon is pointing up"}, {if: "value=calc( {_direction:centerpoint}deg + 180deg)", then: "Point south if the icon is pointing up"},{if: "value=calc( {_direction:centerpoint}deg + 270deg)", then: "Point west if the icon is pointing up"}]
|
||||
* ifunset: Do not rotate
|
||||
*/
|
||||
rotation?: string | TagRenderingConfigJson
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue