Hi Greg,
> > I think we should remove (ignore) the --route option, as it is mandantory.
> > If possible, we should allow to create maps that don't contain
> > a NOD section, I think this is wanted by some users.
>
> I'm not sure what you mean. It sounds like having
> basic/advanced/routing is desireable from the list consensus. But I
> would suggest that routable maps be the default, when mkgmap is invoked
> without special arguments. Perhaps keep --net and --route, but allow
> --no-net and --no-route and make --net and --route default (and of
> course make route imply net)
What I meant is this:
The current implementation of mkgmap does more or less
assume that --route is used. Many functions are not executed
without that option, although they are not needed for routing,
only for the creation of the NET data.
For example, --housenumber has no effect without --route,
but if I got that right you may want to be able to search for
housenumbers without being able to route to them.
NET data is not written without --route.
In the current implementation it is not simple to write NET data
without also writing NOD data.
I agree that we should support NET without NOD.
Gerd
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
