Differences

This shows you the differences between two versions of the page.

Link to this comparison view

standards:domain:start [2014/03/19 05:24]
waidyanatha [PFIF]
standards:domain:start [2017/04/27 02:38] (current)
waidyanatha [OCHA]
Line 9: Line 9:
 PFIF was created by Ka-Ping Yee in 2006, in response to the impact of hurricane Katrina along the US Gulf Coast, and the resulting proliferation of pop-up, incompatible web sites for missing-person reports. ​ Through version 1.1, its repository was hosted by Salesforce, Inc.  Version 1.2 addressed the Haitian earthquake of January, 2010, by including improvements to make the format more international. ​ This was done in association with Google, which became the main data aggregator with its “Google Person Finder” (PF) repository. ​ This version was also deployed during the Chile and Christchurch,​ New Zealand earthquakes. ​ Version 1.3 was defined in early 2011, and deployed towards the end of reporting about the earthquake and tsunami that devastated the Tohoku region of Japan. ​ Traditionally considered a de facto standard, PFIF (now up to version 1.4) has been incorporated as a component of the new "​Tracking Emergency Clients"​ specification,​ now under formal standardization consideration by OASIS. PFIF was created by Ka-Ping Yee in 2006, in response to the impact of hurricane Katrina along the US Gulf Coast, and the resulting proliferation of pop-up, incompatible web sites for missing-person reports. ​ Through version 1.1, its repository was hosted by Salesforce, Inc.  Version 1.2 addressed the Haitian earthquake of January, 2010, by including improvements to make the format more international. ​ This was done in association with Google, which became the main data aggregator with its “Google Person Finder” (PF) repository. ​ This version was also deployed during the Chile and Christchurch,​ New Zealand earthquakes. ​ Version 1.3 was defined in early 2011, and deployed towards the end of reporting about the earthquake and tsunami that devastated the Tohoku region of Japan. ​ Traditionally considered a de facto standard, PFIF (now up to version 1.4) has been incorporated as a component of the new "​Tracking Emergency Clients"​ specification,​ now under formal standardization consideration by OASIS.
  
-[PFIF] Specifications (pre-TEC) for version 1.1 - 1.4 are at http://​zesty.ca/​pfif/​  +  * [PFIF] Specifications (pre-TEC) for version 1.1 - 1.4 are at http://​zesty.ca/​pfif/​  
- +  ​* ​[MPCI] Missing Persons Community of Interest http://​www.mpcionline.org ​
-[MPCI] Missing Persons Community of Interest http://​www.mpcionline.org ​+
  
 Sahana'​s Krakatoa incorporated early PFIF code, with the first production fetch from Google PF during the Haiti earthquake. ​ Krakatoa'​s successor, Vesuvius, and its US National Library of Medicine "​People Locator"​ (PL) instance, continue to incorporate PFIF as it evolves, and participate in active exchange (e.g., during the Japanese tsunami). ​ Currently, interchange of data between PL and PF supports PFIF 1.4 in both directions, but some elements of the Vesuvius user interface need to evolve during 2013 to reflect changes between PFIF 1.3 and 1.4.  ​ Sahana'​s Krakatoa incorporated early PFIF code, with the first production fetch from Google PF during the Haiti earthquake. ​ Krakatoa'​s successor, Vesuvius, and its US National Library of Medicine "​People Locator"​ (PL) instance, continue to incorporate PFIF as it evolves, and participate in active exchange (e.g., during the Japanese tsunami). ​ Currently, interchange of data between PL and PF supports PFIF 1.4 in both directions, but some elements of the Vesuvius user interface need to evolve during 2013 to reflect changes between PFIF 1.3 and 1.4.  ​
Line 56: Line 55:
  
 The UN Office for the Coordination of Humanitarian Affairs has been supporting the definition of "​Common Operational Data Sets" (e.g., [[http://​www.pacificdisaster.net/​pdnadmin/​data/​documents/​3965.html|in the Pacific and Asia]]). ​ The effectiveness of this ambitious effort is as yet unclear. The UN Office for the Coordination of Humanitarian Affairs has been supporting the definition of "​Common Operational Data Sets" (e.g., [[http://​www.pacificdisaster.net/​pdnadmin/​data/​documents/​3965.html|in the Pacific and Asia]]). ​ The effectiveness of this ambitious effort is as yet unclear.
 +
 +===== OSM =====
 +**OpenStreetMap Humanitarian Geo-tagging work with the Humanitarian Data Model**
 +
 +Humanitarian OpenStreetMaps Team (HOT) work on HDM this applies only to the Humanitarian OSM tags. It is just a subset of the whole HDM. Current initiatives - there are two active/​funded HOT projects that are related to it directly, the [[http://​export.hotosm.org/​en/​|HOT Export Tool]] and the development of a field campaigning app as part of the project in Turkey/​Uganda. Next step would be the creation of a tagging model that is comprehensive and up-to-date, a middle way between key lifeline infrastructure and features that are relevant in humanitarian response for both responders and affected population. It looks as if most updates will occur in the field of intra- and transnational migration, mobile financial services and access to digital services (old model is from 2013). Then it will have to be integrated as preset into platforms such as Java OSM, and mobile data collection tools.
 +
 +**Resources:​**
 +  * Unordered List Itemgithub https://​github.com/​hotosm/​osm-export-tool2/​tree/​master/​api/​presets https://​github.com/​hotosm/​osm-export-tool2/​issues/​79
 +  * Unordered List Itemwiki https://​wiki.openstreetmap.org/​wiki/​Humanitarian_OSM_Tags
 +
  
 ===== Related Sahana Discussions ===== ===== Related Sahana Discussions =====
standards/domain/start.1395206678.txt.gz · Last modified: 2014/03/19 05:24 by waidyanatha
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
chimeric.de = chi`s home Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0