Repository navigation
Favorite gpx import ignores trk and trkpt attributes #102
Description
Activity
jancborchardt commented
on Aug 31, 2019 on Aug 31, 2019 · Hidden as resolvedshow commentMore actionsjancborchardt commented
on Aug 31, 2019 on Aug 31, 2019 · Hidden as outdatedshow commentMore actionssimonspa commented
on Sep 2, 2019 on Sep 2, 2019 · Hidden as off-topicAuthorshow commentMore actions- changed the title
[-]Some feedback on Favorites/Tracks[/-][+]Favorite gpx import ignores trk and trkpt attributes[/+]on Sep 2, 2019 I'm actually not so sure of that. If we look at how big commercial maps applications handle this, it's rather only used to store individual locations. Otherwise we start duplication functionality, because tracks are also read from file store...
Maybe we can keep it as it is, only import
wptfeatures and show a warning iftrks are present but not imported?I agree with @simonspa, right now favorite's is for locations, not a general favorite folder which can store tracks, devices or contacts, too.
So I think the general question is, if favorites is more like a bookmark of different things (places, tracks, contacts, devices etc.), than the current favorites would need to be renamed to places.
Or if we keep it as a favorite places (short favorites) and we show a warning or import trk points directly to tracks?Personally I have no preference.
Ahh ok. No, Favorites should stay as it is then, so just for places. Basically we should keep wording and the flow "compatible" with Google Maps, so to say.
Then probably there should be some sort of notice if a favorites file has Tracks, and then to separately upload them? Could also work automatically in the future.
Reacted by Arne HamannFavorites are definitely only about places and not lines or polygons IMO.
Hmmm so we should just warn that only waypoints (
<wpt>) will be imported when done from "favorites" context menu. We could also rename "Your favorites" to "Your favorite places". What do you think?Favorites is fine as a name, hence other applications use the same.
@eneiluj lets only show the warning if there are any trk points etc. in the gpx. Otherwise it would just bother people.- added a commit that references this issue
on Sep 15, 2019 - added a commit that references this issue
on Sep 16, 2019
First of all huge thanks to all contributors, I have been following the work on this app for a while now and decided tonight was the time to spin up a Docker image to test it - and I am very, very impressed! Many things already work very beautifully.
When importing some GPX files via the "Favorite" section I noticed that only way points (i.e.
<wpt>tags) are imported and shown on the map, while the<trk>and<trkpt>attributes are ignored. I understand you want this feature to only focus on places (and later offer the import from Google via #66 ) - maybe you can make this more clear somehow?Again, this is really just suggestions for polishing, I'm super happy with the current state already (and imported my 700+ contacts from my production Nextcloud just to see them on the map...)