Support cemetery/graveyard sectors

[soshial]

Expected behavior

At least show ref number or sector name. See wiki.

Actual behavior

Links and screenshots illustrating the problem

[jeisenbe]

@soshial thank you for opening this issue.

The tag cemetery=sector was not approved when there was voting in July 2014, but it has been used in some places since then.

https://wiki.openstreetmap.org/wiki/Tag:cemetery%3Dsector

But usage is patchy: it’s not been used in England, and only in a few US States, and even in central Europe where it is regionally common it isn’t used in most provinces:

Usage is increasing in small jumps, probably since a large number are added at a time by a few mappers:

It would be good to talk about this tag in some public forums such as the Tagging mailing list to see if there are any issues with it, or if there are other tags used in a similar way. To increase support for the tag, if the community agrees, it would be helpful to see if iD and other editor applications would want to make it a preset option for mappers.

Unfortunately it would not be possible for us to render this feature right away, because the key cemetery=* is not imported as a polygon in our local database set-up. This same issue affected allotments=plot which has some similarities - see https://wiki.openstreetmap.org/wiki/Tag:allotments%3Dplot and issue #432 here, as well as PR #3786 which now allows allotments= features to be imported as polygons when mapped as closed ways.

If we decide to support this tag, it won’t be until after the next database reload when we could start rendering it, but at some point we will need to decide if it should be included as an option or not.

[Adamant36]

Is there a good way to know how many graveyard sectors are just tagged with the ref tag? Because that might be something to look into before going anywhere with this.

Update: Doing

[bbox:{{bbox}}][timeout:1800];

way["landuse"="cemetery"];map_to_area->.a;
( node(area.a)[ref];
way(area.a)[ref];
);
foreach(
(._;>;);
is_in;
way(pivot)[ref];
out geom;
);

In Overpass Turbo didn't result in anything. Although it could have been the area I searched or the query is just wrong somehow.

[aceman444]

The sectors are also mapped as nodes (where the extent isn't clear), and also have a 'name' instead of 'ref', even if is is kinda numeric like "XII." (that can be fixed in the data if that is wrong).

Also, JOSM does have a preset for the cemetery=sector feature.

[jeisenbe]

Usage is now 20k, with 15k areas and 5k nodes

11k (55)% have a name= tag
11k (54)% have a ref= tag

https://taginfo.openstreetmap.org/tags/?key=cemetery&value=sector#combinations

Usage is a little more spread in Europe but not much elsewhere

It is now supported by JOSM and Vespucci but not iD editor - it would be a good idea to ask for it to be added there first - https://github.com/openstreetmap/iD/issues

Adding any rendering would require database reload, which was last done 2 years ago for v5.0

[jidanni]

All I know is I mapped plenty of these with ease in ID.... in fact it would seem to be the ideal local school project.

Alas what's the point of encouraging kids to do something that won't show up anywhere?

It's like, if you're alive your house number gets shown on the map even if you're house number fell off your house.

But when you're dead, even hundreds of you grouped together, after fancy funerals and all that fuss, don't even get a single letter to your name.

Might as well be tossed in the ocean.

[Dimitar5555]

It is now supported by JOSM and Vespucci but not iD editor

It was added in iD in August 2022 (openstreetmap/id-tagging-schema#517)

Usage is now close to 28k, with ~21.6k areas and 6.3k nodes

13k (47)% have a name= tag
16k (58)% have a ref= tag

It has also spread to most parts of Europe, UK, and ~25-30 US states.

[Dimitar5555]

@imagico Is there any chance to consider adding some form of rendering for cemetery=sector? Or at least give an opinion on how it should be rendered (only ref, only name or both, border or no border for ways and MPs, border colour, fill etc.)?

Personally I think that rendering ref is mandatory, name can also be rendered in the format name \n ref (assuming both are present and \n being a new line).

Maybe something whiteish/greyish could work for the border, but it might be too similar to the currently rendered barrier= features. Filling is likely not needed, if there is a border.

Rendering only name/ref/name \n ref should work for nodes with cemetery=sector.

iD Editor	Carto

[imagico]

This issue is open, suggestions or concrete design work to add this is welcome.

Note though that so far mapping of this has a strong regional (and cultural) focus. Hence it is important to consider different traditions/conventions to structure and manage cemeteries in different parts of the planet.

And labeling several different tags will only be acceptable if the design ensures it is universally clear which part of the label is from which tag. We don't want another case like #4629.