Initial commit: OpenClaw Skill Collection
6 custom skills (assign-task, dispatch-webhook, daily-briefing, task-capture, qmd-brain, tts-voice) with technical documentation. Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.
This commit is contained in:
37
openclaw-knowhow-skill/docs/channels/location.md
Normal file
37
openclaw-knowhow-skill/docs/channels/location.md
Normal file
@@ -0,0 +1,37 @@
|
||||
# Channel Location Parsing
|
||||
|
||||
OpenClaw converts location data from messaging platforms into both readable text and structured fields. The system supports Telegram, WhatsApp, and Matrix channels.
|
||||
|
||||
## Text Rendering
|
||||
|
||||
Locations appear as formatted strings appended to messages:
|
||||
|
||||
- A pin displays as `"📍 48.858844, 2.294351 ±12m"`
|
||||
- A named venue shows the location name alongside coordinates
|
||||
- Live location shares are prefixed with a satellite emoji
|
||||
|
||||
User captions or comments are added on subsequent lines when provided.
|
||||
|
||||
## Structured Data
|
||||
|
||||
When locations are detected, the auto-reply context receives these fields:
|
||||
|
||||
- Latitude and longitude (numeric)
|
||||
- Accuracy measurement in meters (when available)
|
||||
- Optional place name and address
|
||||
- Source type designation
|
||||
- Live-sharing status indicator
|
||||
|
||||
## Platform-Specific Details
|
||||
|
||||
### Telegram
|
||||
|
||||
Processes venue data into name and address fields. Live locations reference the `live_period` attribute.
|
||||
|
||||
### WhatsApp
|
||||
|
||||
Extracts comments from location messages and captions from live sharing.
|
||||
|
||||
### Matrix
|
||||
|
||||
Parses the `geo_uri` standard, treating all locations as static pins regardless of the `LocationIsLive` designation.
|
||||
Reference in New Issue
Block a user