Why Journal For Geography

Keep A Field Journal If You Want To Actually Retain Anything From Your Geography Work

I started journaling properly around 2014 when I was doing qualitative spatial analysis for a housing study in Bristol. My initial approach was basically transcribing interview notes verbatim. That lasted three weeks before I realized I had spent more time organizing raw transcripts than actually understanding the patterns in the data. The breakthrough came when I stopped treating the journal as a storage device and started using it as a thinking tool instead. The core idea is straightforward but people keep missing the practical angle. Geography is an interdisciplinary field that sits somewhere between hard social science and natural science depending on who you ask. Your research methods reflect that ambiguity. A lab-based climate modeler needs different documentation habits than a human geographer doing participatory mapping. The journal bridges both because it forces you to record not just what you found but what you were thinking when you found it. That distinction matters more than most beginners realize. Here is how I structure a working journal entry now. I use a simple three-column format that I adapted from a methods paper by Rose (2007) on visual methodology, though I have modified it significantly. The left column is for raw observations. The middle column is for immediate interpretation. The right column is for methodological notes about what I should do differently next time. This prevents the common problem where your interpretive layer gets tangled up with your observational layer and you cannot tell later whether a pattern was real or just something you wanted to see.

I keep digital journals in Obsidian because it handles backlinking well and the markdown syntax is lightweight enough that I can export to CSV when I need to run quantitative analysis on my own notes. I used to use OneNote and the formatting got too heavy after about six months of entries. The file size became unmanageable and search performance degraded noticeably. Switching to plain markdown files solved that entirely.

The Practical Mechanics

Entry timing is where most people mess up. There is a difference between writing in your journal immediately after fieldwork and writing it two days later when you remember to. I learned this the hard way during a rural land-use survey in Devon. I had written my initial notes at home on Wednesday evening about a site visit I did on Tuesday morning. By Wednesday night I could not recall whether the soil I described as \"waterlogged\" was actually just damp from recent rain or genuinely waterlogged due to poor drainage. The distinction changed how I interpreted the entire land-use pattern for that plot. I had to return to the site a week later just to verify something I should have recorded correctly in the first twenty minutes after leaving. The workaround was simple. I now carry a small waterproof notebook and use it exclusively for field observations. Then I transcribe and expand those notes into the digital journal within twelve hours of returning. The twelve-hour window is not arbitrary. Research on cognitive psychology suggests that procedural memory decays significantly after about a day for spatial information, especially when you are dealing with multiple sites in a single trip. I also record GPS coordinates and timestamp each entry. This sounds like overkill until you need to revisit a specific location three years later for a follow-up study. Another thing that catches people out is the temptation to make the journal look nice. I spent about four months in my second year making color-coded diagrams and inserting printed photographs with captions. This took roughly three hours per entry for something that was maybe a one-hour field session. My actual analysis time dropped by about sixty percent because I was spending more time on presentation than on interpretation. I switched to black and white handwritten photos stuck in with tape and a single pen for annotations. My output quality improved noticeably because I was no longer treating the journal as a product and started treating it as a process document.

Common Pitfalls And What They Cost You

The biggest waste of time I see is the lack of a consistent coding system for recurring themes. Without one you end up with entries that reference \"community resistance\" in three different ways across six months and you cannot track the evolution of that concept through your own data. I use a simple alphanumeric tag system where the first letter indicates the thematic category (S for social, E for economic, P for political, Env for environmental) and the number is assigned once and reused. It takes about ten minutes to set up the codebook and another five minutes per entry to apply the tags. This adds maybe fifteen percent to your entry time but cuts your coding and analysis phase down by roughly forty percent. A second issue is the reflex to journal about everything. Some students I have worked with feel that if something happened during fieldwork they must record it. This produces journals that are kilometers long and virtually useless because signal and noise are indistinguishable. I now use a simple rule: if I cannot articulate in one sentence why a particular observation matters for my research question, I do not include it in the main journal. I keep a separate \"raw dump\" file for things I might want to reference later. This usually cuts journal volume by about half without losing any analytically significant material.

When Journaling Does Not Work

I should be clear about where this method breaks down. If you are doing large-scale quantitative work involving thousands of data points from remote sensing or GIS-based spatial analysis, the traditional field journal is mostly irrelevant. You are better off maintaining structured metadata logs and version-controlled code repositories. A physical or digital prose journal does not scale to that level of data. In those cases, comment-rich scripts and automated data diaries serve the same function with far less overhead. Similarly, if your research is entirely desk-based and involves secondary data analysis, the value of continuous journaling drops considerably. You can still benefit from a research log for tracking decisions about data sources, transformation steps, and analytical choices, but the investment of time needed to maintain a proper journal may not yield proportional returns. A simple decision log with dates and rationales is sufficient and takes about five minutes per research session instead of the thirty to forty five minutes a full journal entry requires.

Getting Started Without Overcomplicating It

If you want to begin, here is the minimum viable approach. Get a notebook or set up a simple digital folder. Write one entry per day during active fieldwork. Use the three-column structure I described. Tag your recurring themes from day one. Transcribe into your digital system within twelve hours. That is it. Do not add templates, do not create elaborate color systems, do not try to make it publication-ready. The journal becomes valuable when you review it periodically, not when you fill it. I do a proper review of my current and previous entries every Friday afternoon. This takes about twenty minutes and usually surfaces patterns or contradictions that I missed during the daily rush. The review habit is what separates an actual analytical tool from an expensive diary. Without regular review, the journal is just written text that nobody reads again. There is no single authoritative source or mandatory software requirement. The method exists in various forms across human geography, physical geography, and related fields like environmental science and urban planning. What matters is consistency and intentionality, not the specific tool you use to record your thoughts. Start simple. Review regularly. Cut the rest.