Improvement request POI -> GPX

[Guzzist]

@BertM said in Improvement request POI -> GPX:

Re: POI improvements!

I would like to see the name of the POI symbol included in the GPX export.

Not sure if I understand you right. But if I create a route and enter POI (no matter if included as Route Point, or just as POI). Then export it as gpx 1.1 (route, track, POI) and open the stored file by text editor. Now I can find the entered POI - inclusive the name I gave them during route planning.

If I import the file to my Garmin Nav, the POI will be visible as well as the route. If the transmitted name will be used by Garmin or other devices, that's not in the responsibility of MyRoute-App.

[BertM]

@Guzzist said in Improvement request POI -> GPX:

@BertM said in Improvement request POI -> GPX:

Re: POI improvements!

I would like to see the name of the POI symbol included in the GPX export.

Not sure if I understand you right. But if I create a route and enter POI (no matter if included as Route Point, or just as POI). Then export it as gpx 1.1 (route, track, POI) and open the stored file by text editor. Now I can find the entered POI - inclusive the name I gave them during route planning.

I am talking about the symbol name not the description name.

GPX from MRA with only the name:

As the POI's in MRA already have different symbols, they have a symbol name, for example "Restaurant". These names are not transferred into the GPX file. As a result the GPX parser will use the default symbol when read by any other program following the topografix standard.

As the symbol is already present in MRA my request is to put it into the GPX exporter from MRA.
(I know it depends on what the GPX importer can read, but "Bar", "Hotel" and "Museum" will be in any Navigation program. Symbols not know will get the standard symbol by default.

*Symbol name added to the GPX file: *

Example:

the following route from the Routelab:
https://www.myrouteapp.com/nl/social/route/10375140?mode=share

Exported GPX from MRA: all the POI's have the same symbol:

The same route imported with the symbol name added into the GPX:

If I import the file to my Garmin Nav, the POI will be visible as well as the route. If the transmitted name will be used by Garmin or other devices, that's not in the responsibility of MyRoute-App.

I am not talking about responsibilities, I only make an improvement request, it is on the developer team to take it into account or leave is as it is. As it is already in the MRA database and the Topografix scheme, it will be " low hanging fruit" to implement I presume.

[Martin Wilcke]

I second this idea!

The GPX <sym> tag is commonly used to classify POIs (<wpt> in GPX terms) and is supported by various apps when importing (or exporting) GPX files.
As already pointed out by @BertM , there is no standard for the <sym> values, but with some copy and paste (or some scripting) this can be managed easily.

[Adrian Avram]

@BertMI it would be nice to be as customizable as Osmand is ...

[Martin Wilcke]

@Adrian-Avram

Sorry, but I didn't get your point.
This is not about displaying POIs in an app but considering the classification in a GPX export.

[Adrian Avram]

@Martin-Wilcke you can classify POIs in Osmand, and then export to GPX ...

[Martin Wilcke]

@Adrian-Avram

Hmmm...
If I export OSMAnd "favorites", the GPX does not contain <sym> tags either. How do you manage this?

[BertM]

@Martin-Wilcke

Looking at the screenshot you made they not following the standard topografix schematic.
You can see that the symbol name is in extensions.
I wonder if the GPX will add the symbol when imported

[Martin Wilcke]

@BertM said in Improvement request POI -> GPX:

Looking at the screenshot you made they not following the standard topografix schematic.
You can see that the symbol name is in extensions.

OSMAnd does not export a <sym> tag, right. However, as they refer to a namespace/schema (xmlns:osmand), its extension complies with Topografic's GPX Spec.

Storing data in an individual extension is a clever way to keep and share information within an ecosystem. If this GPX is re-imported into OSMAnd, the category (and symbol) will be restored.

But I don't think any other app will parse this extension, identify "amenity:restaurant" as a category (even if it's pure OSM semantic) and transform this value into its terminology.

The <sym> tag is a far better option for sharing a category with other apps. It would be perfect if OSMAnd added a <sym> tag with "Restaurant" - and that's what MRA should do as well.

I wonder if the GPX will add the symbol when imported

What do you mean by "the GPX"? Any other app?

[BertM]

@Martin-Wilcke said in Improvement request POI -> GPX:

@BertM said in Improvement request POI -> GPX:

Looking at the screenshot you made they not following the standard topografix schematic.
You can see that the symbol name is in extensions.

OSMAnd does not export a <sym> tag, right. However, as they refer to a namespace/schema (xmlns:osmand), its extension complies with Topografic's GPX Spec.

Storing data in an individual extension is a clever way to keep and share information within an ecosystem. If this GPX is re-imported into OSMAnd, the category (and symbol) will be restored.

I agree, that is also what other applications do.
But as MRA is a platform that is used by a lot of other navigations app, I do not think you would look for an platform specific schema.

Osmand pulls the POI from OSM and that is one way to do it.
On the other hand I like the MRA solution better. If they can safe the symbol by export ( and import) this will be an huge improvement.

What do you mean by "the GPX"? Any other app?

Yes