[Routing] Binary file format

[Adrian Stabiszewski]

> Actually there are quite some in-memory-databases for mobile
> devices that are very fast. I found parsing the xml broken up into
> "tiles" to be much faster then any database. But then a binary-format
> could probably save a lot of flash/ram-space and io-bandwidth.
> 

Well ok, I must admit you're right, but those DBs aren't preinstalled on the
devices I now. My phone hasn't one ;)
But this is not my point. The idea here is to create a binary file format
for the OSM data that would work like the tiles. Where you can jump in at
any location you want and then start moving... Because this is like
navigation should be working. At least I think so.

Besides this you also need a list with locations and street names. I'm
working here on tree based binary file.

> 
> > During my tests
> > travelling-salesman couldn't even find a route between two streets which
> > were only several hundreds meters apart...
> 
> That is strange. I'm regularly routing between streets inside major
> cities with long motorways and villages between the cities.
> 
> Do you have some repeatable test-case that I can investigate?

Try navigating from Gundelsheim, Hebelstraße to Gundelsheim
Heilbronnerstraße. I get here something like:

Exception in thread "AWT-EventQueue-0" java.lang.IllegalStateException: no
way found for id 12337829!
	at
org.openstreetmap.osm.data.searching.WayReferencePlace.getResult(WayReferenc
ePlace.java:64)
	at
org.openstreetmap.travelingsalesman.navigation.NavigationManager$RouteCalcul
ator.<init>(NavigationManager.java:500)
	at
org.openstreetmap.travelingsalesman.navigation.NavigationManager.setDestinat
ions(NavigationManager.java:350)
	
I was using a current checkout from svn for this.