or you could add all changes in such a way that they are also
added to the tool that Ben proposes.
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.
No, not for local use, but to share the updates with other mappers.
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.
So I think this got misinterpreted here. I'm envisioning any tool to
be some sort of man-in-the middle.
Glenn
(*) Except Routino ( http://http://routino.org/ ) which creates fast
local storage to serve.
http://routing.bitless.be/www/routino/router.html
_______________________________________________
Talk-be mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-be
