[mkgmap-dev] barrier=gate

2013-12-22 Thread Gerd Petermann
Hi, the default style points file contains barrier=gate { addaccess no; set mkgmap:road-speed=1; } I think this should be changed to allow pedestrians and bicycles, else this would be treated like a closed door when --link-pois-to-ways is used. Gerd

[mkgmap-dev] Commit: r2906: Merge the mergeroads branch.

2013-12-22 Thread svn commit
Version mkgmap-r2906 was committed by wanmil on Sun, 22 Dec 2013 Merge the mergeroads branch. * Roads are merged which reduces the number of road entries by 7-25% using the default style. This results in slightly better routing calculation times and slightly smaller img file sizes. * The four

Re: [mkgmap-dev] Final call for merging the mergeroads branch

2013-12-22 Thread WanMil
Yes, please post a better changed text. Thanks WanMil Can you please phrase it so that people not so familiar with the terminology are not confused or put on the wrong track? As a start, I would suggest trying to word it without the use of quotation marks, which instantly imply that you need to

Re: [mkgmap-dev] Final call for merging the mergeroads branch

2013-12-22 Thread Colin Smale
Can you please phrase it so that people not so familiar with the terminology are not confused or put on the wrong track? As a start, I would suggest trying to word it without the use of quotation marks, which instantly imply that you need to understand what those words ("not persistent") mean in

Re: [mkgmap-dev] Final call for merging the mergeroads branch

2013-12-22 Thread Minko
Ah now I understand what you mean. Just change it into "Please note that actions in the finalize section are "not persistent" in terms of the continue or continue with_actions statement" > I think it must be clarified in the documentation that actions in the > finalize section are "not persist

Re: [mkgmap-dev] Final call for merging the mergeroads branch

2013-12-22 Thread WanMil
But then it conflicts with "statements continue to work with the > >element but without any action of the finalize section applied"? > >I don't understand why it conflict with the continue handling of the >finalize sections. >But I think the way is handled the same in trunk and in branch so I >it

Re: [mkgmap-dev] Final call for merging the mergeroads branch

2013-12-22 Thread Minko
Wanmil wrote: > > But then it conflicts with "statements continue to work with the > > element but without any action of the finalize section applied"? > > I don't understand why it conflict with the continue handling of the > finalize sections. > But I think the way is handled the same in trunk

Re: [mkgmap-dev] Final call for merging the mergeroads branch

2013-12-22 Thread WanMil
Hi Minko, Question about the Finalize section: Actions in the finalize section modify only the element for the current executed element type definition. The continue or continue with_actions statements continue to work with the element but without any action of the finalize section applied.