Add explanation for using more than one option at a time
Merge pull request #129 from rodo/master

Add explanation for using more than one option at a time
Merge branch 'master' of git+ssh://github.com/graphhopper/graphhopper
Merge origin/master into ratrunexperiments
Austria cycleway routing works now far better compared to the original code
Refactoring of parameter names
Wheeler introduction.
Don't consider gate and other barriers as absolute. Whith a bike one can pass all of these.
Fix of boosting formular and a couple of other small improvments.
First working improved routing instructions for bicycle routing. The code is uggly as it sums up the pavement and wayType Codes of all Encoders.
Make routing tests to pass with the new bicycle rounting instructions.
Personal GraphopperWebChanges/do not commit!
Deletion of XmlReader - I have no idea where it came from.
Check that we do not exceed the initial calculated maximum speed limit with our boosting.
-> now the previously commented test case can be enabled.
Additional a test for exceeding maximum negative boosting added.
Add issue number to the FIXME marks.
Revert "Personal GraphopperWebChanges/do not commit!"

This reverts commit c5ad7629e1b68545a0d26f5ed33496579222b696.
Code cleanup.
Revert personal change in nbactions.xml, introduced in change e1f5531 Austria cycleway routing works now far better compared to the origina…
Adoption of expected test results in testMonacoBike to what we get. All distances are shorter comared to before.
Anyhow, one test still fails and I don't have an idea why. The failed test output is as following:
Failed tests: 
  RoutingAlgorithmIT.testMonacoBike:161 FOUND 1 ERRORS.
astarbi|SHORTEST returns path not matching the expected points of 84	 Returned was 94	 (expected distance 1671.0, was 1671.983439569666) from:468-966  43.73068455771767,7.421283689825812, to:49-482  43.72768520610984,7.418755948656445.
 expected:<0> but was:<1>
Fix of the failed testcase: Just by co-instance it happened that two different routes with the same length, but different amount of locations were found. Now I moced the starting point a bit and now the algorithms "astarbi" and "dijkstrabi" give the same result.
Deletion of unused code.
Avoid special tratement of mtb allowed ways.
"mtb" intended ways are now treated as pushing sections.
Renaming of instruction "wheeler" into "pushing section", this seems to be the right translation.
Introduction of OSM file "krems" which is used for route relation testing.
Adding of some more BikeFalgEncoder Tests.