Please or Register to create posts and topics.

converting tracks->routes -- poor matching against legit track

Hi Guido,

I've read the documentation I could find, and haven't seen any better hints on how to do this better.

I receive tracks from my friends which I import into Scenic. The tracks are generated by the onthegomaps website, and the blue line matches roads perfectly on Scenic's maps, so it's not a maps not lining up problem. If, for instance, the track is routing through a town with gridlines, Scenic will opt to ignore the track and pick different streets on the grid. If I'm routed onto a frontage road of a major freeway, Scenic will opt to ignore that and put it the route down the freeway.  Can we do something like have Scenic perform the track->route conversion, and when they diverge, be more stringent about adding vias where necessary?

 

Yes. I understand what you mean. I'm working on a bigger update for the fall where I will take this into account. Meanwhile, what you could do is place additional via points yourself during import.

Best regards,

Guido

 

 

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

Yeah, it's just surprisingly bad and manually entering so many Vias is getting annoying. In a day's ride, it takes me 15+ minutes to enter about 30 vias. I was thinking about writing some code to do my own track->garmin route conversion, but it requires full access to an OSM map that might not match the Garmin HERE maps, and it's a LOT of work.

Thanks, glad you'll look into this.