mkgmap has a LineMergeFilter but that does not merge the road network. Attached patch performs a merging in the OSM data just before the road network is created. This has the advantage that the source code for the merging is quite easy. Turn restrictions and through routes are considered. I tested some data in germany and got a reduction of 5% to 12% (number of roads). I did not find any improvements but also no downgrades in routing. But I did not test long distance routing (> 600km). I think the merge results can be improved if the access handling and some other parts are moved from source code to the style files. This makes it easier for the merger to say that two roads have the same attributes and can be merged without problems. But that's a task for the future... I have already uploaded a compiled version: http://files.mkgmap.org.uk/detail/148 For anyone who is interested in the code: Please check the tag list (variable flatCompareTags) in the new RoadMerger. This taglist gives all tags that must be equal so that two roads can be merged. Is this list complete? Can I remove some tags from it? Have fun! WanMil
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi WanMil, I think the list should contain all tags which are used in style-files, or are these keys are checked in a seperate way and the list contains only internal tags? Henning Am 27.08.2013 21:31, schrieb WanMil:
For anyone who is interested in the code: Please check the tag list (variable flatCompareTags) in the new RoadMerger. This taglist gives all tags that must be equal so that two roads can be merged. Is this list complete? Can I remove some tags from it?
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32) iQEcBAEBAgAGBQJSHQWfAAoJEPFgsWC7jOeToj4H/1d+pxpMndbepjhkoFHlPgJb EKYQL6jR+HBIImP95vz2+yEHWWUoyz7nJCk3Eqt0+1TMr9AjMRzCqZTcv40TWzKd LvaBV+MBgg4nv94HIWUGi2wxv6nCVkYAJYNw37V9QocBy2N+3DbwAD1g+g3DLdb0 JxdE9dz7gMm4akIqlAO5pR60rAi1NQ3QZdFZv1dQz9fumoZ9qk6BxBV0uOE1/amr 8suSaUFlbosIPTFJ7evbWgN1cI5xW6VK1/U1xxtR3xY4V4Mob8G3pfH7yKVrVhwJ 3GOsHNbtg3kckjnLL7Vgjx1tIszSagHrGr33LeDbeDSiWvAY9UCP/lspKCkzCDo= =X+2q -----END PGP SIGNATURE-----
Hi WanMil, I think the list should contain all tags which are used in style-files, or are these keys are checked in a seperate way and the list contains only internal tags?
Henning
Hi Henning, the list need not contain all tags of the style file because the ways are merged after the style files are processed and before the intermediate garmin objects are created. One simple example: Way 1: highway=motorway,ref=A 1 Way 2: highway=motorway,bridge=yes,ref=A 1 Way 3: highway=motorway,ref=A 1 The three ways are connected (1-2-3). The style file creates for each way a 0x01 garmin motorway and an overlay for the bridge. The 0x01 ways can be merged without considering the tag bridge=yes. Only those tags evaluated by mkgmap internally after the style file processing need to be considered. WanMil
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi WanMil, so you are merging objects with the same Garmin-ID, unless they containing one key of the mentioned list. In this case the list seems to be quite ok. Wasn't there something like mkgmap:street or streetname or am I wrong? As you pointed out already this list should be reduced by access-keys. Henning Am 27.08.2013 22:33, schrieb WanMil:
Hi Henning,
the list need not contain all tags of the style file because the ways are merged after the style files are processed and before the intermediate garmin objects are created.
One simple example: Way 1: highway=motorway,ref=A 1 Way 2: highway=motorway,bridge=yes,ref=A 1 Way 3: highway=motorway,ref=A 1
The three ways are connected (1-2-3). The style file creates for each way a 0x01 garmin motorway and an overlay for the bridge. The 0x01 ways can be merged without considering the tag bridge=yes.
Only those tags evaluated by mkgmap internally after the style file processing need to be considered.
WanMil _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32) iQEcBAEBAgAGBQJSHRBVAAoJEPFgsWC7jOeTJcMIAMYF/WvjU5zJUJsF6eY+TmYF 5rV5ynQVUXkzv24zjn9thoXZ2Duro/3k0gqtSp7UlPQz98n+c1KvABbh3Eoibmp1 5R5qNSgogV5NPdR8tO1NLDje6mo5v6EZrRsb6Y/FCmkcmfpZpKKHOqwitiMguF1r xFtqXOd2jFpKoN6qY0QMx41JLFHBR4J6FEGiq8/tmJrZzfprznjaiFj/E+wVhtrK /5BDYb14bRRHHx82uqxvPE/OCJxyqSYvGWwlVMPipPDxlc/79n3YGUO5FoJo0Nh9 a2hfZvo/T0PfKBUkbRzlNgE9dYfvSd6FN2uvEwKpdBm31UuA6saz6lZf7rrsJcM= =dsmc -----END PGP SIGNATURE-----
Hi, does roads have to have the same post code? I don't know internal representation of these data, but in mp sources single road can have parts with different post code or city/region. Do you check angle at which roads are merged? Imagine a two-way road, which splits into 2 one-way roads before a crossroad. You can get this one-way roads merged. I don't know if this would be a problem for routing, but a weird layout anyway. Or you can get a crossroad where roads can be merged in many configurations. In that case I would prefer to get straight roads after merging. If you merge two roads, that form a turn at a crossover, there could be missing announcement from navigation. This probably depends on angle, but I'm not sure about details. Again, I prefer to merge only roads that goes nearly straight. -- Best regards, Andrzej
Hi Andrzej, thanks for your comments!
Hi,
does roads have to have the same post code? I don't know internal representation of these data, but in mp sources single road can have parts with different post code or city/region.
AFAIK roads cannot have more than one postcode (with the current mkgmap implementation...).
Do you check angle at which roads are merged?
Not yet.
Imagine a two-way road, which splits into 2 one-way roads before a crossroad. You can get this one-way roads merged. I don't know if this would be a problem for routing, but a weird layout anyway.
Yeah, sounds reasonable. I will add that. Which angle do you think is the max angle I should allow? 90, 120, 130, 160? I guess 130 should be allowed.
Or you can get a crossroad where roads can be merged in many configurations. In that case I would prefer to get straight roads after merging.
Sounds also reasonable. That is a slightly bigger change but I probably will add that too.
If you merge two roads, that form a turn at a crossover, there could be missing announcement from navigation. This probably depends on angle, but I'm not sure about details. Again, I prefer to merge only roads that goes nearly straight.
What do you mean with "turn at a crossover"? I am not sure... Can you post an ASCII drawing? WanMil
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A | | D--+--B | | C Merging Center-A and Center B to one road can lead to a situation where you should get a turn left/right message but the device just think its a corner but no crossing. I don't know how Garmin handels merging on intersections. As I remeber correct you said, that they store housenumbers to roadsegments, so I would think that they split the road on intersections. So maybe we shouldn't merge highways, if there are more then two highways containing the same node. Henning Am 28.08.2013 22:07, schrieb WanMil:
If you merge two roads, that form a turn at a crossover, there could be missing announcement from navigation. This probably depends on angle, but I'm not sure about details. Again, I prefer to merge only roads that goes nearly straight.
What do you mean with "turn at a crossover"? I am not sure... Can you post an ASCII drawing?
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32) iQEcBAEBAgAGBQJSHlvHAAoJEPFgsWC7jOeTKmIIALR9tOSFiFOhhdVmITRQnQWZ gyavvBapNitRxSFWn3cpbR32+xtQWp4RCLRRgzLKUVNlMuwWYA+p9CJfok/jH2Hv YsGMKe2wxtu0d486C+ZpjCCmnWlWraVm6PKVz/6wRJ+ZWmGITiBx0iVaTSOfktWQ WzMU6gk/tbV6IQ9rW6F2PnISOsDxZziO83u7I7OjThmoaLARRTYOscA0dikTux3n 40o9ijbPkCHiPchdbkWthWI3dB/NElDh86mKJHw7vuiYl5gf0aYkyGlafKeR5He9 munZlHLqWoeWG6tfUn4ugLBnOUQK9UXj2ZJoeAfuPoJqk3me9MaaWbEmLtu6Zz8= =GURC -----END PGP SIGNATURE-----
Hi,
Which angle do you think is the max angle I should allow? 90, 120, 130, 160? I guess 130 should be allowed.
I'm using 135 for this purpose, which is an arbitrary value. And if node connects only 2 roads, then angle can be ignored.
What do you mean with "turn at a crossover"? I am not sure... Can you post an ASCII drawing?
I don't have any particular example. It was a general notice, that while navigating GPS issue messages that depend on angle between roads and on whether roads are merged or not. I think there could be arrangement where you can hear "keep left/turn left" when not merged and no message after merging. But maybe this is more general problem and there is no reason to deal with it in merging procedure. -- Best regards, Andrzej
Seems to work fine so far (also using maxspeed patch), however I get quite a lot of theese (between 0 to 20 per country): SEVERE (MapBuilder): c:\openmtbmap\maps\64180000.osm.pbf: possible routing problem: road end-points not both coordNodes: ((M5), http://www.openstreetmap.org/browse/way/152908991) (serbia from geofabrik). Dunno really what to do with it.... On 27.08.2013 21:31, WanMil wrote:
mkgmap has a LineMergeFilter but that does not merge the road network.
Attached patch performs a merging in the OSM data just before the road network is created. This has the advantage that the source code for the merging is quite easy. Turn restrictions and through routes are considered.
I tested some data in germany and got a reduction of 5% to 12% (number of roads). I did not find any improvements but also no downgrades in routing. But I did not test long distance routing (> 600km).
I think the merge results can be improved if the access handling and some other parts are moved from source code to the style files. This makes it easier for the merger to say that two roads have the same attributes and can be merged without problems. But that's a task for the future...
I have already uploaded a compiled version: http://files.mkgmap.org.uk/detail/148
For anyone who is interested in the code: Please check the tag list (variable flatCompareTags) in the new RoadMerger. This taglist gives all tags that must be equal so that two roads can be merged. Is this list complete? Can I remove some tags from it?
Have fun! WanMil
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Seems to work fine so far (also using maxspeed patch), however I get quite a lot of theese (between 0 to 20 per country): SEVERE (MapBuilder): c:\openmtbmap\maps\64180000.osm.pbf: possible routing problem: road end-points not both coordNodes: ((M5), http://www.openstreetmap.org/browse/way/152908991) (serbia from geofabrik). Dunno really what to do with it....
Thanks for the hint. I have no idea why you get that message but later on I will use serbia for some testing... WanMil
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi WanMil, I got the following list as an output: SEVERE (RoadMerger): 10000124.o5m: Through route 2174274/361817 [WAY: 79386593 null(46.65438652038574/7.7636003494262695) [mkgmap:city=Leissigen,mkgmap:postcode=3706,mkgmap:admin_level2=CHE,mkgmap:admin_level4=Bern - - Berne,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:postal_code=3706,mkgmap:admin_level8=Leissigen,mkgmap:region=Bern - - Berne,highway=tertiary,mkgmap:country=CHE], WAY: 34288580 null(46.65485858917236/7.7637505531311035) [mkgmap:admin_level2=CHE,rrk:nat_ref=9,8,mkgmap:admin_level4=Bern - Berne,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:admin_level8=Leissigen,highway=secondary,mkgmap:country=CHE,mkgmap:city=Leissigen,ref=6;11,mkgmap:postcode=3706,rrk:Radweg=yes,rrk:level=5,rrk:nat_name=ncn 9 - Etappe 4 (Spiez?Meiringen),ncn 8 - Etappe 2 (Meiringen-Spiez),mkgmap:postal_code=3706,mkgmap:region=Bern - Berne], WAY: 34288580 null(46.65485858917236/7.7637505531311035) [mkgmap:admin_level2=CHE,rrk:nat_ref=9,8,mkgmap:admin_level4=Bern - Berne,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:admin_level8=Leissigen,highway=secondary,mkgmap:country=CHE,mkgmap:city=Leissigen,ref=6;11,mkgmap:postcode=3706,rrk:Radweg=yes,rrk:level=5,rrk:nat_name=ncn 9 - Etappe 4 (Spiez?Meiringen),ncn 8 - Etappe 2 (Meiringen-Spiez),mkgmap:postal_code=3706,mkgmap:region=Bern - Berne], WAY: 79386593 null(46.65438652038574/7.7636003494262695) [mkgmap:city=Leissigen,mkgmap:postcode=3706,mkgmap:admin_level2=CHE,mkgmap:admin_level4=Bern - - Berne,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:postal_code=3706,mkgmap:admin_level8=Leissigen,mkgmap:region=Bern - - Berne,highway=tertiary,mkgmap:country=CHE]] SEVERE (RoadMerger): 10000124.o5m: Through route 2174274/361817 [WAY: 79386593 null(46.65438652038574/7.7636003494262695) [mkgmap:city=Leissigen,mkgmap:postcode=3706,mkgmap:admin_level2=CHE,mkgmap:admin_level4=Bern - - Berne,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:postal_code=3706,mkgmap:admin_level8=Leissigen,mkgmap:region=Bern - - Berne,highway=tertiary,mkgmap:country=CHE], WAY: 34288580 null(46.65485858917236/7.7637505531311035) [mkgmap:admin_level2=CHE,rrk:nat_ref=9,8,mkgmap:admin_level4=Bern - Berne,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:admin_level8=Leissigen,highway=secondary,mkgmap:country=CHE,mkgmap:city=Leissigen,ref=6;11,mkgmap:postcode=3706,rrk:Radweg=yes,rrk:level=5,rrk:nat_name=ncn 9 - Etappe 4 (Spiez?Meiringen),ncn 8 - Etappe 2 (Meiringen-Spiez),mkgmap:postal_code=3706,mkgmap:region=Bern - Berne], WAY: 34288580 null(46.65485858917236/7.7637505531311035) [mkgmap:admin_level2=CHE,rrk:nat_ref=9,8,mkgmap:admin_level4=Bern - Berne,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:admin_level8=Leissigen,highway=secondary,mkgmap:country=CHE,mkgmap:city=Leissigen,ref=6;11,mkgmap:postcode=3706,rrk:Radweg=yes,rrk:level=5,rrk:nat_name=ncn 9 - Etappe 4 (Spiez?Meiringen),ncn 8 - Etappe 2 (Meiringen-Spiez),mkgmap:postal_code=3706,mkgmap:region=Bern - Berne], WAY: 79386593 null(46.65438652038574/7.7636003494262695) [mkgmap:city=Leissigen,mkgmap:postcode=3706,mkgmap:admin_level2=CHE,mkgmap:admin_level4=Bern - - Berne,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:postal_code=3706,mkgmap:admin_level8=Leissigen,mkgmap:region=Bern - - Berne,highway=tertiary,mkgmap:country=CHE]] SEVERE (RoadMerger): 10000125.o5m: Through route 2178461/375627 [WAY: 37110393 null(46.745216846466064/8.059372901916504) [mkgmap:city=Brienz (BE),ref=6;11,mkgmap:admin_level2=CHE,mkgmap:streetname=Hauptstrasse,lanes=2,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:admin_level4=Bern - Berne,name=Hauptstrasse,mkgmap:admin_level8=Brienz (BE),highway=primary,mkgmap:region=Bern - Berne,mkgmap:country=CHE], WAY: 25932045 null(46.744701862335205/8.060081005096436) [mkgmap:region=Bern - Berne,embankment=yes,mkgmap:city=Brienz (BE),mkgmap:admin_level2=CHE,mkgmap:streetname=Hauptstrasse,lanes=2,mkgmap:admin_level5=Verwaltungsregion Oberland,oneway=no,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,name=Hauptstrasse,mkgmap:admin_level8=Brienz (BE),highway=primary,mkgmap:admin_level4=Bern - Berne,mkgmap:country=CHE], WAY: 25932045 null(46.744701862335205/8.060081005096436) [mkgmap:region=Bern - Berne,embankment=yes,mkgmap:city=Brienz (BE),mkgmap:admin_level2=CHE,mkgmap:streetname=Hauptstrasse,lanes=2,mkgmap:admin_level5=Verwaltungsregion Oberland,oneway=no,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,name=Hauptstrasse,mkgmap:admin_level8=Brienz (BE),highway=primary,mkgmap:admin_level4=Bern - Berne,mkgmap:country=CHE], WAY: 37110393 null(46.745216846466064/8.059372901916504) [mkgmap:city=Brienz (BE),ref=6;11,mkgmap:admin_level2=CHE,mkgmap:streetname=Hauptstrasse,lanes=2,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:admin_level4=Bern - Berne,name=Hauptstrasse,mkgmap:admin_level8=Brienz (BE),highway=primary,mkgmap:region=Bern - Berne,mkgmap:country=CHE]] SEVERE (RoadMerger): 10000125.o5m: Through route 2178461/375627 [WAY: 37110393 null(46.745216846466064/8.059372901916504) [mkgmap:city=Brienz (BE),ref=6;11,mkgmap:admin_level2=CHE,mkgmap:streetname=Hauptstrasse,lanes=2,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:admin_level4=Bern - Berne,name=Hauptstrasse,mkgmap:admin_level8=Brienz (BE),highway=primary,mkgmap:region=Bern - Berne,mkgmap:country=CHE], WAY: 25932045 null(46.744701862335205/8.060081005096436) [mkgmap:region=Bern - Berne,embankment=yes,mkgmap:city=Brienz (BE),mkgmap:admin_level2=CHE,mkgmap:streetname=Hauptstrasse,lanes=2,mkgmap:admin_level5=Verwaltungsregion Oberland,oneway=no,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,name=Hauptstrasse,mkgmap:admin_level8=Brienz (BE),highway=primary,mkgmap:admin_level4=Bern - Berne,mkgmap:country=CHE], WAY: 25932045 null(46.744701862335205/8.060081005096436) [mkgmap:region=Bern - Berne,embankment=yes,mkgmap:city=Brienz (BE),mkgmap:admin_level2=CHE,mkgmap:streetname=Hauptstrasse,lanes=2,mkgmap:admin_level5=Verwaltungsregion Oberland,oneway=no,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,name=Hauptstrasse,mkgmap:admin_level8=Brienz (BE),highway=primary,mkgmap:admin_level4=Bern - Berne,mkgmap:country=CHE], WAY: 37110393 null(46.745216846466064/8.059372901916504) [mkgmap:city=Brienz (BE),ref=6;11,mkgmap:admin_level2=CHE,mkgmap:streetname=Hauptstrasse,lanes=2,mkgmap:admin_level5=Verwaltungsregion Oberland,mkgmap:admin_level6=Verwaltungskreis Interlaken-Oberhasli,mkgmap:admin_level4=Bern - Berne,name=Hauptstrasse,mkgmap:admin_level8=Brienz (BE),highway=primary,mkgmap:region=Bern - Berne,mkgmap:country=CHE]] SEVERE (RoadMerger): 10000260.o5m: Through route 2270182/407435 [WAY: 8157012 null(48.7128210067749/8.74260663986206) [mkgmap:way-has-pois=true,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Calw,mkgmap:admin_level7=Verwaltungsgemeinschaft Calw,name=Stuttgarter Straße,mkgmap:admin_level8=Calw,highway=primary,mkgmap:country=DEU,mkgmap:city=Calw,ref=B 296,mkgmap:postcode=75365,mkgmap:streetname=Stuttgarter Straße,mkgmap:postal_code=75365,mkgmap:region=Baden-Württemberg], WAY: 37132510 null(48.7128210067749/8.74260663986206) [mkgmap:way-has-pois=true,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Calw,mkgmap:admin_level7=Verwaltungsgemeinschaft Calw,name=Bischofstraße,mkgmap:admin_level8=Calw,highway=primary,mkgmap:country=DEU,mkgmap:city=Calw,ref=B 296;B 463,mkgmap:postcode=75365,mkgmap:streetname=Bischofstraße,mkgmap:postal_code=75365,mkgmap:region=Baden-Württemberg]] SEVERE (RoadMerger): 10000260.o5m: Through route 2270182/407435 [WAY: 8157012 null(48.7128210067749/8.74260663986206) [mkgmap:way-has-pois=true,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Calw,mkgmap:admin_level7=Verwaltungsgemeinschaft Calw,name=Stuttgarter Straße,mkgmap:admin_level8=Calw,highway=primary,mkgmap:country=DEU,mkgmap:city=Calw,ref=B 296,mkgmap:postcode=75365,mkgmap:streetname=Stuttgarter Straße,mkgmap:postal_code=75365,mkgmap:region=Baden-Württemberg], WAY: 37132510 null(48.7128210067749/8.74260663986206) [mkgmap:way-has-pois=true,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Calw,mkgmap:admin_level7=Verwaltungsgemeinschaft Calw,name=Bischofstraße,mkgmap:admin_level8=Calw,highway=primary,mkgmap:country=DEU,mkgmap:city=Calw,ref=B 296;B 463,mkgmap:postcode=75365,mkgmap:streetname=Bischofstraße,mkgmap:postal_code=75365,mkgmap:region=Baden-Württemberg]] SEVERE (RoadMerger): 10000260.o5m: Through route 2269961/408390 [WAY: 48448460 null(48.71290683746338/8.743550777435303) [mkgmap:way-has-pois=true,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Calw,mkgmap:admin_level7=Verwaltungsgemeinschaft Calw,name=Stuttgarter Straße,mkgmap:admin_level8=Calw,highway=primary,mkgmap:country=DEU,mkgmap:city=Calw,ref=B 296,mkgmap:postcode=75365,mkgmap:streetname=Stuttgarter Straße,mkgmap:postal_code=75365,mkgmap:region=Baden-Württemberg], WAY: 44332977 null(48.70846509933472/8.765480518341064) [mkgmap:way-has-pois=true,mkgmap:city=Calw,ref=B 295,mkgmap:postcode=75365,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Calw,mkgmap:admin_level7=Verwaltungsgemeinschaft Calw,mkgmap:admin_level8=Calw,mkgmap:region=Baden-Württemberg,highway=primary,mkgmap:postal_code=75365,mkgmap:country=DEU]] SEVERE (RoadMerger): 10000260.o5m: Through route 2269961/408390 [WAY: 48448460 null(48.71290683746338/8.743550777435303) [mkgmap:way-has-pois=true,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Calw,mkgmap:admin_level7=Verwaltungsgemeinschaft Calw,name=Stuttgarter Straße,mkgmap:admin_level8=Calw,highway=primary,mkgmap:country=DEU,mkgmap:city=Calw,ref=B 296,mkgmap:postcode=75365,mkgmap:streetname=Stuttgarter Straße,mkgmap:postal_code=75365,mkgmap:region=Baden-Württemberg], WAY: 44332977 null(48.70846509933472/8.765480518341064) [mkgmap:way-has-pois=true,mkgmap:city=Calw,ref=B 295,mkgmap:postcode=75365,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Calw,mkgmap:admin_level7=Verwaltungsgemeinschaft Calw,mkgmap:admin_level8=Calw,mkgmap:region=Baden-Württemberg,highway=primary,mkgmap:postal_code=75365,mkgmap:country=DEU]] SEVERE (RoadMerger): 10000264.o5m: Through route 2272599/416469 [WAY: 23307483 null(48.764684200286865/8.936455249786377) [mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Stuttgart,mkgmap:admin_level6=Landkreis Böblingen,name=Hauptstraße,mkgmap:admin_level8=Renningen,highway=tertiary,surface=asphalt,mkgmap:country=DEU,mkgmap:city=Renningen,mkgmap:postcode=71272,mkgmap:streetname=Hauptstraße,mkgmap:postal_code=71272,mkgmap:region=Baden-Württemberg,rrk:surface=paved], WAY: 23281812 null(48.764684200286865/8.936455249786377) [mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Stuttgart,mkgmap:admin_level6=Landkreis Böblingen,name=Magstadter Straße,mkgmap:admin_level8=Renningen,highway=tertiary,surface=asphalt,mkgmap:country=DEU,mkgmap:city=Renningen,ref=L 1185,mkgmap:postcode=71272,mkgmap:streetname=Magstadter Straße,mkgmap:postal_code=71272,mkgmap:region=Baden-Württemberg,rrk:surface=paved]] SEVERE (RoadMerger): 10000264.o5m: Through route 2272599/416469 [WAY: 23307483 null(48.764684200286865/8.936455249786377) [mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Stuttgart,mkgmap:admin_level6=Landkreis Böblingen,name=Hauptstraße,mkgmap:admin_level8=Renningen,highway=tertiary,surface=asphalt,mkgmap:country=DEU,mkgmap:city=Renningen,mkgmap:postcode=71272,mkgmap:streetname=Hauptstraße,mkgmap:postal_code=71272,mkgmap:region=Baden-Württemberg,rrk:surface=paved], WAY: 23281812 null(48.764684200286865/8.936455249786377) [mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Stuttgart,mkgmap:admin_level6=Landkreis Böblingen,name=Magstadter Straße,mkgmap:admin_level8=Renningen,highway=tertiary,surface=asphalt,mkgmap:country=DEU,mkgmap:city=Renningen,ref=L 1185,mkgmap:postcode=71272,mkgmap:streetname=Magstadter Straße,mkgmap:postal_code=71272,mkgmap:region=Baden-Württemberg,rrk:surface=paved]] SEVERE (RoadMerger): 10000264.o5m: Through route 2272000/413333 [WAY: 29550786 null(48.74831199645996/8.867554664611816) [mkgmap:way-has-pois=true,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Stuttgart,mkgmap:admin_level6=Landkreis Böblingen,name=Grabenstraße,mkgmap:admin_level8=Weil der Stadt,highway=secondary,mkgmap:country=DEU,mkgmap:city=Weil der ,ref=L 1182,mkgmap:postcode=71263,mkgmap:streetname=Grabenstraße,mkgmap:postal_code=71263,mkgmap:region=Baden-Württemberg], WAY: 149174086 null(48.7518310546875/8.869163990020752) [mkgmap:way-has-pois=true,mkgmap:city=Weil der ,mkgmap:postcode=71263,mkgmap:admin_level2=DEU,mkgmap:streetname=Paul-Reusch-Straße,mkgmap:admin_level4=Baden-Württemberg,mkgmap:admin_level5=Regierungsbezirk Stuttgart,mkgmap:admin_level6=Landkreis Böblingen,mkgmap:postal_code=71263,name=Paul-Reusch-Straße,mkgmap:admin_level8=Weil der Stadt,highway=secondary,mkgmap:region=Baden-Württemberg,mkgmap:country=DEU]] SEVERE (RoadMerger): 10000283.o5m: Through route 2290277/399786 [WAY: 4087265 null(49.14401292800903/8.578476905822754) [mkgmap:admin_level2=DEU,lanes=1,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,oneway=yes,mkgmap:admin_level6=Landkreis Karlsruhe,mkgmap:admin_level7=Verwaltungsgemeinschaft Bruchsal,mkgmap:admin_level8=Forst,highway=secondary,mkgmap:admin_level4=Baden-Württemberg,mkgmap:country=DEU,mkgmap:city=Forst,ref=L 556,mkgmap:postcode=76694,hgv=destination,mkgmap:postal_code=76694,mkgmap:region=Baden-Württemberg], WAY: 223683841 null(49.143733978271484/8.5783052444458) [mkgmap:way-has-pois=true,mkgmap:admin_level2=DEU,lanes=3,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,oneway=yes,mkgmap:admin_level6=Landkreis Karlsruhe,mkgmap:admin_level7=Verwaltungsgemeinschaft Bruchsal,mkgmap:admin_level8=Forst,highway=primary_ol,mkgmap:admin_level4=Baden-Württemberg,mkgmap:country=DEU,mkgmap:city=Forst,ref=L 556,mkgmap:postcode=76694,mkgmap:postal_code=76694,mkgmap:region=Baden-Württemberg]] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJSJPWgAAoJEPFgsWC7jOeTb3QH/3rvKjzGJ9fI8r26ZuQBKim8 Kw+thx4q8VC81peXzq9EUHGfszG7CUIBA0Uo7bU7LKxMl6hHJz0uOTj3xsDZXAWQ O2U1gQ+tu3xJU4Ssf4wp42adllYdQ9KkSeQzhDkW+3cPRm/PE2CfJF5/WkZhOKbS HpnztFfaIYTJdu2dGK/SkE2jdw1BDVAaBRxevYcmAHsxS7YpsR+OMBDLmX9YZ0r5 1dtDK8+XyzTZw8BrHD1yAWrwigF6uZnDF9ecUS9qZbKVcmVwuKX3nr1lYF8RP8vH GqztCxfN4ZZEQeQsBwMR4ZoI+IccXRtNbPIyWv2bUsQbkl8UTzdUaYvcvMjV52U= =fS+5 -----END PGP SIGNATURE-----
well it happens on most countries actually. Serbia was just an example.. On 30.08.2013 22:14, WanMil wrote:
Seems to work fine so far (also using maxspeed patch), however I get quite a lot of theese (between 0 to 20 per country): SEVERE (MapBuilder): c:\openmtbmap\maps\64180000.osm.pbf: possible routing problem: road end-points not both coordNodes: ((M5), http://www.openstreetmap.org/browse/way/152908991) (serbia from geofabrik). Dunno really what to do with it....
Thanks for the hint. I have no idea why you get that message but later on I will use serbia for some testing...
WanMil
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
El 27/08/13 21:31, WanMil escribió:
For anyone who is interested in the code: Please check the tag list (variable flatCompareTags) in the new RoadMerger. This taglist gives all tags that must be equal so that two roads can be merged. Is this list complete? Can I remove some tags from it?
I'm sorry for the late, late look at this thread. What about these ones: maxheight, maxwidth, maxlength, maxweight, narrow?
Hi Carlos, these tags are not evaluated in mkgmap, means, there is no java code to handle them. Of course, if your style assigns different types or road-speed or road-class etc. the RoadMerger will recognize that. Gerd
Date: Sat, 28 Sep 2013 19:36:42 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] [PATCH v1] Merge road network
El 27/08/13 21:31, WanMil escribió:
For anyone who is interested in the code: Please check the tag list (variable flatCompareTags) in the new RoadMerger. This taglist gives all tags that must be equal so that two roads can be merged. Is this list complete? Can I remove some tags from it?
I'm sorry for the late, late look at this thread. What about these ones: maxheight, maxwidth, maxlength, maxweight, narrow? _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Thank you for the clarification. It's fine then. El 29/09/13 09:54, Gerd Petermann escribió:
Hi Carlos,
these tags are not evaluated in mkgmap, means, there is no java code to handle them. Of course, if your style assigns different types or road-speed or road-class etc. the RoadMerger will recognize that.
Gerd
Date: Sat, 28 Sep 2013 19:36:42 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] [PATCH v1] Merge road network
El 27/08/13 21:31, WanMil escribió:
For anyone who is interested in the code: Please check the tag list (variable flatCompareTags) in the new RoadMerger. This taglist gives all tags that must be equal so that two roads can be merged. Is this list complete? Can I remove some tags from it?
I'm sorry for the late, late look at this thread. What about these ones: maxheight, maxwidth, maxlength, maxweight, narrow? _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Por favor, no me envíe documentos con extensiones .doc, .docx, .xls, .xlsx, .ppt, .pptx, .mdb, mdbx Instale LibreOffice desde http://es.libreoffice.org/descarga/ LibreOffice es libre: se puede copiar, modificar y redistribuir libremente. Gratis y totalmente legal. LibreOffice está en continuo desarrollo y no tendrá que pagar por las nuevas versiones.
participants (6)
-
Andrzej Popowski -
Carlos Dávila -
Felix Hartmann -
Gerd Petermann -
Henning Scholland -
WanMil