No, CT does not record rides 

However, there is a 'Travel Tiles' option if using the app. 

More info in Helpcycle.travel/help/travel_tiles

Scorbutico's request is essentially the same as that made on 24th Dec 25 by Alexander Turner ("Feature request: Convert travel tiles data into ride statistics".)

Given storing ride stats is a common/popular feature on other platforms, I suspect that building up a record of the rides would be popular with quite a lot of CT users. If one barrier to doing this is it would incur added costs for additional server capacity, might it be done as a feature that is only available to supporters? I'm mindful that we users need to make it worthwhile for RF to continue to provide this great platform, which currently is almost entirely free of charge at point of use, but not free of underlying costs.

In all fairness, I'd imagine there is a significant difference between tagging a square on a map to say 'I woz ´ere' and tagging the speed, direction and rate of elevation. 

I'd expect demands along the line of X platform does this, why doesn't CT? and foresee a glut of follow on requests for data analysis and compatibility with various other devices (watches, cadence sensors etc.) with such a feature.  

While I'm pretty sure that cost would be a factor, I'm just as confident that labour would be too. These other platforms generally have teams of people.  Then there's the deep pockets. Komoot was recently bought for Euro 300 million, Strava is worth $2.2 billion. RWGPS is more opaque but received outside investment of $3 million a couple of years ago. (source: a quick Google). There's not just the labour in setting everything up, but also the time commitments involved in maintaining it. 

To be quite honest, what one person has done here is pretty darn impressive! An excellent route planner - at the end of the day that is the key - and an app that is incredibly useful for the casual bike traveller. And pretty much all the features are free! 

Speaking for myself, I wouldn't require such a feature*. Anything that moves CT towards a more performance/sport outlook would be retrograde in my humble. It will, by necessity, complicate the app. Perhaps, a separate 'CycleTravelSports' app could be spun off :-)  

The more focused we become, the more specific tools we need. Away on the bike, camping, a folding knife does the job. In my kitchen at home I have a set of knives, each one for a different job. My camping knife doesn't cut it. :-) 

I'd rather see any excess time and energy ( :-)  )  go into the development and promotion of recreational and utility cycling along with travelogues and possibly a community. I recall how reading about journeys long and short were the key part in my education about travel on a bike. There is no shortage of offerings out there to track performance, precious few that are accessible, safe & educational. In other words, I'm in full agreement with the About us page. 

* For the sake of transparency, I should note that I do record many of my bike journeys, but on a dedicated gps unit. I'm of the opinion that while a phone can navigate (and track) it's at too high a risk and cost. 

Hobbes: 

I sympathise with much of what you say re the benefits of focus and simplicity; and of course what RF does as a one-person effort is remarkable. I was (and am) simply noting there are 2 user requests that are essentially the same, who do seemingly wish to be able to record something more when the route is ridden (eg perhaps simply the date and overall elapsed time start to end for the planned route, without any other bells and whistles; the planned route distance and elevation is already held in CT.). I am adding the thought that not everything has to be free. 

The question of whether RF wishes (or is able to) to develop his product in this direction is for him to decide, of course. 

I am at the very simple end of the request: record a ride and have the map availble should I decide to try a new route whilst out and about.  Most of my riding takes place from home, and I find it useful to keep a track of routes and, out of interest, my mileage.  I was not asking for a new feature, just making sure that I hadn't missed something.  I understand the points that HobbesOnTour makes, and at the end of the day it is up to the developer do decide on whether new features are to be added.  

It was prompted because the Komoot app on my phone has recently become unreliable and they are unable to resolve the problem, but I shall persevere with that for now, and use CT on my planned spring Edinburgh to home (York) ride. 

Scorbutico, if I'm understanding correctly from this ....

have the map availble should I decide to try a new route whilst out and about.

I think there is a website feature that may help.

Assuming you build up a library of routes around your home, if you save them all in one folder you can see all those routes displayed simultaneously on a map. 

If you're out for the day and decide that you'd like to go a bit further or change direction you can open the website on your phone, see your saved routes, choose one and either edit it on the spot to take your current position into account or open that route on the app. 

Back in the day I'd plan several different versions of a route from A to B, set off on one, invariably wander off course then when time was getting critical have a look, find the closest version to my current location and follow that. It's very liberating to wander around while having a 'safety net'. 

Of course, you can also use the app to create a completely new route. 

Judicious use of the marker feature can also be helpful as a source of inspiration for on-the-go planning on the app. 

Just remember that online access is required for any planning or editing (or access to the website). Routes previously downloaded to the app (and the underlying maps) won't need online access to select & navigate.

As for recording, as mentioned earlier, I use a gps unit that is linked to both RWGPS & Strava. My Strava account is used for touring - it is a simple process to add any photos taken on the journey to give a great reminder of the day. My RWGPS was used simply as a tracker for distance so I could keep an eye on a few maintenance things. It would be possible to record any rides on either of those on your phone - but of course, this may add to battery usage. 

If not familiar with these apps, I'd suggest the complexity of them, the various payment options, the differences between website & app and the way that they frequently get changed around as evidence for my stance mentioned above. 

I am not a fan of Komoot.

