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.

팔로우
8

댓글

  • Shops, gas stations and other sources of water and food on the map.

    In the hot season it is difficult to take enough water with you for long trip. And on a weekend, finding a working store or gas station is not so easy. It would be great if, when planning a route, shops or gas stations were displayed on the map.

    Personal marks on the map

    And in general, It would also be great if I could mark places on the map (shops, home, work, interesting places and others). And later, when making a route, use these points.

    5
    댓글 작업 고유 링크
  • A small and easy-to-fix, yet annoying bug.

    When a route created not from scratch, but via a "duplicate" functionality ("clone an older route"), or from an activity ("create route" button on activitie's map), the new route inherits creation date from the old route or activity.

    Here's is an example case where it is a problem:
    * I open an activity from last year, because I want to make a similar route. I create a route from it, make adjustments, save. That new route has the same creation date as the one I cloned from (so last year).
    * I open my wahoo element roam app, sort routes by creation date and do not see it on the top (because Strava made it "old")

    It's not easy for me to quickly find the route, I'm not even sure it synced properly to the device. I have to search alphabetically, which is inconvenient and sometimes hard ("how did I named this route?").

    If you simply used current date for each newly created route, this problem would be solved. 2 minutes to make the fix + 2 days for code review, tests and deployment ;-)

    0
    댓글 작업 고유 링크
  • Hi Mateusz Mucha,

    Thank you for bringing this to our attention and sorry to hear the Created on date is incorrect. We were able to reproduce this condition and have made our team aware of this issue.

    Unfortunately, I do not have a resolution timeframe for you, but please know our engineering team will work on a resolution.

    Cheers,
    Skippy
    Strava Support Team

     

    0
    댓글 작업 고유 링크
  • Create route preferring paved roads in mobile app

    Many of us want to create a new route on the fly when out cycling but have a road bike which cannot go on dirt (gravel).  The current mobile app routes through dirt tracks when using the manual Create Route feature so is unusable.

    0
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • The route redirection for running has become very bad recently. I can't incorporate paths I run just about every day because the app thinks they aren't traversable despite being footpaths on main roads (bridges are especially bad for this.)

    This is the deciding feature for my subscription but it has become too frustrating to use. 

    2
    댓글 작업 고유 링크
  • Include single trail difficulty to map

    Please add a map with single trail difficulty (OSM mtb:scale and mtb:scale:uphill). Just today, I had to carry my MTB up an S4 uphill trail (S2 down), because the global heat map suggested routing along that trail would be a good idea. This is not only important information for mountain biking, but for gravel biking as well.

    0
    댓글 작업 고유 링크
  • I have feedback on the #gradientmap statmap (posting here because I couldn't find a more relevant topic to post under). When you use #gradientmap, flat gradients are light yellow, and descents are green. On a small mobile screen, these are almost impossible to see, and only the red climbs are visible. I've attached a screenshot below.

     

    Can you please change the color scale that is used for #gradientmap activities? It's a great idea in theory to show friends how much climbing/descending you did, but right now the usability is sub-par so I end up never using it (and most frequently use #elevationmap instead, which is much more readable).

    0
    댓글 작업 고유 링크
  • As someone planning a long multi day trip (1000+ miles) I would like an easy way of splitting a route into manageable legs. This would allow me to export each leg as a separate gpx file, so I can see how far to the end of the current section.

    0
    댓글 작업 고유 링크
  • I really miss the old feature that strava had where you could find hills in terms of categories (HC, Cat 1,2,3,4). I know most are cat 4 in UK but it was super useful to find climbs. Now I sit there and press refresh about 10x in an area trying to find segments with a gradient. It is PAINFUL. I mean it means I can go explore and try to find them myself but it is a limiting factor being a hill climber and trying to go to different places to train around the UK and finding it really hard to plot routes for my training.

    0
    댓글 작업 고유 링크
  • Improvement to suggested routes feature on mobile app that may solve a problem too. I believe the global heat map in Atlanta, Georgia includes race routes (as, I'm sure everywhere). Parts of these race routes frequently become suggested routes for regular runs. The problem is that the route can actually be quite dangerous with no sidewalks or traffic or freeway on-ramps, etc. because the races were run when streets are closed to traffic. I think the races artificially inflate that route making it appear that runners are always on it. I would like the algorithm for the route suggestion to be improved such that streets or paths with large numbers of runners on a single day on a route (aka a race) are excluded from suggestions. It would also be helpful to be able to toggle "suspected races" on/off the global heat map on the website.

    0
    댓글 작업 고유 링크
  • Hello.  I am having trouble setting up a route on Strava, a route around the outside of three community football (soccer) pitches near me.  I have already run it (well, walked mostly, but I'm a beginner!) and I can see it on my personal heatmap, and I can see from the global heatmap that other people have used it as well.  It seems to work just fine when I create it as a route using the mapping tools, but when I save it, it breaks it up and has segments that are along the road on the other side of some trees, and uses existing segments that are the other side of an impenetrable fence.  

    How can I persuade the mapping tools that I know exactly what I want?

    0
    댓글 작업 고유 링크
  • 1) Please allow for routes to be sorted by date, distance, name, height difference, tags,...

    2) It would be very nice to have the possibility to use an existing route as a template for creating a new route, e.g. shown as a different color on the drawing map. It happens that I made a nice trip however with some parts that could be improved, or I want to use a nice part of an existing route to include in a new route. If I could draw a new route on top of the original one, knowing where to deviate from the original one, that would be very useful. It was a feature in good old GPSies that I frequently used and that I am really missing.

    0
    댓글 작업 고유 링크
  • Patrick D agree that routing in STRAVA has become problematic, despite claimed efforts to improve integration with OSM.  After countless attempts at creating routes for my run club using STRAVA and a lack of pedestrian data in some areas, I took it upon myself to get an OSM account and start running every street/sidewalk/trail in my city in order to provide more comprehensive mapping for STRAVA to use.  It's frustrating that the algorithm still generates routes in seemingly random directions.

    0
    댓글 작업 고유 링크
  • I want to update routes on my wahoo element bolt device. It will allow me to have the same routes on strava and on my wahoo element bolt device. The reason that is important is because of I have rename all my routes on strava in order to find/choose a route more easily. An example of when I needed that was I have rename my route "Ride 3" with "Paris - Provins (200km)" in order to find this route easily on my wahoo element bolt device.

    Exemple :

    • I have a route with a very unfriendly name "Ride 3"
    • After synchronize routes on my wahoo element bolt device, I can find/choose "Ride 3"
    • Now I have many routes. Some of them start from my home, some others start from a place I use to go in holiday, some others from an another place. It is difficult to find the route I want in my routes list
    • I have rename all my routes to be able to choose one easily. The name begin with the start place (name of the city), then something describing the route (like "Follow the sea", "Big climb", ...)
    • After synchronize routes on my wahoo element bolt device, I still have the old names :(
    0
    댓글 작업 고유 링크
  • Hi Strava, my feature request is to indicate in which way the route has bien initially created by the author of the route (especially for cycling). My brother and I have been struggling with this issue more than once and we had to take streets in countersense or find a new route.

    A quick fix would be to add a few little arrows in the route for example.

    Thank you and keep going, Strava rocks !

    0
    댓글 작업 고유 링크
  • Request to filter and create routers by 100% pavement, not 'prefer pavement' which still gives me gravel roads = flat tires.  

    I like to create custom road cycling routes and use the strava suggestion feature when and I always select 'prefer paved surfaces' given I have a road bike, but often the strava recommended routes still include some dirt roads. please make a filter tool to 'use only paved roads 100%' so users who use road bikes don't get caught on gravel or dirt roads. Thanks.

    0
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • I'm not sure if I'm just not seeing it, but for some reason, I can't rename my routes from the edit mode in Routes.  I feel like I could do this in the past but now I can't find where that function is.  Any help or update to this is appreciated!

    0
    댓글 작업 고유 링크
  • Feature Request - Route folders!

    This has probably been requested already but it would be great if there was an option to create folders for your routes so you can organise them how you like.  This would make it much easier to find a route when you need it.  Thanks.

    2
    댓글 작업 고유 링크
  • Has something changed with the basemap?  All of a sudden the routebuilder is useless for building routes on local trails.  Bike-legal trails that I could automatically route along a few weeks ago don't work anymore and I have to use the manual routing feature which is really clunky

    0
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • Varun 🥐 P., I meant to comment about the same issue that Markus K. has. There are trails near my house where only the entrance is unrouteable and I need to use manual routing to "enter". The rest of the trail is routeable, as well as other trailheads.

    One section has a road between trailheads and even the part of the road is unrouteable when I'm trying to connect there. The route builder makes a large detour backtracking on the trail and exiting at a different trailhead. I tried to go a different direction, clicking in a spot on the map 1/2 a mile away and then the road was routeable all of a sudden (but still making the large backtracking detour).

    0
    댓글 작업 고유 링크
  • Varun 🥐 P. Hey Varun, in the past Strava would be able to route me on a path that it can't anymore (in bike mode). It's a footpath through a local neighborhood. Looking at OSM, its "Allowed Access" parameters are:

    All: yes

    Foot: designated

    Motor vehicles: no

    Bicycles: Not specified

    Horses: Not specified

     

    Is this intended behavior? It seems to me like "All" would indicate that bikes are fine to go through.

    I've gone ahead and manually changed the Bicycles setting to "Yes", though.

    0
    댓글 작업 고유 링크
  • 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
    댓글 작업 고유 링크
  • Dan Tsai based on https://wiki.openstreetmap.org/wiki/Key:access#Transport_mode_restrictions, that case does appear to be a bug on our end in that access=yes, motor=no, bicycle=unspecified should allow bike routing still. We will make sure this is fixed with the next basemap build (which will also take in your new tag).

    Andy Wong 🍑📷 it would be most helpful if you had the example trail (as an OSM link if you'd like), or if you'd like to submit the route, filing a support ticket would be helpful and I'll make sure our rep looks out for it and directs it to me.

    Something that may have addressed both cases separately though is last week we've added a small change that attempts to use our own quantitative heat data to infer when routeability restrictions on footpaths from OSM may not line up with athletes' expectations, and still allow them to be made. This is a process we use across the rest of the basemap and routebuilding rules, but were not specifically using in the "cyclists on footpaths" case.

    Thanks for the feedback and this and looking forward to continuing to capture these nuances in improvements to the basemap.

    0
    댓글 작업 고유 링크
  • Exclude Long Term Road Closures

    I want the route planner to exclude long term road closures. It will allow me to actually ride the route I planned and not be surprised and disappointed when I actually encounter the road closure as I'm out riding. The reason that is important is because I wasn't able to ride my planned route and had to improvise how I continued my ride. An example of when I needed that was today, when I planned a route that included a section of road that is closed to vehicles AND bicycles until October 8. I've attached a screencap of that same section from Google Maps.

    0
    댓글 작업 고유 링크
  • Option not to follow bicycle paths

    Varun 🥐 P.

    For few weeks while creating routes I have problem with Strava's routing algorithm. It tries to follow bicycle lanes as much as possible and that is a problem, since OpenStreetMap data in place where I live are not complete. This results in all kind of crazy route suggestions, like one in attached pictures. Is it possible to add option which will give user a choice not to follow bicycle paths when creating route?


    I am OpenStreetMap contributor, but I can't solve mapping mistakes or add missing data for whole country.

     

    0
    댓글 작업 고유 링크
  • My request is to implement the „track up“ function of the map if I record a Route or drive on a saved or imported Route. Actually there‘s only the function „north up“ or a manually adjusted direction.

    2
    댓글 작업 고유 링크
  • Yes! This is the very least functionality that Routes must have. Ideally audio turn-by-turn navigation also, but without auto directional map orientation Routes is useless on a smartphone.

    0
    댓글 작업 고유 링크

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