[mkgmap-dev] Simplify setting access tags in the mergeroads branch
From WanMil wmgcnfg at web.de on Sun Oct 6 21:26:22 BST 2013
> It's quite the same as your proposal, but without new special options. Hi Henning, you're right, but that's exactly what I don't like. You propose to have a special handling for set mkgmap:access='xxx' and add mkgmap:access='xxx' I think special handlings are better documented and more intuitive by using special commands: setaccess 'xxx' and addaccess 'xxx' Of course the names setaccess and addaccess could be changed to something else if someone has a better name for it. @All other: what do you think/prefer? I don't mind implementing the set/add mkgmap:access behaviour if the list favours that variant. I am just thinking about what is the most intuitive and best explainable solution. WanMil
- Previous message: [mkgmap-dev] Simplify setting access tags in the mergeroads branch
- Next message: [mkgmap-dev] Simplify setting access tags in the mergeroads branch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list