-
Notifications
You must be signed in to change notification settings - Fork 819
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
embankment and cutting as man_made #2902
Comments
For info (in case it provides inspiration) I'm also looking at embankments elsewhere, For example, http://map.atownsend.org.uk/maps/map/map.html#zoom=18&lat=53.281645&lon=-0.782162 shows a footway on an embankment to the south of the stream, and an embankment without a path on it to the north. I tried a bunch of different renderings, but "2 sided cliff" (for just an embankment) and "not quite a bridge" for a footway on one) looked best to me. |
Tag man_made=cutting has only 98 uses. Should we render it? |
For me I think so, because it is the opposite of embankment and also used on way line roads. It should be very strange when cutting=yes is on the road and a embankment is drawn next to it. |
Ways with embankment=yes: 134 356 So: As an additional road attribute, cutting is less frequent than embankment, but still frequent. Currently, we render neither of them. Anyway, for embankment=yes on roads, we have yet the ticket #791 which will probably not be solved fast. Nevertheless, the numbers show that “cutting” is a feature that exists yet in OSM. So the usage of man_made=cutting might grow in the future beyond the current 98 objects… |
Note that especially for cutting=yes tagged on a highway element, there is unfortunately lots of inappropriate usage. While the embankment and cutting tags were likely originally developed based on the symbols visible in topographic maps, especially those used to depict large embankment and cuttings of railways and motorways, people less experienced with reading or using true topographic maps misinterpret the tags and use it for all kinds of stuff I consider inappropriate, and making uncluttered rendering difficult:
|
Tags with low usage and no documentation should not be rendered in this style. |
Is it possible to have properly looking map and render both man_made=embankment and embankment=yes? In case that it is not possible I think that more detailed tagging (man_made=embankment) should be encouraged. |
I think we should close this issue now. It can be reopened once there's some discussion on Tagging list and wiki page at least, but also few thousands of usage is highly recommended. |
Also, it is almost duplicate of #791 In general I recommend promotion of tags by using them, documenting on wiki, adding them to editing presets - not by requesting to render tag used less than 1000 tones. |
On a roadline, way, there is embankment=yes and cutting=yes.
Embankment
You can also draw it beside the road, draw two parallel ways then we use a way with man_made=embankment, we place it on the highest edge line, where the embankment characteristic is a raised bank, in the landscape, with on top a road or something else, topographically correct.
The opposite is a lowered bank, a cut in the landscape, we should use there man_made=cutting, like embankment have a two unit. So should cutting have the same.
The characteristic of cutting is a lowered bank.
The pitfall is now people use embankment because the other is not rendered, this is not right.
I like to use the man_made=cutting. Although it has not a wiki page, yet, and not often used so far.
It feels so normal to have a opposite tag.
This for sunken lane, hollow way
With for OSM use, hillshade ground-level layers, I could draw the landcsape cutting line in. Where the cut is.
Also on other places.
The text was updated successfully, but these errors were encountered: