Maps on Nanikore

All the Kurviger(.de)

Mon, 24 Aug 2020 06:07:50 +0000

TL;DR: In this post I’m taking a look at why I use kurviger.de map and route planner, and why you should give it a try because it creates some fantistic twisty routes.

Route planning is often the unsung hero - or villain - of a day out, as we curse missed turns, closed roads or things simply beyond anyone’s control like a road sliding away, or being blocked by a tree.

There’s a wealth of sites, devices and applications available for us to find the best way to get from point A to point B, and potentially a few points in the middle. However, many of these sites and applications make this bizarre assumption that you want to get there as quickly as possible on the straightest roads. How very bizarre. One that I find myself using quite often is Kurviger.de.

Why Kurviger? Well, let’s take a look at it.

It’s a map and routing site based on the OpenStreetMap map base, with a few sub-versions available. It has all the usual functionality of a start, end, mid points, extensions, points of interests, petrol stations and all those kind of things - it also has as a nice list of GPS coordinates of your set points which is nice too.

One of the fun features is how you can ask it to calculate a route for you - as fastest, fast and curvy, curvy or super curvy road types. The latter really is a fun thing to try - a lot of turns, often going a longer, more scenic way also.

Here’s a simple example from here in Japan, where Kurviger makes hugely different routes depending on which algorithm we ask for - straight, or super curvy.

As a motorcyclist, I like this kind of feature, partly to find new roads to places I know, but also for just creating something fun to ride.

The site now also has an account system so you can create your route and save it on their server for the next time you need it. You could also technically just bookmark it, as much (I suspect not all) of the data is in the URL you’re looking at. I currently export mine as a gpx track, which I can also upload later if I want to do another version of it. I then use these gpx track files in my smartphone OSMAnd+ app to use as a navigation file. One other way to find routes on the site is via ’tourcodes’ which are rides created or recommended by various magazines and journalists.

Kurviger themselves also have a mobile app, although I haven’t used it that much so I can’t give a full review, but it does seem decent. They also have a forum if you have questions, which I’ve used a couple of times, and found the response to be quite and helpful.

So this is all well and good as a website to mobile app, but what’s it life in real life? As you can likely imagine, when we get to super curvy, Kurviger is going to find some small and real backwater roads. Better to say ‘ways to go’. A few times I’ve been down real agricultural dirt tracks. Once I ended up on a basic concrete service track just a couple of metres wide, riding a meter above some rice fields, which narrowed as it got to the real road. It was a beautiful ride, with my only fear being someone coming the other way! Another time I ended up in a road in the hills so rarely used there was debris all over it which was a fun hour clearing a safe path for my road tyres. Yes, it would have been quicker to back, but where’s the fun in that?

These are not a Kurviger issue, but highlights it will choose any road it has in its system. If you’re of the right mindset though, it’s a great way to find some interesting routes and server something up if you’re drawing a blank on where to go that day.

Twistybutt Map Tips

Sun, 10 May 2020 14:40:49 +0000

[2022 May Update] I wrote this in late Summer 2019 as a reminder for myself. It's had some good feedback, and I've learned a bit too, so please go to this updated page which I'll update going forwards!

What is GPS?

The Global Positioning System [GPS] is a US military Global Navigation Satellite System which gives you a location pretty much anywhere on the planet Earth as a set of coordinates. There’s actually a growing number of these systems being deployed as countries and companies look to reduce their dependency on something which could be taken away at some point. There’s a decent list here for those interested.

What about Twistybutts?

So when you do a Twistybutt, unless you’re one of the brave few (and probably on a Ducati classic) using a piece of paper taped to your handlebars, you’ll be using some form of GPS navigation system on the ride, aiming to follow the path TougeExpress has carefully crafted for us.

You get this file, shove it into your device or phone and then just go right? Oh, it’s not that simple? When is it ever. Let’s review this to ensure happy happy Twistybutts.

