At times, an emergency plan's resources become unavailable due to their proximity to the affected area. This problem definition supports drawing and storing a series of affected area shapes on a map, and using that geo-data to adapt the facility and staff resource plan by automatically offlining those resources that would be negatively affected.

Note on contribution: Please feel free to fill out sections of the specification as this project is a collaborative effort; however, if you feel your ideas could be in conflict to previous ideas or you want to change sections already fleshed out please use the discuss tab first and find consensus with others working on this module or section.

At times, an emergency plan's resources become unavailable due to their proximity to the affected area. This problem definition supports drawing and storing a series of affected area shapes on a map, and using that geo-data to adapt the facility and staff resource plan by automatically offlining those resources that would be negatively affected.

In the event of an unexpectedly large coastal storm, a municipality's sheltering system may find that some of it's shelters are in an area that is now underwater. Currently, emergency managers would be required to get situational reports from each individual shelter, however, if administrators had the ability to simply draw the flood areas on a map, the system could use the geo-coded shelter addresses to automatically offline those shelters that are no longer usable, and instead activate some of the standby shelters.

An earthquake destroys a major bridge. Half of the earthquake response team cannot get to the staff just-in-time training camp at the base of the bridge because of the bridge's status. An administrator draws a polygon indicating that the bridge area and several others are affected and impassable. The system, now aware of the newly destroyed bridge, does not attempt to deploy those staff who live on the other side of the bridge. As a result, the response team is not short-staffed because the system was able to adjust its staff pool and draw upon the reserve team that lived further away but did not have to cross that bridge to get to the training camp.

However the geo-provider is handled, the assumption should be that up to 250,000 records might be queried against the polygon. This significantly limits geo-provider options since most have terms of service that dictate daily usage maximums well below that figure.

Mayon currently uses TIGER/Line data for its primary geo-source when it comes to matching addresses, but hasn't selected a source for generic polygons or map integration.

    * Show active facility resources on a map, color coded by status

<What shouldn't this piece do?>

• Mapping capabilities have yet to be integrated with Mayon and would have to be constructed before any geo-related module was build. Currently, the functionality is built into the schema but not implemented in any front-end.

<What screens should the user see? How should the work flow through the module? Good to include some sketches or pictures.>

Note on contribution: Please feel free to fill out sections of the specification as this project is a collaborative effort; however, if you feel your ideas could be in conflict to previous ideas or you want to change sections already fleshed out please use the discuss tab first and find consensus with others working on this module or section.