This article or section may contain out-of-date information. The information is no longer correct, or no longer has relevance. If you know about the current state of affairs, please help keep everyone informed by updating this information. (Discussion)

OpenStreetMap: Tags in Current Usage

These are tags reporting status of infrastructure, building collapses and other related types of information relating to site conditions in the field - ad-hoc tags found in current use (Haiti response effort, Jan 2010, based on Haiti Tagstat):

Keys and values currently in use via Tagstat (1/16/09) - This table is sortable, click on headings to sort

Recommendations and Guidelines

Observations: earthquake:damage currently appears to have far more widespread usage as a primary condition assessment key being used in recording Haiti observations; others in use are far more ad-hoc. Roadway passability is very inconsistent - DruidSmith

Recommendation: Develop a basic, accessible ontology for describing site conditions - this should hopefully address

Building condition (collapse, danger of collapse)

Transportation (road passability, bridge collapses, et cetera)

Victims - trapped individuals, deceased individuals

Hazardous Materials - spilled chemicals, et cetera

and others (please add and contribute)

Models may include those developed by the Fire Service et al. From my own experience, DHS models may be cumbersome for short-term and perhaps better for long-term usage, whereas Fire Service is a bit more streamlined for quick understanding and use. -DruidSmith

Verification - how to provide information on verification of conditions, et cetera?

This, and the rest of SAR tags, should behave like the several levels of administrative boundaries: grids are inside sectors that are inside the area, and all of them share the edges. The area should be the sum of the sectors, etc.

This, and the following Search-and-Rescue tags are just a proposal - feel free to comment or modify as needed -- Ivansanchez

Means "One SAR team, or one SAR workforce, per sector". Goal is to prevent two teams or workforces to cover the same terrain twice. Optionally, use operator=* to specify the name of the team or workforce assigned to the sector.