uploading waypoints onto flyxc

[Piterson85]

I have a route of 90 gps points which i have previosly created on earlier flyxc app and saved on my desktop. This file after uploading onto flyxc does show any route at all,although it coordinates are inside.the only way i can view the route is by having the link of where i have left off. Also,the more waypoints i add the more for system it takes to process it (up to 40sec for the route to get updated.

[vicb]

This file after uploading onto flyxc does show any route at all

Route (i.e. waypoints) loading is not implemented in flyxc.
For now you can only load tracks (igc, gpx, ...)
It will be implemented as some point...

Also,the more waypoints i add the more for system it takes to process it (up to 40sec for the route to get updated.

Could you explain more about the issue here ?
Where do you see such a delay ?

[Piterson85]

hi Best i can explain this is by sending you a gpx file of my route.I started it near nice and went all the way up to chamonix/sion.There is about 90 turnpoints.Now i want to carry on with this further towards the alps tomorrow.But even if i upload the gpx file (which i have added to this email for your view) my track still does not load up. Try adding another waypoint to what you see already and you will know what i mean by lagging time :) For now i can only save the URL of my work in progress but in case i forget to save it i might loose a lot of time. hope that makes sense :)

…

On Sun, Jan 3, 2021 at 5:03 PM Victor Berchet ***@***.***> wrote: This file after uploading onto flyxc does show any route at all Route (i.e. waypoints) loading is not implemented in flyxc. For now you can only load tracks (igc, gpx, ...) It will be implemented as some point... Also,the more waypoints i add the more for system it takes to process it (up to 40sec for the route to get updated. Could you explain more about the issue here ? Where do you see such a delay ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASKYRAANQKG2YCGBESGBWCTSYCIOZANCNFSM4VR4XPDA> .

[vicb]

Hey @Piterson85 ,

I missed the notification and only see your message now. Sorry for the delay :(

But even if i upload the gpx file (which i have added to this email for your view) my track still does not load up.

As I explained in my first reply, loading waypoints is not supported yet.
You can load a track (igc, gpx, ...) but you can not load waypoints.
So this is expected.

Try adding another waypoint to what you see already and you will know what I mean by lagging time :)

I have created a route with a lot of points and it is indeed quite slow.
My guess is that the optimization algo is slow when there are too many points.
I need to confirm that and think about a fix.
There are ways to improve that but I want to make sure the effort is not too big vs the benefits.

A simpler fix could be to disable auto optimization when there are too many points and only optimize on request (i.e. by pressing a button).

[Piterson85]

Its not a big deal for me anymore In the end i just gonna have enire route split intro 5 smaller ones. Thank anyway!

…

On Mon, 8 Feb 2021, 00:25 Victor Berchet, ***@***.***> wrote: Hey @Piterson85 <https://github.com/Piterson85> , I missed the notification and only see your message now. Sorry for the delay :( But even if i upload the gpx file (which i have added to this email for your view) my track still does not load up. As I explained in my first reply, loading waypoints is not supported yet. You can load a track (igc, gpx, ...) but you can *not* load waypoints. So this is expected. Try adding another waypoint to what you see already and you will know what I mean by lagging time :) I have created a route with a lot of points and it is indeed quite slow. My guess is that the optimization algo is slow when there are too many points. I need to confirm that and think about a fix. There are ways to improve that but I want to make sure the effort is not too big vs the benefits. A simpler fix could be to disable auto optimization when there are too many points and only optimize on request (i.e. by pressing a button). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASKYRAEROKO2MYF3ASY427TS54VP7ANCNFSM4VR4XPDA> .

[vicb]

Thanks for letting me know.

What I will implement is:

• loading waypoints,
• do not block the UI while optimizing tracks.

It should come later this year.

[nvanetten]

Any update on this (allowing user to upload waypoints)?

[vicb]

It's still in the plan but I need to find some time. Probably not before a few months.

[vicb]

You can now load GPX routes and XCTSK files.
More format will come later.