You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Re-opening would require convincing new arguments. The case example pointed to is a graveyard where every single grave is tagged `historic=tomb`. That speaks against rendering the tag under the premise of this issue (which is rendering `historic=tomb` as a class of historic sites).
For reference: Current use numbers:
historic=tomb: 66k uses, 26k with building=*, 25k with tomb=*
I have kept the latest of the four new issues opened on the same matter - please don't spam the issue tracker like this. There are lots of people following this who do not see it favorably to be unnecessarily bombarded with redundant notifications.
Regarding the suggestion itself. cemetery=grave is quite consistently used for contemporary individual burial sites. The mapping focus is so far fairly European (86k of 100k uses).
The main issue is that a 14 pixel symbol at z19 at the equator is more than 4 meters - which is substantially larger than the average space for an individual burial site on a dense cemetery. Bottom line: A meaningful depiction of individual graves at z19 on a global map would require using a much smaller symbol than our standard 14 pixel size.
And of course the question how meaningful it is to display individual burial sites on a cemetery independent of their physical setup would need to be discussed. Looking at various cemeteries with individual graves mapped but no mapping of trees (and other plants), barriers and incomplete mapping of footways (surface, width etc.) puts that into question.
You told me: @in that case, you can change the topic from Render historic=tomb to Render cemetery=grave.
We don't re-purpose issues like that. If you want to request rendering cemetery=grave as representing an individual grave in a cemetery please open a new issue for that.
I told you to open a new issue in the sense of one new issue, not four (#5036, #5037, #5038, #5039) of them. Anyway - just keep in mind for the future to be a bit more careful.
This icon shows that its dimensions are sufficient so that they don't overlap.
So, please create an icon for the tag "historic=tomb" for the OpenStreetMap.org map.
We already have entire cemeteries mapped, such as in Czarna Woda
https://www.openstreetmap.org/#map=18/53.834347/18.102832
https://taginfo.openstreetmap.org/tags/historic%3Dtomb#overview
We also have an updated " Wyszukiwarkę grobów na OSM (OSM Grave Finder)" that allows you to display grave descriptions:
https://dotevo.github.io/gravemap-osm/#16/50.0759/19.9550
Originally posted by @wlakom in #1068 (comment)
For reference: Current use numbers:
historic=tomb
: 66k uses, 26k withbuilding=*
, 25k withtomb=*
cemetery=grave
: 100k uses.Not really relevant here, but piece of advice: Before you add things like https://www.openstreetmap.org/relation/18092768 it might be a good idea to discuss with your local community first. See also https://wiki.openstreetmap.org/wiki/Limitations_on_mapping_private_information
Originally posted by @imagico in #1068 (comment)
The text was updated successfully, but these errors were encountered: