[GH-ISSUE #458] How does the geo: URL in a view work? #351

Closed
opened 2026-05-07 00:23:20 +02:00 by BreizhHardware · 3 comments

Originally created by @jpmens on GitHub (Oct 30, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/458

I can't get geo: to workd in ntfy 1.28.0, neither with the CLI program nor when posting with curl.

I'm trying the example from the documentation (though I'd like to specify lat,lon only):

$ ntfy publish --actions '[ { "action" : "view", "label": "Jane lives here", "url":"geo:0,0?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA" }]' mytopic

and I'm rewarded with (formatted for clarity):

{
  "id": "ddIAjxyW2v4P",
  "time": 1667169268,
  "event": "message",
  "topic": "mytopic",
  "message": "triggered",
  "actions": [
    {
      "id": "wHhMdkN8Qd",
      "action": "view",
      "label": "Jane lives here",
      "clear": false,
      "url": "geo:0,0?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA"
    }
  ]
}

The UI (here in Chrome) displays:

rabbit-9710

but when I click on the link, Chrome opens a new tab with about:blank. (For the record: the ntfy iOS app does nothing)

I'm sure I must be formatting the URL incorrectly, but how?

I've also tried this, but there's no distinct behavior:

"url": "geo:48.856826,2.292713"
Originally created by @jpmens on GitHub (Oct 30, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/458 I can't get `geo:` to workd in ntfy 1.28.0, neither with the CLI program nor when posting with curl. I'm trying the example from the documentation (though I'd like to specify `lat,lon` only): ```console $ ntfy publish --actions '[ { "action" : "view", "label": "Jane lives here", "url":"geo:0,0?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA" }]' mytopic ``` and I'm rewarded with (formatted for clarity): ```json { "id": "ddIAjxyW2v4P", "time": 1667169268, "event": "message", "topic": "mytopic", "message": "triggered", "actions": [ { "id": "wHhMdkN8Qd", "action": "view", "label": "Jane lives here", "clear": false, "url": "geo:0,0?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA" } ] } ``` The UI (here in Chrome) displays: ![rabbit-9710](https://user-images.githubusercontent.com/60706/198905083-696b7b18-e908-41b5-b613-042c5bd90172.png) but when I click on the link, Chrome opens a new tab with `about:blank`. (For the record: the ntfy iOS app does nothing) I'm sure I must be formatting the URL incorrectly, but how? I've also tried this, but there's no distinct behavior: ```json "url": "geo:48.856826,2.292713" ```
BreizhHardware 2026-05-07 00:23:20 +02:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@jpmens commented on GitHub (Oct 31, 2022):

In FireFox, the result of clicking on the geo: URL is:

rabbit-9712

<!-- gh-comment-id:1296732959 --> @jpmens commented on GitHub (Oct 31, 2022): In FireFox, the result of clicking on the `geo:` URL is: ![rabbit-9712](https://user-images.githubusercontent.com/60706/198960573-3e1233b0-b162-4dd8-ae42-65e7b82a5dfd.png)
Author
Owner

@binwiederhier commented on GitHub (Oct 31, 2022):

geo: URIs are not universally understood by all operating systems, similar to tel:. Android knows what to do with them, but apparently your OS does not. I'm sure there's some application you can install that will handle the geo: URL. If you send a Google Maps link instead, it'll likely have the same desired effect.

<!-- gh-comment-id:1297249153 --> @binwiederhier commented on GitHub (Oct 31, 2022): `geo:` URIs are not universally understood by all operating systems, similar to `tel:`. Android knows what to do with them, but apparently your OS does not. I'm sure there's some application you can install that will handle the `geo:` URL. If you send a Google Maps link instead, it'll likely have the same desired effect.
Author
Owner

@jpmens commented on GitHub (Oct 31, 2022):

Thanks for the clarification.

I suppose I was expecting ntfy do do the "magic" conversion to proper URLs, but what you say makes sense.

<!-- gh-comment-id:1297263090 --> @jpmens commented on GitHub (Oct 31, 2022): Thanks for the clarification. I suppose I was expecting ntfy do do the "magic" conversion to proper URLs, but what you say makes sense.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#351
No description provided.