-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Render reedbed with a non-transparent color #2013
Comments
Currently this style is trying to use pattern only rendering without a fill color for wetlands where the ground is sometimes/partly water covered. This is the case for reed which grows to considerable water depth - see: https://en.wikipedia.org/wiki/Phragmites The problem here is more that mapping tends to put the waterline at the outer edge of the reed bed and the actual water line within the reed is not mapped. This is perfectly understandable and also makes sense from a certain perspective but strictly seen there is no convention in OSM mandating that. More generally color fills are also problematic for wetlands at the moment since they render differently when overlapping with ocean compared to overlapping with natural=water. This is a problem for tidal flats for example. Once the move to water polygons is made (#1982) this could be reconsidered. |
sent from a phone
I d suggest to put the waterline at the actual position, so to comprise the reed bed, which not only solves the rendering issue but also is more consistent and closer to reality. |
Knowing what I know from the pretty common reedbeds here in the Netherlands, this will be nearly impossible. Reed can grow extremely dense both on land and in water (logged) positions. Including the reed bed as part of a water feature will therefore be as many times wrong as it may be right. In fact, reed used to cover roofs is often collected from fields that may be water logged part of the year, with a soft peaty soil, and may be dry in other parts of the year. Other times, reed is collected in harsh winters, when the soil or water is frozen so its accessible. |
I've reported a similar issue in #2025. My suggestion is to keep rendering For instance, while |
I think that primary problem is
Overriding water data and always rendering reed bed as on land or on water will worsen display in places with correct data. I think that it would not be desirable. |
Thinking about it i would probably support adding a plain color background to all vegetated wetland types (grass for saltmash/reedbed, wood for swamp/mangrove) after #2066 and moving the ocean layers above the landcover base layer. |
I agree, it should be possible to distinguish coastline/waterline inside the redbeed, and transparency allows that. There are different ways to determine coastline. For instance, it may match the zero level of (local) datum. Imported coastline data by national land survey of Estonia at least partly uses this method. Generally, reedbed lies on both sides of this coastline. |
Nobody is currently involved in this problem, it's stale for almost 2 years. Would you like to propose a code solving it? |
My comment was about why it'd be good to keep given style transparent. So if this question is addressed to me then I rather wouldn't propose a code "solving" it. I found this issue as I was planning to map a large reed area. Now I doubt if I should as actual coastline might be lost because of that later on. |
@kocio-pl, do you want to close this issue since it seems mostly resolved? |
Well, I don't understand wetlands too much, so it's hard for me to say what state is this problem in. |
wetland=mud is rendered with a semi-transparent brown, so that the coastline or edge of the natural=water is still visible. This has the disadvantage of creating 2 new colors, and could also lead to mixing with other backgrounds, as seen with military areas and mud currently. Does anyone have thoughts about this? |
sent from a phone
On 30. Dec 2018, at 00:49, jeisenbe ***@***.***> wrote:
wetland=mud is rendered with a semi-transparent brown, so that the coastline or edge of the natural=water is still visible.
This has the disadvantage of creating 2 new colors, and could also lead to mixing with other backgrounds, as seen with military areas and mud currently.
Does anyone have thoughts about this?
I would not render “mud” at all, it isn’t on the wetland wikipage, IMHO for a reason: “mud” is odd amongst all those wetland types, it isn’t a type of wetland.
|
I always thought mud was a wierd tag. Its not really a thing in itself, but the temporary state of something else (dirt). How would someone confirm a muddy area is constantly that way anyway? Unless its the shore of a water body or part of a wetland. In which case it should just be tagged as those things or a shoreline. Personally, I usually just tag them as intermittent ponds. |
Sorry, my mistake. We render natural=mud and wetland=tidal_flat in
this way, but in landcover it's listed as wetland_mud. I think of the
rendering as "mud", as that is the name of the color in landcover.mss
Natural=mud and wetland=tidal_flat are both rendered with the same
sort of semi-transparent background fill color:
`rgba(203,177,154,0.3); // produces #e6dcd1 over @land`
- this has alpha 0.3, so it is 70% mixed with the background color
(usually land-color or water-color)
…On 12/30/18, dieterdreist ***@***.***> wrote:
sent from a phone
> On 30. Dec 2018, at 00:49, jeisenbe ***@***.***> wrote:
>
> wetland=mud is rendered with a semi-transparent brown, so that the
> coastline or edge of the natural=water is still visible.
>
> This has the disadvantage of creating 2 new colors, and could also lead to
> mixing with other backgrounds, as seen with military areas and mud
> currently.
>
> Does anyone have thoughts about this?
>
I would not render “mud” at all, it isn’t on the wetland wikipage, IMHO for
a reason: “mud” is odd amongst all those wetland types, it isn’t a type of
wetland.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#2013 (comment)
|
Regarding color mixing due to transparency - this was specifically addressed when the original change was made in #1497 by rendering mud/tidalflat before all other landcovers and it was tested back then. If you now get color mixing with other landcovers this is a bug introduced by later changes.
|
@imagico, do you think mangroves and reedbeds could be rendered reasonably
well, by using a similar method?
I recall that your earlier recommendation was to switch to water polygons
first, and the render the ocean water above the landcover background
(without transparency).
…On Sun, Dec 30, 2018 at 7:20 PM Christoph Hormann ***@***.***> wrote:
Regarding color mixing due to transparency - this was specifically
addressed when the original change was made in #1497
<#1497> by
rendering mud/tidalflat before all other landcovers and it was tested back
then. If you now get color mixing with other landcovers this is a bug
introduced by later changes.
#e6dcd1 was the original mud color before #1497
<#1497>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2013 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AoxshFc1DWHFJaKSLy8-canuD0hcHFMUks5u-JOBgaJpZM4G9g-k>
.
|
As said before my approach would be to move to water polygons, do the layer re-ordering and start from there. But this style has meanwhile moved into a different direction making this rather difficult. |
What is blocking move to water polygons? As far as i'm aware the problem was that somebody had problems with rendering on some setup, but I might confuse something, since I was not directly interested in it. |
I have not followed all of the more recent changes but i don't think compatibility with using water polygons has been a consideration any more. Can't say which changes exactly might be a problem here but at least #3065 is not compatible. |
Do you think that it's incompatible as an implementation or not doable with water polygons at all (as an idea)? |
Regarding #3065 i don't know. In general it seems compatibility with water polygons has not been a consideration for changes during the last 1-2 years so i have no idea what other problems there might be. It could also depend on what kind of layer ordering you ultimately want to have. |
Unfortunately I'm not interested in wetlands etc, so can't help much, but it looks like it would need to check what might be conflicting here first. Probably not an easy task. |
Now the ocean and water areas are rendered above landcover fill, so we can add a color to reedbeds (and mangroves) without problems. What color should we use? Options would be: A) Use the same light green used for grass and marshs:
B) Use brownish-green heath color
C) B) Use mid-green-gray color of Advantages:
Disadvantages
D) Use the light yellow-green color Advantages:
Disadvantages:
E) Find a new color, perhaps a shade of mid-green, greenish-brown, yellow-green or blue-green? Advantages:
Disadvantages
Right now my favorite idea is to use the light yellow-green color of |
Test images:
Current rendering (Italy)wetland=reedbed around a small reservoir Bradano river - reedbed where it enters a lake. 1) Reedbed with scrub color fill -
|
Tests in Zeeland, the Netherlands 0) Current rendering - z161) Reedbed with scrub color fill -
|
3 for me |
Bradano river - reedbed where it enters a lake. |
To be clear, what is the effect of proposed changes on redbeed areas that lie on both sides of the coastline (discussed above)? E.g. is coastline still going to be distinguishable here: https://www.openstreetmap.org/#map=17/58.74029/23.78967? |
Water areas and seas are rendered above the landcover fill color, so the
background will still be blue for areas of reedbeds over water or outside
of the coastline. The coastline will be shown by the line between green and
blue.
|
Currently, if one considers a reed-bed to be in the water, then choosing where to draw the waterline is an unsatisfying choice, because of the rendering. Either one draws the waterline:
Here is my current example of the latter. I propose to always give the bed a more solid colour, no matter on which side the shore is. |
This does not look like a comment on the (closed) issue but a new request. As such it seems, however, a duplicate of #3854. |
See above comments that also discuss the third option, i.e. one draws the actual waterline between these two. You normally can't distinguish the actual waterline inside reedbed based on aerial image alone, but sometimes this data is available from open data sources, and the data shouldn't be skewed only because some might think that skewed data looks nicer on a map. |
Apparently the rendering has changed. There is one problem that I came across: DRY reed-beds. As far a I know there no good alternative for wetland=reedbed, but this is not what I mean, because of the wet aspect. It also creates the problem that paths or tracks drawn through it are badly visible, because of the blue stripes. I think I will add a separate issue. |
An area of reedbed is currently rendered as an overlay with a transparent color. This is imho incorrect because one doesn't see any water.
Example (the brown area in the west and north is reedbed):
The current rendering result (https://www.openstreetmap.org/#map=14/54.8719/8.3219):
I recommend to render reedbed this way (example):
Regards Klaus
The text was updated successfully, but these errors were encountered: