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.

팔로우
11

댓글

  • I can only find segments near my place? It would be usefull If I could find other users routes (if set to public) because they know the area. This same feature was in Endomundo. The explore route option could add all user routes instead of only 3 suggested generated routes

    1
    댓글 작업 고유 링크
  • Enable other activites in "My Stats"

    First of all, Strava, thank you very much for the recent update and improvement for everything that has to do with snow related sports. I find a lot of joy in going through my ski activites on Strava. (Note: When I refer to "ski" or "skiing" I am referring to Cross country/Skate/Nordic ski.)

    Although I love everything you have to offer, I really miss the ability to see my ski activity in the "My Stats"-widget. Over the last 4 days I have been skiing 80km, but I look like the biggest slob on "My Stats", seeing as this only shows swimming, cycling and running. I am fairly certain I am not alone in this, seeing as skiing is a very popular sport in Norway (and the Nordic countries too). Strava would highly likely be a lot more fun for Norwegians and Scandinavians during the winter months if we could compare our stats with what we actually spend our time doing.

    To give my plea some statistical support, I here present some exercise statistics from Norway in 2019, showing the percentage of how many times people above age 16 have conducted a certain activity over the last 12 months:

      0 times 1-2 times 3-10 times 11-24 times 25+ times
    Jogging 61 2 9 6 22
    Nordic ski 63 5 16 9 8
    Swimming 78 2 8 5 7
    Cycling 64 2 9 5 18

    Source: https://www.ssb.no/kultur-og-fritid/statistikker/fritid (translated to English by me)

    As you can see from the table, skiing is by far the most popular activity in Norway. This is especially true this year, as the Corona lockdowns have driven people to the ski tracks in the woods. As a matter of fact, so many people in Oslo took public transport to get to the woods to go skiing, that the Municipality of Oslo now has started bringing snow into the parks in the city... (see photo below):

    Source: https://www.aftenposten.no/oslo/i/nAvr4x/naa-kjoerer-oslo-kommune-snoe-til-byens-parker

    If corona stops us from getting to the ski tracks, we bring the ski tracks to us! :)

    So, dear Strava, you could not go wrong in enabling "Nordic ski" as a "My Stats" activity in the Scandinavian region. It cannot come a minute too soon!

    Best Regards,

    Amalie

    1
    댓글 작업 고유 링크
  • 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.

    1
    댓글 작업 고유 링크
  • Took the ride from a mate, made a route of it, you can see in the picture that it rearranged itself. The dark blue lines is where the route shuld be, the segment is no problem, that dont rearrange itself.

    So, how can I get past this bug or whatever it is? We are trying to arrange club-rides corona-style, but no one is going to get around a track/route if it breaks up or rearrange itself to I-dont-know-what.......

     

    I hope you dont mind my basic skills in english.....not my main language..

    1
    댓글 작업 고유 링크
  • I'm regularly getting routes detail showing in imperial even though my settings are metric.  Hard to use when I can't understand the distances or elevations.

    1
    댓글 작업 고유 링크
  • It would be great if we were able to group our routes into folders. For example, I have 100+ routes of all different types of rides in different regions. It would be great to be able to have a folder of local rides or destination rides or gravel vs. pavement, etc. This would help facilitate my love of route-making by getting rid of the only downside: clicking through different pages to find a route I made a few weeks back, or more. For that matter, it would be great to be able to attach keywords to routes too. Both folders and keywords would make it easier to search through all the routes you've made. 

    1
    댓글 작업 고유 링크
  • Indicate direction of travel for routes on mobile app for club events

    Every time a strava club event is created with a route attached everyone has to be told verbally which way the route goes at the beginning of the ride.  There is no way to determine the direction when the start and stop point is at the same place on the mobile apps.  At least on the web page you can run the cursor through the route and have an indication which way it travels, but not on the mobile app.

    A simple possible solution would be an occasional arrow on the blue highlighting of the route.

    1
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • BUG REPORT: I have just discovered the following Strava Route editor issue. On Tiger Mountain near Seattle there is a number multi-purpose trails - they are one directional for MTB and two-directional for hiking. Even though I am making a running route, Strava route editor still allows me route over a number of trails only in one direction. It is really a pain because I have to switch to the manual mode all the time.

    1
    댓글 작업 고유 링크
  • It would be helpful if Strava allowed adding manual-mode points into existing routes. Often I want to duplicate an existing route and make a few changes, but I can't get the route I want due to Strava not allowing certain connections. I'll switch in and out of manual mode when building a route from scratch, but adding manual-mode points to edit an existing route isn't possible at present.

    1
    댓글 작업 고유 링크
  • I see a similar issue as Tarek. I've updated the Surface Type attribute on OSM for many nearby streets, and on the Strava route builder, they're all still "Not Specified", despite having updated them to Asphalt or Dirt many months ago.

    1
    댓글 작업 고유 링크
  • Tarek, these trails are one-way for MTB only. Is one-way supposed to be applied to pedestrian traffic? Probably not if the trail is multi-use. I've never seen that. Perhaps Strava should never apply one-way restrictions when editing running routes.

    1
    댓글 작업 고유 링크
  • Autogenerate routes including chosen segments

     

    The route generation tool is neat, and the heatmap is great, but I'd love to be able to say "make me a route including segments A, B, and C, starting at X and ending at Y".  

    1
    댓글 작업 고유 링크
  • I either don't know how to or your mapping does not come with mile markers. It would be helpful if there were mile markers on see below:

    The route is confusing without know where each mile is. If this can be remedied easily, please let me know?

    1
    댓글 작업 고유 링크
  • We are a sporty couple. We contact you to suggest a potential evolution of your application. We have an idea to share with you. We use your "Strava" application for every sport and more particularly for mountain biking and trail running. Often, especially in spring, we meet obstacles in the forest such as cut tree trunks. So, the idea would be to be able to integrate into the "Strava" application an option by which it would be possible to notify the paths concerned by an embarrassing event and thus share it with the sportsmen. This is very similar to the capabilities of GPS routing systems like the ability to report problem on Waze.
    I hope to hear from you. Thank you in advance.

    1
    댓글 작업 고유 링크
  • It's high time you implemented "route search" feature.

    Route organisation features have been asked for many times here – for 2 years already, and many times before in the previous support forum. It's embarrassing that such reputable sport-related application cannot deliver such simple and basic feature for so many years.

    1
    댓글 작업 고유 링크
  • Ascent per Distance (e.g. meters climbed per kilometre)

    I would like a feature to be added which gives the ascent per distance as a figure for a route. I think this would be a great way of comparing the average upward gradient of a route.

    Thanks

    1
    댓글 작업 고유 링크
  • Dan Tsai we appreciate you bringing this up. 

    This is a Mapbox SDK issue.  We’re very aware of this occurrence and have flagged it to them as a high priority fix.

    1
    댓글 작업 고유 링크

댓글을 남기려면 로그인하세요.