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.

Seguir
16

Comentários

195 comentários
  • 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
    Ações de comentário Permalink
  • I'm not sure what's happened with Strava's routing functionality lately, but it's become unusable for creating rides around Atlanta, GA. I start putting points on a map and get an error message that Strava is unable to link them together. Same thing when I try editing an existing route. I'm trying to do anything fancy here—simply creating routes from my house like I've done dozens of times in the past. Bike paths around town that cross streets over/under grade have also become unroutable in many cases—Strava treats the crossings as barriers. You need to use manual mode to make the route cross them, but that's only an option when creating a route from scratch since there's no way to insert manual-mode segments into an existing route. And when it comes to on-grade connections between bike paths and roads, Strava often refuses to recognize them, often creating ridiculous detours using the connections it does understand. I've literally gone into OpenStreetMap and fixed these connections. RideWithGPS has picked them up. Why hasn't Strava?

    1
    Ações de comentário Permalink
  • 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
    Ações de comentário Permalink
  • 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
    Ações de comentário Permalink
  • When switching between "most direct" and "most popular" or between prefer "dirt" and "paved surfaces", I would like to be asked if I want my route to be re-generated.  I have been on several rides where I didn't find my intended route because Strava re-routed parts of my route when I hit those switches.  (It would be even cooler if it did something like Google Maps and showed alternatives: least elevation vs most direct vs most popular.)

    1
    Ações de comentário Permalink
  • I'd like to suggest an improvement. I use Strava almost every day to log my walks. Sometimes, I walk somewhere, get to the train station, hit "pause", get to my next destination, hit "resume", and keep logging my miles. On the map, that distance on the train is not added to my miles, but it is shown as a big straight red line! Since Strava knows that I am on pause, can you just cut those miles out of the activity? Or show them in some other color that indicates non-activity, maybe as grey? The same would hold true for biking, running, etc. 

    I am attaching a screen grab that shows the problem, from a recent marathon walk. I left my home, walked 42 kilometers to the train station in a town called Villeneuve, paused, took the train to a town near my home called Renens, then resumed the app and walked another km. Anyone looking at the map, though, would be extremely puzzled by the straight-line segment from Villeneuve to Renens. I work in IT, and can't imagine it would be difficult to implement code that says, "on pause, switch to grey. on resume, switch to red"

    1
    Ações de comentário Permalink
  • I originally suggested the ability of 'Sorting/Filtering Routes' back in 2016! For some strange reason, it is an idea that Strava has no intention of implementing...!

    1
    Ações de comentário Permalink
  • Hi,

    Garmin Connect supports naming of waypoints which is really useful to show for example coffee stops on a route. In strava we can add waypoints but cannot name them and they don't use the "wpt" tag in the file. Can we please enhance the recently added points of interest feature, allowing them to be referenced as named waypoints in the route file?

    Thanks

    1
    Ações de comentário Permalink
  • Hi, I am testing subscription benefits, mainly i wanted to try route builder.

    Shouldn't route builder snap to heatmap and segments?

    From my testing it behaves like any other free online route builder that uses osm maps and graphhopper route calculation.

    I think in the past there was some presentation of snapping to heatmap.

    Thanks.

    Igor.

    1
    Ações de comentário Permalink
  • I would like to second the other posts asking for exporting of turn cues/turn-by-turn data when exporting routes as a GPX file.  This would allow me to A) stop printing cue sheets (bad for the environment), B) to ride without accessing my phone or requiring the Strava app to be open, C) to stop using third party competitor applications to import GPX files just for the sake of adding turn cues to them before re-exporting and syncing to my device.

    Since the data already seems to exist, this would be a major win for those of us that use devices that can provide turn-by-turn directions.  For me personally, my rides are generally longer than the the battery on my phone, whereas my Coros Apex will last for many days without a charge.

    1
    Ações de comentário Permalink
  • Another vote for turn-by-turn directions. Audio directions would be the most useful starting feature (since we do already have a route map, even if it doesn't give turn-based navigational assistance), and then visual directions could be useful for cycling.

    Why would I ever use Strava to make routes if I can't follow them with Strava? Right now I make and navigate my cycling routes using Komoot, and just use Strava to record because Strava is where my friends are. Would happily ditch Komoot and pay for Strava if navigation was included as a (premium) feature.

    1
    Ações de comentário Permalink
  • Brendan, I've been asking for just this for at least 5 years! I do exactly what you do: create route in Strava, export to Komoot, go ride. It's a real pain and my only real gripe about Strava.

    1
    Ações de comentário Permalink
  • Can't edit/move a waypoint??

    OK, trying to move a waypoint to a different road. Well, not a waypoint per se, it's just a route, there are waypoints but not at this point. Anyway, i click and drag on the route, it updates to what I wanted/did, but then as soon as I release, it jumps back to what it was ... though now with a new waypoint where I grabbed it.

    Any ideas what's going on? This is on Safari/Mac, but is the same through other browsers.

    1
    Ações de comentário Permalink
  • All, there has to have been a route map update recently with a bug.  I try to build routes now and the builder almost 100% refuses to use a road instead of a sidewalk or greenway.  And this is supremely annoying.  I drag the waypoint back to the road and it just snaps right back over.  I make the distance between waypoints shorter, and when passing by an intersection on a road with a greenway the route builder forces the route onto the greenway.  This is with "shortest" enabled or "most popular", both have the issue.  This needs looked into now as this is the primary reason I pay for premium, route building capabilities.

    1
    Ações de comentário Permalink
  • For a while, I haven't been able to reliable add waypoints in an existing route by just clicking and dragging the route to another road.

    This doesn't seem to work in either mobile or the web.

    Am I missing something, is there a magic key combination I have to use when I want to drag an existing route?

    This used to work pretty good.

    My current workaround is to delete the complete route and then carefully add the waypoints one after the others with the knowledge that I won't be able to add more later.

    1
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário Permalink
  • Vaughan Hunt thanks for letting us know. The issue with seeing Routes in your non-preferred units should now be fixed!

    0
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário Permalink

Publicação fechada para comentários.