Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support rendering tracks on Map tab #1201

Closed
lfcnassif opened this issue Jul 2, 2022 · 5 comments · Fixed by #1457
Closed

Support rendering tracks on Map tab #1201

lfcnassif opened this issue Jul 2, 2022 · 5 comments · Fixed by #1457
Assignees

Comments

@lfcnassif
Copy link
Member

lfcnassif commented Jul 2, 2022

This should help identifying paths instead of isolate points of tracks/routes.

@patrickdalla
Copy link
Collaborator

The current parser extract track points from GPX or KML as individual items, as they can have timestamps or other metadata associated. The track itself, within the file, is also extracted as a subitem of the file.
So we could identify track items as such, and plot the lines when selected. Also, when a item of this track is clicked, when can identify if it have a track as the immediate parent, and plot the lines.

@patrickdalla
Copy link
Collaborator

Is there already implemented method on API to:

  • get the parent IItemId of a specific Item?
  • get the children IItemId of a specific Item?

Or should I create lucene querys to achieve this results?

@lfcnassif
Copy link
Member Author

  1. If I remember you can get the parent ID then, using IIPEDSource, get the corresponding IItem
  2. For this one I think a query search should be done

@patrickdalla
Copy link
Collaborator

The track are being correctly parsed and shown. But now the navigation buttons can be confusing. May it follow the track order or the table sort order (original navigation behaviour).

@patrickdalla patrickdalla linked a pull request Dec 21, 2022 that will close this issue
@lfcnassif
Copy link
Member Author

Hi @patrickdalla. I never thought those buttons a must, since user can already navigate through items using the (sorted) table and the selection is propagated to the map, maybe when it was implemented at first the panels were not detachable.

So I think we can change the behavior to follow the track order when the item is part of a track, and maybe update the button labels to try to avoid confusion with old behavior. When the item is not part of some track, maybe those button could be disabled.

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

Successfully merging a pull request may close this issue.

2 participants