Skip to content

Commit 1008df8

Browse files
committed
Skill update
1 parent d58d3aa commit 1008df8

1 file changed

Lines changed: 25 additions & 0 deletions

File tree

skills/map-view/SKILL.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,27 @@ If the [obsidian-skills](https://github.com/kepano/obsidian-skills) plugin is no
1515
Geolocations: When the content to be added contains named real-world places (restaurants, venues, hotels, attractions, etc.), format each as a Map View inline geolink -- [Place Name](geo:lat,lng) -- rather than plain text.
1616
If coordinates are not already known, use this skill to look them up before appending.
1717

18+
### Tagging geolinks (default: tag every place)
19+
20+
Map View inline tags go **after** the geolink, separated by a space, as `tag:name` -- bare word, **no `#`**. This is different from the `tag:#name` syntax used inside `mv-query` queries (the inline marker `tag:food` is matched by the query `tag:#food`). Multiple tags are space-separated.
21+
22+
Examples:
23+
24+
```
25+
- [Nono](geo:32.14,34.89) tag:food
26+
- [The Rally Hotel](geo:39.75,-104.99) tag:sleep
27+
- [Some Trail](geo:32.7,35.1) tag:hike tag:hike/water
28+
```
29+
30+
**Default to tagging.** Before writing geolinks, figure out the right tag:
31+
32+
1. Check the project's `CLAUDE.md` for a documented geolocations tag vocabulary.
33+
2. Grep an existing note in the vault that contains similar places to see the actual conventions in use, e.g.:
34+
```bash
35+
grep -h "geo:" zk/*trip*.md | head
36+
```
37+
3. Only omit a tag if no plausible match exists in the user's vocabulary -- **never invent a new tag**. Prefer no tag over a made-up one.
38+
1839
## Commands
1940
2041
```bash
@@ -43,6 +64,8 @@ Opens Map View filtered to show only the locations in that note. Use after addin
4364
4465
Consider actively asking the user if he wants to see the results after adding geolocations.
4566
67+
**Important:** when using `mv-focus-note`, it's recommended that the focused note will not contain links to other notes that contain geolinks. This is because the user might have a `linkedFrom` query template set for `mv-focus-note`, so it will show much more than intended. If using `mv-focus-note`, and you were not asked to link to other notes, do not add unnecessary links.
68+
4669
```bash
4770
obsidian mv-query query="<query>"
4871
```
@@ -77,6 +100,8 @@ obsidian mv-query "distancefrom:32.08,34.78<5km"
77100
obsidian mv-query "distancefrom:32.08,34.78<500m AND tag:#restaurant"
78101
```
79102

103+
Note: inside `mv-query`, tags are written with a `#` (e.g. `tag:#food`). The corresponding **inline** tag in a note body is written _without_ the `#` (e.g. `tag:food`). See the "Tagging geolinks" section above.
104+
80105
Radius can be in `km`, `m`, `mi`, or `ft`. This is the fastest way to find vault markers near a given point — no routing API key required. Use it to quickly narrow down candidates before calling `mv-calc-route` only on the ones that are geographically plausible, or to answer the users for queries like "what do I have in my vault that is around...".
81106
82107
## Getting rich place data (opening hours, ratings, etc.)

0 commit comments

Comments
 (0)