Module 2: Coordinate Systems

 Module 2: Coordinate Systems


I chose Tennessee as my area of interest. For Tennessee, I selected the Tennessee State Plane (NAD83) coordinate system because it provides optimal accuracy across the entire state through a single zone configuration. Alternative options like UTM were rejected since Tennessee spans zones 16N and 17N, which would introduce edge distortion where the zones meet. A custom state system would be unnecessary given the state's complete coverage by a single State Plane zone that already minimizes distortion across Tennessee's geography


Comments

Post a Comment

Popular posts from this blog

GIS 5103 - GIS Programming - M1: Python Environments & Flowcharts

Image
  Python Module 1 Recap: From Scripts to Flowcharts and Zen Principles Converting 3 Radians to Degrees To convert 3 radians to degrees, we use a simple formula: degrees = radians * 180 / pi Below is the flowchart illustrating the conversion process: Running the calculations in IDLE gives us:  ≈ 171.887 Interpretation of the Zen of Python The "Zen of Python" showcases the philosophy and guiding principles of Python programming. It emphasizes simplicity, readability, and clarity in code. In other words, “Zen of Python” promotes straightforward and elegant solutions over complicated ones. By valuing explicitness over implicitness, the basis of Python encourages clear and understandable code. Moreover, The principles highlight the importance of practicality and avoiding unnecessary complexity— why use 4 lines of code when 1 will do the same thing? This mentality helps to balance between purity and practicality. Overall, the “Zen of Python” advocates for writing code that is easy ...
Read more

Module 4: Color Concepts & Choropleth Mapping

Image
Creating Meaningful Color Ramps Linear Progression  Adjusted progression ColorBrew Comparing the three color ramps reveals distinct approaches to color progression in data visualization. The linear progression maintains mathematically consistent steps (~53.4 units each). However, it does not account for human perception, while the adjusted progression attempts to improve this by decreasing step sizes from ~73.8 to ~36.8 units as values get lighter, acknowledging increased human sensitivity to changes in lighter values. ColorBrewer's progression demonstrates the most sophisticated approach, with carefully calibrated non-linear steps that start large (~85.7 units), peak in the second step (~95.7 units), and then gradually decrease (~41 units), creating a perceptually balanced sequence that best accounts for both human vision characteristics and practical visualization needs. Mapping Change Using Choropleth Mapping Based on the histogram's distribution, Natural Breaks with 6 class...
Read more

GIS 5103 - GIS Programming - M3: Debug & Error Handling

Image
 Script 1 Objective: Fix errors in Mod3_Script1_Template.py to list field names from parks.shp. Flowchart Output for Script 1 After Corrections Script 2 Objective: Fix errors in Mod3_Script2_Template.py to list layer names from TravisCountyAustinTX.aprx. Flowchart Output for Script 2 After Corrections Script 3 Objective: Modify Mod3_Script3_Template.py to handle errors using try-except statements without fixing the errors. Flowchart Output for Script 3 After Try-Except Statements In Mod3_Script3_Template.py, the script is divided into two parts: Part A and Part B. Part A: This part of the script is intentionally left with an error to demonstrate error handling. Instead of the program crashing and not moving further, I used a try-except statement to catch any errors and print an error message. The error message while also print what went wrong before continuing on to Part B. This is a crucial aspect of debugging since it provides immediate feedback on issues within the code. Par...
Read more