clean cucumber comments, fixes 'file to long' problem with latest version of cucumber

features/bicycle/access.feature

@@ -1,6 +1,6 @@
 @routing @bicycle @access
 Feature: Bike - Access tags on ways
-Reference: http://wiki.openstreetmap.org/wiki/Key:access
+# Reference: http://wiki.openstreetmap.org/wiki/Key:access
 
     Background:
         Given the profile "bicycle"

features/bicycle/access_node.feature

@@ -1,6 +1,6 @@
 @routing @bicycle @access
 Feature: Bike - Access tags on nodes
-Reference: http://wiki.openstreetmap.org/wiki/Key:access
+# Reference: http://wiki.openstreetmap.org/wiki/Key:access
 
     Background:
         Given the profile "bicycle"

features/bicycle/cycleway.feature

@@ -1,6 +1,6 @@
 @routing @bicycle @cycleway
 Feature: Bike - Cycle tracks/lanes
-Reference: http://wiki.openstreetmap.org/wiki/Key:cycleway
+# Reference: http://wiki.openstreetmap.org/wiki/Key:cycleway
 
     Background:
         Given the profile "bicycle"

features/bicycle/oneway.feature

@@ -1,7 +1,7 @@
 @routing @bicycle @oneway
 Feature: Bike - Oneway streets
-Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
+# Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
-Usually we can push bikes against oneways, but we use foot=no to prevent this in these tests
+# Usually we can push bikes against oneways, but we use foot=no to prevent this in these tests
 
     Background:
         Given the profile "bicycle"

features/bicycle/restrictions.feature

@@ -1,7 +1,7 @@
 @routing @bicycle @restrictions
 Feature: Bike - Turn restrictions
-    Ignore turn restrictions on bicycle, since you always become a temporary pedestrian.
+# Ignore turn restrictions on bicycle, since you always become a temporary pedestrian.
-    Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
+# Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
 
     Background:
         Given the profile "bicycle"

features/bicycle/stop_area.feature

@@ -1,7 +1,7 @@
 @routing @bicycle @stop_area @todo
 Feature: Bike - Stop areas for public transport
-Platforms and railway/bus lines are connected using a relation rather that a way, as specified in:
+# Platforms and railway/bus lines are connected using a relation rather that a way, as specified in:
-http://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dstop_area
+# http://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dstop_area
 
     Background:
         Given the profile "bicycle"

features/bicycle/train.feature

@@ -1,6 +1,6 @@
 @routing @bicycle @train
 Feature: Bike - Handle ferry routes
-Bringing bikes on trains and subways
+# Bringing bikes on trains and subways
 
     Background:
         Given the profile "bicycle"

features/bicycle/way.feature

@@ -5,8 +5,8 @@ Feature: Bike - Accessability of different way types
         Given the profile "bicycle"
 
     Scenario: Bike - Routability of way types
-    Bikes are allowed on footways etc because you can pull your bike at a lower speed.
+    # Bikes are allowed on footways etc because you can pull your bike at a lower speed.
-    Pier is not allowed, since it's tagged using man_made=pier.
+    # Pier is not allowed, since it's tagged using man_made=pier.
 
         Then routability should be
             | highway        | bothw |

features/car/access.feature

@@ -1,6 +1,6 @@
 @routing @car @access
 Feature: Car - Restricted access
-Reference: http://wiki.openstreetmap.org/wiki/Key:access
+# Reference: http://wiki.openstreetmap.org/wiki/Key:access
 
     Background:
         Given the profile "car"

features/car/oneway.feature

@@ -1,6 +1,6 @@
 @routing @car @oneway
 Feature: Car - Oneway streets
-Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
+# Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
 
     Background:
         Given the profile "car"

features/car/restrictions.feature

@@ -1,7 +1,7 @@
 @routing @car @restrictions
 Feature: Car - Turn restrictions
-    Handle turn restrictions as defined by http://wiki.openstreetmap.org/wiki/Relation:restriction
+# Handle turn restrictions as defined by http://wiki.openstreetmap.org/wiki/Relation:restriction
-    Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
+# Note that if u-turns are allowed, turn restrictions can lead to suprising, but correct, routes.
 
     Background: Use car routing
         Given the profile "car"

