<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Greg,<br>> > I think we should remove (ignore) the --route option, as it is mandantory.<br><div>> > If possible, we should allow to create maps that don't contain <br>> > a NOD section, I think this is wanted by some users.<br>> <br>> I'm not sure what you mean. It sounds like having<br>> basic/advanced/routing is desireable from the list consensus. But I<br>> would suggest that routable maps be the default, when mkgmap is invoked<br>> without special arguments. Perhaps keep --net and --route, but allow<br>> --no-net and --no-route and make --net and --route default (and of<br>> course make route imply net)<br><br>What I meant is this:<br>The current implementation of mkgmap does more or less<br>assume that --route is used. Many functions are not executed<br>without that option, although they are not needed for routing,<br>only for the creation of the NET data.<br>For example, --housenumber has no effect without --route,<br>but if I got that right you may want to be able to search for<br>housenumbers without being able to route to them.<br>NET data is not written without --route.<br><br>In the current implementation it is not simple to write NET data <br>without also writing NOD data. <br>I agree that we should support NET without NOD.<br><br>Gerd<br></div> </div></body>
</html>