Proposal:Funeral hall=*
The Feature Page for this approved proposal is located at Key:funeral hall |
Funeral hall subtag | |
---|---|
Proposal status: | Approved (active) |
Proposed by: | Vollis |
Tagging: | funeral_hall=* |
Applies to: | |
Definition: | a building or room for funeral ceremonies ancillary to some other facility such as a funeral directors shop or a crematorium |
Statistics: |
|
Draft started: | 2020-09-17 |
RFC start: | 2020-09-17 |
Vote start: | 2020-01-29 |
Vote end: | 2020-02-13 |
Rationale
The present proposal is an offshoot of the - now approved - proposal for amenity=funeral_hall.
While the tag amenity=funeral_hall is for a place for holding a funeral ceremony, other than a place of worship, it was suggested in the description there not to use that tag if the room is clearly ancillary to either a shop=funeral_directors or an amenity=crematorium. Nevertheless, during the discussion there, it emerged that subtags would be useful for such shops/amenities, to indicate whether they have a room for funeral ceremonies or not.
In the discussion here, on the other hand, the point was made that it can still make sense to map the funeral hall apart (e.g. when its location within the premises is known), but there can be cases where this is not practical.
This leads to the reformulation of the proposal as seen below:
Proposal
It is proposed to use a subtag with the key funeral_hall=* whenever it isn't practical or seems inadequate to map a funeral hall apart from the main feature (such as a crematorium or funeral directors shop) to which it is linked.
This would result in the following combinations:
shop=funeral_directors
funeral_hall=yes/no
and
amenity=crematorium
funeral_hall=yes/no
In other words, the proposal is to simply have a flag at our disposal that can be added to the main feature if necessary, without in any way affecting the possibility to map the funeral hall apart instead.
What this proposal is not
The present proposal does not
- discourage the distinct mapping of a funeral hall, whenever it seems feasible and approprate to the mapper,
- prejudge (be it positively or negatively) any other future use of the tag.
Comments
Please comment on the discussion page (a first voting attempt was transferred there).
Voting
- Log in to the wiki if you are not already logged in.
- Scroll down to voting and click 'Edit source'. Copy and paste the appropriate code from this table on its own line at the bottom of the text area:
To get this output | you type | Description |
---|---|---|
{{vote|yes}} --~~~~
|
Feel free to also explain why you support proposal. | |
{{vote|no}} reason --~~~~
|
Replace reason with your reason(s) for voting no. | |
{{vote|abstain}} comments --~~~~
|
If you don't want to vote but have comments. Replace comments with your comments. |
~~~~
automatically inserts your name and the current date.For full template documentation see Template:Vote. See also how vote outcome is processed.
- I approve this proposal. --Gendy54 (talk) 15:40, 31 January 2021 (UTC)
- I approve this proposal. --Something B (talk) 14:06, 4 February 2021 (UTC)
- I approve this proposal. --EneaSuper (talk) 11:56, 7 February 2021 (UTC)
- I approve this proposal. --Reino Baptista (talk) 12:25, 7 February 2021 (UTC)
- I approve this proposal. --V-Li (talk) 12:48, 7 February 2021 (UTC)
- I approve this proposal. --Mannivu (talk) 13:34, 7 February 2021 (UTC)
- I approve this proposal. --Martin minheim (talk) 14:28, 7 February 2021 (UTC)
- I approve this proposal. --Santamariense (talk) 15:26, 7 February 2021 (UTC)
- I approve this proposal. --Gileri (talk) 18:35, 7 February 2021 (UTC)
- I approve this proposal. --RCD49
- I approve this proposal. --JOlshefsky (talk) 12:11, 10 February 2021 (UTC)
- I approve this proposal. --Krystek (talk) 15:50, 11 February 2021 (UTC)
Voting on this proposal has been closed.
It was approved with 12 votes for, 0 votes against and 0 abstentions.