Write a Python script to alter the existing MXD to make a map for each county and export that map to a PDF. 

 

IT 338 Scripting Project Seven Guidelines and Rubric.pdf

IT 338 Scripting Project Seven Guidelines and Rubric
Overview: In this course, you will be responsible for completing seven scripting projects. Learning to program in Python requires developing an understanding of
general programming concepts and learning the syntax of the Python programming language. These scripting projects will build on each other and help you
cultivate your Python scripting knowledge. It is recommended that you do not limit your practice to just that which is graded. The more you write your own
scripts, the more proficient you will become with the tools available to you in Python and ArcGIS.
Prompt: You are a newly hired GIS technician for a mapping consultancy group. You have been given the task to create general maps showing roads, streams,
and towns for every county in Virginia. (There are a lot of counties). Write a Python script to alter the existing MXD to make a map for each county and export
that map to a PDF.
The data files for this scripting project can be downloaded here.
Your submission should include your Python script complete with a brief description of the file in a commented ‘header’ section.
The following critical elements should be addressed in your project submission:
I. Code Description: A brief explanation of the code and a brief discussion of any issues that you encountered while completing the exercise. II. Functioning Script: A script must meet its specifications and behave as desired. To develop proper code, you should produce fully functioning code
(produces no errors) that aligns with accompanying annotations. You should write your script in such a way that the submitted code actually executes,
even if it does not produce the correct output. You will be given credit for partially correct output that can actually be viewed and seen to be partially
correct. III. Script Results: Properly generated results dictate that your script:
a. Generates accurate output; and
b. Produces results are streamlined, efficient, and error-free. IV. Annotation/Documentation: All code should also be well-commented. This is a practiced ‘art’ that requires striking a balance between commenting
everything, which adds a great deal of unneeded noise to the code, and commenting nothing. Well-annotated code requires you to:
a. Explain the purpose of lines or sections of your code detailing the approach and method the programmer took to achieve a specific task in the
code;
b. Document any section of code that is producing errors or incorrect results. V. Style and Structure: Part of the lesson to be learned in this course is how to write code that is clearly readable and formatted in an organized manner.
To achieve this, you should:
a. Develop logically organized code that can be modified and maintained; b. Utilize proper syntax, style, and language conventions/best practices.
Guidelines for Submission: For each exercise, include the Python file (xxx.py) containing code that should start with a header comment containing a title (name,
course, date, project number) and a discussion of the code.
Instructor Feedback: This activity uses an integrated rubric in Blackboard. Students can view instructor feedback in the Grade Center. For more information,
review these instructions.
Rubric
Critical Elements
Code Description Functioning
Script Script Results:
Accurate Output Script Results:
Efficiency Annotations/
Documentation:
Explanation of
Purpose Annotations/
Documentation:
Errors Exemplary (100%)
Meets “Proficient” criteria and
the explanation is provided and
includes elements of scholarly
research
Meets “Proficient” criteria and
aligns with the accompanying
annotated code Proficient (85%)
A complete explanation of the
code is provided and difficulties
are discussed Needs Improvement (55%)
The code description is
incomplete Not Evident (0%)
No explanation is provided Value
10 Program is fully functioning and
includes code to meet all
specifications
Data results are accurate in
regards to the given problem Program does not run or
significant details of the
specifications are violated or
omitted
Program does not produce
results for the given problem 20 Meets “Proficient” criteria and
the program is capable of
producing accurate results
beyond the specifications of the
given problem
Meets “Proficient” criteria and
included sophisticated
techniques such as error
handling or reference to user
created functions
Meets “Proficient” criteria and
clarity of annotations facilitates
script navigation for a varied
audience, and is written in a
concise manner Program is not fully functioning
or does not include all of the
specifications of the given
problem
Program produces incorrect
results for the given problem Writes the script resulting in a
professional-grade, functional,
and highly efficient script Written script is inefficient or
produces errors under certain
circumstances Script incomplete 20 Code annotations fully explain
the code and facilitate
navigation of the script code Code is not fully or logically
annotated 5 Meets “Proficient” criteria and
sections that might have
preferable or alternative
solutions are clearly annotated Sections of code that produce
errors are clearly annotated and
include a summary of the issue Comments provide little
assistance with understanding
the code. Code annotations do
not fully explain the code or do
not facilitate navigation of your
script code
Sections of code producing
errors or incorrect results are
identified, but no further
explanation of the issues is
provided Sections producing errors or
incorrect results are not
documented 5 15 Style and
Structure:
Logically
Organized Code Style and
Structure:
Syntax
Style and
Structure:
Best Practices Meets “Proficient” criteria and
the script is stylistically welldesigned. The code is well
organized and presented in a
way that it can be modified and
maintained
Meets “Proficient” criteria and
demonstrates deliberate
attention spacing, whitespace,
and variable naming
Meets “Proficient” criteria and
demonstrates an understanding
of why certain techniques are
considered “best practice” The code is logically organized The code contains portions that
are not logically organized Code is poorly organized or very
difficult to read 5 Code follows proper syntax and
conventions Code contains variations from
established syntax and
conventions Contains significant variations
from established syntax and
conventions 10 Best practices were used in
designing and writing the script,
but some errors are present Best practices were used in
designing and writing the script,
but many errors are present Best practices were not used in
designing and writing the script 10 Earned Total 100%