Skip to content
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

Reformat semicolons in road names #1086

Closed
1ec5 opened this issue Oct 22, 2014 · 3 comments
Closed

Reformat semicolons in road names #1086

1ec5 opened this issue Oct 22, 2014 · 3 comments
Labels

Comments

@1ec5
Copy link

1ec5 commented Oct 22, 2014

When a street has multiple, equally common names, it’s common to place them all in the name tag, delimited by a semicolon but no space. This stylesheet displays that unpadded semicolon verbatim, which looks like a typo to me no matter how long I’ve been mapping.

If I recall correctly, Mapbox Streets handles semicolons by turning them into em dashes, which are more presentable. But that might get confusing in cases where an em dash is intended. It would be better if the names could somehow be spaced apart by a couple ems or something – less than the space between consecutive labels along a way, but enough to look intentional.

@matkoniecz
Copy link
Contributor

Multiple names in the name tag is an incorrect tagging - see http://wiki.openstreetmap.org/wiki/Name "The common default name.". alt_name tag should be used in this situation.

Yes, unfortunately it is sometimes unclear what should go into alt_name and what into name.

@dieterdreist
Copy link

2014-10-22 9:00 GMT+02:00 Mateusz Konieczny [email protected]:

Multiple names in the name tag is an incorrect tagging - see
http://wiki.openstreetmap.org/wiki/Name "The common default name.".
alt_name tag should be used in this situation.

Yes, unfortunately it is sometimes unclear what should go into alt_name
and what into name.

+1
if there are even more alternative names, they can go into loc_name,
nat_name, reg_name. When the names are in different languages (e.g. in your
area there is more than one language in use) you should use
language-suffixes, like name:en alt_name:en etc.

@matkoniecz matkoniecz added the wontfix-unfeasible Issues closed because of lack of suitable solution label Oct 22, 2014
@matkoniecz matkoniecz added declined and removed wontfix-unfeasible Issues closed because of lack of suitable solution labels Mar 24, 2016
@1ec5
Copy link
Author

1ec5 commented Dec 17, 2022

if there are even more alternative names, they can go into loc_name,
nat_name, reg_name. When the names are in different languages (e.g. in your
area there is more than one language in use) you should use
language-suffixes, like name:en alt_name:en etc.

This may be, but as numerous disputes and discussions among mappers have shown over the years, sometimes it isn’t tenable to limit name to just one value, even in conjunction with these subkeys. I refiled #4755 with a broader scope to cover not only road names but other things like place names as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants