Worldwide routable Garmin maps: Missing/incorrect feature requests

At present there is a problem with “Istambul tile”, both selecting it during a custom map generation or downloading Turkey ready map as whole.
If you select the Istambul containing tile and generate a custom map you obtain a map containing the “Friburg” tile

Massimiliano “Bibo” Segreto

This is a known problem and discussed there, but offtopic here.

I’m seeing a small problem. In the Zuiderpark, Den Haag there is an athletics track. It is properly mapped as “leisure=track”. But because of the “track” the outline of the track shows in BaseCamp as a “path”.

In the Zuiderpark:
http://www.openstreetmap.org/?mlat=52.05472&mlon=4.28783#map=17/52.05472/4.28783

The other athletics track in Den Haag, same problem (of course):
http://www.openstreetmap.org/?mlat=52.07749&mlon=4.24358#map=17/52.07749/4.24358

Wiki about leisure=track:
http://wiki.openstreetmap.org/wiki/Tag:leisure%3Dtrack

The problem is should it be tagged as a way (the track itself) or the whole sports area (where the track(s) is/are located).
In the wiki this is unclear. If you look in the right tabel it recommends not to use it on the area:

Used on these elements:
should not be used on nodes
may be used on ways
should not be used on areas
may be used on relations

So therefore the mapping on OSM is wrong, one should map the actual race track with leisure=track (which is represented as path in Basecamp) and not on the whole sports area.

Reading the wiki again, I am not sure how to solve this. All situations are different.

The “Areas?” paragraph states that the handling of areas is a bit unclear at the moment.

In Rijswijk there is a cycling track. That is definitely not properly mapped (highway=cycleway). But when it would be mapped with “leisure=track” (as it should be, I think) you want the track to show as a real path. But athletics track are commonly mapped as areas.

And leisure=track is also used for horse racing. Duindigt is also mapped as an area. But maybe other horse racing tracks are mapped different.

Cycling track in Rijswijk:
http://www.openstreetmap.org/?mlat=52.02869&mlon=4.33443#map=17/52.02869/4.33443

Duindigt:
http://www.openstreetmap.org/?mlat=52.1074&mlon=4.3446#map=16/52.1074/4.3446

I think the lack of a clear guideline results in that every renderer and mapper interprets it on a different way… :confused:

Incorrect runabout exit indication

I use a Nüvi 55 with primarily maps from Denmark. I have the latest revision of the Denmark map… 09-09-2014

There is an error:
For example, my journey takes me though a roundabout. It is a straight forward roundabout with 4 exists, 3 o’clock , 6 o’clock , 9 o’clock 12 o’clock , where I am entering the roundabout at 6 o’clock and should exit the it at 9 o’clock to reach my destination.

The voice prompt navigates me though the roundabout correctly… “take exit number three, bla bla bla”…

The small icon to the top left of the navigational window on my Garmin, indicating the specific roundabout with the exit to take, incorrectly indicates that I should exit the roundabout at 6 o’clock.

I find this to be the matter with all roundabouts… the icon to the top left on the navigational window displaying an exit later that the actual exit that I need to take.

Welcome to the forum. :slight_smile:

First, do you have any other maps loaded and possibly enabled, covering the same area?

What maps was your unit sold with?

This problem occurs very occasionally on my Zumo (I suspect it’s a firmware bug), but if this is consistent then it warrants further investigation.

Regards,
Peter.

Hey Peter

Thank you for the welcome. I have disabled all other maps on my device… for example “city navigator europe nt lifetime” that came with the GPS.

(I have tried the downloadable *.img file that I copied directly onto my device and *.exe file for installing the map to BaseCamp, where I then uploaded the map to my device via BaseCamp. The result is the same)

Regards,
Johan

P.S. I’m worried that it actually might be a firmware bug… just like you mentioned.

Can you try another GPS map, not produced from OSM? I have a suspicion…

I have already tried it with the Garmin map that followed with the device and there is no problem with it.

Yes, I expect that it will work correctly with all of Garmin’s maps. But can you try a different kind of map? You can try our own NZOGPS map and put your unit into demo mode (i.e. turn off the receiver). You can position your pointer somewhere in NZ and route to another location on the map.

