Looks fine, thanks. We need support to determine the city in the code and confirm the appid with the bbbike.org guys in order to ship it. Otherwise just minor stuff.

src/plugins/runner/bbbike/BbbikePlugin.cpp
27	should be false.
37	Should be "BBBike" here.
52	"http://bbbike.org/ bicycle routing service" just in case people don't get it from the URL.
src/plugins/runner/bbbike/BbbikeRunner.cpp
64	I see two options to receive the city: Use their API to query it at runtime, possibly cache the result for subsequent routing requests. The disadvantage is that we have to wait another time to transmit things via a possibly slow Internet connection Provide a set of GeoDataLatLonBox <-> city mappings that are part of the plugin. This spares the second http calls, but has the disadvantage that the set of shipped mappings might be out of date e.g. when bbbike.org adds another supported city Any preferences which way to go here? I kinda think the first one is better, mostly because caching the result city will reduce the disadvantages of another http query a lot.
65	Guess we still have to contact them to confirm the marble appid?

Revision Contents
Changeset List

		Path
M		src/plugins/runner/CMakeLists.txt (1 line)
A	M	src/plugins/runner/bbbike/BbbikePlugin.h (51 lines)
A	M	src/plugins/runner/bbbike/BbbikePlugin.cpp (80 lines)
A	M	src/plugins/runner/bbbike/BbbikeRunner.h (62 lines)
A	M	src/plugins/runner/bbbike/BbbikeRunner.cpp (207 lines)
A	M	src/plugins/runner/bbbike/CMakeLists.txt (10 lines)