Module 3: Debugging


Module 3: Debugging


Mod 3 Script 1 results:                                                                 







Mod 3 Script 2 results: 










Mod 3 Script 3 results:                                            
















For Script 3, there was an exception error that had to be remedied, using the try-except function. 

The first step that was taken to figure out where the try-except statement was supposed to go, was toggling through the debugger to identify what line of code the exception error was on. The Debugger was able to identify the run-time error was present in the first part of the code. So, the try statement went after importing arcpy, and before the first part of the code. The except statement wen after the last print of part A and before part B. the exception read as follows: 

except Exception as e: 
print(e)

In simpler terms, the try-except function encompasses the part of the code that contains the error (an error sandwich, if you will) and allows the code to run with the exception.
The indentation on the code was incorrect, so it was also necessary to go through and indent the appropriate print statements. 


Other Notes
It was easy to identify syntax errors in the first exercise, however it took quite a bit of time to figure out that one of the main errors I was encountering was related to the file path. The file path was incomplete and the data needed for the script was in a different folder than what was printed. 



Comments

Post a Comment

Popular posts from this blog

Module 5: Exploring and Manipulating Data

Image
 Module 5: Exploring and Manipulating Data  This module focused on the implementation of cursors and dictionaries within newly created geodatabases. We learned a lot of different functions and techniques applying to geospatial data. The most notable problem I encountered this week was compiling the search cursor queries into one script. One of the steps in the project was to create a Search Cursor for the cities layer to find the Name, Population (POP_2000), and Feature of all County Seat Cities. Initially, I could only get the cursor to run by dividing each of these categories into a separate cursor file, generating a long list of either city names, populations, and features, respectively. This was for all intents and purposes functional, but was practically illegible and a definite eyesore. By trial and error I was able to create separate variables, and vitally separate print row.getValue statements for each of my fields to make the same script generate all inquiries simulta...
Read more

GIS internship: Post #4

 GIS Day   This week, our internship cohort was assigned to organize a GIS day celebration to bring people together through shared interest in remote sensing and geo-data. Luckily, I already had something up my sleeve that fit the bill, so I'm wholeheartedly embracing the serendipitous coincidence without any remorse. I joined forces with the GIS staff at my university to put together a drone course on campus, courtesy of the kind folk at Gulf Coast State College (GCSC), with whom we connected via a GIS user's group conference a few months back. This course will teach participants how to collect, manage, process, and interpret a suite of aerial data with the added plus of learning how to fly a drone... very cool stuff. The application of remote sensing capabilities in the GCSC lab is emergency management focused, so we will likely be interpreting data through a public safety lens, which is a very interesting perspective, likely novel to most of us.   The course start...
Read more