The file is usually sent by TougeExpress as a .kml or .gpx file created on Google Maps, so let’s start there.

What is .kml?

KML(Keyhole Markup Language) is a standard file type usually associated with Google Maps and Google Earth. It’s called that because Google bought the company Keyhole to start it all. These are usually .kml files but there’s also a .kmz file, which is a zipped format containing the .kml file and any other useful meta info. It’s designed as a presentation format for annotating maps.

What is .gpx?

GPX is another file format which is designed to encapsulate a lot of data about topography, including GPS data and other locations. The format has explicit formats for routes, waypoints, and tracks as distinct data types.

.gpx is generally considered the better option for transferring data between GPS devices and it’s widely supported.

However, there’s more to it than that. Again.

Waypoints, Routes and Tracks

Waypoints: These are single fixed locations which you may have set yourself, or the application may have chosen, such as a good restaurant or a geographic location, stored as a GPX location.

Track: this a larger file, but has a higher resolution, a higher number of GPS points to follow, meaning an app can usually place them on a map and get the roads you wanted more accurately. A potential downside being that some apps and devices may have a limit to how many of these points they can render. These are also usually the type files created when you record a run/hike too, like a bread-crumb trail.

Route: this is lower resolution, has fewer waypoints, fewer GPS positions and your app/device may use its own logic to decide how you will navigate from one waypoint to the next, depending on your settings. This means that two riders with two different apps or devices and settings, may go down different roads.

Basemaps

The maps we use, be them paper or digital are not the same. Indeed, some are intentionally not the same. These differences can make a difference as to how a device sees and chooses your route (also see ‘Why is my route different?’). We need to be aware then of what map we’re using and test to see what differences that has to the one the route/track was created on.

All other factors being equal, OpenStreetMap and Google Maps are sufficiently different that designing a route on one may not get you the exactly same sequence of roads as on the other. This is often because we’re going on small, minor roads with lots of branches.

So what do I do for the Twistybutts?

Let’s look at my own example:

My first year I had the source route “golden master” [GM] .kml from TougeExpress made in Google Maps. I imported that .kml file into trip planning website Furkot.

It didn’t go so well.

When I missed a turn the app running on my smartphone would then try to recalculate to get me to the next waypoint, since it was the only real information it had, and to get there may or may not on the GM route since it was finding the way between waypoints.

Some of this was my lack of understanding of the application (See ‘Know your navigation system’) but I also didn’t understand that the exported Furkot route was still using Google Maps base, and OSMAnd + is based on OSM (OpenStreetMap). An exported track would’ve been better, but not perfect.

The next year I used Kurviger which also uses OSM. I went the long way of making a 1:1 copy of the GM by comparing the route natively in Google Maps and Kurviger side by side and then exporting from Kurviger as a .gpx track. This meant I had to split the route into 3 sections as this is a high resolution solution, and at the time Kurviger seemed to struggle with more than a certain number of its route designing points.

[2022 edit - it seems that Kurviger is now able to handle more route designing points.]

Breaking it into multiple parts as a track also meant my OSMAnd+ phone app could follow it, and guide me back to the track, not a waypoint if I went off it. This took a long time but you should know what to look for along the way anyway. This worked well for me.

These days, TougeExpress will give you a Google derived .gpx track if you ask, so all you have to do now is to import that into a site / app which has your system’s basemap and check it against that GM. You may have to carve it up for the site or your navi to handle.

This was my last way - I imported that into Kurviger, did a quick side by side, made some minor tweaks, and then sliced it into 3 parts and exported it as a track.

Also, don’t forget to mark the fuel stops / places of interest in your system too, and that the fuels stops are open - sometimes they aren’t open when you think they are (sigh).

The Final Checks

Now you have your 3 .gpx files (or what is appropriate for your system - see below). Now load them on your navigation system and quickly compare to the GM - did it get it? Even at this point I’ve seen some subtle issues which could put you on the wrong road, so I’ve gone back, tweaked, re-exported/imported and checked again. I’d attribute this to very minor differences in the way the application renders the way.

