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 archeological site polygons as tourism boundary #3958

Closed
StyXman opened this issue Oct 29, 2019 · 2 comments
Closed

Render archeological site polygons as tourism boundary #3958

StyXman opened this issue Oct 29, 2019 · 2 comments

Comments

@StyXman
Copy link
Contributor

StyXman commented Oct 29, 2019

Archeological sites are usually tourist attractions. We already render them as amenity points, but some of them are frankly quite big, and mapped as polygons. Just render the same polygon effect for zoos and theme parks for those polygons.

@matkoniecz
Copy link
Contributor

repeat of #732 but not a duplicate, as provides a specific rendering idea that makes sense and has decent chance to be an overall improvement

@imagico
Copy link
Collaborator

imagico commented May 23, 2022

I suggest to close this - if an archeological site has a physically manifested verifiable boundary then that should be mapped and rendered as such (like barrier=*) same applies if ruins are visible and can as such be mapped. But rendering legal bounds of sites as such (which practically is often simply guesswork or abstract wrapper polygons) is something we should reduce rather than extend IMO.

Indicating visually in some form which mapped ruins belong to a certain (named) archeological site would be something interesting to consider i think - but it would require (a) an established tagging for the ruins of an archeological site, (b) an established way to map which ruins belong to a site and (c) probably quite a bit of work to develop an efficient and visually suitable way to depict that.

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

Successfully merging a pull request may close this issue.

4 participants