Magic highway symbols on Vista CX failing

Hello I seem to have a problem with the default style and the highway tagging on my Garmin Vista CX with mkgmap rev. 1114. When I tag highway=secondary, name=Grand River and ref=MI 123, the result is a road with name "Road". It works as expected, however, with highway=primary. So I did some research and I think the problem is that not all of the "magic" symbols in src/uk/me/parabola/mkgmap/osmstyle/actions/HighwaySymbolFilter.java are available on the unit. Also they are named wrongly for this unit. I made an OSM test file[1] to check all symbol names given in the above source file. It contains parallel road segments with ref=MI 43 name=Grand River I-VI and highway tags of motorway,trunk,primary,secondary,tertiary,residential respectively. Then I used a slightly modified default line style[2] (which assigns one highway symbol to each of the above road types) to generate a map[3] with the --gmapsupp command switch. After uploading the result to my Vista CX, it renders like in this picture[4]. The styles are (from bottom to top): interstate,shield,round,hbox,box,oval. Some remarks: * Styles "interstate" and "shield" look exactly like hbox and box but they prepend "US" and "Hwy." to the reference (only appears when hovering the pointer over the street). This is not so useful for OSM data, since the US tagging scheme in the Wiki says those should be included in the ref tag (i.e. ref="I 94" or ref="US 127"). * Style "box" is misnamed, as it produces an oval * Style "oval" does not work, it seems to break the entire name of the road * Style "round" is misnamed, it produces a framed box I don't know how other units render these symbols, so I can't say whether the names should be changed or not. But I do think that "oval" should at least not be used in the default style for secondary roads, as it actually breaks the name display on my (not quite uncommon) unit. If you need more information or want me to run more tests, please let me know. Alexander [1] http://alex.wittig.name/sonstiges/mkgmap/test.osm [2] http://alex.wittig.name/sonstiges/mkgmap/lines [3] http://alex.wittig.name/sonstiges/mkgmap/gmapsupp.img [4] http://alex.wittig.name/sonstiges/mkgmap/P1020125.JPG

On Jul 31, 2009, at 19:54, Alexander Wittig wrote:
So I did some research and I think the problem is that not all of the "magic" symbols in src/uk/me/parabola/mkgmap/osmstyle/actions/HighwaySymbolFilter.java are available on the unit. Also they are named wrongly for this unit.
Just out of interest, have you tried using the --latin1 option when you compile your map? This switches to 8-bit mode (or something) which uses different byte codes for the highway symbols. It is possible that there are errors in the 6-bit codes. At any rate, I compile my maps with this option, and the highway symbols appear correctly, both in Mapsource and on my eTrex Vista HCx, which I assume should be very close to your Vista CX in display characteristics. When I tested this, I also noticed that the US Interstate and other highway shields were of limited use, as they appeared to only display numeric values. Therefore I stayed with the highway-symbol:hbox, box and oval symbols.

Am 01.08.2009 5:09 Uhr schrieb Clinton Gladstone:
On Jul 31, 2009, at 19:54, Alexander Wittig wrote
So I did some research and I think the problem is that not all of the "magic" symbols in src/uk/me/parabola/mkgmap/osmstyle/actions/HighwaySymbolFilter.java are available on the unit. Also they are named wrongly for this unit.
Just out of interest, have you tried using the --latin1 option when you compile your map?
I did not. If I do, the symbols appear correctly. I'm not familiar with neither the Garmin encoding nor mkgmap's handling of it, but would it be possible to add the codes for the symbols to the names in a way that they work with both 6bit and 8bit encoding? Alexander

Hi
I did not. If I do, the symbols appear correctly. I'm not familiar with neither the Garmin encoding nor mkgmap's handling of it, but would it be possible to add the codes for the symbols to the names in a way that they work with both 6bit and 8bit encoding?
Sure it just looks like a bug. I've just commited a fix, try version r1116 and see if that is any better. ..Steve

Am 02.08.2009 15:16 Uhr schrieb Steve Ratcliffe:
I did not. If I do, the symbols appear correctly. I'm not familiar with neither the Garmin encoding nor mkgmap's handling of it, but would it be possible to add the codes for the symbols to the names in a way that they work with both 6bit and 8bit encoding?
Sure it just looks like a bug. I've just commited a fix, try version r1116 and see if that is any better.
Great, thanks. Now it works with and without --latin1. Alexander
participants (3)
-
Alexander Wittig
-
Clinton Gladstone
-
Steve Ratcliffe