features/foot/access.feature

@@ -1,6 +1,6 @@
 @routing @foot @access
 Feature: Foot - Access tags on ways
-Reference: http://wiki.openstreetmap.org/wiki/Key:access
+# Reference: http://wiki.openstreetmap.org/wiki/Key:access
 
     Background:
         Given the profile "foot"

features/foot/access_node.feature

@@ -1,6 +1,6 @@
 @routing @foot @access
 Feature: Foot - Access tags on nodes
-Reference: http://wiki.openstreetmap.org/wiki/Key:access
+# Reference: http://wiki.openstreetmap.org/wiki/Key:access
 
     Background:
         Given the profile "foot"

features/foot/oneway.feature

@@ -1,6 +1,6 @@
 @routing @foot @oneway
 Feature: Foot - Oneway streets
-Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
+# Handle oneways streets, as defined at http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing
 
     Background:
         Given the profile "foot"

features/foot/restrictions.feature

@@ -1,6 +1,6 @@
 @routing @foot @restrictions
 Feature: Foot - Turn restrictions
-    Ignore turn restrictions on foot.
+# Ignore turn restrictions on foot.
 
     Background:
         Given the profile "foot"

features/foot/roundabout.feature

@@ -6,8 +6,8 @@ Feature: Roundabout Instructions
     
     @todo
     Scenario: Foot - Roundabout instructions
-    You can walk in both directions on a roundabout, bu the normal roundabout instructions don't
+    # You can walk in both directions on a roundabout, bu the normal roundabout instructions don't
-    make sense when you're going the opposite way around the roundabout.
+    # make sense when you're going the opposite way around the roundabout.
     
         Given the node map
             |   |   | v |   |   |

features/options/files.feature

@@ -1,11 +1,11 @@
 @routing @options @files
 Feature: Command line options: files
-    Normally when launching osrm-routed, it will keep running as a server until it's shut down.
+# Normally when launching osrm-routed, it will keep running as a server until it's shut down.
-    For testing program options, the --trial option is used, which causes osrm-routed to quit
+# For testing program options, the --trial option is used, which causes osrm-routed to quit
-    immediately after initialization. This makes testing easier and faster.
+# immediately after initialization. This makes testing easier and faster.
-
+# 
-    The {base} part of the options to osrm-routed will be expanded to the actual base path of
+# The {base} part of the options to osrm-routed will be expanded to the actual base path of
-    the preprocessed file.
+# the preprocessed file.
 
     Background:
         Given the profile "testbot"

features/testbot/bad.feature

@@ -45,8 +45,8 @@ Feature: Handle bad data in a graceful manner
 
     @poles
     Scenario: Routing close to the north/south pole
-    Mercator is undefined close to the poles.
+    # Mercator is undefined close to the poles.
-    All nodes and request with latitude to close to either of the poles should therefore be ignored.
+    # All nodes and request with latitude to close to either of the poles should therefore be ignored.
 
         Given the node locations
             | node | lat | lon |

features/testbot/bearing.feature

@@ -141,8 +141,8 @@ Feature: Compass bearing
             | f    | e  | abcdef | W       | 270     |
 
     Scenario: Bearings at high latitudes
-    The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html,
+    # The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html,
-    to form square with sides of 1 km.
+    # to form square with sides of 1 km.
 
         Given the node locations
             | node | lat       | lon      |
@@ -176,8 +176,8 @@ Feature: Compass bearing
             | d    | b  | bd    | NW      | 315     |
 
     Scenario: Bearings at high negative latitudes
-    The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html,
+    # The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html,
-    to form square with sides of 1 km.
+    # to form square with sides of 1 km.
 
         Given the node locations
             | node | lat        | lon      |

features/testbot/example.feature

@@ -1,6 +1,5 @@
 @routing @testbot @example
 Feature: Testbot - Walkthrough
