Talk:Proposed features/assembly point:purpose

From OpenStreetMap Wiki
Jump to navigation Jump to search

Looks good to me Aharvey (talk) 08:34, 29 September 2018 (UTC)

I think this is this proposal is a great solution. Here's an image of a tornado shelter that you might include. The image is CC-BY licensed, so there should not be any licensing issues as long as credit is given. -- Micahcochran (talk) 14:47, 29 September 2018 (UTC)

+1 from me as well, it’s important to differ between the various types of emergency collection points! --LukeLR (talk) 20:23, 29 September 2018 (UTC)

Hello, I'm french. Excuse me for my english. I work too on emergency situation and I like your proposed feature. However I would distinguish the assembly points of the shelters: assembly point can be outdoors while the shelters are necessarily indoors. I haven't made any proposals yet on emergency shelters (assembly_point vs amenity=shelter; shelter_type=*. I think there is something to do on that side. What's your opinion about this? Gendy54 (talk) 00:32, 1 October 2018 (UTC)

I think that emergency=assembly_point and amenity=shelter specify two different and indipendent features. An assembly point can be or not be also a shelter. A shelter can be or not be also an assembly point. So assembly points and shelters are already distinguished and this proposal should not influence amenity=shelter. Danysan (talk) 09:59, 1 October 2018 (UTC)

I personally would like the assemble_point:purpose variant, multiple purposes can always be added as a ;-separated list. This is what is used e.g. in the railway tagging and has IMHO the advantage that is takes much less code to catch multiple values at once. The only thing is that the separator has to be explicitely specified in the tag documentation to make it explicit which one is to use. One other thing is that the usual assembly points you may find in urban areas (in Germany) is not for a specific purpose, but more for an area (sign). It's like "if anything goes wrong (in the building), go there". The most common case would probably be fire, but they may also be used for bomb warnings, gas leaks or whatever. --Dakon (talk) 08:13, 14 October 2018 (UTC)

Yes, you can add a list of emergency types to assembly_point:purpose=*, but then you would be implying that the point is only suitable for these types; however that may not be true. For example you could know that an assembly point is designed for fires and floods but not know if it is designed for earthquakes; writing assembly_point:purpose=fire;flood implies that it's only designed for fires and floods; writing assembly_point:fire=yes+assembly_point:flood=yes instead does not imply anything about earthquakes, unless you specify assembly_point:earthquake=no. - Danysan (talk) 12:48, 15 October 2018 (UTC)

It is a bit sad that I might make this suggestion, but in the USA, the plague of school shootings (it is an ugly social topic) has caused many schools and school districts to create very detailed plans in case this emergency happens at a particular school. For an assembly_point=* of this sort, we might also include assembly_point:active_shooter=yes as a tag on a node or way where students are to gather safely in case of this sort of "attack" (whether for drills or the real event). This is especially true as many high- and middle-school students have recently begun to "micro map" their campus in a surge of youth crowdsourced mapping activity in the USA. Stevea (talk) 09:08, 14 October 2018 (UTC)

As I understand it, assembly_point is an outdoor thing. Similar to a bomb or fallout shelter, I assume the spot to gather for a school in an active shooter situation is not outdoors. I would consider that location a version of a shelter.
The school may also have an assembly_point - the Athletics field or park nearby in case of fire or earthquake evacuation - but if the cafeteria or a designated room in a building or a designated building in a campus is a safe room from a shooter - this doesn't sound like assembly_point, more like a form of shelter. Javbw (talk) 11:25, 14 October 2018 (UTC)