[mkgmap-dev] [locator] What's next?

Mon Jun 6 19:54:13 BST 2011

Hi,
there are tools like o5mfilter or osmfilter. They should be faster, but 
they can't write pbf, just o5m or osm-xml. The Format o5m is much better 
for filtering data, but there isn't any tool, which converts o5m to pbf. 
So maybe the the hole process wont be faster. Also o5m is faster then 
pbf, if you would update your local file with change-sets. I know that 
this isn't the task of locator-branch, but maybe reading o5m would be 
one of the next things for bnd-generation and splitter. :-)

I will ask in german forum, how to use osmfilter for our filtering and 
compare it to osmosis.

Henning

Am 06.06.2011 20:33, schrieb WanMil:
> 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.