-
 # A complete walk-through of how this data is processed can be found at:
 # https://github.com/DennisOSRM/Project-OSRM/wiki/Processing-Flow
 

features/testbot/impedance.feature

@@ -1,9 +1,8 @@
 @routing @testbot @impedance @todo
 Feature: Setting impedance and speed separately
-These tests assume that the speed is not factored into the impedance by OSRM internally.
+# These tests assume that the speed is not factored into the impedance by OSRM internally.
-Instead the speed can optionally be factored into the weiht in the lua profile.
+# Instead the speed can optionally be factored into the weiht in the lua profile.
-
+# Note: With the default grid size of 100m, the diagonals has a length if 141.42m
-Note: With the default grid size of 100m, the diagonals has a length if 141.42m
 
     Background:
         Given the profile "testbot"
@@ -55,8 +54,8 @@ Note: With the default grid size of 100m, the diagonals has a length if 141.42m
             | c    | b  | btc   |
 
     Scenario: Use both impedance and speed (multiplied) when picking route
-      OSRM should not factor speed into impedance internally. However, the profile can choose to do so,
+    # OSRM should not factor speed into impedance internally. However, the profile can choose to do so,
-      and this test expect the testbot profile to do it.
+    # and this test expect the testbot profile to do it.
         Given the node map
             |   | s |   | t |   |
             | a |   | b |   | c |

features/testbot/penalty.feature

@@ -1,6 +1,6 @@
 @routing @penalty @signal
 Feature: Penalties
-Testbot uses a signal penalty of 7s.
+# Testbot uses a signal penalty of 7s.
 
     Background:
         Given the profile "testbot"

features/testbot/projection.feature

@@ -1,13 +1,13 @@
 @routing @projection
 Feature: Projection to nearest point on road
-Waypoints are projected perpendiculary onto the closest road
+# Waypoints are projected perpendiculary onto the closest road
 
     Background:
-        The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html
+    # The coordinas below was calculated using http://www.movable-type.co.uk/scripts/latlong.html
-        The nodes are placed as follows, with ab, bc and bd all being 1 km in length each:
+    # The nodes are placed as follows, with ab, bc and bd all being 1 km in length each:
-            |   |   | c |
+    #   |   |   | c |
-            |   | b |   | (this is sketch only, real data is in the table below)
+    #   |   | b |   |   (this is sketch only, real data is in the table below)
-            | a |   | d |
+    #   | a |   | d |
 
         Given the profile "testbot"
         Given the node locations

features/testbot/routes.feature

@@ -5,7 +5,7 @@ Feature: OSM Route Relation
         Given the profile "testbot"
 
     Scenario: Prioritize ways that are part of route relations
-    This scenario assumes that the testbot uses an impedance of 0.5 for ways that are part of 'testbot' routes.
+    # This scenario assumes that the testbot uses an impedance of 0.5 for ways that are part of 'testbot' routes.
 
         Given the node map
             | s |  |  | t |  |  |   |

features/testbot/time.feature

@@ -1,9 +1,9 @@
 @routing @time
 Feature: Estimation of travel time
-Testbot speeds:
+# Testbot speeds:
-Primary road:    36km/h = 36000m/3600s = 100m/10s
+# Primary road:    36km/h = 36000m/3600s = 100m/10s
-Secondary road:    18km/h = 18000m/3600s = 100m/20s
+# Secondary road:    18km/h = 18000m/3600s = 100m/20s
-Tertiary road:    12km/h = 12000m/3600s = 100m/30s
+# Tertiary road:    12km/h = 12000m/3600s = 100m/30s
 
     Background: Use specific speeds
         Given the profile "testbot"

features/testbot/turns.feature

@@ -98,7 +98,7 @@ Feature: Turn directions/codes
             | g | e | xg,xe | head,sharp_right,destination  |
 
     Scenario: Turn instructions at high latitude
-    https://github.com/DennisOSRM/Project-OSRM/issues/532
+    # https://github.com/DennisOSRM/Project-OSRM/issues/532
         Given the node locations
             | node | lat       | lon      |
             | a    | 55.68740  | 12.52430 |