
Hi WanMil,
Henning,
just a question: How does bnd-file creation work? Does it process everything inside the osm or pbf-file or just relations and ways containing boundary=administrative? If not, this would be a great improvement, because no osmosis is needed. osmosis isn't a very fast tool for filtering data.
bnd-file creation processes the whole input file. It does not filter for boundary=administrative. The reason for this is that postal_codes are also accepted. The osmosis step is required because otherwise you probably will have memory problems. If you use unfiltered data for the bnd-creation mkgmap must first read *all* points and *all* ways from the input file. And if you don't have a machine with tons of GB this will exhaust your memory. Maybe someone can do some research if there is a better tool for filtering the boundary data.
Another thing would be the generation of a working gmapsupp.img directly with mkgmap.
Yes, that would be nice but it's not the aim of the locator branch. The locator branch should do a better city/region/country/zip matching but no improvement to the garmin index format.
Henning
WanMil