Actually I just thought about one possible problem, as I don't know how the mkgmap:noindex=true will be implemented.
What happens when a user simply rebuilds the address index of existing .img files without using a style-file when mkgmap:noindex=true had been set for problematic cases? a) will it then slow down if many roads have the same name b) doesn't matter, the names are now in such a position that mkgmap will not use them for address index? If a) is the case, then I think there would also need to be a switch to enable say 300 roads same name, don't index. If b) is the case then the mkgmap:noindex=true setup is sufficient. On 10.11.2011 13:25, Steve Ratcliffe wrote: > On 31/10/11 10:40, WanMil wrote: >> I think it's a good idea to use a flag like 'mkgmap:noindex=true' which >> can be set in the style file. That provides the best flexibility. > The option appears a popular choice! > It might be a good addition, although I think it would have > to work with all element types and not just roads. > > So I will take it that there is no-one in favour of just removing > often repeated names automatically, and really as long as they > don't cause any harm I don't see any problem with them. > > So I will merge later the current simplify-sorted-roads branch which > now only uses the modified algorithm when there is a large number of > same named roads. It never takes more than a fraction of a second. > > ..Steve > > _______________________________________________ > 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