Become a supporter
I don't use a bike GPS to guide me on the road. I make my own cue-sheets which are much simpler than full the turn by turn print-out which is too verbose to be practical on the go. It is inspired by the traditional cyclo-touring cue-sheets.
It would be so great if CT could help me create a simplified cue-sheet. I love that I am able to use Streetview from within CT so I would use this feature to view signs where important turn-off points can be tricky in order to better prepare my cue-sheet.
Basically, my version of a simplified cue-sheet consists of a list of localities with distance and possibly, elevation gain.
This is how I would envision it:
1) use a special flag (tick box?) on a waypoint to include it in cue-sheet (much like "write a note")
2) generate a comma separated file to be imported in a spreadsheet where I could add comments and modifiy text and possibly make custom calculations (for instance time where I can set pause time for lunch as an example). The localities (or selected waypoints) would be rows. Columns would contain distance to next waypoint, distance from finish and elevation., elevation gain to next waypoint, and empty comment area. Ideally, expected time to next point (using current speed calculation method). If my spreadsheet is properly designed, I can then calculate local time by setting start time and pause durations.
Anyone else interested in such a feature?
Firstly, let me thank you again for a fantastic site. I'm back from a trip to Burgundy and again, CT proved to be very valuable to route me neatly thorugh the beautiful countryside, in very picturesque landscapes.
I have found a case, though, where CT made a choice which proved wrong (in my view).
In order to always improve your routing engine, let me share it with you.
I created a test route here.
The chosen small road goes up a very steep section (10% or even more on about10 meters) where another option would have averaged out the climb and avoided that effort. I reckon the avoidance of D158 Route St Honoré was based on assuming higher traffic. You probably do not have the traffic data for the Nièvre Département, but still, without knowing, I would think that the trade-off traffic vs steep climb would hardly seem worth it for such a small distance. If my assumption is right, the parameter to consider might be how much of the "busier" road is it worth avoiding when steepness (or distance) are concerned. In my humble opinion, I think not much. And that's assuming the road is busy, which it isn't (but that, CT may not be able to know).
Again, this is very minor. I still thought I'd share it because it might give you a real-life test case on a matter which is probably less trivial than it looks. In those situations, nothing replaces real examples.
Just a case where CT's decision making could be improved.
I've used CT extensively this summer during a touring holiday in French and Swiss Jura (nice area to visit BTW), and also during the planning phase. Great help, thanks Richard.
However, I might have missed something but I haven't managed to set a "From" simply being my current position (from the mobile phone, where this is applicable).
Of course destination has to be typed-in, but oddly, I have to also enter text in the "From" text box to get a route computed by CT. It is sometimes difficult to know exactly the name of the place where I am standing.
Have I missed something? Is there a better "workaround" to achieve what I want to do?
PS: maybe it could default, when geolocation is active, to "current position" in the "From" text box, or only demanding a "From" text when geolocation isn't active, assuming then that if the box is left empty the "From" should be set to the current position.
Since some of the very good IGN maps have changed license to Etalab 2.0 would it be eventually possible to choose the "Plan" background maps one day in CT?