Stratbook vs Obsidian for Spatial Research
A clear comparison of Stratbook and Obsidian for researchers who like markdown, linked notes, and knowledge bases but need spatial context.
Image placeholder
Markdown graph vs spatial workspace
Markdown notes vs spatial notes
Obsidian is a powerful markdown editor and personal knowledge base. It is excellent for linked thinking, local-first notes, plugins, and long-lived personal archives. Stratbook starts with a different assumption: some research is not document-first or graph-first. It is place-first.
If the main unit of your work is an idea, a person, or a document, Obsidian may fit beautifully. If the main unit is a port, route, district, border crossing, facility, or event location, a map-first workspace can reduce friction.
Obsidian's official help describes it as both a Markdown editor and a knowledge base app, with links as first-class citizens and plain text ownership as a major advantage. Stratbook should respect that strength. The comparison is not about replacing a personal knowledge base; it is about what changes when the knowledge base needs a geographic spine.
Where Stratbook differs
Stratbook keeps markdown in the workflow but gives each note a coordinate-aware context. That means a note can live inside a broader map, connect to surrounding layers, and become part of a shareable spatial brief.
For analysts, the difference is retrieval and synthesis. You are not only asking “what did I write about this topic?” You are asking “what do we know about this place, what is nearby, and what should the briefing say?”
This matters most when the evidence is spatially clustered: multiple claims about one facility, a route with several incidents, an infrastructure network, or a city where neighborhoods carry different operational meaning. In those cases, a map is not an attachment to the note. It is the index.
Image placeholder
Coordinate-aware markdown note
Which should you choose?
Use Obsidian when you want maximum control over a personal markdown vault. Use Stratbook when your notes, sources, and outputs need to stay anchored to geography and become understandable to teammates or public readers through a map.
A hybrid workflow can also work: maintain deep personal notes in Obsidian, then use Stratbook for the spatial subset that needs pins, layers, public examples, or AI-assisted briefing. The cleaner the boundary, the better: Obsidian for personal knowledge, Stratbook for place-based intelligence artifacts.
How to move spatial notes into Stratbook
A useful migration pattern is to start with one area of interest, not the whole vault. Export or copy only the notes that have a clear location, convert each location into a pin, preserve backlinks as related-pin references, and keep one summary note for the analytic question.
Do not try to recreate every graph edge on the map. Spatial work benefits from restraint. The map should show places, routes, areas, and relationships that matter to the decision, not every possible association in the archive.