Become a supporter
(RFE stands for Request For Enhancement and is what we used to ask our customers to submit when they had ideas about new features they wanted added to our software, back in the days when I worked as technical software sales support.)
I think that the ability to somehow save points that I find "interesting" for one reason or other would be a great enhancement to CT. The shortlist is good but right now it only lets me save points that "you" (Richard & C:o) know about and only lodging places. I'd like the ability to save my own interesting sights, eating places, friends' addresses...The list goes on. Primarily, I'd only expect mine to be visible to me. Being able to share them with others would be nice but could lead down the slippery slope of requiring "you" to validate them and that would mean more administrative work for you, so it's best left as "out of scope" (as we used to say when customers wanted features that we felt didn't fit with the intended use of the product).
It needn't be fancy. A small flag symbol, pair of long/lat coordinates and a name, would be enough for me. Some sort of "category" tag (lodging, food, whatever, possibly just strings that I choose myself) counts as a "nice to have" function and in a pinch I could just prefix the names with something like "Eat_", "Sleep_", "See_" so this has much lower priority. And unlike the lists of campgrounds and hotels "you" maintain (and which must contain thousands and thousands of entries) "my" list would be orders of magnitude smaller so I don't think it would put much load on your servers.
So, I'm planning for a tour next year, about three weeks (~1500 km) in the Netherlands, Germany and a bit of Belgium. And right now I'm trying to figure the best way to use c.t for my planning and navigation. I've noticed that if I plan a multi-day trip in the web version of c.t, the black "overnight stay" markers don't make it to the Android app, so I'm led to believe that the recommended way is to let the web service split the route into separate days and then open them on the phone, on a day-by-day basis. Is this a correct interpretation of the designer's intentions?
And if I change my mind about where to go or when to sleep, will I be better off adjusting the "master route" and splitting it again?
What if, in some area where campgrounds (or wild camping spots) are plentiful and rarely far apart, I just follow the route outline without any pre-determined places to stay overnight, will the c.t phone app be able to recognize next day where I am and understand that I want to resume the tour from this location? Even if I've, say, made a multiday stopover with sightseeing at some nice place along the way?
Made in the Cotswolds. Published by Éditions Système D Ltd.
Log in with your cycle.travel account:
| Password |
Or simply use your account on:
