Arch
Married to Night Train
- Location
- Salford, UK
Setting your own up "in the meanwhile" will be a waste of time, unless you do decide to port the data across to the newer service.
I'm afraid that's where I start to hear 'la la la'....
Bikehike uses google maps API - and could be implemented.
I have an idea of how I personally would do it - but I am not going to dictate or deliberate it with another site owner/developer.
1. Allow users to mark stretches of roads with a rating of say "friendliness", 1-10.
2. Take the average for the section in question to give you an overall figure (and deal with overlapping lines separately etc).
3. Allow when planning a route to "avoid roads rated less than 4" (etc) to automatically go around it, etc etc.
This is a rough idea, and is implementable - lest i'm not going to do it.
That sounds good. The one issue I can foresee is that we all have different ideas of what roads are friendly, and which rideable. For example, when I use Cyclestreets to plan a route to the office, even when I ask for fastest, it takes me along a convoluted route down side streets, when I actually use a straight forward route that happens to be a bit more main road - and I'm perfectly happy with it, although I'm on the cautious side generally. So I might rate my route as 5, when others would think of it as 1 and others as 8. There are some who'd happily ride roads I wouldn't touch with a bargepole.
That's the advantage of Dell's descriptive idea - from a good description, one can assess a road on one's own terms. But that's hard to then shape into a simple rating. Swings and roundabouts, if you'll pardon the minor pun.