gravitystorm / openstreetmap-carto

A general-purpose OpenStreetMap mapnik style, in CartoCSS
Other
1.55k stars 822 forks source link

Render cemetery=grave #5039

Open wlakom opened 3 weeks ago

wlakom commented 3 weeks ago
          I think it's time to reopen this topic and add an icon representing a grave, similar to https://umap.openstreetmap.fr/en/map/new/#19/53.83448/18.10317

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 https://github.com/gravitystorm/openstreetmap-carto/issues/1068#issuecomment-2450356627

          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:

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 https://github.com/gravitystorm/openstreetmap-carto/issues/1068#issuecomment-2450509404

imagico commented 3 weeks ago

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.

wlakom commented 3 weeks ago

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.

imagico commented 3 weeks ago

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.