Re: [mkgmap-dev] max-speed and arbitrary values

2009-06-03 Thread Felix Hartmann
I tested a lot with maps today. Setting maximum of *speed_class=2* works quite nice. However Routing over longer distances gets broken, not too bad but significantly. The lower you set the speeds, the straigther the route. Lowering speed_class thereby achieves similar routing like you can achie

[mkgmap-dev] [PATCH] Generate copies of ways using the relations style file *Experimental*

2009-06-03 Thread Thilo Hannemann
The attached patch allows to generate ways from a relation. To do so simply write the way generating statement into your relations style file, e.g. type=route & route=bicycle & network=tcn { name 'Touristic cycleroute' } [ 0x02 road_class=3 road_speed=6 level 3 ] generate_ways_from_rela

Re: [mkgmap-dev] max-speed and arbitrary values

2009-06-03 Thread Thilo Hannemann
Hi Felix, Am 03.06.2009 um 12:06 schrieb Felix Hartmann: Is it possible to encode arbitrary maxspeed values or can we only set in steps of 10km/h? For example having road road_speed=7 associated with 35km/h, road road_speed=6 with 27, road_speed=5 with 23, road_speed=4 with 20, road_spe

Re: [mkgmap-dev] Commit: r1059: New approach to the too many nodes in region problem - carry on regardless.

2009-06-03 Thread Clinton Gladstone
On Wed, Jun 3, 2009 at 5:41 PM, Mark Burton wrote: > > Let's see how this does - I have tried it out on 63660006.osm and the > resulting map loads into mapsource OK and is generally fine. Trying to > route through the broken region does cause mapsource to either draw a > straight line or pop up th

Re: [mkgmap-dev] Commit: r1059: New approach to the too many nodes in region problem - carry on regardless.

2009-06-03 Thread Mark Burton
Let's see how this does - I have tried it out on 63660006.osm and the resulting map loads into mapsource OK and is generally fine. Trying to route through the broken region does cause mapsource to either draw a straight line or pop up the "your map's broken" dialog. A real gps would probably hang

[mkgmap-dev] Commit: r1059: New approach to the too many nodes in region problem - carry on regardless.

2009-06-03 Thread svn commit
Version 1059 was commited by markb on 2009-06-03 17:34:08 +0100 (Wed, 03 Jun 2009) New approach to the too many nodes in region problem - carry on regardless. Now, instead of croaking when too many nodes are in a region, it throws them away and tries to continue the best it can. The routing wil

[mkgmap-dev] Commit: r1058: Add means to flag node as being discarded.

2009-06-03 Thread svn commit
Version 1058 was commited by markb on 2009-06-03 17:34:04 +0100 (Wed, 03 Jun 2009) Add means to flag node as being discarded. The goal here is to be able to call getOffsetNod1() without bombing even though the routing will be broken because the node has been discarded. _

Re: [mkgmap-dev] Commit: r1054: When subdivision fails to reduce number of nodes, report bbox and croak.

2009-06-03 Thread Marko Mäkelä
On Wed, Jun 03, 2009 at 03:12:59PM +0100, Mark Burton wrote: > > Hi Felix, > > > a) has something in mkgmap changed > > No, it has always (well at least as far as I have been involved with > it!) been capable of failing in this way. > > > b) is there some tool out that destructs osm data by mis

Re: [mkgmap-dev] Commit: r1054: When subdivision fails to reduce number of nodes, report bbox and croak.

2009-06-03 Thread Johann Gail
b) is there some tool out that destructs osm data by mistake? Or is there some dumb mapper who generated the same ways 50 times? Just a thoght: May it have to do something with the new v0.6 interface? May this ways be old revisions or somthing similar? ___

Re: [mkgmap-dev] Commit: r1054: When subdivision fails to reduce number of nodes, report bbox and croak.

2009-06-03 Thread Clinton Gladstone
On Tue, Jun 2, 2009 at 11:04 AM, svn commit wrote: > Version 1054 was commited by markb on 2009-06-02 10:04:38 +0100 (Tue, 02 Jun > 2009) > > When subdivision fails to reduce number of nodes, report bbox and croak. You know, I'm not too crazy about the "croak" part. For example, yesterday I att

Re: [mkgmap-dev] Commit: r1054: When subdivision fails to reduce number of nodes, report bbox and croak.

