Opened 13 months ago
Last modified 13 months ago
#23404 new enhancement
ID style some bug
Reported by: | jmxtzgbv9 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | External mappaint style | Version: | |
Keywords: | ID style | Cc: | Klumbumbus |
Description (last modified by )
iD style missing some style,for example:
All highway no tunnel style.(But in iD edtior have)
ridge and valley color are #8CD05F
.
piste:type line's color are #AA99DD
.
if them can were fixed. I'd appreciate it.
Attachments (0)
Change History (7)
comment:1 by , 13 months ago
Description: | modified (diff) |
---|
comment:2 by , 13 months ago
Component: | Core → External mappaint style |
---|---|
Description: | modified (diff) |
Milestone: | Longterm |
Version: | latest |
follow-ups: 4 7 comment:3 by , 13 months ago
Cc: | added |
---|---|
Type: | defect → enhancement |
@jmxtzgbv9:
I am sorry but I had to revert you last change as it was broken.
- For the valley and ridge you need to adjust the color for
way[natural=ridge] {
andway[natural=valley] {
. Last time you modified the rendering of the nodes which are deprecated. - If some
military=*
have some new color, you need to create a new code block with the tags. Last time you did insert the new color within a block which damaged the whole style. piste:type
is a bit more tricky. At least highways should not be overridden ([!highway]
) and we have colors forpiste:difficulty
at z-index -1. Was the support forpiste:difficulty
dropped in iD? Is this only about ways withouthighway=*
And how to handle ways withhighway=*
andpiste:type
but withoutpiste:difficulty
:Maybe even different widths per zoom level are useful for the ways withoutarea[piste:type][!highway][!piste:difficulty][area=yes]::core_piste { fill-color: piste_type#aa99dd; } way[piste:type][!highway]::core_piste { width=3 color: piste_type#aa99dd; } way[piste:type][highway][!piste:difficulty]::core_piste { z-index: -1; /* below line style from highway=* tag */ modifier: false; /* suppress default line if there is no style on default layer */ width: 6; color: piste_type#aa99dd; }
highway=*
follow-up: 5 comment:4 by , 13 months ago
Replying to skyper:
@jmxtzgbv9:
I am sorry but I had to revert you last change as it was broken.
- For the valley and ridge you need to adjust the color for
way[natural=ridge] {
andway[natural=valley] {
. Last time you modified the rendering of the nodes which are deprecated.- If some
military=*
have some new color, you need to create a new code block with the tags. Last time you did insert the new color within a block which damaged the whole style.piste:type
is a bit more tricky. At least highways should not be overridden ([!highway]
) and we have colors forpiste:difficulty
at z-index -1. Was the support forpiste:difficulty
dropped in iD? Is this only about ways withouthighway=*
And how to handle ways withhighway=*
andpiste:type
but withoutpiste:difficulty
:Maybe even different widths per zoom level are useful for the ways withoutarea[piste:type][!highway][!piste:difficulty][area=yes]::core_piste { fill-color: piste_type#aa99dd; } way[piste:type][!highway]::core_piste { width=3 color: piste_type#aa99dd; } way[piste:type][highway][!piste:difficulty]::core_piste { z-index: -1; /* below line style from highway=* tag */ modifier: false; /* suppress default line if there is no style on default layer */ width: 6; color: piste_type#aa99dd; }highway=*
I'm,sorry. But,how to reate a new code block with the tags?
follow-up: 6 comment:5 by , 13 months ago
Oh, I forgot to mention that the right click menu in the Map Paint Style panel offers to save any style as a local file to modify and test it, locally.
Replying to anonymous:
I'm,sorry. But,how to create a new code block with the tags?
Delete the line with the tag in its current block and add e.g.:
area[military=danger_area] { fill-color: military#ff5555; }
comment:6 by , 13 months ago
Replying to skyper:
Oh, I forgot to mention that the right click menu in the Map Paint Style panel offers to save any style as a local file to modify and test it, locally.
Replying to anonymous:
I'm,sorry. But,how to create a new code block with the tags?
Delete the line with the tag in its current block and add e.g.:
area[military=danger_area] { fill-color: military#ff5555; }
And,why watreway no tunnel style, too?
comment:7 by , 13 months ago
Replying to skyper:
@jmxtzgbv9:
I am sorry but I had to revert you last change as it was broken.
- For the valley and ridge you need to adjust the color for
way[natural=ridge] {
andway[natural=valley] {
. Last time you modified the rendering of the nodes which are deprecated.- If some
military=*
have some new color, you need to create a new code block with the tags. Last time you did insert the new color within a block which damaged the whole style.piste:type
is a bit more tricky. At least highways should not be overridden ([!highway]
) and we have colors forpiste:difficulty
at z-index -1. Was the support forpiste:difficulty
dropped in iD? Is this only about ways withouthighway=*
And how to handle ways withhighway=*
andpiste:type
but withoutpiste:difficulty
:Maybe even different widths per zoom level are useful for the ways withoutarea[piste:type][!highway][!piste:difficulty][area=yes]::core_piste { fill-color: piste_type#aa99dd; } way[piste:type][!highway]::core_piste { width=3 color: piste_type#aa99dd; } way[piste:type][highway][!piste:difficulty]::core_piste { z-index: -1; /* below line style from highway=* tag */ modifier: false; /* suppress default line if there is no style on default layer */ width: 6; color: piste_type#aa99dd; }highway=*
in iD, give up support for piste:difficulty dropped.(add That tag just a white line.)
It looks like you've modified wiki:Styles/iD in the past. Have you considered making further modifications yourself?
If you aren't particularly familiar with MapCSS, wiki:Help/Styles/MapCSSImplementation has some good documentation.
For example, for
piste:type
, I would have a rule something likeway["piste:type"]{color: #AA99DD;}