The Final Quest: Capstone Archives

Version 1.0: The Introduction

Hello, and welcome to my blog! This masterpiece will chronicle my experiences as I traverse my capstone project in Computer Science…but before we get to that, let me introduce myself.

My name is Kjirsten, pronounced KEER-sten (English), SHER-sten (Norwegian), or simply KJ. I grew up in a small town (pictured above) on the Oregon coast. You can tell it truly is a small town by the lack of buildings in the photo. And yes, it was taken within city limits. Nowadays, I live in Texas and have worked in sales, project management, and purchasing. Oh, and life has changed a little. I’m currently living in a dry climate (no ocean in sight), a major city (almost 2 million people), and am now completing a degree in… Computer Science?

I suppose to understand the track from small-town nature lover to big city Computer Science geek, we might need to rewind a little. Well, actually, we’ll need to rewind a lot, back to freshman year of college.

After graduating from high school, I initially went to a private University, where Philosophy through the 400-level was a requirement of any major. As an undeclared major myself, I started with Philosophy 101. The first few weeks we were introduced to boolean logic, and not long after, logical fallacies. Then, as a fan of logic and reasoning, it wasn’t long before I fell in love.

Alas, shortly after my newfound love was discovered, the limited professional careers deterred me from a Philosophy major. Being a lover of math and logical systems (and also, oddly, waste to energy plants and energy systems), I hopped over to Mechanical Engineering. The knowledge I’d gained from philosophy on logic and reasoning, abstraction, and algorithmic thinking was packed away for another day.

Years later, I looked to continue my education. Not any less logical in approach, I began to pursue the engineering colleges. This time, my love of philosophy would finally relate to a Computer Science degree. My previous education with boolean logic and reasoning became an integral facet in this decision. This time, however, the nature lover in me would add another degree to the mix: Sustainability.

As of today, that is who I am. A lover of logic and algorithms with a side passion to integrate technology for a more sustainable future.

What I’ve Learned Along the Way

A sneak peek into all the fun I’ve had in coding

Python

Implemented with Object-Oriented Programming, Functional Programming with microservices for data analysis, and Web Development.

JavaScript

Full-stack web development using JavaScript, creating interactive web pages with front-end and back-end integration.

SQL

Database management and data manipulation. My main project in SQL was combined with JS and Handlebars to create a Library management system.

Handlebars

Utilized Handlebars with Node.js to render HTML pages featuring dynamic content, specifically data retrieved from an SQL database.

React

Created dynamic web pages with interactive front-end components using React. These components were integrated with RESTful APIs to ensure efficient data retrieval and interaction.

Networks

Developed a comprehensive understanding of network protocols by implementing Reliable Data Transfer (RDT) and traceroute programs. Gained hands-on experience in socket programming!

The Final Quest: Capstone Archives

Version 1.1: Shapefiles and Geospatial Data

And so we embark on to the main content of this blog: the capstone. With my Sustainability degree in mind I have ventured in to working with Shapefiles, more broadly, Shapefiles and environmental data. Perhaps after spending too much time in programs like ArcGIS I have developed a strong desire to handle the Shapefiles myself. Or, more accurately, I want to know what is going on behind the scenes.

Of course, if we (my capstone team and I) are going to be working with environmental data, it is pertinent that we get the Shapefiles into a more usable form. That’s where I come in. I will be tackling the job (feel free to be impressed) of converting the Shapefiles into GeoJSON for data analysis (this is where you give an audible ‘wow’).

On a more serious note, I will be using some new libraries this time. While I have worked with converting data to JSON before, it has primarily been in other formats. On top of that, this data will need to be encrypted. This task will be a bit foreign to me, so I will be hitting the books to optimize my approach.

With all of that being said (at length), I am excited to tackle something new, and I am feeling that the finish line of this part of my education is in sight. As I begin this final experience, I am reminded that the next chapter is quickly approaching and that I will likely be a beneficial member of a corporate team one day. I will approach this capstone with that in mind, honing my skills where I am able.

What is a Shapefile?

A shapefile is a popular geospatial vector data format for geographic information system (GIS) software. It is used for mapping and analysis, and is actually a set of files (listed below).

Mandatory Files 

  1. .shp: Stores the geometry of the features (points, lines, polygons). 
  1. .shx: Contains the index of the feature geometry. 
  1. .dbf: Holds attribute data in a tabular format. 

Optional Files 

  1. .prj: Contains the coordinate system and projection information. 
  1. .xml: Stores metadata about the shapefile. 
  1. .sbn and .sbx: Spatial index files that improve spatial query performance. 
  1. .cpg: Specifies the character encoding used. 

“The unexamined life is not worth living.”

Plato’s Apology, 38a