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

Rendering of historic=high_cross #4833

Closed
b-unicycling opened this issue Jun 22, 2023 · 2 comments
Closed

Rendering of historic=high_cross #4833

b-unicycling opened this issue Jun 22, 2023 · 2 comments

Comments

@b-unicycling
Copy link

Expected behavior

It would be great if historic=high_cross could be rendered in some way, the easiest would be, if they were rendered like historic=wayside_cross.
More than half are National Monuments; it would be useful to have those shown on the map.

Actual behavior

Not rendered at all, because the tag didn't go through proposal process.

Screenshots with links illustrating the problem

Screenshot 2023-06-22 165136

@Sirorezka
Copy link

Sirorezka commented Jun 22, 2023

I agree, noticed same issue. Some historic objects and especially points are not rendered at all. One more example:

Link:
map_link

Screenshots:
image
image

@imagico
Copy link
Collaborator

imagico commented Jun 22, 2023

Thanks for the suggestion. historic=high_cross currently has 56 uses, almost all of them in Ireland, almost all of them added in the last 6 months. So too little basis so far to assess if the tag is sufficiently accepted by mappers and consistently used with a well defined meaning.

It is somewhat odd that given that

  • we render man_made=cross
  • man_made=cross would by most be considered valid tagging for the features in question
  • tagging man_made=cross would not collide with historic=high_cross in any way

hardly any of the 56 use cases are tagged man_made=cross.

And to be clear - proposal processes have very little bearing on if or not we render a tag.

@Sirorezka - different issue - see #331.

Closing this for the moment because lack of sustained broader use so far makes proper assessment impossible. This does not in any way prejudice a later assessment based on a better data basis.

@imagico imagico closed this as not planned Won't fix, can't repro, duplicate, stale Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants