this post was submitted on 21 Jan 2025
34 points (88.6% liked)

OpenStreetMap community

4302 readers
156 users here now

Everything #OpenStreetMap related is welcome: software releases, showing of your work, questions about how to tag something, as long as it has to do with OpenStreetMap or OpenStreetMap-related software.

OpenStreetMap is a map of the world, created by people like you and free to use under an open license.

Join OpenStreetMap and start mapping: https://www.openstreetmap.org.

There are many communication channels about OSM, many organized around a certain country or region. Discover them on https://openstreetmap.community

https://mapcomplete.org is an easy-to-use website to view, edit and add points (such as shops, restaurants and others)

https://learnosm.org/en/ has a lot of information for beginners too.

founded 5 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
34
The OSM Community discusses the Trump Administration's renaming of "The Gulf of Mexico" to "The Gulf of America" (community.openstreetmap.org)
submitted 1 day ago* (last edited 1 hour ago) by Kalcifer to c/[email protected]
37 comments fedilink hide all child comments
 

References

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 23 hours ago (3 children)

Looks like the thread is gone now, what was the discussion like?

[–] [email protected] 3 points 17 hours ago* (last edited 17 hours ago)

To put it simple, they say each country can decide what name to use for where, and that's what OSM uses as a reference.

What it is called however is not by defined by what the president says alone though, it has to go through the entire government bureaucracy thing.

[–] [email protected] 5 points 22 hours ago (1 children)

The thread still works for me.

[–] [email protected] 4 points 22 hours ago* (last edited 22 hours ago) (1 children)

Oh I see the issue

The link in the post is fine, the link in the post body goes to a "page doesn't exist or has been deleted" message because of the period at the end

https://community.openstreetmap.org/t/gulf-of-america-gulf-of-mexico/124571

vs.

https://community.openstreetmap.org/t/gulf-of-america-gulf-of-mexico/124571.

Thanks :)

[–] Kalcifer 5 points 21 hours ago* (last edited 7 hours ago)

[…] the link in the post body goes to a “page doesn’t exist or has been deleted” message because of the period at the end […]

Ah! Interesting! That's good to know. I didn't consider that some Lemmy apps or browser UI's might not format the Markdown how I've been expecting. The correct CommonMark Markdown syntax for plain text links is to do <uri-inside-angle-brackets> ^[1]^; I'll change the URL in the post's body to that format to improve support. Thanks for letting me know! 😊

References

  1. "CommonMark Spec". John MacFarlane. Version: 0.31.2. Published: 2024-01-28. Accessed: 2025-01-21T01:27Z. https://spec.commonmark.org/0.31.2/#autolinks.
    • §6.5 ("Autolinks"):

      Autolinks are absolute URIs and email addresses inside < and >. They are parsed as links, with the URL or email address as the link label.

      A URI autolink consists of <, followed by an absolute URI followed by >. It is parsed as a link to the URI, with the URI as the link’s label.

      An absolute URI, for these purposes, consists of a scheme followed by a colon (:) followed by zero or more characters other than ASCII control characters, space, <, and >. If the URI includes these characters, they must be percent-encoded (e.g. %20 for a space).

      For purposes of this spec, a scheme is any sequence of 2–32 characters beginning with an ASCII letter and followed by any combination of ASCII letters, digits, or the symbols plus (“+”), period (“.”), or hyphen (“-”).

[–] Kalcifer 4 points 22 hours ago (1 children)

Looks like the thread is gone now […]

Hrm, I can still see it.

[–] [email protected] 4 points 22 hours ago

I just checked, and it's only the link in the post body

It has a period at the end, and so my client opened an error page. I can see it now :)