Importing form kurviger.de - Tracks vs Routes
Quote from TotalEgal on 04.07.2023, 01:23Hi,
I have read the previous posts and I have read the FAQ entry regarding the difference between tracks and routes. As far as I have understood I will have to manually adjust the import to use the full functionality of Scenic. Am I right?
Are there any plans that Scenic will do these adjustments automatically by itself. It is already able to import the track itself. Why not adding the necessary data to match the routing with the track?
Hi,
I have read the previous posts and I have read the FAQ entry regarding the difference between tracks and routes. As far as I have understood I will have to manually adjust the import to use the full functionality of Scenic. Am I right?
Are there any plans that Scenic will do these adjustments automatically by itself. It is already able to import the track itself. Why not adding the necessary data to match the routing with the track?
Quote from Guido on 04.07.2023, 04:45I don’t rule this out. But it would be dependent on the HERE framework supporting such a feature. If not, it will always be a time and resource consuming process:
1. Add a via point, delete a via point or change a via point location
2. calculate route with new via points
3. see if match with track is better
4. if not, revert and try something else, if yes, move to next via point.
repeat this until you get the best match with the track
As you might see, there can be thousands of combinations / via point collections, meaning you could need thousands of route calculations to iterate over.
What makes this even more difficult is that the ‘best’ match isn’t necessarily a 100% (this can happen if there are differences on map data between source and Scenic, e.g. source thinks a stretch allows two way traffic, while scenic thinks it’s one way). In that case it will take more iterations as you never reach that 100%, so you don’t know when you’re finished really.
Have you read this blog article? https://scenic.app/turn-turn-instructions-gpx-tracks-everything-never-wanted-know/
In the ‘Side Note’ paragraph I mention another method. This is the method I’m referring to above that would need to be supported by the HERE framework. They are actually working on such a feature at the moment, but if and when it will be ready and good enough, I wouldn’t dare to say.
Cheers,
Guido
I don’t rule this out. But it would be dependent on the HERE framework supporting such a feature. If not, it will always be a time and resource consuming process:
1. Add a via point, delete a via point or change a via point location
2. calculate route with new via points
3. see if match with track is better
4. if not, revert and try something else, if yes, move to next via point.
repeat this until you get the best match with the track
As you might see, there can be thousands of combinations / via point collections, meaning you could need thousands of route calculations to iterate over.
What makes this even more difficult is that the ‘best’ match isn’t necessarily a 100% (this can happen if there are differences on map data between source and Scenic, e.g. source thinks a stretch allows two way traffic, while scenic thinks it’s one way). In that case it will take more iterations as you never reach that 100%, so you don’t know when you’re finished really.
Have you read this blog article? https://scenic.app/turn-turn-instructions-gpx-tracks-everything-never-wanted-know/
In the ‘Side Note’ paragraph I mention another method. This is the method I’m referring to above that would need to be supported by the HERE framework. They are actually working on such a feature at the moment, but if and when it will be ready and good enough, I wouldn’t dare to say.
Cheers,
Guido