Other alternatives are fitness trackers available as a phone app or on a simple smartwatch. They'll record all the details (start, end, speed, distance, elevation etc.) of a bike ride with minimum usage of the phone battery (and none if on a watch!) Google Fit will track your mileage as you navigate with the CT app.

This is an interesting thread – thank you for all this!

Server resource is not a huge issue in this case – as Hobbes alludes, it’s more a case of developer resource (i.e. me).

I don’t think c.t will ever aspire to a fraction of what the big ride-tracking platforms do, but I’m not against adding some minimal recording functionality. I don’t know whether that would be just offering the ability to download a GPX of today’s ride, or automatically storing rides ridden with the ability to view them on the map, or whatever.

Recording rides is not something I ever do personally, so I’m slightly in the dark here. So if you could articulate what the absolute bare bones might be, I’m all ears.

Richard

2 general thoughts:

1)  Every potential development has an opportunity cost - the things that you would otherwise do to CT instead. So when we users lob our suggestions in your direction, it could well be we actually would give higher priority to some other thing that you would otherwise do!

2) Arising from above: the participation in these threads is very limited. I suspect many CT users never even look at the forum. Your assessment of the scale of significance of the ideas/suggestions must be basically your intuition guided by your appreciation of what the scale of the development would be (and whether it piques your interest, too). Would it perhaps be worth giving thought (and some development time?) to how you could do some more wide-reaching engagement with CT users to better assess appetite for potential developments, and to rank them? Say, some way for you to broadcast to all (or a sample of ) users  a "RFQ" regarding a possible development (perhaps a discreet temp pop-up in the map offering a link to a survey?) ?

(And I do thing Hobbes is right to highlight upthread a concern if added bells and whistles get in the way of the focus and ease of use of CT, which is a great asset.)

Recording rides is not something I ever do personally, so I’m slightly in the dark here. So if you could articulate what the absolute bare bones might be, I’m all ears.

You asked :-)

Bare bones for me would be a record of the gpx, perhaps automatically transferred to a 'completed rides' folder within the app (which would then, by default, be available on the website (My Journeys)). I know nothing about what data is recorded in a gpx file but I'd imagine there'd be a time stamp. Perhaps that time and date can actually be the name which would cover the basic desire for a record of each ride with useful data. Since they are all in a folder, we can see them all displayed on a map (on the website). My (very basic) understanding is that recorded rides are often designated as FIT files. That may have an impact? 

Since we can take photos within the app (haven't tried this) an attractive feature, if possible, would be to 'pull' any photos from the phone camera taken on that ride and 'associate' them with the gpx file. 

Would it be possible to create a default travelogue with the gpx on a map (a saved route?) and these photos automatically added? Users could then go back to add comments, delete photos etc. The bare bones of a travelogue 'presented' automatically. I'd see a lot of potential for those going on a cycling holiday! It should be private until the account holder changes it to public. 

If you want ideas on travelogues I have a few ideas somewhere :-)

However, I'd have no doubt that there would be an overwhelming demand for more. Stats such as daily/weekly/monthly/annual distance, elevation gain. Temperature records. Integration with heart rate monitors, cadence sensors and all that jazz. Stats from that data. The ability to record separately for different bikes. Requests to merge separate rides. 

I'd also anticipate a more vociferous reaction to any bugs or glitches that interrupt recording. Then there'd be a steady stream of more personalised requests such as the ability to record offline and upload when back online. 

Are there any legal implications in the difference between hosting planned & completed rides?  

I wonder if the user base has changed since the introduction of the apps? And if so, what impact that has on user expectations?

I'd have 2 concerns about the future development of CT.

The first would be a drift away from the intuitive and user friendly operation. It's second to none and while no online planner is 100% accurate CT has consistently kicked the big boys' asses. (I'd like to charge Komoot for attempted murder :-) )

I'd point out that when someone requests an option to avoid hills as just one example, they are politely told that there are limits on what CT can take into account.  Suggestions for alternative platforms are made. If going down the recording route, I'd suggest a similar approach.  

My second would be about the toll on you. Perhaps my own history plays a part, but anyone in a customer facing role these days has to deal with a lot. Constant, escalating demands, unfounded criticism,  minimum gratitude. That kind of stuff can be body and soul destroying. Especially if on a public forum.  I take my hat off to you and I'll take the opportunity to say Thank you for all that you've done and are doing. 

So many great points from the replies that it is impossible to reflect on all of them.  Having used the app for real for the first time today for navigating a route it did not go entirely to plan, so I have some learning to do on it before I decide if it will be my choice of app for my planned Edinburgh to Stillington, York ride at the end of March.  So, with only one, not entirely successful, route under my belt, then the following has to be read with that in mind.

As for route recording, my wish list would be:

The map live on the screen whilst I'm out and about (e.g. OS maps does a great job of recording a ride but allows the screen to shut down on the display time out, and so is not what I am personally looking for).

'Live' data of distance covered, average speed when in motion, and elevation.  Finally,  that data saved at the end of the ride.  

I think a lot of the data that HobbesonTour refers to would only be relevant to sports riders and I am sure that they are already well served and would not be looking at CT as an option.  Users can request but at the end of the day it is the developer who decides, and if someone decides that the app no longer meets their needs then they can choose one of the many other options out there.  

The sign of a successful business is the users wanting more. Hence a one man show becomes a room full of salary paid scribblers.