ISO 7010 is a set of symbols to depict conditions (warnings, info).
How can I map their location? Can we define a similar tagging schema like traffic sign ?
These symbols are used for evacuation maps, and if we have a standard, they can be easily rendered with MapComplete
These are a special case of wayfinding sign. I’ve been wondering the same thing, since some versions of the U.S. national traffic sign standard cover both outdoor traffic signs and indoor wayfinding. For example, Ohio’s standard includes any sign that the highway department might need to put up inside a rest area:
I’ve documented these signs along with the usual signs with the justification that foot traffic is a kind of traffic too. But the VA Signage Design Manual really pushes the limits, as fully a third of the signs are only for indoor use inside hospitals, and another third are for parking garages and elevators:
I’d assume these indoor signs are only of interest to the most dedicated of indoor mappers. Then again, airports have their own wayfinding systems as well, and airports tend to be some of the most thoroughly micromapped places in OSM.
Ha, interesting how the Columbus Airport Authority came up with their own exit sign—at least, I presume it’s an exit sign—that’s basically the same as the internationally-recognized one, just in the internationally-recognized colour meaning “prohibited” or “firefighting-related thing”. 
That tornado pictogram is kinda neat though. I half-expected it to include a teeny pictogram of a cackling witch on a broom, with a speech bubble reading “I’ll get you my pretty, and your little dog too!”
You guessed right, it’s an emergency exit sign. Almost every building code in the U.S. requires textual “EXIT” signs, and some states and cities require red while others require green. But the combination of a red pictogram is unusual, both international and provincial at the same time. Rather fitting for the state that posted this traffic sign at rest areas until a few years back:
It’s for a tornado shelter. Most airports in Tornado Alley use a similar glyph, also without witch on broomstick. ISO 7010 lacks a suitable sign for tornado shelters; the closest thing is a warning that you’re entering a tornado zone, whatever that means.
As with traffic sign standards, individual countries have their own own addenda to the international standards (plural). A major challenge for devising a tagging scheme will be that multiple standards can coexist in a given region, since these signs are regulated by industry-specific standards. And then, of course, there’s the U.S., where these standards can be devolved all the way down to the local level or left up to the whims of individual manufacturers. Wikimedia Commons has an impressive collection of these safety sign diagrams that we could use to craft a reasonably extensible syntax.
As far as the key to use, I haven’t seen any gain much traction yet. A proposal for hazardous_materials=* aimed to cover U.S. “fire diamonds”, which are common on building exteriors. For the UN hazard pictograms, we could borrow some hazmat:*=* tagging since these signs also appear on roads in the U.S. Some German and Austrian mappers have begun putting national codes in sign=*, in a manner reminiscent of traffic_sign=*.
[offtopic]
We had the same textual signage in Canada—as far as I know always red text on white or white text on red—but the 2010 National Building Code changed it to the ISO “green running man”, and provincial building codes have followed suit (it’s been code in Alberta since the adoption of the 2014 Alberta Building Code).
Every once in a while one might still come across one of these bad boys though:
[/offtopic]
That Wikipedia article is conflating things a bit. ISO 7010 is a signage standard, whereas the GHS, US HMIS and Canadian WHMIS are chemical labelling standards. GHS pictograms are used here on truck trailers and things like that, not on road or building signage.
The American analogue to ISO 7010 is ANSI Z535; I don’t really know how prevalent that ANSI standard’s use is in practice though.
ISO 7010 is probably the most logical starting point, even if it does have some local variations in implementation.
GHS pictograms appear on some hazmat signs in the U.S., reflecting truck placarding and in turn container labeling. Many more hazmat restrictions are expressed in terms of GHS-harmonized divisions. But I agree that ISO 7010 would be a good starting point more generally.
Sigh, maaan, why d’you guys gotta be such weirdos with your traffic signs?
Thank you for your messages, but I still not sure how to map them?
What about something like this followed by the symbol code?
prohibition_sign=*
mandatory_sign=*
warning_sign=*
safecondition_sign=*
firesafety_sign=*
In this way, OSM could easily generate any emergency/security/hazard map.
I think I’d use either wayfinding_sign=* or safety_sign=*. It’s hard to come up with a key that encompasses these standards. You’re focused on evacuation maps, but the standards are broader than that, and scoped to industries or situations rather than the kinds of categories we usually deal with for traffic signs. There’s also some overlap with traffic sign standards, as noted earlier. We do have an escape hatch (heh) in the form of man_made=sign message=*, but something more specific would be better.
