Mock Incident Response Plan
EDMG230 – Mock Incident Response Plan – Powerpoint Presentation
This assignment is your opportunity to demonstrate your understanding of the material we have covered during the course. For this project students will come up with a fictitious incident response plan and develop a Powerpoint presentation containing a minimum of 10 slides.
Develop a response plan for a mock incident involving a facility or location in Colorado. This is a single incident of your choosing, such as a fire, active shooter, natural disaster, etc. We are looking for you to simulate an incident response and use your project as an opportunity to demonstrate what you have learned about the incident command process during the course. The Powerpoint presentation should contain the following slides:
- Slide 1 – Title Page
- Slide 2 – Overview of the Incident
- Slides 3 – 9 – Comprehensive Response Plan
- Last slide – References
Decide who will be the Incident Commander (IC). Or you could choose a Unified Command (UC). Develop the five ICS functional areas and specific responsibilities for each area pertaining to your incident. A completely developed and detailed Incident Action Plan (IAP) should be included as part of your presentation. You should also include maps, images as well as the completed ICS Forms (excel file) we worked on during the Week 6 Forum.
You should use a minimum of three sources to support your plan. These sources may include applicable federal, state, or local laws, as well as research or other sources relevant to your plan.
Your powerpoint presentation should contain a minimum of 10 slides, including your title and reference slides. All sources used must be properly cited. Your references should be formatted in APA style.
External research will generally be required in addition to the assigned readings. Please create your final project in Microsoft Powerpoint, and upload as an attachment for submission
Please view and use attachments
Menu
d
6/18/2005
List
Prepared
Prepared
0817
:
0
12/25/10 12/25/10
(All Risk)
Incident
Safety
Analysis
Vehicle Inventory
Operations Summary
202
203
204
205
206
207
211
211 Big
214
215 AR
215 Wild
215-A
218
220
221
223
IAP Order
Add a 204
Generic Cover
Clear Contents for Printing
Tips
and Instructions
202
| 1. | Incident Name | 2. | Date Prepared | 3. | Time Prepared | ||||||||||||||||||||
| 4. Operational Period (Date and Time) | |||||||||||||||||||||||||
| 5. | General | ||||||||||||||||||||||||
| 6. Weather Forecast for Operational Period | |||||||||||||||||||||||||
| 7. General Safety Message | |||||||||||||||||||||||||
| 8. Attachments (check if attached) | |||||||||||||||||||||||||
| ICS-202 | 9. Prepared by (PSC) | 10. Approved by (IC) |
&LICS-202
Enter short, clear, concise statements of the objectives for managing the incident, including alternatives.
Control objectives usually apply for the duration of the incident.
Be sure to include objectives for the operational period!
Enter known Safety hazards and specific precautions for the operational period. Be sure to reference a specific safety message, form 223, if one is attached.
Return
203
| ORGANIZATION ASSIGNMENT LI | ST | 9. Operations Section | ||||||||||||||||
| 1. Incident Name | Chief | |||||||||||||||||
| 2. Date | 3. Time | Deputy | ||||||||||||||||
| 4. Operational Period | a. Branch I – | Division/Group | ||||||||||||||||
| 5. | Incident | Command | Branch Director | |||||||||||||||
| Incident Command | Professor Salmon | |||||||||||||||||
| Safety Officer | ||||||||||||||||||
| Information Officer | ||||||||||||||||||
| Liaison | ||||||||||||||||||
| 6. | Agency | |||||||||||||||||
| b. Branch II – Division/Groups | ||||||||||||||||||
| C. Branch III – Division/Groups | ||||||||||||||||||
| 7. | Planning Section | |||||||||||||||||
| Resource Unit | ||||||||||||||||||
| Situation Unit | d. Air Operations Branch | |||||||||||||||||
| Documentation Unit | Air Operations Branch Director | |||||||||||||||||
| Demobilization Unit | Air Support Supervisor | |||||||||||||||||
| Human Resources | ||||||||||||||||||
| Air | Attack | |||||||||||||||||
| Technical Specialists | Hilicopter Coordinator | |||||||||||||||||
| Air Tanker | ||||||||||||||||||
| 10. Finance Section | ||||||||||||||||||
| Time Unit | ||||||||||||||||||
| 8. | Logistics Section | Procurement Unit | ||||||||||||||||
| Comp/Claims Unit | ||||||||||||||||||
| Cost Unit | ||||||||||||||||||
| Service Branch | ||||||||||||||||||
| Support Branch | ||||||||||||||||||
| Supply Unit | ||||||||||||||||||
| Facilities Unit | Prepared by (Resource Unit | Leader | ||||||||||||||||
| Ground Support Unit | ||||||||||||||||||
| Communications Unit | ||||||||||||||||||
| Medical Unit | ||||||||||||||||||
| Security Unit | ||||||||||||||||||
| Food Unit |
&LICS-203
Return
204
| DIVISION ASSIGNMENT LIST | 1. Branch | 2. Division/Group | ||||||||||||||||||||||||||||||||||||||
| 3. Incident Name | ||||||||||||||||||||||||||||||||||||||||
| 5. Operations Personnel | ||||||||||||||||||||||||||||||||||||||||
| Operations Chief | Division/Group Supervisor | |||||||||||||||||||||||||||||||||||||||
| Air Attack Supervisor | No | |||||||||||||||||||||||||||||||||||||||
| 6. Resources Assigned this Period | ||||||||||||||||||||||||||||||||||||||||
| Strike Team/Task Force/Resource Designator | Number | Trans. | Need | Drop Off PT./Time | Pick Up PT./Time | |||||||||||||||||||||||||||||||||||
| 7. Control Operations | ||||||||||||||||||||||||||||||||||||||||
| 8. Special Instructions | ||||||||||||||||||||||||||||||||||||||||
| 9. Division/Group Communication Summary | ||||||||||||||||||||||||||||||||||||||||
| Function | System | Grp/Channel | Frequency | |||||||||||||||||||||||||||||||||||||
| Prepared by ( | RESL | Approved by (PSC) | ||||||||||||||||||||||||||||||||||||||
&LICS-204
Provide a statement of the tactical objectives to be achieved within the operational period. Include any special instructions for individual resources.
Enter statement calling attention to any safety problems or specific precautions to be exercised or other important information.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
Return
Add a 204
Add a 204
204 (2)
DIVISION ASSIGNMENT LIST 1. Branch 2. Division/Group
3. Incident Name 4. Operational Period
EDMG230 Date: 12/25/10 Time: (Insert Time)
5. Operations Personnel
Operations Chief 0 Division/Group Supervisor
Branch Director Air Attack Supervisor
6. Resources Assigned this Period
Strike Team/Task Force/Resource Designator Leader Number Persons Trans. Needed Drop Off PT./Time Pick Up PT./Time
7. Control Operations
8. Special Instructions
9. Division/Group Communication Summary
Function System Grp/Channel Frequency Function System Grp/Channel Frequency
Command 0 0 0 Support 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
Prepared by (RESL) Approved by (PSC) Date Time
12/25/10 0817
&LICS-204
Provide a statement of the tactical objectives to be achieved within the operational period. Include any special instructions for individual resources.
Enter statement calling attention to any safety problems or specific precautions to be exercised or other important information.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
This information is automatically filled from the 205.
Return
Add a 204
Add a 204
205
| INCIDENT RADIO COMMUNICATIONS PLAN | Date/Time | Operational Period Date/Time | ||||||
| 4. Basic Radio Channel Utilization | ||||||||
| Radio | Type | Group/Channel | Frequency/Tone | Remarks | ||||
| 5. Prepared by (Communications Unit) |
&LICS-205
Enter the function each chanel number is assigned (i.e. command, support, division tactical, ground-to-air, etc.)
Enter the function each chanel number is assigned (i.e. command, support, division tactical, ground-to-air, etc.)
Enter the function each chanel number is assigned (i.e. command, support, division tactical, ground-to-air, etc.)
Enter the local system or radio cache system assigned and used on the incident. (e.g. 800mhz, Wolfforth, Lamb
, etc.)
Enter the local system or radio cache system assigned and used on the incident.(e.g. 800mhz, Wolfforth, Lamb County, etc.)
Enter the radio call group and/or channel numbers assigned.
If applicable, enter the frequency and tone numbers assigned to each specified function (e.g. 153.400/88.5) or (Tx: 154.000 Rx: 154.500/88.5)
Enter the ICS organization assigned to each of the designated frequencies (e.g. Branch I, Division A).
This section should include narrative information regarding special situations.
Enter the radio call group and/or channel numbers assigned.
Enter the local system or radio cache system assigned and used on the incident.(e.g. 800mhz, Wolfforth, Lamb County, etc.)
If applicable, enter the frequency and tone numbers assigned to each specified function (e.g. 153.400/88.5) or (Tx: 154.000 Rx: 154.500/88.5)
If applicable, enter the frequency and tone numbers assigned to each specified function (e.g. 153.400/88.5) or (Tx: 154.000 Rx: 154.500/88.5)
Enter the radio call group and/or channel numbers assigned.
Enter the ICS organization assigned to each of the designated frequencies (e.g. Branch I, Division A).
Enter the ICS organization assigned to each of the designated frequencies (e.g. Branch I, Division A).
This section should include narrative information regarding special situations.
This section should include narrative information regarding special situations.
Return
206
| 5. Incident | Medical Aid Stations | ||||
| Location | Paramedics | ||||
| Yes | |||||
| 6. Transportation | |||||
| A. Ambulance Services | |||||
| Address | Phone | ||||
| B. Incident Ambulances | |||||
| 7. Hospitals | |||||
| Travel Time | Helipad | Burn Center | |||
| Grnd | |||||
| 8. Medical Emergency Procedures | |||||
| ICS-206 NFES 1331 | Prepared by (Medical Unit Leader | Reviewed by (Safety Officer) |
Note any special emergency instructions for use by incident personnel. Be sure to include designated helicopter landing coordinates.
Return
207
| Deputy IC | ||||||||||||||||||||||||||||||||
| Public Information | ||||||||||||||||||||||||||||||||
| Planning Chief | Logistics Chief | Fin./Admin. Chief | ||||||||||||||||||||||||||||||
| Branch 1 | Branch 2 | Air Ops. Branch | TIME | |||||||||||||||||||||||||||||
| Div/Grp | SITL | COML | SUPL | PROC | ||||||||||||||||||||||||||||
| Helibase | Heli Cord | DOCL | MEDL | FACL | COMP | |||||||||||||||||||||||||||
| Fixed Wng | DMOB | FDUL | GSUL | COST | ||||||||||||||||||||||||||||
| SECM | ||||||||||||||||||||||||||||||||
| Agency Representatives | ||||||||||||||||||||||||||||||||
| Specialty | ||||||||||||||||||||||||||||||||
| ICS-207 |
Return
207 8×14
| Branch 3 | |
| Support Sup. | Attack Sup. |
| Helibase Mgr. | Helibase Cord. |
| Fixed Wing | |
Return
209 AR
| Incident Intelligence Summary (ICS-209) | |||||||||||||||
| Initial | Final | Incident Number | |||||||||||||
| Incident Type | Start Date/Time | Cause | Incident Commander | IMT Type | State | ||||||||||
| Lattitude and Longitude | Short Location Description | ||||||||||||||
| Current Situation | |||||||||||||||
| Size/Area Involved | % Contained | Expected Containment | ($)Cost to Date | Declared Controlled | |||||||||||
| Injuries Today | Fatalities | Structure Information | |||||||||||||
| Threat to Human Life/Safety | Type of Structure | # Threatened | # Destroyed | ||||||||||||
| Evacuation in progress | |||||||||||||||
| Residence | |||||||||||||||
| No evacuation imminent | |||||||||||||||
| Potential future threats | Commercial | ||||||||||||||
| No likely threats | |||||||||||||||
| Hazards Involved: | |||||||||||||||
| Other | |||||||||||||||
| Resources Threatened: | |||||||||||||||
| Current Weather Conditions | Resource benefits/objectives | ||||||||||||||
| Wind Speed: | Temperature: | ||||||||||||||
| Wind Direction: | Relative Humidity: | ||||||||||||||
| Significant events today: | |||||||||||||||
| Committed Resources | |||||||||||||||
| Total | |||||||||||||||
| SR | |||||||||||||||
| Outlook | |||||||||||||||
| Estimated Control | Projected Final Size | Estimated Final Cost | Tomorrow’s Forecasted Weather | ||||||||||||
| Critical Resources Needs: | |||||||||||||||
| Actions planned for next operational period: | |||||||||||||||
| Projected movement/spread during next operational period: | |||||||||||||||
| Major problems and concerns: | |||||||||||||||
| Describe resistance to control in terms of : | |||||||||||||||
| 1. Growth potential – | |||||||||||||||
| 2. Specific difficulty – | |||||||||||||||
| How likely is it that containment/control targets will be met, given the current resources and strategy? | |||||||||||||||
| Projected Demobilization start date: | |||||||||||||||
| Remarks: | |||||||||||||||
| Prepared | by: | Approved by: | Sent to: | ||||||||||||
&LICS-209
Return
ICS 209
| Incident name | ||||||||||
| Latitude and Longitude | Short Location Description (in reference to nearest town) | |||||||||
| Line to Build | ($) Cost to Date | |||||||||
| Threat to Human Life/Safety: | ||||||||||
| Evacuation(s) in Progress: | Commercial Property | |||||||||
| No Evacuation(s) Imminent: | ||||||||||
| Potential Future Threat: | Outbuilding/Other | |||||||||
| No Likely Threat: | ||||||||||
| Fuels involved | ||||||||||
| Resource Benefits/Objectives(for prescribed/wildland fire use): | ||||||||||
| CRW 1 | CRW 2 | HEL1 | HEL 2 | HEL3 | ENG | OVHD | DOZR | WTDR | Camp Crew | Total Personnel |
| Cooperating agencies not listed above: | ||||||||||
| Tomorrow’s Forecasted Weather | ||||||||||
| Critical Resource Needs: | ||||||||||
| Projected incident movement/spread during next operational period: | ||||||||||
| For fire incidents, describe resistance to control in terms of: | ||||||||||
| 1. Growth potential | ||||||||||
| 2. Difficulty of terrain | ||||||||||
| How likely is it that containment/control targets will be met, given the current resources and suppression strategy? | ||||||||||
| Projected Demobe Start (date and time): | ||||||||||
| Prepared by: | ||||||||||
| By: |
&LICS 209
Enter number assigned to incident by Agency.
Provide name given to incident by Incident Commander or Agency.
Enter first initial and last name of Incident Commander.
Enter Agency or Municipality.
Enter County where incident is occurring.
Enter type incident, e.g., wildland fire (enter fuel type), structure fire, hazardous chemical spill, etc.
Enter legal description and general location. Use remarks for additional date if necessary.
Enter date and time incident started.
Enter specific cause or under investigation.
Enter area involved, e.g., 50 acres, top three floors of building, etc.
Enter latitude and longitude by degrees, minutes, seconds.
Enter estimate of percent of containment.
Enter estimate of date and time of total containment.
Enter actual date and time fire was declared controlled.
Enter estimated dollar value of total damage to date. Include structures, watershed, timber, etc. Be specific in remarks.
Indicate line to be constructed by chains or other units of measurement.
Enter any seriors injuries which have occurred since the last report. Be specific in remarks.
Enter any deaths which have occurred since the last report. Be specific in remarks.
Report significant threat to watersheds, timber, wildlife habitat, or other valuable resources.
Indicate current weather conditions at the incident.
Indicate predicted weather conditions for the next operational period.
List agencies which have resources assigned to the incident.
List by name those agencies which are providing support, e.g., Salvation Army, Red Cross, Law Enforcement, National Weather Service, etc.
The remarks space can be used to list any information that is not listed above.
This will normally be the incident Situation Unit Leader.
This will normally be the incident Planning Section Chief.
Enter control problems, e.g., accessibillity, fuels, rocky terrain, high winds, structures.
Enter resource information under appropriate Agency column by single resource or strike team.
Report significant threat and number of destroyed improvements.
Enter actual date and time fire was declared controlled.
Provide estimated total cost for entire incident.
List types of fuels involved in incident.
Provide estimated total size of incident.
Enter control problems in relation to fire growth and terrain problems
Estimated date and time of demobilization of incident
Describe how likely the incident will come to a close using the current strategy.
List unfilled resources needed to accomplish the assigned mission
Enter date report completed.
Enter time report completed.
211
| INCIDENT CHECK-IN LIST | Check-In Location | |||||||||||||||||||||||||||||||
| Specify type of equipment contained on this sheet, or Misc. | ||||||||||||||||||||||||||||||||
| Check-In Information | ||||||||||||||||||||||||||||||||
| Single | Kind | I.D. Number or Name | Order/ Request No. | Date/ Time Check-in | Leader’s Name | Total # Persons | Manifest Yes No | Crew or Individaual Weight | Home Base | Departure Point | Method of Travel | Incident Assign. | Other Quals. | Sent to RESTAT Time/Int | Last Day Off | |||||||||||||||||
| Page | Prepared by (Name and position) use back for remarks | |||||||||||||||||||||||||||||||
| ICS-211 | NFES 1335 |
Return
211 Big
Return
214
| UNIT LOG | 2. Date Prepared | 3. Time Prepared |
| 4. Unit Name/Designators | 5. Unit Leader (Name and Position) | 6. Operational Period |
| 7. Personnel Roster Assigned | ||
| ICS Position | ||
| 8. Activity Log | ||
| Major Events | ||
| 9. Prepared by (Name and Position) |
&LICS-214
Return
215-AR
| Kinds of Resources | Date & Time | Operational Period (Date & Time) | |||||||||||||||||||||||||||
| Division/ Group/ Other Location | Work Assignments | Overhead | Special Equip. and Supplies | Reporting Location | Requested Arrival Time | ||||||||||||||||||||||||
| Req. | |||||||||||||||||||||||||||||
| Have | |||||||||||||||||||||||||||||
| ICS-215 All Risk | Total Resources Required | Single Resource Strike Teams | Prepared By: | ||||||||||||||||||||||||||
| Total Resources On Hand | Single Resource Strike Teams | ||||||||||||||||||||||||||||
| Total Resources Needed |
Return
215-AR 8×11
Return
215 Wild
| Operational Period (Date & Time) | ||
| Crews | Engines | Dozers |
| ICS-215 Wildland |
Return
215-A
| Incident Safety Analysis | Identified Risks |
| Mitigation Actions | |
| ICS-215A All Risk |
Return
218
| Support Vehicle Inventory | ||||
| Vehicle Information | ||||
| Make | Capacity/Size | Agency/Owner | I.D. No. | Release Time |
| ICS-218 | Prepared by (Ground Support Unit) | |||
| NFES 1341 |
Return
220
| AIR OPERATIONS SUMMARY | Helibases | |||||
| Fixed Wing Bases | ||||||
| 4. Personnel and Communications | Air/Air Frequency | Air/Ground Frequency | 5. Remarks (Spec. Instructions, Safety Notes, Hazards, Priorites) | |||
| Air Operations Director | ||||||
| Helicopter Coordinator | Air Tanker Coordinator | |||||
| 6. Location/Function | 7. Assignment | 8. Fixed Wing | 9. Helicopters | 10. Time | 11. Aircraft Assigned | 12. Operating Base |
| Available | Commence | |||||
| 13. Totals | ||||||
| 14. Air Operations Support Equipment | 15. Prepared by (include Date and Time) | |||||
&LICS-220
Return
221
| Demob. No. | |||||
| Unit/Personnel Released | |||||
| Transportation Type/No. | |||||
| Actual Release Date/Time | Manifest Yes No | ______________ | |||
| Area/Agency/Region Notified | |||||
| Destination: | ________________________________________ | ||||
| Unit Leader Responsible For Collecting Performance Rating: | |||||
| Unit/Personnel: You and your resources have been released subject to sign off from the following: Demob Unit Leader Check Appropriate Box [ ] | |||||
| _____________________________________________________ | |||||
| Ground Support Unit Leader | |||||
| Finance/Administration Section | |||||
| ___________________________________________________________________________ | |||||
| Remarks: ________________________________________________________________________ ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ | |||||
| ICS-221 | |||||
| NFES 1353 |
Return
223
| Incident Action Plan | ICS 223 | |
| Date Prepared: | Time Prepared: | |
| 40537 | ||
| Operational Period Date: | Operational Period Time: | |
| Major Hazards and Risks: | ||
| Narrative: | ||
| ICS Position: | ||
| Approved By: |
Return
Safety
| SAFETY MESSAGE |
| Incident: |
| Operational Period: |
| Major Hazard and Risks: |
| Narriative: |
| SAFETY OFFICER |
Describe problems that will be faced while on the incident.
Date form is prepared
Time form is prepared
List in bullet points the major hazard and risks
Who prepared the safety message?
Date and time of operational period
Incident name
IAP Order
11.
Traffic Plan
1. Cover
2. 202 – Incident Objectives
3. 203 – Organizational Assignment List
4. 204 – Division Assignments
5. 205 – Communications Plan
6. Safety Message
8. Weather
9. H. R. Message
12. Misc. – Phone List, Press Releases, etc.
13. 214 – Unit Log
Return
Generic Cover
Return
Warning
| Warning! | |
| Are you sure? Clearing the contents cannot be undone! | |
| Yes Clear the contents. | This clears the bottom of the 204 and the whole 207! |
| No, I want to go back! |
Clear the contents of the Menu, 203, and 205!
Return to the Menu
Tips
| Tips and Instructions |
| Macros are used for navigation only. The completed 203 fills ot the 207 automatically and the completed 205 places the information on the bottom of the 204’s. |
| Start by inserting your incident name, date, etc. This information will automatically be inserted into the other forms. |
| This Information will be placed on the 207 for printing. |
| Do not rename the original 204 because the macro that duplicates the 204 needs the original. If you have more than 8 Branches, Divisions, Groups, etc., you will have to change the communications information of the bottom of the 204’s to reflect the correct information. |
| The top 8 lines of the 205 are automatically transferred to the 204’s. |
| The 207 is automatically filled from the information on the 203. If you have a complex incident all of the information will not be transferred. |
| There are two versions of the 209. One is wildland and the other is more all-risk. The wildland version is only accessible from the sheet tabs at the bottom of the page. |
Return
Organization List (ICS 203)
Organization List (ICS 203)
Traffic Plan
Traffic Plan
Communications Plan (ICS 205)
Communications Plan (ICS 205)
Incident Map
Incident Map
Assignment List (ICS 204)
Assignment List (ICS 204)
Medical Plan (ICS 206)
Medical Plan (ICS 206)
EDMG101 Risk Mapping
Introduction
This week’s Chapter 6 reading emphasizes the importance of Emergency Managers creating localized maps of hazards and their area of effect.
Name one significant hazard in your community of residence and create a map demonstrating its location and possible area of effect. Do not use a military facility or installation. I am looking for a community-based natural, technological, or human-source hazard.
You may also want to identify Critical Infrastructure and Key Resources (CIKR) that would be affected by your hazard. CIKR elements can include Police, Fire, Hospital, EMS, Water, Power, Communications, Mortuary, etc.
Use online tools such as
Google MyMaps
and FEMA
regional HIRA mapping
and
historical data
to inform and display information on your hazard.
While you are free to display your hazard and its area of effect using any online tool that can be shared in the APUS classroom, these instructions will demonstrate how to use Google Maps. You may alternatively use another mapping service, or compile spreadsheets, lists, etc.
In the forum, you will post:
· a link to your map or presentation displaying your chosen hazard and its area of effect
· a 150 word introduction to your map, listing key takeaways as to the vulnerability of your location to the hazard, such as the amount of population or CIKR elements.
· your experience in using the tool
· ways in which you can see yourself using it in your current or future profession.
Suggested Steps
Google Account
If you have a Google account, log in at
accounts.google.com
.
If you do not have a Google account, select the “Create Account” link and follow the steps.
Google MyMaps
On your computer, sign in to Google
My Maps
.
https://MyMaps.Google.com
Additional Help can be found using the menu in the top left corner or at this link:
https://support.google.com/mymaps#topic=3024924
.
Create a New Map
Select Create a new map.
Go to the top left and select “Untitled map.”
Give your map a name and description, stating which location you are mapping; ie “Madison SD Hazard Area.” Select Save.
Zoom in to your location, or type the name of your location to be automatically zoomed in.
Choose Your Terrain Type
Next to “Base map” in the bottom of the left panel, select the Down Arrow.
To choose a style, select one of the images.
Name Your Hazard Layer
Select “Untitled Layer” and change its name to your identified hazard. Select Save.
Drawing Lines
To draw lines and shapes on your map, select the “Draw a Line” tool and select “Add line or shape.”
Click on the map to set points. Click on the end point to end the line.
Add a name and description to the line. Select “Save.” The distance will be automatically calculated.
Drawing Shapes
Only custom polygons are available, simple circles or other standardized shapes are not available. To draw a polygon shape, use the Line tool to plot points, and click on the beginning dot to close the shape.
Provide a name and description for the shape. The area and perimeter will be automatically calculated.
You can also color code the area using the Style icon to more easily distinguish multiple shapes.
Identifying Locations
Select “Add layer” and a new untitled layer will appear. Select “Untitled layer” and change it to the name of a category, such as “Police.”
Search & Add Locations
In the search bar, type the CIKR category, such as “Police,” and hit enter or press the search button.
A list of results will appear in the left menu, as well as on the map. Hover over the result to see it circled on the map. You can also select on the result to see detailed information.
If the result is what you want, select Add to map .
You can also manually add items by using the Pin icon under the search bar, and choosing the location on the map. Give the location a name and description.
Continue to add items to this category until you are done. You can clear your search by selecting the X above the results.
Theme the Icons
Go to your layer, and select the Style icon .
Under “Group places by”, pick a style.
· Uniform style: One color and icon for the entire layer.
· Sequence of numbers: Mark places on the map with a number.
· Individual styles: Each map feature has its own color and icon.
· Style by data column: Group items by data values. Each group has its own colors and icons. You can sort by ranges or categories.
In this example, choose “Uniform Style” and close that menu.
To pick colors and icons, point at each map feature or group of features (“All Items”) and select the Color icon .
You then can choose the color of this layer’s markers. You also can set the icon by choosing “More Icons.”
Browse for the icon you want and select it. Then click OK.
You can view all layer features by using the arrow under the layer name.
Repeat
Repeat the process for all the location categories you are interested in (eg. Hazards, Police, Fire, Hospital, etc). Add a layer, name your layer, search for locations, add locations, and theme your layer.
Share
In the left panel, select Share .
Make your map public: Go to “Who has access” and select Change.
Choose “On – Public on the web”
Under “Access: Anyone (no sign-in required)” choose “Can View.”
When you’re done, select Save. Copy the Link to share. Select Done.
Post in Classroom
Create a forum post in your APUS classroom and type your introduction to your map and your forum post.
At the end of your post, use the Link tool to insert your map’s link.
Post your message.