[Routing] libosmscout, was: monav, RAM and disk usage

[Tim Teulings]

Hello!

> Some minor issues:
> 1.CitySearchDialog.h loses a header guard.

Fixed.

> 2.Missing of build tool generated headers under msvc, (currently simply
> commented out).

I would suggest adding special versions of these files 
(config-msvcXXX.h) that are left out of the autoconf build but are part 
of Visual Studio projects.

> 3.MapPainterQt.cpp uses log2() which is missing in msvc (I see the
> Log2() in Util.h, and use it instead)

Fixed.

>> I'm able to build libosmscout and run the import on your data
> Yes, the importer also works under msvc8.

Fine.

>> (though Visual Studio seems to be much slower at some stages for yet
>> unknown reasons. I'll do some profiling).
> Under debug mode or release mode? You may try turning off the debug
> iterator
> support(http://msdn.microsoft.com/en-us/library/aa985982%28VS.80%29.aspx)

Import was slow in some steps using release and debug builds. Import of 
your *.osm file should take less than a second. I had not yet the time 
to do some profiling.

> The official site offers a pre-built lib built by msvc9. You may use it
> with vs2010, but the debug lib will be invalid.

I might take a look at it later. I'm already happy that it builds and 
works under Visual Studio.

>> It would be nice if you could test the current version and give me
>> some feedback!
> Yes, tested under msvc8/9 with test.osm.
> Some issues:
> 1. While panning the canvas, sometimes it won't do the redraw. The
> canvas is just moved along mouse drag.

Fixed.

> 2. Crash while zoom to some level. According to debugger, it comes from
> AreaNodeIndex::GetNodes() on line 96. The iterator debugging gives
> "map/set iterator not dereferencable".

I could not reproduce this, but nevertheless found the possible cause. 
So possibly also fixed.

> Good job.

Thank you. There is also some initial support for QGLPixBuffer 
rendering. I get some debugging output on the terminal, so possibly the 
code needs improvements but rendering speed is much improved (however 
"text along the path" looks ugly).

> I'd also expect a Qt based TravelJinni or OSMScout with routing feature.

TravelJinni already has some very simple routing integration and I will 
integrate simular functionality to OSMScout (the Qt based demo), too. 
Note however that these are just demos.

The routing algorithm is also very slow and needs improvement or 
integration of other, faster algorithms - thats the point where we are 
back to my initial mail regarding this topic (possible integration of a 
monav based routing implementation to libosmscout).

-- 
Gruß...
    Tim