Bases Map View does not render stand-alone GPX files referenced via frontmatter link property

[Pakos091]

Description

First of all, thank you for the excellent plugin — Map View has become a core part of my workflow.

I’m using Obsidian 1.10+ with Bases integration enabled in Map View.

My data model is structured as follows:

• Markdown files represent domain objects (e.g. segments, tours, ride days)
• Each note contains a frontmatter property referencing a stand-alone GPX file
• The GPX files are stored separately (e.g. 40_Tracks/segments/)

Example:

kind: segment
country: CH
track_file: [[CH-GRA-001.gpx]]

The GPX files render correctly in the following cases:

• When opened directly in Map View
• When used in an embedded mapview block with a query such as:

{"query":"linkedfrom:\"$filename$\""}

So the path files themselves are valid and properly indexed.

---

The Issue

When using Bases + Map View layout, the following happens:

1. The Base filter correctly returns markdown files (e.g. kind = "segment" AND country = "CH").
2. Switching the Base view to Map View results in an empty map.
3. Even though the returned markdown files contain valid wikilinks to existing GPX files.

From the documentation:

“Filtering will be based on your Base filter, and you can add an additional Map View query…”

However, it seems that:

• Bases operate only at the resolution of complete files
• Stand-alone path files are not resolved indirectly via frontmatter link properties
• The Map View integration does not automatically render GPX files referenced via properties such as track_file

---

Expected / Desired Behavior (Feature Request)

It would be extremely powerful if Bases Map View could:

• Take the filtered markdown files
• Detect stand-alone path files referenced via frontmatter wikilinks (e.g. track_file)
• Automatically render those GPX paths on the map

In other words:

Domain-driven filtering via Bases
→ automatic rendering of associated stand-alone track files

This would allow clean separation between:

• Domain metadata (kind, country, status, etc.)
• Raw track files (GPX/KML)
• Visualization logic

Without requiring:

• Filename prefix conventions
• Manual dashboard notes
• Custom query workarounds

---

Why This Would Be Valuable

Many structured workflows separate:

• Semantic domain objects (markdown notes)
• External spatial data (GPX files)

Supporting resolution of stand-alone path files referenced via frontmatter properties would make Map View + Bases a truly domain-driven mapping system.

---

Environment

• Obsidian version: Version 1.11.7 (Installer 1.11.7)
• Map View version: 6.1.2
• Bases integration: enabled
• Stand-alone path files: GPX

---

Thank you for considering this feature.