What I suspect is that your GPS can’t handle roundabouts in maps other than Garmin’s.

OSM maps are produced by a compiler called mkgmap. By trying another kind of map I want to eliminate this, as other free maps are generally produced with cgpsmapper. The output should be pretty much the same, but this is just what we are trying to prove.

Ok, I managed to download the NZ map… but first I had to register.

I selected two waypoints in Christchurch…
S43.55101° E172.54557°
and
S43.55205° E172.54589°
(there is a roundabout between the two points)

I did a simulation of the route and no problem whatsoever. Both the voice prompt and the icon indicating the exit in the roundabout (top left of navigation screen) is correct.
:wink:

Right, well done!

On the face of it your Nuvi seems to have a problem with roundabouts compiled with mkgmap, but cgpsmapper created maps and Garmin’s own (naturally) are ok. 1 attempt is not proof, of course, but I think there is a lead that can be followed - but not here. This forum is for tweaking the appearance/functionality of the maps produced by Lambertus.

May I suggest you take your findings to the mkgmap mailing list?

Kind regards,
Peter.

hi,

I’m new to OSM for Garmin.

I downloaded the new style routeable maps for my local area (Washington DC) and use it both on Garmin Montana 600 and GarminXT on a Nokia E71 symbian phone.

Problems I’ve discovered with New Style routable maps:
on my Garmin Montana, the maps features such as parks, school fields appear as dark patch on the map in night mode, this makes these area features less visible at night. also the OSM maps seems in conflict with some other Garmin format maps such as MyTrails. with MyTrails enabled, OSM map is not visible in some areas.

On GarminXT with Nokia E71 symbian phone, some of the fonts for rivers, bays displayed as double typefaced fonts, this makes the names for these map features hard to read.

Hi, welcome on this forum.
Less important features that appear less visible is imho intended on night mode to make it less distracting.
If you like to change that, there are two options

  • turn on the daylight mode
  • Customize the map colours with a typ file editor. You can give every map item the colour that you like.

I dont know if Garmin XT supports a typ file, if it does you can optimize the map for your Nokia as well.

Yes, a general rule of thumb with all garmins is do not enable multiple maps, because it will indeed cause conflicts.

I generally downloads the Brazilian maps from garmin.osm.nl and have encountered two problems:

  1. In the Generic Routable style the tile named BR Vila Velha seems corrupt, it gives only a white tile without no roads, no rivers, no ocean

  2. In the Generic Routable (new style) it seems like the maxspeed tag is ignored, missed, omitted. I get generic speeds for highway types instead of the speeds I am expecting, I have exessively used the map in Simulator mode in order to detect possible errors and to test the map usability for my needs, and until now never seen the simulation use speed limits I know have been tagged for years. The generic speed limits from highway types does not fit with on-the-ground reality in Brazil, resulting in Arrival Time calculations always being wrong. - Biggest problem is motorway resulting in speeds of 240 km/h, highest speed limit I have observed in Brazil is 110 though suspect there might be roads with 120.

@Skippern,

  1. There seems nothing wrong with that tile. Do you have the latest version? Did you zoom in enough? Maybe crtl-G 2x (clear cache) helps in Mapsource or Basecamp.
  2. Do you see this recently? Is the generic (old) style ok?
  1. I gave up on that style about a year ago. Checked all zooms and routing. It broke routing, and zooming all the way out would give me coastline if I remember correctly, but closer zoom gave me only clear land, even at sea
  2. Currently testing with new style version 01-10-2014, do not have bandwidth to update until beginning of December, for same reason have not tried with any other styles.

I have a request on the way Fuel station info is processed. I presume the MKGMAP program looks for amenity=fuel. then searches name and operator, putting one, or both into the Garmin. If there is no info, then it gets labelled Unnamed Fuel Station
A lot of fuel stations in OSM (in Thai at least), just have the brand tag completed, and more recently, I am seeing the name in Thai script, with name:en in English. I assume MKGMAP tries to translate the Thai, and possibly ignores name:en
Can the prog be amended to check the tags in order, looking for the first valid English name, but to include brand & operator?
Only one needs to be displayed on the Garmin map.
Possible, or too difficult ??
:slight_smile: Russ.