(aka ‘Why is my route different?’ )

I didn’t fully understand some of OSMAnd+’s options on my first run - as well as not appreciating routes vs. tracks. It all added up to wasted time and missed turns - to the tune of ~3 hours. That was on me.

You need to know what maps your system uses. You need to know if you have a track or a route file and what map that’s from. You need to understand what your settings are for routing too. For example, if you have ‘get me there quick’ enabled, there’s a good chance it could generate an unintended route, or when you go off a route, it’ll put you on a main road to the next waypoint - that is not The Twistybutt Way. This may even happen with a track on some devices. Essentially, you need to know how you app or device works.

Some people have tried to use Google Maps, only to find on the day no data signal in the mountains, so no streaming Maps. Some people found on the day they didn’t know how to tell Google Maps to follow a specific route. You don’t want to discover these gems on the day. Learn your app.

[As of late 2019, Google Maps now allows downloads in Japan which should reduce issues with not being able to get map data when out of signal areas - providing you remember to download the map data beforehand.]

Map Not Keeping Up?

Another factor to remember is that on some systems there can be a lag (or accuracy issue) where the device/app thinks you are based on the GPS information its receiving, meaning if you’re going quickly - but still inside legal limits obviously - you might miss a turn, so be aware a bit before and keep an eye out for the kind of turn you’re going to be making.

Getting hot.

One issue phone users face (and this is seemingly less of an issue for dedicated device users) is that their devices can get hot, and either become functionally unstable or flat out shut down.

Firstly, local map solutions like OSMAnd+ seem to have this less as they’re not streaming map and position information in and out.

There are other things you can do: remove any covers on the phone, close any applications you aren’t using, turn WiFi off (even Bluetooth if you don’t really need it) and reduce the screen brightness as much as you can. Also, mount the phone where it’ll get some breeze. This might mean moving it on your handlebars, or adjusting/removing your screen. Anything to get some cooler air around it.

All good?

Get out there and ride, and be sure to talk about any issues as opportunities for exploration at the bar later.

If this all seems like a lot of work, and yours works fine out of the box, that’s great, but if you do the Twistybutts and have ‘issues with the map/route’, take the time to see if there are any potential fixes here.

Also, bring a paper map and a paper list of road and town names. It never hurts.

Remember: The is NO substitute for knowing your route, or at least recognizing when you are not on it.

[Apps I know people use include the OSMAnd+ I use, Google Maps, MotionX and Kurviger, as well as the dedicated Navis from Garmin and OEMs. For paper maps, the Mapple Touring books are excellent.]

Review: OSMAnd+

Sat, 23 Mar 2019 00:34:43 +0000

When I’m out and about I’ll often take a look at my map book to get a rough idea for a route or destination, and then just go, stop if I think I’ve missed a turn somewhere, or keep going if I just accidentally found a really good road. It’s a fairly relaxed approach I admit.

Sometimes though, I want to follow a specific route, either one someone has sent me, one I’ve specifically made myself, or even one the fevered algo on Kurviger.de has come up with. In early 2017 I started trying out some different smartphone apps, as well as dedicated route navigation devices such as those from Garmin. After a bit of poking around, borrowing kit from friends, and a lot of tea drinking, I settled on the (free or) pay-for OSMAnd + app on Android and iOS.

The Maps

Per its name, it uses the free and open source OpenStreetMap [OSM] data and has the benefit that you can download map regions to your phone for free via the app - no update fees like the older Garmins, no sending units away or any of that.

Having it local is also going to save on data during rides if you even have signal, and some power and heat on the phone as it works it’s tracking and calculating magic.

I should explain a caveat at this point: currently here in Japan, we can’t download Google Maps for licensing reasons, so to use them you’ll be needing need signal and when I go up into the mountains, there often isn’t any. Also, Garmin support is via a fairly pricey 3rd party.

