I have committed a change to the locator branch (r1994) affects some
location specific mkgmap options in the branch.
1. boundsdirectory has been renamed to bounds
2. location-autofill now contains a list of parameters
location-autofill=[option1,[option2]]
Controls how country, region, city and zip info is gathered for
cities, streets and pois.
Default: bounds
bounds The preprocessed boundaries are used. The assignment
of boundary type => country, region etc. is configured in
the style file
is_in The is_in tag is analyzed for country and region
information if these information is not already
set
nearest If all methods before failed the city/hamlet points that
are closest to the element are used to assign the missing
information.
The old location-autofill values (0 to 3) are autoconverted to the new
options although some buggy and bad coded functionality has been removed
from the Locator and has to be reimplemented (e.g. fuzzy search - need
to be reimplemented by a good soundslike algorithm).
So now anybody can control with the mkgmap options if the time costly
usage of the preprocessed boundaries should happen or not.
WanMil
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
