Hi all, the default style contains these rules for roundabouts: # Roundabouts junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=3 road_speed=2 resolution 18] junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 19] junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 20] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22] The wanted effect is that the Garmin device/software produces hints like "enter roundabout" or "Take the 2nd right onto" ... The disadvantage is that the roundabout is not rendered. I replaced all the above rules by junction=roundabout & highway=* [0x0c road_class=0 road_speed=0 resolution 24 continue] I tried this with car + bicycle routing and it seems to give the expected results (routing hints and rendered roads). Also the --check-roundabouts option doesn't complain. Alternative might be to keep the distinction of road types for better time estimation, important point is that "resoltion 24 continue " is used. Comments? Gerd
Gerd, I have used such approach for my bicycle maps and received quite a few negative reports with two routable lines on top of each other, especially near and at roundabouts. A lot of devices will crash (completely shut down) so I'd not recommend this. In Lambertus' generic new we use an invisible 0x0c line in the typ file and after the roundabout rules the junctions are made unroutable so we don't have two routable lines on top of each other. https://github.com/ligfietser/mkgmap-style-sheets/blob/master/styles/generic... ________________________________ Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <GPetermann_muenchen@hotmail.com> Verzonden: zondag 12 februari 2017 03:39:45 Aan: mkgmap-dev@lists.mkgmap.org.uk Onderwerp: [mkgmap-dev] roundabouts Hi all, the default style contains these rules for roundabouts: # Roundabouts junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=3 road_speed=2 resolution 18] junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 19] junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 20] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22] The wanted effect is that the Garmin device/software produces hints like "enter roundabout" or "Take the 2nd right onto" ... The disadvantage is that the roundabout is not rendered. I replaced all the above rules by junction=roundabout & highway=* [0x0c road_class=0 road_speed=0 resolution 24 continue] I tried this with car + bicycle routing and it seems to give the expected results (routing hints and rendered roads). Also the --check-roundabouts option doesn't complain. Alternative might be to keep the distinction of road types for better time estimation, important point is that "resoltion 24 continue " is used. Comments? Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi ligfietser, in fact the OFM lite style was the reason that I tried to find a better solution. I noticed some strange routing results for this roundabout: https://www.openstreetmap.org/way/8325782 coming from north (e.g. node 76474542 going south (to node 1601722162). with setting "OFM racing bike". With other bike types routing looks good. The style creates several lines for the roundabout (not sure about the order), two are routable: 0x5 with road_class=1 road_speed=3 toll=no 0xc with road_class=1 road_speed=1 toll=yes 0x10007 0x10105 I think the at least the rule junction=roundabout {set access=no} doesn't work as you expect. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von lig fietser <ligfietser@hotmail.com> Gesendet: Sonntag, 12. Februar 2017 12:59:31 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] roundabouts Gerd, I have used such approach for my bicycle maps and received quite a few negative reports with two routable lines on top of each other, especially near and at roundabouts. A lot of devices will crash (completely shut down) so I'd not recommend this. In Lambertus' generic new we use an invisible 0x0c line in the typ file and after the roundabout rules the junctions are made unroutable so we don't have two routable lines on top of each other. https://github.com/ligfietser/mkgmap-style-sheets/blob/master/styles/generic... ________________________________ Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <GPetermann_muenchen@hotmail.com> Verzonden: zondag 12 februari 2017 03:39:45 Aan: mkgmap-dev@lists.mkgmap.org.uk Onderwerp: [mkgmap-dev] roundabouts Hi all, the default style contains these rules for roundabouts: # Roundabouts junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=3 road_speed=2 resolution 18] junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 19] junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 20] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22] The wanted effect is that the Garmin device/software produces hints like "enter roundabout" or "Take the 2nd right onto" ... The disadvantage is that the roundabout is not rendered. I replaced all the above rules by junction=roundabout & highway=* [0x0c road_class=0 road_speed=0 resolution 24 continue] I tried this with car + bicycle routing and it seems to give the expected results (routing hints and rendered roads). Also the --check-roundabouts option doesn't complain. Alternative might be to keep the distinction of road types for better time estimation, important point is that "resoltion 24 continue " is used. Comments? Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, IMO you won't get good routing for cars, if you set all roundabouts to class 0. My understanding is, that roads with road_class 4 and 3 should create a proper, continuous network. If you break network at roundabouts, long distance routing will suffer. I doubt you will get a nice rendering with all cases. Probably a roundabout will be still visible below road type 0x06. But if you are satisfied with rendering, I suggest to use pairs: roundabout with proper road_class/road_speed and non-routable line in range 0x108xx, these looks like standard roads: 0x10800 == 0x01, 0x10801 == 0x02 and so on. -- Best regards, Andrzej
Hi Andrzej, good points. I'll try your suggestions. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Sonntag, 12. Februar 2017 13:56:32 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] roundabouts Hi Gerd, IMO you won't get good routing for cars, if you set all roundabouts to class 0. My understanding is, that roads with road_class 4 and 3 should create a proper, continuous network. If you break network at roundabouts, long distance routing will suffer. I doubt you will get a nice rendering with all cases. Probably a roundabout will be still visible below road type 0x06. But if you are satisfied with rendering, I suggest to use pairs: roundabout with proper road_class/road_speed and non-routable line in range 0x108xx, these looks like standard roads: 0x10800 == 0x01, 0x10801 == 0x02 and so on. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 02/12/2017 12:59 PM, lig fietser wrote:
I have used such approach for my bicycle maps and received quite a few negative reports with two routable lines on top of each other, especially near and at roundabouts. A lot of devices will crash (completely shut down) so I'd not recommend this.
In my style I avoid this problem by having a routable, but invisible line 0x0c and different visible but not routable lines 0x11e04-0x11e07 on top: junction=roundabout & highway=trunk [0x11e04 level 5 continue] junction=roundabout & highway=trunk [0x0c road_class=1 road_speed=2 resolution 18] junction=roundabout & highway=primary [0x11e04 level 5 continue] junction=roundabout & highway=primary [0x0c road_class=1 road_speed=2 resolution 19] junction=roundabout & highway=secondary [0x11e05 level 4 continue] junction=roundabout & highway=secondary [0x0c road_class=1 road_speed=2 resolution 20] junction=roundabout & highway=tertiary [0x11e06 level 3 continue] junction=roundabout & highway=tertiary [0x0c road_class=1 road_speed=2 resolution 21] junction=roundabout & highway=unclassified [0x11e07 level 3 continue] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=2 resolution 21] junction=roundabout [0x11e07 level 3 continue] junction=roundabout [0x0c road_class=1 road_speed=2 resolution 22] 0x11e04 looks exactly like the normal highway=trunk line 0x16. Works nicely. Now that I think of it, I just might omit the "resolution" for 0x0c, it's not visible anyway.
Hi Ralf, I also thought that this would be the best solution, so I tried to modify the OFM lite style like that, but without success. My knowledge about typ files is near zero :-( Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ralf Kleineisel <ralf@kleineisel.de> Gesendet: Sonntag, 12. Februar 2017 13:40:58 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] roundabouts On 02/12/2017 12:59 PM, lig fietser wrote:
I have used such approach for my bicycle maps and received quite a few negative reports with two routable lines on top of each other, especially near and at roundabouts. A lot of devices will crash (completely shut down) so I'd not recommend this.
In my style I avoid this problem by having a routable, but invisible line 0x0c and different visible but not routable lines 0x11e04-0x11e07 on top: junction=roundabout & highway=trunk [0x11e04 level 5 continue] junction=roundabout & highway=trunk [0x0c road_class=1 road_speed=2 resolution 18] junction=roundabout & highway=primary [0x11e04 level 5 continue] junction=roundabout & highway=primary [0x0c road_class=1 road_speed=2 resolution 19] junction=roundabout & highway=secondary [0x11e05 level 4 continue] junction=roundabout & highway=secondary [0x0c road_class=1 road_speed=2 resolution 20] junction=roundabout & highway=tertiary [0x11e06 level 3 continue] junction=roundabout & highway=tertiary [0x0c road_class=1 road_speed=2 resolution 21] junction=roundabout & highway=unclassified [0x11e07 level 3 continue] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=2 resolution 21] junction=roundabout [0x11e07 level 3 continue] junction=roundabout [0x0c road_class=1 road_speed=2 resolution 22] 0x11e04 looks exactly like the normal highway=trunk line 0x16. Works nicely. Now that I think of it, I just might omit the "resolution" for 0x0c, it's not visible anyway. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 02/12/2017 01:45 PM, Gerd Petermann wrote:
I also thought that this would be the best solution, so I tried to modify the OFM lite style like that, but without success. My knowledge about typ files is near zero :-(
You don't need a lot of knowledge to copy a polyline definition with Typviewer,
Ralf's approach is better, if I would start rebuild my map I would choose to do the same, but it will take too much time to rebuilt my map from scratch. @Gerd, I see now that setting junction=roundabout {set access=no} after the roundabout rules doesn't work at all, do you have any explanation why? ________________________________
Hi lig fietser, hmm, maybe I was mislead by the results of GPSMapEdit. It seems that it shows some defaults when a line with a routable type is not in the NOD file. So, only the type 0xc line is added to the NOD file, but we also know that it is not good to use routable types without a road_speed or road_class attribute. Maybe that explains the problems? Note the warnings from check-styles: Warning: routable type 0x08 is used for non-routable line with level 0. This may break routing. Style file lines, line 175 Warning: routable type 0x16 is used for non-routable line with level 0. This may break routing. Style file lines, line 232 Warning: routable type 0x060 is used for non-routable line with level 0. This may break routing. Style file lines, line 243. Type is overlaid with 0x06 Warning: routable type 0x050 is used for non-routable line with level 0. This may break routing. Style file lines, line 250. Type is overlaid with 0x05 Warning: routable type 0x040 is used for non-routable line with level 0. This may break routing. Style file lines, line 255. Type is overlaid with 0x04 Warning: routable type 0x030 is used for non-routable line with level 0. This may break routing. Style file lines, line 261. Type is overlaid with 0x03 Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von lig fietser <ligfietser@hotmail.com> Gesendet: Sonntag, 12. Februar 2017 13:48:56 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] roundabouts Ralf's approach is better, if I would start rebuild my map I would choose to do the same, but it will take too much time to rebuilt my map from scratch. @Gerd, I see now that setting junction=roundabout {set access=no} after the roundabout rules doesn't work at all, do you have any explanation why? ________________________________
Hi Gerd, Regarding routable types without a road_speed or road_class attribute: this can create other problems when searching for an address along that street, routing could cause straight lines on the device. Since it is unlikely that there are any addresses on a roundabouts you can ignore those warnings. Those crashes that were reported were related to my Style where I have used 0x02 for cycling routes on top of routable highways. Both lines were routable and this could crash the device, in particular at roundabouts where three routable lines were used (02, 0c and normal highways). ________________________________ Hi lig fietser, hmm, maybe I was mislead by the results of GPSMapEdit. It seems that it shows some defaults when a line with a routable type is not in the NOD file. So, only the type 0xc line is added to the NOD file, but we also know that it is not good to use routable types without a road_speed or road_class attribute. Maybe that explains the problems? Note the warnings from check-styles: Warning: routable type 0x08 is used for non-routable line with level 0. This may break routing. Style file lines, line 175 Warning: routable type 0x16 is used for non-routable line with level 0. This may break routing. Style file lines, line 232 Warning: routable type 0x060 is used for non-routable line with level 0. This may break routing. Style file lines, line 243. Type is overlaid with 0x06 Warning: routable type 0x050 is used for non-routable line with level 0. This may break routing. Style file lines, line 250. Type is overlaid with 0x05 Warning: routable type 0x040 is used for non-routable line with level 0. This may break routing. Style file lines, line 255. Type is overlaid with 0x04 Warning: routable type 0x030 is used for non-routable line with level 0. This may break routing. Style file lines, line 261. Type is overlaid with 0x03 Gerd <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev>
Hi Gerd, just have tested following version: # Roundabouts junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=4 road_speed=2 resolution 24 continue] junction=roundabout & (highway=trunk | highway=trunk_link) [0x10801 resolution 18] junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 24 continue] junction=roundabout & (highway=primary | highway=primary_link) [0x10802 resolution 19] junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 24 continue] junction=roundabout & (highway=secondary | highway=secondary_link) [0x10803 resolution 20] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 24 continue] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x10804 resolution 21] junction=roundabout & highway=minor [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22] This adds secondary line for roundabout defined as trunk, primary, secondary and tertiary only. I think other types will work well enough with standard rendering. Maybe even tertiary can be standard. Map looks ok, see attached picture with roundabout rendered as primary (no TYP). Side note: this is example, where style-option can be used. You can make this extra lines active in style only when a proper style-option is defined. -- Best regards, Andrzej
Hi Andrzej, yes, works fine without typ file on Mapsource, Basecamp and my Oregon 600 . I think the default 0xc type looks like 0x06, so we need the overlay for tertiary (0x05). The only one still looking bad is highway=service (0x07). I tried to add extra rules for it but It seems that 0x10806 doesn't work. Maybe you have another idea? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Sonntag, 12. Februar 2017 20:15:59 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] roundabouts Hi Gerd, just have tested following version: # Roundabouts junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=4 road_speed=2 resolution 24 continue] junction=roundabout & (highway=trunk | highway=trunk_link) [0x10801 resolution 18] junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 24 continue] junction=roundabout & (highway=primary | highway=primary_link) [0x10802 resolution 19] junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 24 continue] junction=roundabout & (highway=secondary | highway=secondary_link) [0x10803 resolution 20] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 24 continue] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x10804 resolution 21] junction=roundabout & highway=minor [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22] This adds secondary line for roundabout defined as trunk, primary, secondary and tertiary only. I think other types will work well enough with standard rendering. Maybe even tertiary can be standard. Map looks ok, see attached picture with roundabout rendered as primary (no TYP). Side note: this is example, where style-option can be used. You can make this extra lines active in style only when a proper style-option is defined. -- Best regards, Andrzej
I don't see the benefit of this, on my devices (oregon 600, old Nüvi) without a typ file, 0x0c is rendered as a fat orange line drawn on top of the 0x108.. types. In Mapsource it works fine, I agree. AFAIK there is no way to make 0x0c invisible without a typ file. I've tried to skip resolution but this didnt work either, it is still rendered. ________________________________ Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <GPetermann_muenchen@hotmail.com> Verzonden: maandag 13 februari 2017 00:42:30 Aan: Development list for mkgmap Onderwerp: Re: [mkgmap-dev] roundabouts Hi Andrzej, yes, works fine without typ file on Mapsource, Basecamp and my Oregon 600 . I think the default 0xc type looks like 0x06, so we need the overlay for tertiary (0x05). The only one still looking bad is highway=service (0x07). I tried to add extra rules for it but It seems that 0x10806 doesn't work. Maybe you have another idea? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Sonntag, 12. Februar 2017 20:15:59 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] roundabouts Hi Gerd, just have tested following version: # Roundabouts junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=4 road_speed=2 resolution 24 continue] junction=roundabout & (highway=trunk | highway=trunk_link) [0x10801 resolution 18] junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 24 continue] junction=roundabout & (highway=primary | highway=primary_link) [0x10802 resolution 19] junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 24 continue] junction=roundabout & (highway=secondary | highway=secondary_link) [0x10803 resolution 20] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 24 continue] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x10804 resolution 21] junction=roundabout & highway=minor [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22] This adds secondary line for roundabout defined as trunk, primary, secondary and tertiary only. I think other types will work well enough with standard rendering. Maybe even tertiary can be standard. Map looks ok, see attached picture with roundabout rendered as primary (no TYP). Side note: this is example, where style-option can be used. You can make this extra lines active in style only when a proper style-option is defined. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Here is a test image from Mapsource (above) and Oregon 600 (below). Both without typ file. I've created 10 lines with the following test style: highway=1 {name '10801'} [0x10801 resolution 18 continue] highway=2 {name '10802'} [0x10802 resolution 18 continue] highway=3 {name '10803'} [0x10803 resolution 18 continue] highway=4 {name '10804'} [0x10804 resolution 18 continue] highway=5 {name '10805'} [0x10805 resolution 18 continue] highway=6 {name '10806'} [0x10806 resolution 18 continue] highway=7 {name '10807'} [0x10807 resolution 18 continue] highway=8 {name '10808'} [0x10808 resolution 18 continue] highway=9 {name '10809'} [0x10809 resolution 18 continue] highway=10 {name '10800'} [0x10800 resolution 18 continue] highway=* [0x0c resolution 24] If you zoom out or take a low resolution, you will see a bigger distinction between the types. Once you zoom in at the highest level, all types are overruled with 0x0c on my Oregon, and in Mapsource with something like 10805 (unclassified?). Highways with a major class will be rendered first here. I haven't tested other devices, it would't surprise me if they show a different behaviour.
I did not see that with real OSM data. Please try to add junction=roundabout because this has an effect on the NOD file. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von lig fietser <ligfietser@hotmail.com> Gesendet: Montag, 13. Februar 2017 12:31:13 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] roundabouts Here is a test image from Mapsource (above) and Oregon 600 (below). Both without typ file. I've created 10 lines with the following test style: highway=1 {name '10801'} [0x10801 resolution 18 continue] highway=2 {name '10802'} [0x10802 resolution 18 continue] highway=3 {name '10803'} [0x10803 resolution 18 continue] highway=4 {name '10804'} [0x10804 resolution 18 continue] highway=5 {name '10805'} [0x10805 resolution 18 continue] highway=6 {name '10806'} [0x10806 resolution 18 continue] highway=7 {name '10807'} [0x10807 resolution 18 continue] highway=8 {name '10808'} [0x10808 resolution 18 continue] highway=9 {name '10809'} [0x10809 resolution 18 continue] highway=10 {name '10800'} [0x10800 resolution 18 continue] highway=* [0x0c resolution 24] If you zoom out or take a low resolution, you will see a bigger distinction between the types. Once you zoom in at the highest level, all types are overruled with 0x0c on my Oregon, and in Mapsource with something like 10805 (unclassified?). Highways with a major class will be rendered first here. I haven't tested other devices, it would't surprise me if they show a different behaviour.
Oops, just recognized that you sample doesn't create a NOD file. No idea if that is important. ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Montag, 13. Februar 2017 12:42:36 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] roundabouts I did not see that with real OSM data. Please try to add junction=roundabout because this has an effect on the NOD file. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von lig fietser <ligfietser@hotmail.com> Gesendet: Montag, 13. Februar 2017 12:31:13 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] roundabouts Here is a test image from Mapsource (above) and Oregon 600 (below). Both without typ file. I've created 10 lines with the following test style: highway=1 {name '10801'} [0x10801 resolution 18 continue] highway=2 {name '10802'} [0x10802 resolution 18 continue] highway=3 {name '10803'} [0x10803 resolution 18 continue] highway=4 {name '10804'} [0x10804 resolution 18 continue] highway=5 {name '10805'} [0x10805 resolution 18 continue] highway=6 {name '10806'} [0x10806 resolution 18 continue] highway=7 {name '10807'} [0x10807 resolution 18 continue] highway=8 {name '10808'} [0x10808 resolution 18 continue] highway=9 {name '10809'} [0x10809 resolution 18 continue] highway=10 {name '10800'} [0x10800 resolution 18 continue] highway=* [0x0c resolution 24] If you zoom out or take a low resolution, you will see a bigger distinction between the types. Once you zoom in at the highest level, all types are overruled with 0x0c on my Oregon, and in Mapsource with something like 10805 (unclassified?). Highways with a major class will be rendered first here. I haven't tested other devices, it would't surprise me if they show a different behaviour. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I also have looked at real OSM data, it renders the same, unfortunately. ________________________________ Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <GPetermann_muenchen@hotmail.com> Verzonden: maandag 13 februari 2017 03:44:09 Aan: Development list for mkgmap Onderwerp: Re: [mkgmap-dev] roundabouts Oops, just recognized that you sample doesn't create a NOD file. No idea if that is important. ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Montag, 13. Februar 2017 12:42:36 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] roundabouts I did not see that with real OSM data. Please try to add junction=roundabout because this has an effect on the NOD file. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von lig fietser <ligfietser@hotmail.com> Gesendet: Montag, 13. Februar 2017 12:31:13 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] roundabouts Here is a test image from Mapsource (above) and Oregon 600 (below). Both without typ file. I've created 10 lines with the following test style: highway=1 {name '10801'} [0x10801 resolution 18 continue] highway=2 {name '10802'} [0x10802 resolution 18 continue] highway=3 {name '10803'} [0x10803 resolution 18 continue] highway=4 {name '10804'} [0x10804 resolution 18 continue] highway=5 {name '10805'} [0x10805 resolution 18 continue] highway=6 {name '10806'} [0x10806 resolution 18 continue] highway=7 {name '10807'} [0x10807 resolution 18 continue] highway=8 {name '10808'} [0x10808 resolution 18 continue] highway=9 {name '10809'} [0x10809 resolution 18 continue] highway=10 {name '10800'} [0x10800 resolution 18 continue] highway=* [0x0c resolution 24] If you zoom out or take a low resolution, you will see a bigger distinction between the types. Once you zoom in at the highest level, all types are overruled with 0x0c on my Oregon, and in Mapsource with something like 10805 (unclassified?). Highways with a major class will be rendered first here. I haven't tested other devices, it would't surprise me if they show a different behaviour. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi, I observe the same. For roundabout as primary road it works well, but not for roundabout as minor road. I have noticed an unexpected outcome. Map is a bit smaller, when using multiple objects for roundabouts - double lines at layer 0 and non-routable lines at upper layers. I would expect opposite effect. Is there any reason, that routable line 0x0C on levels 1 and up takes more memory, than non-routable line 0x108xx? Looks suspicious to me. -- Best regards, Andrzej
Hi Andrzej, the only thing that comes to my mind is that extended types are stored in a different part of the map and therefore don't fill an area with limited size. The result might be fewer splits of sub regions. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Montag, 13. Februar 2017 16:05:33 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] roundabouts Hi, I observe the same. For roundabout as primary road it works well, but not for roundabout as minor road. I have noticed an unexpected outcome. Map is a bit smaller, when using multiple objects for roundabouts - double lines at layer 0 and non-routable lines at upper layers. I would expect opposite effect. Is there any reason, that routable line 0x0C on levels 1 and up takes more memory, than non-routable line 0x108xx? Looks suspicious to me. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I'm sorry for the late message on this thread, but I could not read list messages last weeks and am now trying to update. First of all, I want to mention up to now I didn't have problems using rules similar to default ones on several devices, MapSource and BaseCamp. It seems Ticker and Chris didn't either, so I ask if you could give more details about the problem. Is it device specific? Regarding roundabouts thread it seems discussion was not finished but after a few days there's a commit (3809). Am I missing something? El 13/02/17 a las 16:21, Gerd Petermann escribió:
Hi Andrzej,
the only thing that comes to my mind is that extended types are stored in a different part of the map and therefore don't fill an area with limited size. The result might be fewer splits of sub regions.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Montag, 13. Februar 2017 16:05:33 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] roundabouts
Hi,
I observe the same. For roundabout as primary road it works well, but not for roundabout as minor road.
I have noticed an unexpected outcome. Map is a bit smaller, when using multiple objects for roundabouts - double lines at layer 0 and non-routable lines at upper layers. I would expect opposite effect. Is there any reason, that routable line 0x0C on levels 1 and up takes more memory, than non-routable line 0x108xx? Looks suspicious to me.
-- Best regards, Andrzej
Hi Carlos, yes, I got a PM from Minko which confirmed that the changes are an improvement in most cases. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Montag, 6. März 2017 21:04:17 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] roundabouts I'm sorry for the late message on this thread, but I could not read list messages last weeks and am now trying to update. First of all, I want to mention up to now I didn't have problems using rules similar to default ones on several devices, MapSource and BaseCamp. It seems Ticker and Chris didn't either, so I ask if you could give more details about the problem. Is it device specific? Regarding roundabouts thread it seems discussion was not finished but after a few days there's a commit (3809). Am I missing something? El 13/02/17 a las 16:21, Gerd Petermann escribió:
Hi Andrzej,
the only thing that comes to my mind is that extended types are stored in a different part of the map and therefore don't fill an area with limited size. The result might be fewer splits of sub regions.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Montag, 13. Februar 2017 16:05:33 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] roundabouts
Hi,
I observe the same. For roundabout as primary road it works well, but not for roundabout as minor road.
I have noticed an unexpected outcome. Map is a bit smaller, when using multiple objects for roundabouts - double lines at layer 0 and non-routable lines at upper layers. I would expect opposite effect. Is there any reason, that routable line 0x0C on levels 1 and up takes more memory, than non-routable line 0x108xx? Looks suspicious to me.
-- Best regards, Andrzej
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi With these default rules, my device (Etrex Legend HCx) renders roundabouts nicely (dark medium line, looks same as 0x04/0x05 line) and has a suitable 'hover' label. No typ file. Ticker On Sun, 2017-02-12 at 11:39 +0000, Gerd Petermann wrote:
Hi all,
the default style contains these rules for roundabouts: # Roundabouts junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=3 road_speed=2 resolution 18] junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 19] junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 20] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22]
The wanted effect is that the Garmin device/software produces hints like "enter roundabout" or "Take the 2nd right onto" ... The disadvantage is that the roundabout is not rendered.
I replaced all the above rules by junction=roundabout & highway=* [0x0c road_class=0 road_speed=0 resolution 24 continue]
I tried this with car + bicycle routing and it seems to give the expected results (routing hints and rendered roads). Also the --check-roundabouts option doesn't complain.
Alternative might be to keep the distinction of road types for better time estimation, important point is that "resoltion 24 continue " is used.
Comments?
Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am 12.02.2017 um 13:56 schrieb Ticker Berkin:
Hi
With these default rules, my device (Etrex Legend HCx) renders roundabouts nicely (dark medium line, looks same as 0x04/0x05 line) and has a suitable 'hover' label. No typ file.
Ticker
Yes, on my Etrex20 and Nuvi 250 I'm also getting a rendering with the default style. Chris
participants (7)
-
Andrzej Popowski -
Carlos Dávila -
chris66 -
Gerd Petermann -
lig fietser -
Ralf Kleineisel -
Ticker Berkin