Hello, the style-file called "lines" contains something like this: highway=secondary {name '${ref|highway-symbol:oval} ${name}' | '${ref|highway-symbol:oval}' | '${name}' } Can you explain me how this should work? I would expect to see somewhere the name of the street, but in Mapsource you can only see the ref of the street (as tooltip holding the mouse pointer over the street). Also the etrex shows me routing information like "ref to ref", but no street name. I think in Germany it's a good idea to show routing information only as ref for highway=motorway and highway=primary. I have never seen the ref for the other streets like K39, L273 and so on at the road signs. Thanks for helping. Ralf
0> In article <925e75ca0910240630g5615dc30w826a2f2f8976d344@mail.gmail.com>, 0> Ralf Reimann <URL:mailto:ralrei@gmx.de> ("Ralf") wrote: Ralf> the style-file called "lines" contains something like this: Ralf> highway=secondary {name '${ref|highway-symbol:oval} ${name}' | Ralf> '${ref|highway-symbol:oval}' | '${name}' } Ralf> Ralf> Can you explain me how this should work? The above means: * If the highway has both 'ref' and 'name' tags, give it a name made of the 'ref' value in an oval box, followed by the 'name' value; else * if the highway has a 'ref' tag, give it a name made of the 'ref' value in an oval box; else * if the highway has a 'name' tag, give it a name made of the 'name' value. Ralf> I would expect to see somewhere the name of the street, but in Ralf> Mapsource you can only see the ref of the street (as tooltip Ralf> holding the mouse pointer over the street). Also the etrex shows Ralf> me routing information like "ref to ref", but no street name. Are you using the default style? If you're using your own style, then perhaps you have another 'name' rule that is overriding this one? It can be quite difficult to see which rules are in effect, unfortunately. I'm not using the default style, but this section is the same in mine, and I do see both ref and name in directions on the eTrex. Ralf> I think in Germany it's a good idea to show routing information Ralf> only as ref for highway=motorway and highway=primary. I have Ralf> never seen the ref for the other streets like K39, L273 and so on Ralf> at the road signs. If you want that (ref but no name), then it's easy to change your lines style thus: /-------- | highway=motorway {name '${ref|highway-symbol:hbox} ${name}' } | highway=trunk {name '${ref|highway-symbol:hbox} ${name}' } | highway=primary {name '${ref|highway-symbol:box} ${name}' } \-------- Does that help?
Toby Speight wrote: The above means:
* If the highway has both 'ref' and 'name' tags, give it a name made of the 'ref' value in an oval box, followed by the 'name' value; else
I understood it in this way, but it doesn't do this. I looked for a lot of primaries and secondaries and all of them are named only by there ref.
Are you using the default style? If you're using your own style, then
Yes I'm usind the default style. I changed nothing.
If you want that (ref but no name), then it's easy to change your lines style thus: /-------- | highway=motorway {name '${ref|highway-symbol:hbox} ${name}' } | highway=trunk {name '${ref|highway-symbol:hbox} ${name}' } | highway=primary {name '${ref|highway-symbol:box} ${name}' } \--------
Sorry, I'm confused. Above you told me this is how to combine ref and name. Can you test it please in Mapsource at the following location? http://www.openstreetmap.org/?lat=51.5916&lon=6.5342&zoom=14&layers=B000FTF Holding the mouse pointer over the streets shows me the name of the street like this: B 57, B 58, K 22, Bönninger Strasse Create a short routing for testing the routing instructions:
From B57 to B58 it tells me: Turn right to B58 (no street name) From B57 to K22 it tells me: Turn left to K22 (no street name) From B57 to Bönninger Straße tells me: Turn left to Bönninger Straße ( but there is no ref stored in the osm data)
Greetings, Ralf
On Oct 25, 2009, at 9:31, Ralf Reimann wrote:
Toby Speight wrote:
The above means: * If the highway has both 'ref' and 'name' tags, give it a name made of the 'ref' value in an oval box, followed by the 'name' value; else
I understood it in this way, but it doesn't do this. I looked for a lot of primaries and secondaries and all of them are named only by there ref.
Are you doing this in MapSource or on your GPS unit? I noticed that MapSource will only display the first part of the name, which is used in the highway shield (for example B57 or B58), but when I view the same streets on my eTrex, cursoring over the area gives me the full name (B58 Weseler Strasse). (If this doesn't work for you, what GPS unit are you using?) I strongly suspect that the MapSource display issue results from the "highway-symbol:hbox" part of the style, which inserts the graphical highway "shield" into the map. I have noted that other maps, produced by cgpsmapper, do not seem to have this limitation. It could be that we need to insert another "magic byte" into the name. Cheers.
Clinton Gladstone wrote: Are you doing this in MapSource or on your GPS unit? I noticed that
MapSource will only display the first part of the name, which is used in the highway shield (for example B57 or B58), but when I view the same streets on my eTrex, cursoring over the area gives me the full name (B58 Weseler Strasse). (If this doesn't work for you, what GPS unit are you using?)
You are right. On my Etrex Legend HCx it shows (B58 Weseler Strasse) when cursoring over the street. In Mapsource 6.15.6 it shows only (B 58). But I tested again the routing instructions on my etrex. Turning in any street with a highway-symbol assigned tells me only to turn right or left to the ref (no street name). Is it in the Garmin City-Navigator the same? Ralf
On Oct 25, 2009, at 17:27, Ralf Reimann wrote:
You are right. On my Etrex Legend HCx it shows (B58 Weseler Strasse) when cursoring over the street. In Mapsource 6.15.6 it shows only (B 58).
But I tested again the routing instructions on my etrex. Turning in any street with a highway-symbol assigned tells me only to turn right or left to the ref (no street name). Is it in the Garmin City-Navigator the same?
Hm... City-Navigator seemed to be kind of weird. For example, B58 is only referred to as B58, even when I put the cursor over it. On the other hand, the cursor displayed either "B57" or "<housenumber> Xantener Strasse". So it looks like in this region Garmin labelled the major roads with just the references (B58, B57), but then in some cases added address information with the street name. The routing display seems to prefer the Street names though ("Right on Weseler Strasse"). (I tested this on a Nüvi, as I don't have Garmin's City Navigator on my eTrex.) Cheers.
Hi, Clinton
I strongly suspect that the MapSource display issue results from the "highway-symbol:hbox" part of the style, which inserts the graphical highway "shield" into the map. I have noted that other maps, produced by cgpsmapper, do not seem to have this limitation. It could be that we need to insert another "magic byte" into the name.
Yes, maps build with cgpsmapper don't have this limitation. As i remember we're talking about it in this thread: "[mkgmap-dev] Handling of Garmin magic label codes (highwayshields etc.) differs from mp-format input to osm-format ?" The way mkgmap handles label codes like "~[0x06]B58 ~[0x1f]Weseler Strasse" differs if the input is in Mp-Format or in osm-Format. You told me the trick to isert e.g. this "1F" as real hex value direct into the lines style-file. This works, but indeed it would be better if mkmap could also handle this type of labels if the data input is in osm-format. cheers Gert
On Oct 25, 2009, at 19:28, Gert Münzel wrote:
You told me the trick to isert e.g. this "1F" as real hex value direct into the lines style-file. This works, but indeed it would be better if mkmap could also handle this type of labels if the data input is in osm-format.
Yes, I was just about to test this. The documentation on the separation codes in the cGPSmapper manual is a little vague. What effect, exactly does the 0x1f code have? Cheers.
Hi, Clinton, sorry for taking long time to answer but i have spent some hours in testing this label stuff. Clinton Gladstone wrotes:
What effect, exactly does the 0x1f code have? Sorry, I can only tell you my observations. dependending on the zoom level on GPS , the first + second part of the label will be shown. On my 60csx until 200m only the label is visible. In Mapsource allways only the first part is visible. Only by wiping over with the mouse cursor, you see the full name. Ex. "~[0x06]B58 ~[0x1f]Weseler Strasse" First "B58" is visible, later also the second part "Weseler Strasse" will be shown on the map. Both parts will be used by the turn instructions like "Left to B58 Weseler Strasse".
By playing with the label i found one thing: As example(without "1F" magic code, but the same thing occurs if there is an "1F" in the label ) label in osm-format data file <tag k="ref" v="B58" /> <tag k="name" v="Weseler Strasse" /> results in img file in: 0006 4235 3820 5745 5345 4C45 5220 5354 5241 5353 4500 4235 38 B 5 8 W E S E L E R S T R A S S E B 5 8 The second "B58" must be out of the ref, because allways i changed it, both were changed. This give you turn instruction like "Left to B58" In Mapsource wipping over for fullname doesn't work. On GPS wipping over for fullname works.(without "1F" magic code in this example full name is visble anayway by zooming) Marking the object with cursor and pushing ENTER-button only shows "B58" ony the description page. mp-format label ~[0x06]B58 WESELER STRASSE results in img file in: 0006 4235 3820 5745 5345 4C45 5220 5354 5241 5353 45 B 5 8 W E S E L E R S T R A S S E This give you turn instruction like "Left to B58 Weseler Strasse" In Mapsource wipping over for fullname works. On GPS wipping over for fullname works.(without "1F" magic code in this example full name is visble anayway by zooming) Marking the object with cursor and pushing ENTER-button shows the fullname "B58 Weseler Strasse" ony the description page. And this is is exactly the result i became by compiling the mp-format file with cgpmapper. If a ref-tag is given in the osm-file, allways an extra label is produced in the img. I think this causes the differences e.g. in turn instructions. Before i tought is was the missing "1F" but the manual injection doesn't solve this. cheers Gert
On Tue, Oct 27, 2009 at 3:26 PM, Gert Münzel <Gert.Muenzel@netcologne.de> wrote:
If a ref-tag is given in the osm-file, allways an extra label is produced in the img. I think this causes the differences e.g. in turn instructions. Before i tought is was the missing "1F" but the manual injection doesn't solve this.
Thanks for checking this. This also confirms what I found. I discovered that the second label appears to be the one used in routing directions and displayed on "mouse over" events. I made a modification which allows you to set the second label using the style file. This corrects the problem that only the ref is displayed in routing directions, which is what I think you and Ralf would like. It definitely makes the routing directions more friendly. I'll send out a patch for this shortly. Cheers.
0> In article <925e75ca0910250131m661f550qbf04efc18e3121b7@mail.gmail.com>, 0> Ralf Reimann <URL:mailto:ralrei@gmx.de> ("Ralf") wrote: Ralf> Toby Speight wrote:
If you want that (ref but no name), then it's easy to change your lines style thus: /-------- | highway=motorway {name '${ref|highway-symbol:hbox} ${name}' } | highway=trunk {name '${ref|highway-symbol:hbox} ${name}' } | highway=primary {name '${ref|highway-symbol:box} ${name}' } \--------
Ralf> Sorry, I'm confused. Above you told me this is how to combine ref Ralf> and name. Oops, sorry - I meant to chop out the ' ${name}' bit, but missed slightly. Ralf> Can you test it please in Mapsource at the following location? I have an eTrex, not Mapsource. Sorry.
participants (4)
-
Clinton Gladstone -
Gert Münzel -
Ralf Reimann -
Toby Speight