Skip to content

Favorite gpx import ignores trk and trkpt attributes #102

Description

@simonspa

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...)

Activity

  1. jancborchardt commented on Aug 31, 2019

    @jancborchardt
  2. jancborchardt commented on Aug 31, 2019

    @jancborchardt
  3. simonspa commented on Sep 2, 2019

    @simonspa
    Author
  4. changed the title [-]Some feedback on Favorites/Tracks[/-] [+]Favorite gpx import ignores trk and trkpt attributes[/+] on Sep 2, 2019
  5. jancborchardt commented on Sep 2, 2019

    @jancborchardt
  6. jancborchardt commented on Sep 2, 2019

    @jancborchardt
    Member

    What do you think @eneiluj @tacruc? I would guess tracks which are part of favorites should also be imported?

  7. simonspa commented on Sep 2, 2019

    @simonspa
    ContributorAuthor

    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 wpt features and show a warning if trks are present but not imported?

  8. tacruc commented on Sep 2, 2019

    @tacruc
    Collaborator

    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.

  9. jancborchardt commented on Sep 2, 2019

    @jancborchardt
    Member

    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.

  10. julien-nc commented on Sep 15, 2019

    @julien-nc
    Member

    Favorites 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?

  11. tacruc commented on Sep 15, 2019

    @tacruc
    Collaborator

    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.

  12. added a commit that references this issue on Sep 15, 2019
  13. added a commit that references this issue on Sep 16, 2019
  14. simonspa commented on Sep 16, 2019

    @simonspa
    ContributorAuthor

    @eneiluj I agree, but I would also implement it as @tacruc suggests: import the waypoints and only warn if there were tracks or polygons which have been ignored.

    Renaming to "Favorite Places" sounds like a good idea, it makes it even more clear what to expect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions