-
Notifications
You must be signed in to change notification settings - Fork 826
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
Rendering Wadi and Intermittent River/Stream #1255
Comments
This is the wrong place for discussing tagging ideas, this should be done on the wiki or the tagging mailing list. Discussion here should focus on how to render tags currently in use and current consensus is that use of |
To be more exact - work is finished and it waits for other maintainer with time to review it. |
Closing per
|
Hi Mateusz, On 25 January 2015 at 08:07, Mateusz Konieczny [email protected]
|
I am sorry if my reply appeared defensive but no one attacked you in any way. If you think the representation of certain geographical features in OpenStreetMap is insufficient (which i agree wholeheartedly to) the usual way would be to:
From classical cartography work you are probably used to a different approach, i.e. first develop a classification scheme based on rendering considerations and then map things according to this scheme but the above is how it is done in OSM. This forum only deals with the last point and this requires the first four things to be done already at least to some extent. I merely tried to point you to this by summarizing the current state of these things wrt. wadi/intermittent waterway mapping. |
Again thanks for the response. I am trying to find my way around and being On 25 January 2015 at 10:12, imagico [email protected] wrote:
|
Welcome @RAytoun! I think your request is essentially the same as #805, so I think it's best to continue the discussion there. I have just merged #1000, which is meant to resolve #805. This will be visible on the main site within a couple of weeks. Note that waterway=river_intermittent is in fact tagged as waterway=river, intermittent=yes. With the new rendering, waterway=river, intermittent=yes will be rendered just like wadi, namely as a pecked blue line. We might consider distinguishing river=wadi and intermittent=yes in the future, but a pecked brown line is probably not the best option as we use this for tracks already. By the way, I haven't seen that many maps of wadis, but the ones I have seen all render wadis as a blue pecked line rather than a brown one. |
Thanks for that. I made a comment regarding that before I received this. On 25 January 2015 at 19:03, math1985 [email protected] wrote:
|
RAytoun, It could be that these are rendered at some point in the main map style but it sounds a more specific need for you (and is most useful) in humanitarian situations so you should focus on getting this rendered for the HOT/humanitarian style first. |
@mkoniecz , @math1985
Hi, my name is Ralph (RAytoun) and I have been a cartographer all my working life. I was Senior Cartographer in Philip's School and World Reference Atlas section...responsible for the research and compilation of all new mapping, additions and amendments for the full range of Philip's World Atlas products. I am at present a member of HOT and a principal tutor for the Missing Maps Project, London.
I have raised a few points in this regard and have been pointed in your direction by Blake Girardot.
I see this issue was under discussion in September last year. Math1985 mentions intermittent should be different to wadi which is quite correct....mkoniecz said wadi is a term for a whole valley as well as dry stream which is also correct but may I add that in the parched and arid areas where wadis abound the sides of these "valleys" are sheer cliff walls and the floor of the valley is a dry flat flood plain. The sides of the flood plain would be added the same as for river banks but the outline would be a pecked line with no fill or is sometimes depicted with a light brown stipple fill.
My points are...
I would like to raise the issue of tags for waterway=river, waterway=stream and waterway=wadi.
The problem that exists with the existing tags is that there is no visual difference on the map for a stream (perennial) and a stream (intermittent) and the only other option is wadi which gives a blue pecked line.
Accepted mapping standards for this would be to show:-
all perennial rivers and streams as a continuous solid blue line (indicating that there is flowing water all year round) or solid blue outline (river banks) with a light blue fill.
all non-perennial rivers and streams as a continuous blue pecked line (indicating that there is flowing water during the wet season but not the whole year). River banks would be pecked blue line with light blue fill.
A wadi would be depicted with a continuous pecked brown line (indicating that it is dry watercourse and could be dry for years at a time...only flowing if there is a flash flood or unusually heavy rain). For wider wadis (valleys) a pecked brown outline with no fill or brown stipple fill.
This would then convey the correct meanings with symbols on the map and make reading the map a lot easier. The categories would still be searchable and distinguish between the three categories of water flow.
The proposed tags would then be
waterway=river ...... waterway= stream ...... continuous solid blue line
waterway=river_intermittent ...... waterway=stream_intermittent ..... continuous pecked blue line
waterway=wadi ..... continuous pecked brown line (a wadi can be so wide that another tag would be needed similar to the tag for river banks) waterway=wadi_bank which would still be a brown pecked line either with no fill or a brown stipple fill.
This would then ease the path for introducing the tags for perennial lakes with a solid blue outline and lighter blue fill, intermittent lakes with a blue pecked outline and a light blue fill and dry pans with a brown pecked outline with a brown stipple fill.
If it is deemed appropriate is there someone who could do this or help me?
Reference...... http://pubs.usgs.gov/gip/TopographicMapSymbols/topomapsymbols.pdf
The text was updated successfully, but these errors were encountered: