Calimoto - not getting on with it…help!
Discussion
As a new user, I’ll admit this is probably my fault, but looking for some help.
It also may just be this ‘bends are better’ mentality that the app seems to have.
Example of my ride yesterday - 90 miles, takes around 1.5hrs on my usual fast ish A roads, nice sweeping roads.
I picked ‘winding’ on the app.
This this took me over broken B roads, through farms and small villages… even took me off the nice road, turn left, right,right,left… ie… took me off the good road just to go over 3 bends on a s
t B road for less than a mile!
So that is not my style of riding… I don’t want changing roads, surfaces, zig zagging etc etc…Nice fast sweepers and making progress is more for me.
The question is… how do I set that up in the App?
Do I just pick ‘fastest’?
Do I need to spend the time in the web version and update each section?
The route yesterday ended up being over 100 miles and nearly 3 hours… and the kicker is… in torrential rain
A bit of a pain… but I decided to stick with it to see how to work it all out..
Help please!
It also may just be this ‘bends are better’ mentality that the app seems to have.
Example of my ride yesterday - 90 miles, takes around 1.5hrs on my usual fast ish A roads, nice sweeping roads.
I picked ‘winding’ on the app.
This this took me over broken B roads, through farms and small villages… even took me off the nice road, turn left, right,right,left… ie… took me off the good road just to go over 3 bends on a s
t B road for less than a mile!So that is not my style of riding… I don’t want changing roads, surfaces, zig zagging etc etc…Nice fast sweepers and making progress is more for me.
The question is… how do I set that up in the App?
Do I just pick ‘fastest’?
Do I need to spend the time in the web version and update each section?
The route yesterday ended up being over 100 miles and nearly 3 hours… and the kicker is… in torrential rain
A bit of a pain… but I decided to stick with it to see how to work it all out..
Help please!
KTMsm said:
It's not intelligent - none of them are
However I love it because it's very easy to look at the route and add "via point" to change the route to suit you - BEFORE you press navigate
How does that work for roads/routes you’ve never been on BEFORE??However I love it because it's very easy to look at the route and add "via point" to change the route to suit you - BEFORE you press navigate
Ok so basically go over the whole route on roads I’ve never been on to try and figure out if they’ll be s
te and adjust the planning from there…?? BEFORE I leave?? That’s going to be fun on my 1100 mile trip down to Italy next week…
The via point thing is actually another annoying bit about it for me.
And again, it’ll be my fault - I don’t actually have my phone out when riding to see the route, it’s in my pocket and I listen to the directions.
That brings up the issue when I put a via point in and don’t hit it exactly - think ‘main street’ and I ride down ‘high street’ same place, just a few meters apart maybe because of road works..
Calimoto then spends the next several miles doing it’s best to turn you around to make sure you go to the exact place it wants….turn around, u turn, recalculating… and on and on…
All the time not figuring out that I’m well on the way to the next point/destination..and turning my music down!
So that means I need to stop the bike, get my phone out and press buttons to move it on to the next step.
It was billed to me as the best nav for motorcycles, but I just don’t see it at the moment..
Uses a lot of data as well compared to google maps….forgot to mention that in my first moan..
I think I might just go back to written list on tank instructions from yesteryear…
Anyway, must be a cloud for me to go and shout at…..
The only time I use it is for roads I haven't ridden before
It's usually pretty obvious, it tries to pick twisty roads and you can quickly zoom in and see if it's a housing estate a B road or an A road
If I was doing 1100 miles I would use Waze or plan it properly
It's hardly it's fault if you decide not to have it on view so you can't see what it's trying to do - I use an ultimate add-ons case
If you can find a system that can intelligently pick the best motorcycling roads let us all know because I'm unaware of one
It's usually pretty obvious, it tries to pick twisty roads and you can quickly zoom in and see if it's a housing estate a B road or an A road
If I was doing 1100 miles I would use Waze or plan it properly
It's hardly it's fault if you decide not to have it on view so you can't see what it's trying to do - I use an ultimate add-ons case
If you can find a system that can intelligently pick the best motorcycling roads let us all know because I'm unaware of one
Found exactly the same thing. We did Tonbridge to Poole via the calimoto route .. kept Criss /crossing the A and B roads and I think after we'd done about 80 miles in something like 2.5 hours, I called time on it and went back to Google maps. We were going down single-track, farm lanes, you name it. I assume their algorithm can't handle a "I'd like twisties, but they have to have a white line down the middle" option....
I'll try the other other all mentioned, but I suspect Google maps with "avoid motorways" is the easiest option...with possibly some manual rerouting for "definitely boring"
A roads like the A30"
I'll try the other other all mentioned, but I suspect Google maps with "avoid motorways" is the easiest option...with possibly some manual rerouting for "definitely boring"
A roads like the A30"
Hated it.
Much prefer the Tom Tom Go App (it's also a lot cheaper).
Either way though you will still end up on the odd stupid detour. I plan any ride more than about 60 miles a few days before so I can work out the best route that is both fun but also doesn't take the piss.
If I purely want to get there quickly then I'll just use Google Maps or Tom Tom avoiding nothing.
Much prefer the Tom Tom Go App (it's also a lot cheaper).
Either way though you will still end up on the odd stupid detour. I plan any ride more than about 60 miles a few days before so I can work out the best route that is both fun but also doesn't take the piss.
If I purely want to get there quickly then I'll just use Google Maps or Tom Tom avoiding nothing.
I've been using Calimoto all year and there have been a few updates along the way, it is getting better but it still needs a few tweaks.
Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
Edited by Freakuk on Monday 5th September 15:51
Freakuk said:
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
That's what I try to do using "best biking roads"The problem is what some people call best might not be what you consider good i.e. it might just have a lovely view
I came back from Glasgow to Warwick across some well known roads ie Buttertubs Pass - the tarmac was appalling, bumpy, potholed, breaking up and narrow - fine on my SM but pretty crap on my Speed R
Freakuk said:
I've been using Calimoto all year and there have been a few updates along the way, it is getting better but it still needs a few tweaks.
Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
If you need to plan the route via their webpage, what's the added value compared to using itnconv or kurviger and then send a gpx file to any nav app on your phone ?Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
Edited by Freakuk on Monday 5th September 15:51
I've been using itnconv for a while with the Michelin map and it's quite easy to find the good bikkng routes without any alhorythm trying to be smarter than you.
To be honest the main problem I'm having at moment is the nav app : I previously used an old sygic version as my phone was old, now that I changed it I've been forced to upgrade sygic as well and the newer versions are unstable as f...
6pi said:
Freakuk said:
I've been using Calimoto all year and there have been a few updates along the way, it is getting better but it still needs a few tweaks.
Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
If you need to plan the route via their webpage, what's the added value compared to using itnconv or kurviger and then send a gpx file to any nav app on your phone ?Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
Edited by Freakuk on Monday 5th September 15:51
I've been using itnconv for a while with the Michelin map and it's quite easy to find the good bikkng routes without any alhorythm trying to be smarter than you.
To be honest the main problem I'm having at moment is the nav app : I previously used an old sygic version as my phone was old, now that I changed it I've been forced to upgrade sygic as well and the newer versions are unstable as f...
If I am out and and want a route I'll let the app sort things, but it's usually get me from A to B, rather than a full day out on the bike.
Freakuk said:
I've been using Calimoto all year and there have been a few updates along the way, it is getting better but it still needs a few tweaks.
Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
Cheers for the notes...Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
Edited by Freakuk on Monday 5th September 15:51
On your last bit, I actually used the "contact us" bit of their website as I realised that you can't use What3Words with it either, again something that is so easily incorporated into something like google maps... and someone from Calimoto actually replied saying they were indeed looking into that, just hadn't got there yet.
I'll give it another try for my trip down to Italy this year, working on the PC first..
the cueball said:
Freakuk said:
I've been using Calimoto all year and there have been a few updates along the way, it is getting better but it still needs a few tweaks.
Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
Cheers for the notes...Some stuff that I have learned: -
1. Plot a route via the webpage, it's much easier and I create waypoints along my route to "force" Calimotos algorithm
2. It's easy to drag a waypoint around if required to adjust the route if required
3. I tend to change the route type across each waypoint to see what it may adjust for that section
4. I never use the relly twisty setting as you'll end up down single track/bad surfaces
5. I tend to provide feedback after my rides on the app, I've no idea if this helps with Calimoto and updates to their algorithm
6. I also add favourites via the app if I hit some really good roads and add a brief note, so I can always refer to them when planning another route.
However, it still isn't perfect... but it is a learning curve and knowing some of the roads etc, letting Calimoto plot it all generally means you'll end up going everywhere but cover very little distance as the crow flies. Also, if you are doing a round trip and you're creating waypoints close to an existing waypoint it has a tendency to auto renumber to include your new waypoint amongst the existing ones, not a later waypoint if you can understand that.
I've probably done somewhere between 4-5000 miles this year using Calimoto and generally it's been pretty good, but it's down to me to make it better for each ride with better understanding I've gleaned from each ride.
I'd love to provide feedback/ideas to Calimoto but I am unsure how, main one being adding favourite roads/routes somehow, so you could see good sections and link them together.
Edited by Freakuk on Monday 5th September 15:51
On your last bit, I actually used the "contact us" bit of their website as I realised that you can't use What3Words with it either, again something that is so easily incorporated into something like google maps... and someone from Calimoto actually replied saying they were indeed looking into that, just hadn't got there yet.
I'll give it another try for my trip down to Italy this year, working on the PC first..
As for what 3 words, I suspect there's a licensing fee for them to pay to get access to their database/geo info. I know when I was working for one the UK's largest courier firms developing a new delivery app we first approached Google to use their maps and the money involved was eye watering so we shifted to here maps, so I am guessing this is where W3W make their $$$ from.
Gassing Station | Biker Banter | Top of Page | What's New | My Stuff