OsmAnd~ 4.6.0#871m, released: 2023-10-13

• try to import favorites-3.gpx.txt (simply delete .txt extention) as .gpx file
• open this track (it consists of only one waypoint) and see if url is present in context menu of this waypoint (open track > points tab > waypoint)

Thanks for the proposal.

However, this is not what #14618 and I are talking about. Your example is an OsmAnd specific solution using <extension>, which is not helpful when working with other apps and geo tools. We are talking about the standard gpx definition: https://www.topografix.com/gpx_manual.asp that natively should support <url> and <urlname>. But OsmAnd actually seems to actively drop these tags, even though they are defined as standard.

But, I mean since it is essentially already implemented within <extension> (also works if importing as Favourite), it shouldn't be hard to also include <url> of <gpx> in the option to deliver an url.

Just that weird removal of <url> by OsmAnd should be dropped.

@ceever please add a link(s) to documentation
it is not clear, why are you speaking about <url> and not a <link> (or whatever else) tag
what is most common implementation of this feature in other apps? (i.e. which tags other apps support?)

The link to the mentioned documentation of GPX is in my comment before. They decided for "url" instead of "link", c'est la vie. I mean what does that even matter? Would that impact the impementation in any way, it is just a word?

@ceever provided link refers to gpx 1.0 schema, and in the beginning of this document it is stated, that this schema is outdated.
According to OsmAnd technical documentation, it uses gpx 1.1 schema (see https://osmand.net/docs/technical/osmand-file-formats/osmand-gpx)
In gpx 1.1 technical documentation it is proposed to use different tags for urls (see https://www.topografix.com/GPX/1/1/#type_linkType). However, as I know, this solution looks a bit complicated, and it is not commonly used. Custom extensions are used instead.

I don't think it is very complicated, that's just the way it is documented, which is a little cumbersome, I have to admit. But anyhow.

I mean if one implements support for a certain file format (GPX), one covers the standards of the file format first to be compatible with other applications, right? I mean it's great that there are these numerous OsmAnd extensions (osmand:color ... etc). But of what use are they as soon as I move out of the OsmAnd universe? Unless, of course, you intentionally wanted to produce incompatibilities and lock users in. But why bother using GPX then in the first place?

Wouldn't a proper implementation be to use the existing standards and always fall back onto it if possible, and only if it goes beyond the standard, one relies on the extension part?

OsmAnd~ 4.6.0#1037m, released: 2023-11-16

Steps to reproduce

• based on .gpx file provided above, created a file that seems to meet the requirements of the 1.1 GPX standard.
  gpx_with_link.gpx.txt
• imported this and 8 other variants of that .gpx file into OsmAnd trying to see link in the Track context menu

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<gpx version="1.1" creator="Mundraub2Use Script" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
  <metadata>
    <link href="https://www.hatinosu.net/house/archives/346">
      <text>Rider House 346</text>
    </link>
  </metadata>
  <wpt lat="43.94073" lon="141.650913">
    <name>Rider House 346</name>
  </wpt>
  <wpt lat="43.322306" lon="145.632708">
    <name>Rider House 349</name>
  </wpt>
</gpx>

Actual result:

• lthe link is not displayed in the Track context menu (see screenshot)

Expected result:

• the link is displayed in the Track context menu, when you tap it, you are redirected to the corresponding resource
• probably it is also possible to copy it to the clipboard

@DmitryAlexei please test original gpx with waypoints extra info this looks as a separate issue

OsmAnd~ 4.6.0#1037m, released: 2023-11-16

Steps to reproduce

• based on .gpx file provided above, created a file that seems to meet the requirements of the 1.1 GPX standard.
  gpx_with_link.gpx.txt
• imported this and 8 other variants of that .gpx file into OsmAnd trying to see link in the Track context menu

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<gpx version="1.1" creator="Mundraub2Use Script" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
  <metadata>
    <link href="https://www.hatinosu.net/house/archives/346">
      <text>Rider House 346</text>
    </link>
  </metadata>
  <wpt lat="43.94073" lon="141.650913">
    <name>Rider House 346</name>
  </wpt>
  <wpt lat="43.322306" lon="145.632708">
    <name>Rider House 349</name>
  </wpt>
</gpx>

Actual result:

• lthe link is not displayed in the Track context menu (see screenshot)

**Expected result:**

• the link is displayed in the Track context menu, when you tap it, you are redirected to the corresponding resource
• probably it is also possible to copy it to the clipboard

Yes, that's not the issue I am talking about. The link is supposed to be part of the way point ... POIs with websites as addition.

Here the proper example:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<gpx version="1.1" creator="Mundraub2Use Script" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
  <wpt lat="43.94073" lon="141.650913">
    <name>Rider House 346</name>
    <link href="https://www.hatinosu.net/house/archives/346">
      <text>Rider House 346</text>
    </link>
  </wpt>
  <wpt lat="43.322306" lon="145.632708">
    <name>Rider House 349</name>
    <link href="https://www.hatinosu.net/house/archives/349">
      <text>Rider House 349</text>
    </link>
  </wpt>
</gpx>
</code>

Here the gpx:
gpx_with_POIs_with_link.gpx.txt

OsmAnd Nightly 4.6.0#1078m, released: 2023-11-22
Nokia 5.3
Android 12

When importing a track using OsmAnd, the import fails, the application freezes. When trying to import using the device file manager, there is no URL in the description.

OsmAnd Nightly 4.6.0#1078m, released: 2023-11-22

To do:

• Links and all other tags should be displayed in Track Context menu
• Links and all other tags should be displayed in Waypoint Track Context menu

Do not show bounds

Display all that inside that file (name, link, desc, author, copyright, extensions)
gpx_with_link.gpx.zip

file with fixed author and copyright tags - gpx_with_link.zip

Review

General

• Created on, icon – ic_action_date_start
• Size, icon – ic_sdcard
• Location, icon – ic_action_folder

Info

<link href="http://docs.osmand.net">
  <text>OsmAnd Documetation</text>
</link>
...
<keywords>gpx, osmand, hiking</keywords>

• Activity, icon = activity icon
• Keywords, icon – ic_action_label
• Link
• • Icon – ic_action_link
• • Color – active
• • Tap should open link in Chrome tabs

Author

<author>
      <name>Author Name</name>
      <email id="your" domain="email.com"/>
      <link href="https://yourwebsite.com" />
</author>

• Name, icon – ic_action_user
• Email, icon – ic_action_at_mail
• • Tap should open default mail client
• • Color – active
• Link
• • Icon – ic_action_link
• • Color – active
• • Tap should open link in Chrome tabs
• • Text is missed? If is present show it instead of link. Tap should work the same

Copyright

<copyright author="OsmAnd B.V">
  <year>2023</year>
  <license>https://github.com/osmandapp/OsmAnd/blob/master/LICENSE</license>
</copyright>

• Author, icon – ic_action_copyright
• Year, icon – ic_action_calendar_month
• License, icon – ic_action_link

Extensions

<extensions>
  <osmand:address>Floyd Avenue (The Fan) 907, Richmond</osmand:address>
  <osmand:icon>place_town</osmand:icon>
  <osmand:background>circle</osmand:background>
  <osmand:color>#ff4e4eff</osmand:color>
  <test:country>United States</test:country>
  <test:state>Virginia</test:state>
  <test:telephone>(804) 828-0100</test:telephone>
  <test:postcode>23284</test:postcode>
  <test:start_date>Thursday, June 8, 2023</test:start_date>
</extensions>

Result

• All tags from <metadata> -> <extensions> should be placed into Additional group
• Tags are misplaced with values

Review 2

Screenshot

• License should be work as link

Screenshot

• Display first symbol of custom tag name as uppercase.

• • address > Address
• • icon > Icon

Review 3

Copyright

• Rename Name to Author on UI

Review 29.03.2024

• re-write this sections of Track Context menu 1 and 2