Routes

This is the post for all feedback and feature requests related to Routes.

 

How to format your new idea and/or feedback:

Feedback that is actionable and constructive is most effective. When sharing, please consider the following when framing your thoughts:

  • If you have a new idea, it's helpful for us to understand why that feature is important for you and the value it will bring. For example: I want __. It will allow me to do ___. The reason that is important is because of ___. An example of when I needed that was ___.
  • Specific examples and details that illustrate the problem/confusion you are experiencing. For example: When I do ___, then ___ happens and that is not ok because ___.
  • Screenshots that help visually illustrate the problem. For example: Here is a picture illustrating my point ___ from above. See how ___ is doing ___?
  • An explanation of why this is important. For example: This is important to me because ___.
  • If you propose a solution, an explanation of how that solution would help you and why that is important. For example: I think a ___ would be great because then I could see ___. This is important to me because I have to ___.

 

If someone has already suggested the same idea as you, you can help us quantify the demand for the feature or improvement by upvoting the original comment. To upvote, click the up arrow on the right-hand side of the comment. 

 

Do you need technical assistance or wish to report a bug?

Keep in mind that this space is reserved for feedback. It is not the optimal place to solicit technical assistance or report bugs. To receive assistance with, or to ask a question about our product, please first search our Help Center for the related article. If you do not find what you are looking for, you can submit a ticket with our support team by following the instructions here. To report a bug, first check our Known Issue section. If you do not see the bug you’re experiencing, you can submit this to our team by following the instructions here.

Follow
9

Comments