OSMAnd+ can read . gpx files in from other navigation systems and sites, so you can make use of the aforementioned Kurviger and other routing packages and websites. More recent versions will also work with .kml files apparently, but I’ve not spent time with that, so I’ll neatly side step it.

Along the way of learning about navigation and GPS systems, I’ve had to try to teach myself a bit about tracks and routes. In broad terms, a track is a larger file, but has a higher resolution number of GPS points to follow, meaning an app can usually place them on a map and get the roads you meant more accurately. The limiting downside being that many apps and devices have a limit to how many of these points they can render. These are usually the files created when you record a run too. A route has fewer points, but then the app/device will use its logic to decide how you get from one point to the next, depending on your settings, so two riders with two different apps or devices and settings, may go down different roads.

In Use

Setting A->B (via C) routes on the phone is simple and whilst there is an array of options around that, the defaults work well. The developers frequently update the app and its user interface, and it’s become a lot neater over the last year or so, and some of the options have been clarified and moved around.

It also allows you to chose what’s on screen while you’re riding such as distance to destination, estimated time left, and even if you’ve accidentally gone a certain amount over the speed limit. There’s quite a lot of information and tutorials on their site and YouTube as well.

You can import tracks or routes to the app from an email attachment, Google Drive or a local file. If you prefer you can make one yourself on your phone by selecting points manually, and letting the app decide the route based on your preferences.

Location points you add and save you can also see on the map by folder group which is great, meaning after you’ve added quite a few, you can choose to only show the ones you need for a certain trip. It can also show points like fuel stations, convenience stores and such from the OSM database. I will admit I sometimes cross reference these with Google Maps for opening times.

It also has text-to-speech voice instructions for a lot of languages, meaning you don’t have to look down at the phone if you have a Bluetooth communicator. Given I ride a lot of tight mountain twisties though, it can get comical when it tries to keep up with the rapid turns, so I often mute it for those stages, as it trips over itself with left and right instructions. One other note on the voice, for a tight turn I would call a hairpin in the UK, the TTS (even the UK English one) refers to it as a ‘U turn’.

The app also has some interesting plug-ins, such as one allowing you to record video and audio into the app for a given location, which is a nice touch if you do ride reviews, and is free. There are also pay for plug-ins such as for nautical information, and specific data like ski areas, and 3D hill shading.

Caveats

OpenStreetMap and Google Maps are sufficiently different that designing a track on one may not get you the exact same thing on the other, though broadly they can interoperate, depending on settings. The main practical issue is that Google doesn’t like outputting .gpx, so you may need to convert with an app or a website, or try that new kml functionality.

In the near two years and multiple versions I’ve used, only once did the OSMAnd+ developers fundamentally break the app for me - a zooming issue in certain languages which sent it into a loop - though the developers did provide an older version for manual install (since Google Play doesn’t easily allow roll-backs), and that was at least a work around. It’s the old adage - “never do an update just before a ride”.

Is it worth paying for?

When I bought my copy, the main difference was the number of .gpx files you could hold at once on a device, but that’s not really a limitation for most people I suspect. I paid to help support it really, and perhaps because of that I saw decent email support responses, but the official forum also seems to get adequate response times. I personally believe in supporting developers of apps I get worth from, and I also bought the contour and shading plug-ins to get an idea of the terrain I’m riding, as I live in a mountainous area, so I can gauge how much vertical I’m looking at. All in all, I find it a useful app for the average touring biker.

My First Google Map

Fri, 07 Aug 2009 15:41:42 +0000

Minor note, I finally finished my first Google Map of my last bike trip; thus, on my MacBook, the last leg isn’t shown until I go to the second list on the left. Maybe I’m missing something.

It was rather laborious as I couldn’t get the ‘follow road’ line tool to do my bidding, but hopefully I can fix that up for the next one, next month.