[Routing] monav, RAM and disk usage

[VeaaC FDIRCT]

Hi,

On Fri, Aug 27, 2010 at 9:04 AM, Tim Teulings <tim at framstag.com> wrote:
> libosmscout (libsomscout.sf.net) implements offline map rendering. It also
> contains infrastructure code to parse and preprocess planet.osm files and
> code for location search by name. It also contains a routing solution but in
> this it cannot compete with other solutions. I thus would be very interested
> in integration of other routing solutions. The benefit for the routing
> solutions would be to drop a lot of its own infrastructure code.

I doubt, that the ContractionHierarchies routing plugin of MoNav could
save much code by using libosmscout's infrastructure. As the
algorithm's speed heavily depends on its preprocessed data and
specialized external memory compressed graph data structure it would
still need to manage its own set of files.
Furthermore it seems that libosmscout uses Cairo for rendering. This
would limit the supported platforms, e.g., no Windows Mobile port of
Cairo is known to me.

Among other things MoNav currently offers several features that no
other routing solution does. Therefore I want to maintain and develop
it as a fully fledged routing solution.

If you want to integrate the ContractionHierarchies routing plugin
into libosmscout you are welcome of course. If you run into any kind
of problems or need help understanding the algorithm I would be happy
to assists you.

Greetings

Christian Vetter