134 comments
  • I can confirm the issue with the manually edited route segments randomly snapping to nearby roads or trails which makes the route nearly unusable. I experienced that when I wanted to plan a route through some relatively new trails that were visible on the map but Strava refused to route over those trails. I used the manual mode to draw a route over those trails, but the route got broken as described above in the comment by Jake Logan

    1
    Comment actions Permalink
  • For those of us that use the app and no Garmin is there a way to get auditory directions? Some are visually impaired, coupled with being on a bike, running, traffic would be very helpful to have auditory directions. I have a very difficult time seeing the app map in full sun, trying to navigate all while maintaining a pace.

    1
    Comment actions Permalink
  • Just tried to build a route using the android app. I'm missing a couple of basic functionalities:

    1) When I select "draw route" and search for a starting location, no flag is added. The level of zoom is insufficient for me to know where it is exactly so please add this flag.

    2) The (android) app does not seem to allow to add a start and end point. Currently I'm only able to select a start point and then either draw my own or select one of the suggested routes. Please add the possibility to enter the end point.

    3) Please add the possibility to search for a route point and add this point to the route. This is possible in the browser version and would be very useable in the (android) app as well.

    I believe the first suggestion can be improved for the browser version as well. The other two are basically a desire to add features to the app that already exist in the browser version. Hope to see some improvements in the near future!

    1
    Comment actions Permalink
  • Two suggestions:

    1. As others have said, it would be helpful to be able to search and filter routes by surface type. I'm a road cyclist, but when up in wine country of Central California this weekend, a route I found in Strava sent me on a dirt/gravel road. The only way I found to avoid this in advance is to go into the route details and see the percentages of different surfaces. But why not allow the user to use that as part of the search criteria?!? Also, it would be helpful to present the route with color-coding of the route line indicating the surface type for each section of roadway.
    2. When following a route, why does the app not provide turn-by-turn directions (ideally with audio cues)? Failing this, it would be helpful to at least center the rider's location on the map. Otherwise, it's far too easy to miss a turn, resulting in a situation that is inconvenient at best and potentially unsafe at worst.
    1
    Comment actions Permalink
  • I would find it very useful to be able to allocate my routes to different groups - e.g. gravel; long rides; hilly rides; etc. This in addition to the ability to search my routes, which has already been suggested by several members in the forum. 

    Thanks,

    Adrian 

    1
    Comment actions Permalink
  • I would like to see the route builder to actually work for trails. Every location where I try to create a loop the software will not snap to the off road trail instead it jumps to the nearest road. The dotted line and heat map shows the trail yet your software ignores it. I wasted my money paying for the subscription.

    1
    Comment actions Permalink
  • Use personal performance history and elevation data to more accurately create new routes

    I like the fact that My Routes uses one's last four weeks average speed when estimating times when creating new routes. However, it seems to apply the same average speed whether one is climbing, descending, or on a flat section. Could the algorithm take account of the percentage slope change to adjust timing based on the user's four week history of actual average speeds for different percentage slopes? The algorithm could have ranges of slope percentages to group the user's data, such as  0 to 1%, 1,1 to 2%, 2.1 to 3%, as well as negative slopes -0.1 to -1%, -1.1 to-2% etc.

    1
    Comment actions Permalink
  • Hi Markus K.

    We are constantly making changes to the basemap, and recently we've integrated more information from OpenStreetMap about designated footways to improve our cycling Routes. https://wiki.openstreetmap.org/wiki/Tag:highway%3Dfootway is a good summary of how OSM intends for the tags on footways to be used, but we do also utilize our own data to attempt to determine what is accessible to bikes.

    If there are trails that you think are improperly tagged in OSM and causing route building to not work as you believe it should, we'd welcome improvements. Here is a tutorial on how to do so - https://support.strava.com/hc/en-us/articles/216917827-Strava-s-Maps-How-to-send-Feedback.

    Likewise, if you have examples where you think Strava is interpreting OSM wrongly, please submit a support ticket with the details and we'll look at making improvements to our routing logic

    1
    Comment actions Permalink
  • Enhancement idea: use standard speed, distance, time calculation to work out estimated moving time for route planning.
    Currently strava just uses your average speed from previous rides and doesn’t take elevation or terrain into consideration.
    Strava has average power figures which could be used to work out rate of accent for climbs or average speed on different types of road surface.
    Average speed on previous rides is just a lazy way of working out estimated moving time. When I’m planning routes while I’m away from home the terrain is not the same so my average speed won’t be the same.
    Please use the data you have to make accurate estimated travel time calculations so people aren’t caught out while exploring new places.

    1
    Comment actions Permalink
  • I'm creating a route and trying to follow, or avoid, my personal heatmap. The default colour for both is red so it can be difficult to make out one from the other. If the default colour for personal and new route was different or either could be user selected, that would be helpful.

    1
    Comment actions Permalink
  • We need more categories than "Ride" for cycling.  I looked at route builder for an area I will be traveling to soon and selected a distance for a road ride that would give me an hour or so of ride time, but Strava estimates it will take me twice as long because my recent outdoor rides have all been MTB or fat bike rides.  Off road rides should not be counted to estimate on road route times.

    You have separate categories for run, walk, hike, and snowshoe but our choices for cycling are ride, e-bike, or indoor trainer...  We need at minimum road bike and mountain bike categories to make your route time estimates more realistic.

    1
    Comment actions Permalink
  • Agreed; another side effect of the lowered opacity is that it's hard to tell how popular a route is; everything feels like the same shade and darkness of blue. Less-popular routes are almost invisible (as Aleksandar pointed out), and more popular routes are just blue (and I can't tell which ones are just "moderately popular" vs "extremely popular"). In other words, more gradations in the heatmap would be helpful in route planning.

    1
    Comment actions Permalink
  • Hi Aleksandar K. thanks for pointing that out. We noticed the change in opacity as well this weekend and realized we had introduced a regression when rolling out Points-of-Interests on the map. That issue should now be fixed and the opacity should be back to what it was before. 

    1
    Comment actions Permalink
  • Steve: I'd recommend checking out https://findthatride.com which allows you to view all of your routes (and rides) on a map to do visual searching.  I find this way easier than searching through my routes on Strava, which I agree can be frustrating.

    1
    Comment actions Permalink
  • Does anyone know if there is a way of showing all my previous 'Activities' on the live map screen? Similar to 'Routes' but instead it displays my existing rides. I want to do this because I'd like to explore areas I've never been to before. 

    Maybe if 'Routes' had the freedom to highlight blocked-out sections of the map (rather than stick to the existing roads) I could do this before I set out for a ride, then see what areas I need to cover?

     

    0
    Comment actions Permalink
  • Tony Iorfino Thanks for this tip.

    Yes I saw this but I'm looking for something that displays it whilst on a live map screen (Similar to what 'Routes' does). 

    Whilst on the subject I use a 3rd party website to display previous routes which I find more clearer. Check it out, I think it's great: http://www.jonathanokeeffe.com/strava/map.php

    Tim

    0
    Comment actions Permalink
  • As Enduro MTB rider, I would filter route by IMBA MTB average/max level to choose the good run depending of my daily goal.

    Those informations are include in MapBox, and update by OSM contributors like me.

    0
    Comment actions Permalink
  • Sven, thank you for the response. This is very helpful. How about the first item on the list? Is there a way to load a route when cycling and be able to see the kilometers remaining and the elevation profile?

    0
    Comment actions Permalink
  • Is it correct that only the last year or so of data is synced into the personal heatmaps feature of the route builder?

    0
    Comment actions Permalink
  • Is there no way to navigate to the starting point using whatever phone navigation's available?

    It seems it should be quite easy to get the starting point location and open it for car navigation?

    0
    Comment actions Permalink
  • Tijl T. your entire athletic history of public activities should show on the Personal Heatmap layer on the Web Routebuilder. If this not the case, please submit a support ticket!

    0
    Comment actions Permalink
  • Feature request: exclude or grey out route section where activity was paused

    Sometimes we start a ride (can apply to other activities too) and continue to point A, have the ride paused, jump on a train to point B and continue the ride from there. Sometimes we might have more than 1 train ride during the workout. However currently Strava algorithm connects all the GPS point even when the ride was on pause between point A and B. Show below in that super straight line. 

    That straight line is a train ride in which recording was paused. I recorded my ride using a head unit (Wahoo in this case) and the route is shows correctly in the head unit's app as shown below. And is then exported to Strava.

    The exact same has happened to my friend. Even though he uses Strava itself to record the ride on his mobile phone. So the same algorithm applies regardless of the source.

    It would be great and useful if Strava can either grey out the section that was not recorded (no data collected between points A and B), or exclude from the map similar to the output shown in the head unit route. Having that section shown in the route map causes confusion for follower to see the actual  distance traveled in a given ride.

    0
    Comment actions Permalink
  • yoku ha - subscribers are currently able to customize the coloring of their activity maps (at least those shown in the main feed and on the activity screen) by using hashtags! For more information see https://support.strava.com/hc/en-us/articles/360049869011-Custom-Activity-Lines-statmaps.

    0
    Comment actions Permalink
  • Request - I think it’s very important to be able to avoid certain types of road. Eg - Bypass, A roads (which here in the uk can be very busy and dangerous)
    Thanks

    0
    Comment actions Permalink
  • This is feedback related to Heatmaps. (This is the closest post I could find to post this feedback in, since there is no post for Heatmaps)

    Please make the Heatmaps UI more mobile friendly (or even better, embed it into the mobile app!). Right now the sidebar and header takes up 2/3 of the screen real estate which makes it unusable on mobile, especially compared to the previous version of heatmaps (see example below).

    Secondly, it would be great if there were a way to share a heatmap with others. In the previous version of heatmaps, I could generate a heat map and the resulting URL would work for anyone I shared it with. I have other friends with similar "Run Every Road" hobbies, and we like to share heatmaps with one another to encourage each other.

    0
    Comment actions Permalink
  • Please add the ability to 'explore routes' on web. It is difficult to explore routes on Strava mobile because of hardware constraints, not sure why this isn't included on the web.

    0
    Comment actions Permalink
  • Feature Creation:

    If you were to add a tire dimension to the bikes that we ride, it would make route selection easier. Using Python you can science that data, the wheel width, to find out what tires are best for what trails. This way as a cyclist who rides road, gravel, and MTB, or any mix of that, you can choose your routes accordingly. This data can be backwards functional by adding this data to the bike, applying it to all the old rides, and then bringing it forward to describe the new trails. From that point, you can also tell which of my bikes is on, rather than having to select it every time. 

    You can also use this to show the difference between downhill MTB and XC or Enduro. Which allows you to tune the fitness metrics more accurately. 

    You can also use this data to look for aberrations of routes for construction and the like. Things like construction that shows up, and how people get around that. The route suggestions can auto update using this sort of data science and machine learning. The MTB DH vs XC/Enduro will also help with the backcountry ski/snowboard vs lift access ski and snowboard. We want to know how long it takes to ascend, and unless you make a segment you can't do that. It's just a change of how you use the data.

    On road bikes or other long rides, you can also find common stopping places with the data provided. These tend to be feeding stations, which are necessary when you're out for over three or four hours. You could also call common start and finish points for certain routes from this data as well. 

    All of this will make the overall experience better for all cyclists, as well as backcountry ski/snowboarders. Especially if you made some of it a paid feature. The best part of it is when you travel to new places, your route finding gets a lot better. Much less stressful and no more hoping you're choosing the right kinds of routes for the bike you brought with you. 

    I'd love to code this. If you gave me access to my own data, I could build POC with it. Especially if my girlfriend could get access to hers, since she has ridden a lot more strava miles than I have, on a greater number of bikes and in more locations. 

    This could be a huge paid feature and earn a lot of subscriptions for the company. And if you let me do it for a stipend, it doesn't move people on your dev team to a new project. They would just have to implement it system wide.

    0
    Comment actions Permalink
  • Vaughan Hunt thanks for letting us know. The issue with seeing Routes in your non-preferred units should now be fixed!

    0
    Comment actions Permalink
  • Hey Strava, this is an easy one!

    Today a friend shared a route he developed in Route Builder. When I view the route on my laptop, I would like to select Global Heatmap as the background (in addition to Standard and Satellite). This will help me evaluate the route.

    0
    Comment actions Permalink
  • An improved estimated moving time for routes would be nice. As is, with both mountain and road bike ride speeds counted exactly the same, the timing is completely inaccurate. Factoring in elevation is critical as well. The current algorithm will say a 10 mile flat ride will take the same time as a 10 mile HC climb. While it is supposed to be just an estimate, a bit more detail and accuracy than this would be good.

    0
    Comment actions Permalink

Please sign in to leave a comment.