How to use maps in Obsidian // Leaflet and Kanban
Based on Nicole van der Hoeven's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use Readwise to sync highlights into Obsidian so research becomes searchable, reusable evidence for decisions like tax planning.
Briefing
A cross-country move becomes manageable when personal knowledge management turns into a working system: Obsidian is used to research Portugal’s tax and housing rules, map out neighborhoods and cities to visit, and then track the real-world tasks needed to finalize a purchase. The core insight is practical—notes aren’t valuable as philosophy or “organizational masturbation,” but as a tool that reduces uncertainty and keeps decisions and deadlines from slipping.
The process starts with tax research. Highlights pulled from articles, books, and other sources via Readwise are synced into an Obsidian vault, creating a growing evidence base. Early highlights from 2020 already contain key details about Portugal’s Non-Habitual Residency program—what it is, eligibility requirements, and tax rates—so the decision isn’t made from scratch during the move. A simple workflow then emerges: search for “taxation in Portugal,” open the relevant page, and connect scattered quotes and requirements into a single decision-ready view. Taxes may have been the initial driver, but the system is also used to validate the choice emotionally and practically.
That validation comes through a reconnaissance trip. To visualize where the couple might fit, an Obsidian Leaflet map of Portugal is built with markers for places worth checking out. Leaflet makes this fast: right-click to add a marker, choose a color, edit the marker to link it to a note, and customize icons (including using built-in marker icons like a thumbtack or water symbol). Markers are organized as layers, and the map supports zooming and panning so the couple can narrow options. Green markers represent destinations that felt promising; as visits happened, notes were created for those locations. Tavira, for example, ends up near the bottom of the map close to Spain, with both factual context (from Wikipedia) and personal impressions.
The map work ties directly into the housing decision. After settling on a region and then a specific house, the system shifts from discovery to execution. A separate Obsidian page documents the house-buying process in Portugal, including what documents are required and what the real estate agent and bank ask for. Because the move is ongoing, the guide is explicitly “in progress”—categories like NIF (tax identification) details and step-by-step buying instructions are being filled in as new requirements appear. The goal is not perfection; it’s usefulness for future repeats of the process, whether in Portugal again or elsewhere.
Finally, once the paperwork is signed, task management takes over. A Kanban board tracks the post-purchase checklist—items like connecting electricity, registering, and dealing with local municipality steps—moving cards across columns as progress happens. Dates and deadlines can be set (e.g., “needs to be done by Friday”), giving a real-time overview of the juggling required to move in. The result is a connected system: research evidence, geographic decision-making, and operational tracking all live in one place and keep updating as the move progresses.
Cornell Notes
The move to Portugal is managed with Obsidian as an end-to-end system: research, mapping, and execution. Readwise highlights are synced into an Obsidian vault to build a decision-ready knowledge base, including details about Portugal’s Non-Habitual Residency program. Obsidian Leaflet then turns travel planning into a visual map with customizable markers that link directly to notes (e.g., Tavira with both Wikipedia facts and personal impressions). After choosing a house, Obsidian pages document the buying process and required documents, while a Kanban board tracks post-signing tasks with deadlines and status changes. The practical takeaway: notes become valuable when they directly reduce uncertainty and coordinate real-world work.
How does the workflow turn scattered research into a decision tool for moving to Portugal?
What role does Obsidian Leaflet play beyond “making a map,” and how is it connected to notes?
How were reconnaissance trips translated into a living knowledge base?
Why keep the house-buying guide “in progress” instead of waiting for a complete reference?
How does Kanban support the post-purchase phase differently from static notes?
Review Questions
- What specific information is consolidated in the Obsidian pages during tax research, and how does that reduce decision friction?
- Describe how a Leaflet marker becomes more than a pin—what customization and linking steps make it useful for later planning?
- How do the Kanban columns and deadlines change the way post-purchase work is tracked compared with a written checklist?
Key Points
- 1
Use Readwise to sync highlights into Obsidian so research becomes searchable, reusable evidence for decisions like tax planning.
- 2
Build a Leaflet map with markers that link directly to location notes, turning geographic planning into an organized workflow.
- 3
Customize Leaflet markers (color, icon, layers) to reflect different categories of interest and keep the map readable.
- 4
Document the house-buying process as a living guide—start with what’s known, then update categories like NIF and document requirements as the process unfolds.
- 5
Use Kanban for the post-signing phase to track tasks by status and deadlines, not just to store information.
- 6
Treat “good enough” notes as publishable drafts; perfection isn’t required for the system to stay useful over time.