Wednesday, June 14, 2017

Module 4 - Debugging and Error Handling


Module 4 - Debugging and Error Handling

This week's assignment had us learning about debugging and error handling

Script 1:

For script 1 we had to find the two errors within the script in order for it to run successfully. The two errors here involved making "fc" all lowercase and ensuring that line 15 read the correct variable. Instead of reading "- for fields in field:" it should read "-for field in fields".


Script 2:

Script 2 was a little more tedious in finding the eight errors that occurred within this script. There were a number of different kinds of errors we had to identify.

Script 3:

 I had a lot of trouble with this in the assignment and unfortunately wasn’t able to correctly have the error message in Part A and have the script run successfully in Part B. I was able to determine the error and allow both Part A and part B to run successfully by including the mxd variable in Line 14 “mapdoc = arcpy.mapping.MapDocument(). I then added a try-except statement asking the script to remove any exceptions that would not allow Part B to run successfully. Once I ran the script however my results in Part A were correct, I received a green error message, however Part B showed an error message that lyrlist had not yet been determined.



Wednesday, May 31, 2017

GIS Programming - Module 2


Module 2 - Python Fundamentals Part 1


For this week's lab, we learned how to successfully run a basic script using our names. I was intimidated at first with the idea of writing a script successfully as I have never worked in programming before but after a few mis-trials I was able to successfully complete our lab and feel more confident in my programming abilities!

The overall goal of this lab was to use our full name, first middle and last names and find the number of characters in our last names, multiplied by 3, and have the script answer this. You can see from the above post I was able to write my last name and have the script run to get an answer of 15. This would be 5 letters in my last name, multiplied by 3.

In order to run the script I first began by writing the string and assigning it to a variable, my full name , written as >>> stringName = "Christine....". I then created a list from the stringName, separating each part of my name using the split method. I was then able to use the indexing function and assign my last name to a variable. In the next step, I used the function len or length in order to determine the number of characters in my last name. I then assigned this a variable called lastNameLen and determined the final output, tripleLastName which determined the total number of characters of your last name, multiplied by 3 and the result printed as 15.

Wednesday, May 24, 2017

GIS Programming Module 1


Introduction to Python

For this first week in GIS Programming, our assignment was to run a script in Python that would create Module folders for each module in this semester along with a Data, Results, and Script folder for each Module folder. I thought this week's lesson was the perfect introduction into Python as it allowed us to go through this simple task and gain an overall understanding of scripts, programming language, how to write pseudocode, amongst some other lessons. 


Monday, May 1, 2017

GIS 4043 - Final Project

Final Project - Bobwhite Manatee Transmission Line Project


 

Though the lab took a long time to push through, I thoroughly enjoyed completing this analysis of the transmission line and completing each objective. Going through each lab this semester, I was able to get a grasp on each topic covered but the real challenge was being able to put this knowledge to the test in this real life map and data analysis project. I am very happy I had the opportunity to complete this project analysis as I was able to prove to myself that I do have a fairly strong grasp on several topics we have covered this semester. The most enjoyable part as well is seeing multiple datasets, sources, shapefiles, basemaps, etc. all come together at the end to produce 4 maps that each have their own information necessary to this project analysis.
Of course I did have trouble in some areas. The one area I had difficulty in was determining the number of parcels within the Manatee and Sarasota counties and I’m not entirely confident in these results.

The overall analysis would be very useful to decision makers as well as those living near the study site. For any parents or guardians in the area, they could look at this analysis and be confident in the fact that the transmission line would not be located near any of their childrens schools or daycare centers. This could be concerning as stated in our Final lab introduction as electric or magnetic lines have been known to cause mild health problems in children. In addition, home or land owners might be curious to know if the tranmission line will be located near their home. Environmentalists would also be concerned if the transmission line might significantly impact a large area of wetlands as well.
Overall, I really enjoyed working through each of the objectives and testing my GIS capabilities and knowledge gained this semester!






Wednesday, April 19, 2017

Module 12 - Google Earth


South Florida and Google Earth


For this weeks lab we learned about VGI or Volunteered Geographic Information and the benefits it has had in the GIS community. In addition, we were able to work more in Google Earth which I have found to be the most fun software to use so far. We started by working with our Dot Density map that was created in Module 10. I had to restructure some of my Dot Density map as I was not sure how to manipulate the Surface Water within the map. After some research and playing around with the map, I was able to differentiate the different surface waters such as lake, stream, and wetlands from each other. From here, we created two kmz files from our maps which we were then able to open in Google Maps. From here, we found several locations across Southern Florida and created Placemarks for each of these locations including Miami metropolitan area, Downtown Miami, Downtown Fort Lauderdale, Tampa Bay Area, St. Petersburg, and Downtown Tampa. We then created a video tour where we stopped at each location and panned the camera around different directions, obtaining visuals of 3D buildings all within the specific area. The result was a video traveling from the six locations in Southern Florida. This was the most fun lab as I had never worked much with Google maps and had no idea the detail that goes into the maps when you're able to move the camera fairly close to the ground seeing the 3D buildings, trees and roads as they really are.
I had some difficulty with my video tour as I turned my Dot Density layer on and off throughout the video as I moved from city to city to show how the layer changed however when I reviewed the video after it was completed, it showed my dot density layer over the cities the entire video so you were unable to see some of the 3D buildings. I tried making the video a few more times but after a couple times Google Maps would not let me press record anymore. Overall, I really enjoyed this lab and working in Google Maps.

Thursday, April 6, 2017

Week 13 - Georeferencing, Editing, and ArcScene

Georeferencing and ArcScene 
in the UWF Community

     This week's lab entailed georeferencing, editing, and working in ArcScene for the first time. Georeferencing involves telling the data where it should be located spatially. To do this, you align the data together by using connector points and clicking on the unknown raster image location first followed by the corresponding point within the referenced data which was our buildings and roads. This took me some time to figure out, as the connector points have to align in such a way that the RMS Error stays at 15 or below and there should be a certain number of connector points for each transformation that is selected. 
     Following this, we learned about editing data and creating buffer points. I had more trouble with this part of the lab as I was not able to get my buffer points to appear in my map, though they showed in my Table of Contents. The buffer layer represented a safe area 330 and 660 feet surrounding an Eagles Nest data point on our map. 
     The final part of the map was creating a 3D image of the UWF community with its roads and buildings layer in ArcScene which we then exported as a 2D file back to ArcMap where we created our final deliverable. I had trouble with this section as well because my uwf_s1 layer would not show in my map. Therefore, it appeared that half my map showed the image with roads and buildings while the other half merely shows my roads and buildings layer. Overall, this was probably the most difficult lab to work through but still very informative. I'm happy to have the experience now of working in ArcScene and enjoyed seeing and navigating around my map in a 3D version.