-
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
Oneway arrows prevent display of long street names #2006
Comments
I can confirm this issue as well. Are there any places where it occurs i monolingual areas as well? |
Here is one example where the label is not shown on zoom 19, though it is on lower zooms: http://www.openstreetmap.org/way/7371850 |
In my opinion it's one of the most irritating bugs, making the map useless in some areas. Street names belong to the most important names, they are essential for navigation and orientation. |
The question is, what is more important, the arrows or the names? Would it be possible to avoid this problem somehow by making the arrows part of the name in the rendering? |
sent from a phone
I would render them before, and render the name over them (because of the halo the names will still be visible) |
@kdudzik Pull Requests are quite welcome! |
@nebulon42 in a few weeks I'll try to configure the environment and start to participate, but at the moment I can only count on others (not much time). Thanks though for the encouragement :) |
I think the arrows are most important, but there are many examples where names could easily have been displayed where instead several arrows are displayed on one street. If it's a short street that doesn't have space for both an arrow and the name, then only an arrow should be shown. If it's a long street where there is enough space for at least one arrow in addition to the name, then both should be shown. Currently you can have very long one-way streets that don't display a name because there are too many arrows. |
Well, België/Belgique/Belgien has a terrible problem, not only very long street names, but also in 2/3 languages. In any case, I just finished moving one way arrow rendering from the The question is: is this move correct? Was there any particular reason to put one way arrow rendering in those layers? I'll clean up and post a PR in the afternoon. |
PR sent, now the classical before/after images :) z15 - included to show some pre-existing rendering diffreneces -- it seems that my fonts are different (this is a Debian Sid setup), and I have a slightly outdated database (not enough free space to keep an updatable db, sorry). Also, no bicycle or horse info. z16 - No bicycle info means no one way arrows in the cycleways to the sides of the tertiary at center right. At least one new name “Rue Saint-Vincent/Sint Vincentiusstraat". z17 - Two more: “Rustplaatslaan” and “Van Cutsem”. z18 - Last one. Even “Dekoster" renders names and arrows. |
Looks great to me! :) |
Just for reference, our arrows used to be made with dasharrays until #1840. Conflicts with names wasn't brought up at the time. |
2016-09-02 10:32 GMT+02:00 Paul Norman [email protected]:
+1, because overlap was possible. The overlap should be reenabled with the |
Long street names (by the looks of it, over 20 characters long) are not displayed on oneway streets. This is especially troublesome in bilingual areas where the name in both languages is used.
See for example http://www.openstreetmap.org/way/22575474:
The text was updated successfully, but these errors were encountered: