Learning Buffers the Hard Way (and the Smarter Way)

 This week’s lab was all about buffers and overlays, and I finally got some hands-on practice with the Buffer, Multi-Ring Buffer, and Union tools in ArcGIS Pro. I started by creating a fixed 300-meter buffer around the Roads layer and then moved on to a variable buffer where lakes were set at 150 meters and rivers at 500 meters. I had to add a new field in the attribute table, assign values with Select by Attributes, and then calculate fields before running the buffer tool—definitely a few steps to keep track of. After that, I tried out the Multi-Ring Buffer tool, which was neat because it made concentric zones at set distances.

The most important thing I learned? Always make sure you’re clicked into the correct layer before running a geoprocessing tool or a select operation. I lost track more than once and ended up with results in the wrong place. That was frustrating, but it drilled in the habit of double-checking inputs.

Compared to my earlier labs, this one went a lot smoother. Setting up a second screen so I could keep the demo videos open while I worked was a game-changer. I didn’t have to print the lab instructions or waste time Googling where tools were hidden in the interface. Having notes from Lab 2 also really paid off, since this lab built directly on what I learned there.

One final lesson: I need to read ahead. The readings and lectures seem to lag a week behind the labs, so skimming forward gives me a clearer picture of what I’m about to do and keeps me from feeling lost. By the end of this lab, even with a few hiccups, I felt like I really understood how the buffer and overlay processes fit together in ArcGIS.

 

Cartography and Map Layouts: Lessons Learned the Hard Way

I went into this week’s map project feeling like I had ArcGIS pretty well under control. Spoiler: I don’t. Working through this assignment taught me that I still have a lot to learn when it comes to cartography and map layouts.

First off, I ran headfirst into some technology frustrations. Citrix on the laptop made everything feel clunky, and working with Google Docs wasn’t much better. I honestly couldn’t tell if the issue was the programs themselves or if I’m just a little too set in my ways. Either way, it slowed me down and left me a little more irritated than inspired.

The actual map building was a mixed bag. I did get the basics in—title, logo, north arrow, and scale bar—but there were plenty of things that didn’t go as smoothly. For example, I never figured out how to get the city names to display correctly. That left my final product feeling incomplete, and I wasn’t entirely happy with how it turned out. It was one of those moments where you look at the map and know it could be better, but you’re out of time and patience.

On the brighter side, I did manage to make the legend work by editing the layer names, and I followed the lab’s recommended color palette (even though I was tempted to go artsy with antique tones). Those choices at least kept the map professional and readable.

The big takeaway from all this? Don’t procrastinate. I definitely waited too long to start and ended up scrambling. I also realized I need to use the resources available to me more effectively—whether that’s tutorials, help forums, or just asking questions sooner rather than later.

So while my Module 2 map wasn’t a masterpiece, it was a wake-up call. By Module 3, I plan to approach things earlier, lean on the resources, and hopefully come away with a product that I feel proud of.