Worldwide routable Garmin maps: URL REMOVED

Usually the maps are updated weekly. But I was on vacation last week, so the current version is available for three weeks (I could not produce a new update in the time between when the planet dump became available and when I left).

The timestamp as given on the homepage is what matters if you want to see new data in the maps. The actual build date of a map is not of importance.

A new update is running as we speak, I guess it’s going to be available somewhere Saturday or Sunday. Just keep an eye on the timestamp on the homepage.

Thanks Lambertus, Very much for the quick response and explanation.

It all makes sense now. I will keep an eye on the date on the home page.

This weeks update is delayed due to invalid XML characters in the planet dump…

When update the costa rican`s maps? to mapsource and the image,
nuvi 265 wt

New maps are going to be built after the next planet update (wednesday evening) and preprocessing (starting thursday until somewhere friday). So next update should become available somewhere saturday or sunday at the latest (provided there is no invalid XML in the planet dump like last week).

Thanks for putting so much work into this. I’m enjoying the map updates, driving around and trying to contribute and fine-tune data where I can.

How does your mkgmap style definition treat names and refs? For example, Oregon state highway 8 is locally known, and signed, as Canyon Road or Tualatin Valley Highway. The GPSr calls it OR8 (the value of the ref tag) when using the maps you generate. Would this example apply?

Well, I’m using the default Mkgmap stylesheet so that should be handled by this. I admit to not have any knowledge of the styling system of Mkgmap so if you have ideas or suggestions then it might be best if you join the Mkgmap mailinglist.

Hmmm… Looks like this patch was submitted to address the issue, and while the Java portion was applied, it looks like the accompanying stylesheet changes were not.

That patch applies to routing instructions only - is your issue with general GPSr map display, or routing instructions in particular?

Both, really. In MapSource, only the highway shield appears, or the text “Or8” on mouseover. In directions, it refers only to the road as “OR8”.

OSM link

The data:

* highway: secondary
* maxspeed: 35 mph
* name: Southwest Tualatin Valley Highway
* name_1: Oregon Route 8
* ref: OR8
* tiger:cfcc: A31
* tiger:county: Washington, OR
* tiger:name_base: Tualatin Valley
* tiger:name_base_1: State Highway 8
* tiger:separated: no
* tiger:source: tiger_import_dch_v0.6_20070808
* tiger:tlid: 158207930
* tiger:upload_uuid: bulk_upload.pl-fa49a608-adf2-4338-8828-4f80569842cc

From the stylesheet, I’d expect it to display like this:

{OR8} Southwest Tualatin Valley Highway

Stylesheet rule:

highway=secondary {name ‘${ref|highway-symbol:oval} ${name}’ | ‘${ref|highway-symbol:oval}’ | ‘${name}’ }

I noticed this same thing on some Garmin maps I was making. I think its caused by the highway shields, as the Garmin can’t display those as well as the name at the same time. I fixed it by setting the “display_name” for the highways. eg a style rule like this:

highway=primary {name '${ref|highway-symbol:box} ${name}' | '${ref|highway-symbol:box}' | '${name}'; add display_name = '${ref} - ${name}' }

That was basically the second part of the patch, and it apparently never made it into the default stylesheet.

(In case you’re wondering if I read this… I’ve forwarded this to the Mkgmap mailinglist)

Edit: The change has been committed and should be visible on the next map update (next weekend).

Hi, What’s wrong with the Australia maps? installed them and no tracks, roads nothing show’s up, and the file size is very small compared to what they used to be.

Something went wrong while uploading the latest update to the webserver: only 145 of the 764 tiles are uploaded. The service is offline until all the tiles are uploaded. Thanks to all the people who reported the problem (via email or the forum).

I noticed today that Ways with “highway=path” are not being shown on the Garmin map output. Is this intentional, or is there just a missing style rule?

I’m not sure what’s the cause, the default style does seem to process the path’s, maybe they’ll show up if you increase the level of detail?

That’s exactly the issue. The resulting Garmin map elements for highway=path are shown at 800ft at tighter zoom levels on my Garmin Etrex HCx when detail is set to “More”. At normal, they’re shown only on 500ft and tighter. One trail I was looking at is partly highway=track and part highway=path and half of it appeared to be “missing” on the map until I zoomed in or turned up the detail setting.

Ok, these issues are very sensitive. You’d want a map that has as much info available without becoming a big blob of lines. I can understand the decision made to render the path less prominent as the stylesheet used is a generic stylesheet (no specific target audience). I hope setting the detail setting to more will suit you…

Yeah, I understand the issues at play here, especially on low-color, limited resolution screens. I’m thinking mkgmap should probably do something smarter when a relation contains ways with different maximum zoom levels in order to avoid having part of a route disappear as one zooms out. Also, it would be nice if it could boost the maximum zoom level for lone ways in otherwise empty areas of the map. I’ll investigate fixing both of these issues in mkgmap as my time permits.