2009-06-03 Thread Mark Burton
Hi Clinton, > You know, I'm not too crazy about the "croak" part. > > For example, yesterday I attempted to compile a map of a large portion > of Europe from Geofabrik.de, which provides daily extracts. The entire > procedure took many hours (osmosis -> split -> mkgmap) on my > antiquated (2 yea

Re: [mkgmap-dev] Commit: r1054: When subdivision fails to reduce number of nodes, report bbox and croak.

2009-06-03 Thread Mark Burton
Hi Felix, > a) has something in mkgmap changed No, it has always (well at least as far as I have been involved with it!) been capable of failing in this way. > b) is there some tool out that destructs osm data by mistake? Or is there some dumb mapper who generated the same ways 50 times? Chee

Re: [mkgmap-dev] Commit: r1054: When subdivision fails to reduce number of nodes, report bbox and croak.

2009-06-03 Thread Felix Hartmann
For me this is the same. However why did this problem not appear until now? a) has something in mkgmap changed or b) is there some tool out that destructs osm data by mistake? Clinton Gladstone wrote: On Tue, Jun 2, 2009 at 11:04 AM, svn commit wrote: Version 1054 was commited by markb on

R: [mkgmap-dev] max-speed and arbitrary values

2009-06-03 Thread Marco Certelli
Hi, As far as I know the map only stores the road_speed and road_class (not the speed in km/h: association road_speed vs. speed is demanded to Garmin devices or mapsource). The turn time penalties I tested was depending on the road_speed (but I presume the penalty is proportional to the speed)

Re: [mkgmap-dev] Commit: r1057: Add --max-jobs option to request concurrent processing of maps.

2009-06-03 Thread Lambertus
Thanks a lot! Mark Burton wrote: Hi Lambertus, Specifying or specifically not specifying? I'm confused: What should be done to get one thread on a single core machine, or two threads on a dual core? Use --max-jobs. To summarise: If --max-jobs is not specified, you get 1 thread no matter

[mkgmap-dev] max-speed and arbitrary values

2009-06-03 Thread Felix Hartmann
Is it possible to encode arbitrary maxspeed values or can we only set in steps of 10km/h? For example having road road_speed=7 associated with 35km/h, road road_speed=6 with 27, road_speed=5 with 23, road_speed=4 with 20, road_speed=3 with 17, road_speed=2 with 10 and road_speed=1 with 5km/h.

Re: [mkgmap-dev] Commit: r1057: Add --max-jobs option to request concurrent processing of maps.

2009-06-03 Thread Mark Burton
Hi Lambertus, > Specifying or specifically not specifying? I'm confused: What should be > done to get one thread on a single core machine, or two threads on a > dual core? Use --max-jobs. To summarise: If --max-jobs is not specified, you get 1 thread no matter how many cores you have. If -

Re: [mkgmap-dev] Commit: r1057: Add --max-jobs option to request concurrent processing of maps.

2009-06-03 Thread Lambertus
svn commit wrote: Version 1057 was commited by markb on 2009-06-03 11:26:34 +0100 (Wed, 03 Jun 2009) Add --max-jobs option to request concurrent processing of maps. Processing of the maps is handled concurrently by a pool of top-level threads. The number of threads in the pool can be specified

[mkgmap-dev] Parallel processing of maps now in trunk

2009-06-03 Thread Mark Burton
Things are a bit quiet on the list this morning so I thought I would commit this patch as it has had a reasonable amount of testing with no problems reported recently. If you have a multi-core machine, specify --max-jobs to get some speedup when processing multiple maps. Cheers, Mark __

[mkgmap-dev] Commit: r1057: Add --max-jobs option to request concurrent processing of maps.

2009-06-03 Thread svn commit
Version 1057 was commited by markb on 2009-06-03 11:26:34 +0100 (Wed, 03 Jun 2009) Add --max-jobs option to request concurrent processing of maps. Processing of the maps is handled concurrently by a pool of top-level threads. The number of threads in the pool can be specified explicitly with th

Re: [mkgmap-dev] routing & rendering penalty with smaller tiles in splitter

2009-06-03 Thread Marko Mäkelä
On Wed, Jun 03, 2009 at 02:04:56PM +0800, maning sambale wrote: > Hi, > > I'm attempting to split the Philippines into smaller tiles using > splitter. This is to make rendering faster. > Currently I've tested with the following: > > --max-nodes=80 > --max-nodes=40 > --max-nodes=20 >