Routable Garmin maps:

Garmin has a specific type for roundabout (0xc, polyline). Can we have all ways tagged as junction=roundabout use this type. Modifying poly.cfg doesn’t seem to work. You might also want to set all roundabouts as oneway=yes if it was not tagged as such.

Thanks for such a great tool

Hi Guys,

I got a program written in python that corrects all the situations that do not fulfil Garmin requirements. But it makes the corrections while reading data. I have never planed to update OSM database itself. This is because I think, that these requirements are Garmin specific and OSM is not. What if there is someone preparing routable maps for X devices and they require roundabouts from one piece and nodes laying no closer that 10 meters? Should he correct the data in OSM? I’m sure not. Correcting data in fly should be no problem.

I quickly (=without lot of work) generated a map of Petersburg with my tool. You can download it here: [link removed]. I made a mistake declaring an area and the city is a bit off centre, but this shouldn’t be an issue. Everything that I have done manually was to declare an area of the map, it’s ID, name and some paths to planet and osm files. The whole process is automatic. I don’t correct any data in OSM. It took about 1,5 hour of computing time, but almost all the time was needed for Osmosis to extract the data from planet file. And obviously I am not yet ready to support cyrillic languages :wink:

I checked the map quick on my eTrex and it seems to be routable. Here is the screenshot:

Admin edit: Link not working anymore

this osm2mp version uses latest tag to determine object type
so if it sees “junction=roundabout” after “highway=” it sets Type=0x0c, or highway type if before
some priority mechanism must be imbplemented to have it always use 0x0c
i’ll think about it :slight_smile:

add line

      $polydir     = 1                  if ("$1=$2" eq "junction=roundabout");


      $polydir     = $yesno{$2}         if ($1 eq "oneway");

I think that certain changes should be put back into the database (all that are non-garmin specific).

It is much faster (and easier) to use OSMXAPI DB for this purpose.

I think it’s garmin to blame here for not using the utf8 fonts.

That should be easy to solve, if koi8r is the russian charset.

iconv -f utf8 -t koi8r planet-extract.osm >russian.osm

Might not parse in all OSM tools (osmosis) after that but it should convert from utf8 to koi8r.

garmin uses cp1251, but it is not an issue here. St. Petersburg area
borders with Finnland (iso8859-1) and Estonia (iso8859-4), so
it’s a pity to loose all national characters, which do not fit into
one codepage.

I agree. But I received several “Internal Server Error” responses while unsuccessfully trying to fetch London area so I switched to planet file which is a pain, but works. I am converting huge amounts of data (several GB) and I currently temporary have rather poor connection.

yes… I’m thinking when we get more routable maps people will see the real benefit of OSM and that can only boost the number of users contributing to the “map”
good job.

i created a wikipage about routable garmin maps. Please add some information:


Do we know how these maps were created ?
I didn’t find any published source code, so it has zero value for me,
compared to the excellent work of liosha.

I think Radomir may release code once the code has reached some point of full completion , but this is what I heard…

This is what actually have kept me away from OSM for some time, couldn’t make use of the maps, but with the recent tools being available I’ve started contributing to the project. A couple of thousand nodes in the last week :slight_smile:
I believe this is the key to getting succesful, along with improving the map making software (I’m currently using latest beta of Meerkartor, which is ok but not perfect, maybe time to convince the guy making GPSMapEdit to build in support for OSM??)

I have read his comments too, let’s hope it will happen soon :slight_smile:

release early and often… :slight_smile:

Radomir, could you please edit the start post of this thread and update it with latest info (like download location). That way new readers don’t have to go through the entire topic when they just want to download the maps. Thanks!

I just received a report from a user of your maps that he can’t search for place/city names. I assume this is a bug somewhere?

I can do place and address search on the Malaysia map, but the full address is a bit off as it picks up not the nearest town/city to the street. I wonder if populating the is_in tag will help.

There are some difficulties with address searching when generating a map:

  1. The data in OSM are often missing.
  2. Currently the algorithm for assigning road to a city is simple (see point 1): take the city closest from the road middle. It obviously needs improvement :slight_smile:

BTW thanks for the Australian maps , I’ve cross posted on the Geocaching Australia forums too.

Many Thanks Radomir for the Aussie Maps (by many. I mean billions)

Although I am a dedicated Mio Map 3 (aka igo) user, last week I purchased a Garmin Nuvi 260 with the expectation that we would soon have some routable maps.

I’ve just loaded them (Australia) into the Nuvi 260. They work wonderfully, even the TTS (which I consider esential for safe navigation) works like a charm. Ok tomorrow I’m going to be driving all over the place with this new toy - checking out our local maps for accuracy and testing the routing system.

Is this the correct forum to notify you of issues, maybe bugs or features :slight_smile: I’m sure I’ll come up with numerous situations, so here’s the first.

My first simulated route showed that roundabouts are not recognised. It said turn right onto Smith Street when other programs would say something like " at the Roundabout, take the 3rd exit onto Smith street".

PS - I’m buying anothe Nuvi 260 tomorrow. That way I can always upgrade one to the latest firmware level without the risk that they will find a way to disallow OSM map uploads.

This is now really FUN - We’ll all have to really clean up the OSM data now to get full benefit from the routing program.