5,013
edits
Team Service Areas: Difference between revisions
From WikiNET
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
<p><span style="color:#ffffff">...</span></p> | <p><span style="color:#ffffff">...</span></p> | ||
[[File:FMAmap.jpg|alt=Map of PF&R FMAs.|thumb|''At one time, a team's Service Area was contiguous with their local Fire Management Area (FMA).'']] | |||
__TOC__ | __TOC__ | ||
<p><span style="color:#ffffff">...</span></p> | <p><span style="color:#ffffff">...</span></p> | ||
== Background == | == Background == | ||
Service Area policies changed several times since Portland NET started in 1994, often reflecting the reach of the program and interests of volunteers. In the first years of NET, Service Areas conformed with [[Portland Fire & Rescue|Portland Fire & Rescue fire management areas]] (FMAs). As the number of NET volunteers increased over the years, Service Area boundaries shifted to follow Portland's neighborhood system. That is how most Service Areas boundaries are drawn today, but PBEM encourages teams to reconsider their boundaries and "right size" them to match resources and team priorities. Creating more nuanced boundaries is also more plausible than in past years thanks to the increased availability of GIS mapping systems. | Service Area policies changed several times since Portland NET started in 1994, often reflecting the reach of the program and interests of volunteers. In the first years of NET, Service Areas conformed with [[Portland Fire & Rescue|Portland Fire & Rescue fire management areas]] (FMAs). As the number of NET volunteers increased over the years, Service Area boundaries shifted to follow Portland's neighborhood system. That is how most Service Areas boundaries are drawn today, but PBEM encourages teams to reconsider their boundaries and "right size" them to match resources and team priorities. Creating more nuanced boundaries is also more plausible than in past years thanks to the increased availability of GIS mapping systems. | ||
