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

Render access=military as access=private #3332

Closed
Penegal opened this issue Aug 7, 2018 · 6 comments · Fixed by #542
Closed

Render access=military as access=private #3332

Penegal opened this issue Aug 7, 2018 · 6 comments · Fixed by #542

Comments

@Penegal
Copy link
Contributor

Penegal commented Aug 7, 2018

Expected behavior

Render access=military as access=private in order to highlight the fact that these ways are not generally accessible.

Actual behavior

Rendered as usual, not highlighting the restriction.

I can take care of this, but, first, is this suggestion relevant?

@matkoniecz
Copy link
Contributor

Can you link to the OSM wiki page documenting access=military?

@kocio-pl kocio-pl added the roads label Aug 7, 2018
@kocio-pl kocio-pl added this to the Bugs and improvements milestone Aug 7, 2018
@Penegal
Copy link
Contributor Author

Penegal commented Aug 7, 2018

It seems there is none; should I create it or is this condition enough to decline the suggestion?

Edit: note, though, that there are about 1800 uses of this tag, and that it seems rather self-describing, in that it highlight that general access is forbidden.

@kocio-pl
Copy link
Collaborator

kocio-pl commented Aug 7, 2018

The best thing is always to document usage of tags so the people know what's really available.

@HolgerJeromin
Copy link
Contributor

Rendering it would promote that the tag is ok.
Which is not imo. =private is correct.

@matkoniecz
Copy link
Contributor

should I create it

I would strongly discussing it first on tagging mailing list - I think that access=private is preferable.

@kocio-pl
Copy link
Collaborator

kocio-pl commented Aug 7, 2018

Until the discussion gives some conclusions, I think we can close it, as this is not a rendering stage. It can be reopened later if there will be a need to discuss rendering it.

@kocio-pl kocio-pl closed this as completed Aug 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants