Module 5 Geoprocessing with Python

This is a screen shot of the script I created using Python for my GIS Programming course.  Most of the script went well, with the exception of the Adding XY data. We had to utilize the "Desktop Help" menu for this. Having absolutely no experience in Python this proved to be a challenge.  We were given some direction so I eventually figured it out. 

Screen Shot for Homeland Security Prepare MEDS Module

This is a screen shot of my seven layer files and BostonData.gdb. This weeks module was to create a Minimum Essential Data Set (MEDS) for use in next weeks module. I am going with the assumption that the better prepared and organized our data is in this week module, the smoother things should go in the follow on module. I guess we will see.

DC Crime Maps

The maps above were created for my GIS Applications course.  This week we have started a three week delve into homeland security and law enforcement.  The first map depicts police station and crime locations along with a graph of total crimes. The second map shows ,once again, police station and crime location along with a proposed location for an additional police sub-station and a graph showing crimes per station.  The final map has four frames three of which show the kernel density of particular crime, Burglary-Homicide-Sex Abuse the fourth shows population density by census block and was added to show the correlation between the number of crimes and population in DC.

Module 4 Dice Game Script

This is a screen shot of the results of a script from my GIS Programming course.  We were given a script with 8 errors and had to find and fix them so the script would run.  This was by far the most challenging module in Programming to date! Not to mention I had to run it about 30 times before Phillip finally won! Just Saying!!

GIS Application Participation Article Review

GIS Application Participation Article Review

Title: The Incident Map Symbology Story

Author:  Lt. Chris Rogers

Date created/posted:  4 May 2012

This article discusses the lack of a set of standardized symbols for mapping incidents concerning first responders such as Firefighters, Police, and Emergency Medical Technicians (EMT’s).   The lack of standardization is experienced from the operation centers of large multi-agency incidents down to the individual first responder dealing with a small incident.  This issue is important for several reasons, safety of first responders and victims,  increases the speed in which information can be digested, and resulting in the ability in which important decisions can be made to mitigate potential hazardous situations before ever arriving on the scene of the incident, are to name but a few.  So, with these things in mind during December of 2010 a plan was put together to look at tactical mapping symbology for emergency services on both pre-incident and incident levels.  The focus was to see what was already available and then identify areas where additional work was needed.

First, a group comprised of first responders with GIS experience from all across North America and belonging to several agencies including the National Alliance for Public Safety GIS (NAPSG) Foundation, the Department of Homeland Security (DHS), the Science and Technology First Responders, and the Federal Emergency Management Association (FEMA) was formed, to start some initial planning.   From this initial planning some things became apparent:

·         Incidents are complex, dynamic, and hard to map

·         Information concerning an incident can be collected before, during, and after the incident

·         Although most public safety agencies use a standard National Incident Management Systems (NIMS) approach to handling an incident, the nuances of the incident change between agencies

With all of this in mind the group set some goals, which included ideas like not re-inventing the wheel, keeping the symbols flexible and scalable, and trying to consider all hazards possible for the responder.   Before the group was to actually meet face to face, the leaders of the group, Lt Chris Rogers and Rebecca Harned assigned some homework. They were to research and identify any existing standard symbols and lessons learned and they were  given a mapping scenario to complete. The scenario was of a small structure fire and they were to create a map depicting hazards on the incident, features to help mitigate an incident, and the location of command functions.  Finally, in March of 2011, the group met in person in Seattle, Washington and for three days discussed their research and mapping projects.  

   At the conclusion of the meeting, the group decided that to improve Incident map symbology the following is required:

·         The need for guidelines not standards

·         Symbols should be broken into different categories (such as pre-incident, hazard, and incident command symbols)

·         The shape of the symbol should be defined by the category

·         Symbols must be able to be hand drawn. (For use in the field on paper maps)

·         Symbols cannot require a lot of training to understand

·         Symbols must be useable in routine business of a safety agency

While this list is by no means complete, it is a good starting point.  This subject is dynamic and will need to be refined over time. I do believe the goals of the project were met; however, one of the biggest problems is getting everyone onboard; some think change is a bad thing. Also getting this material out to the end users will take time and technology.  As more and more first responders buy into these guidelines, become more comfortable with the system, and see the results the system will grow exponentially and this will benefit all concerned.

Hurricanes

The maps depicted above were created for the third and final installment of Natural Hazards in my GIS Applications course.  Using data provided I created one map showing the path and intensity of Hurricane Sandy, the other map depicts a damage assessment I conducted using pre and post storm aerial photography. I do not consider these maps some of my better work, however this module was without a doubt the most time consuming, frustrating exercise to date! (I mean that in a good way!) While working through this module anything that could have gone wrong did.   Then to top it off when I went in to ArcMap to export my maps all the data I had created for my geodatabases was gone, and the data in the TOC was display with the dreaded red exclamation point! After hours of trouble shooting I said UNCLE and started over.  This time things went much smoother, the result of keeping good notes I would like to think.  Looking back, although frustrating, I probably learned more during this module than most others.

Tsunami Lab Part 3 Model

This is a screen shot of the model I created for Part 3 of the Tsunami lab.  I find using model builder for this type of task much easier than running each tool individually. With model builder being visual you can easily track what you are doing, and see the logical progression toward your final output.

Part 3 Tsunami Lab

This map was created using actual data from the tsunami that struck Japan in March of 2011.  By depicting the areas affected by the tsunami more accurate evacuation zones can be determined which in turn could save literally thousands of lives in the future.

Japan Tsunami Lab

This is a map I created for Module 3 of my GIS Applications course. We are continuing with the theme of Natural Hazards.  This week we worked with data from the tsunami that struck Japan on 11 March 2011.  The highlight's were creating a Geodatabase and populating it with feature classes and feature data sets. We also determined several evacuation zones using the multi-ring buffer tool in ArcGIS.

GISProgramming Module 3 Script

This screen shot is the result of a python script that I wrote for my GIS Programming course. We are currently in the third week. In this module we were to create a script that would identify the number of letters in our last name, and multiply that number by 3, and finally print our last name and that number. In my case as you can see it was “Carter 18”