<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote
cite="mid:CAJKJX-SsrXCLYPbfnp43tu4_4jr2WsXFpiob8G=XYHup5DM7TA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div class="im">
<blockquote type="cite">
<div dir="ltr">
<div>or you could add all changes in such a way
that they are also added to the tool that Ben
proposes. <br>
</div>
</div>
</blockquote>
<br>
</div>
I would just not invent a new output format to work with
locally... Although using sqlite as a locale storage
(whatever tool) would also help a lot speedwise.<br>
<br>
</div>
</blockquote>
<div> </div>
<div>No, not for local use, but to share the updates with
other mappers. <br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Local use context = your workmemory, when dealing with possible
large datasets I would use a way to not do load it all in memory
first before launching logic at it : if you want those kind of tools
try whatever is around to provide routing with OSM (*) data.<br>
<br>
So I think this got misinterpreted here. I'm envisioning any tool
to be some sort of man-in-the middle.<br>
<br>
Glenn<br>
<br>
(*) Except Routino ( <a class="moz-txt-link-freetext" href="http://http://routino.org/">http://http://routino.org/</a> ) which creates
fast local storage to serve. <br>
<a class="moz-txt-link-freetext" href="http://routing.bitless.be/www/routino/router.html">http://routing.bitless.be/www/routino/router.html</a><br>
</body>
</html>