Additional filter for route search
Quote from Toku75 on 09.06.2020, 17:46The routes database is a really great feature, but I find it hard to define a filter to get only 50 routes in the area of interest. Is it possible to implement a filter that selects all routes, that lead through the rectangle? It‘s important, that the routes don‘t have to be fully inside of the rectangle. With this filter you can define only a small part of the map to be inside of the rectangle without cutting away many interesting and long routes.
As an alternative, a filter that selects all routes with a selectable maximum distance from a special position would give the same benefit. The distance should be measured between the special position to the nearest point of the route.
Best Regards,
Tobias
The routes database is a really great feature, but I find it hard to define a filter to get only 50 routes in the area of interest. Is it possible to implement a filter that selects all routes, that lead through the rectangle? It‘s important, that the routes don‘t have to be fully inside of the rectangle. With this filter you can define only a small part of the map to be inside of the rectangle without cutting away many interesting and long routes.
As an alternative, a filter that selects all routes with a selectable maximum distance from a special position would give the same benefit. The distance should be measured between the special position to the nearest point of the route.
Best Regards,
Tobias
Quote from Guido on 10.06.2020, 04:25Hi Tobias,
I had this with Scenic 1, but as the database of public routes kept growing these requests started to slow down the server, almost to a complete stop on busy days.
Such a request is inherently more resource (cpu and/or memory) consuming. With current way server only needs to check if bounding box of a route fits completely in selected area (in other words if north-west and south-east coordinates of min square map area containing the route, are both inside the selected map area).
For a request such as yours you have to see if each route bounding box overlaps with selected area (I.e. at least one of 4 bounding box corners needs to be inside selected area) and then check for each route where there is an overlap, if it actually passes through selected area (by checking if key coordinates along the route are in selected area) because overlapping bounding box does not necessarily mean that route itself goes through selected area.
Let me give this another try to see if I can make it more efficient. Open to suggestions.
cheers,
guido
Hi Tobias,
I had this with Scenic 1, but as the database of public routes kept growing these requests started to slow down the server, almost to a complete stop on busy days.
Such a request is inherently more resource (cpu and/or memory) consuming. With current way server only needs to check if bounding box of a route fits completely in selected area (in other words if north-west and south-east coordinates of min square map area containing the route, are both inside the selected map area).
For a request such as yours you have to see if each route bounding box overlaps with selected area (I.e. at least one of 4 bounding box corners needs to be inside selected area) and then check for each route where there is an overlap, if it actually passes through selected area (by checking if key coordinates along the route are in selected area) because overlapping bounding box does not necessarily mean that route itself goes through selected area.
Let me give this another try to see if I can make it more efficient. Open to suggestions.
cheers,
guido
Quote from Toku75 on 10.06.2020, 14:24Hi Guido,
Okay. This sounds like a time consuming algorithm. I wouldn‘t have thought, that you have to do it like this.
Would it be more efficient to calculate the minimum distance from some location to the nearest point of each route? I fear this is not very efficient also.
I‘m just looking for something to get a better overview of possible routes without missing just the best one because I have to select a small area. Maybe I‘ll have further ideas in the future.
Best regards,
Tobias
Hi Guido,
Okay. This sounds like a time consuming algorithm. I wouldn‘t have thought, that you have to do it like this.
Would it be more efficient to calculate the minimum distance from some location to the nearest point of each route? I fear this is not very efficient also.
I‘m just looking for something to get a better overview of possible routes without missing just the best one because I have to select a small area. Maybe I‘ll have further ideas in the future.
Best regards,
Tobias
Quote from Aososki on 15.09.2020, 02:18This exact thing. I want to find all the great routes that start within say 15 miles of my house. I’m happy to ride 150 miles or so, but if I make the bounding box big enough to give that length of ride, a) I have to keep adding filters to get it below 50 results so I’m missing out on too many, b) most of them start 50 or more miles away so no use to me.
I want to be able to tap in to routes that intersect near enough for me to join them easily.Thanks @guidomm for a fantastic app! I show it every biker I ride with.
This exact thing. I want to find all the great routes that start within say 15 miles of my house. I’m happy to ride 150 miles or so, but if I make the bounding box big enough to give that length of ride, a) I have to keep adding filters to get it below 50 results so I’m missing out on too many, b) most of them start 50 or more miles away so no use to me.
I want to be able to tap in to routes that intersect near enough for me to join them easily.
Thanks @guidomm for a fantastic app! I show it every biker I ride with.
Quote from Guido on 15.09.2020, 02:25I'm going to change this behaviour a bit for Scenic 3 (next motorcycle season), offering you more ways to find public routes.
I'm going to change this behaviour a bit for Scenic 3 (next motorcycle season), offering you more ways to find public routes.
Quote from 2wheelsyyz on 14.05.2023, 04:47Is this still under consideration? I am at the point where I never use the search feature on this app. Trying to find a 400-500 km route around my house is just impossible. In order to get less than 50 results, I have to make the search square so small that all I get are routes that are less than 80 km long.
Or perhaps I am missing something?
Is this still under consideration? I am at the point where I never use the search feature on this app. Trying to find a 400-500 km route around my house is just impossible. In order to get less than 50 results, I have to make the search square so small that all I get are routes that are less than 80 km long.
Or perhaps I am missing something?
Quote from Guido on 14.05.2023, 06:35It is. Will be part of the big update I’m working on now.
It is. Will be part of the big update I’m working on now.
Quote from Guido on 14.05.2023, 12:22Meanwhile you can also use the filters to reduce the number of search results (Min. avg rating, at least x ratings, distance). That should at least allow you to make the square a bit bigger.
Meanwhile you can also use the filters to reduce the number of search results (Min. avg rating, at least x ratings, distance). That should at least allow you to make the square a bit bigger.
