Roads with cycleway=track not usable by cars

Showing 1-5 of 5 messages
Roads with cycleway=track not usable by cars Malcolm Morgan 8/11/19 12:03 AM
Hi OTP Devs,

I'm using OTP in the UK and I have lots of roads with the tag cycleway=track,


These are normal roads but OTP says that cars don't have permission (see debug layer attached)

Is this a but in OTP or a problem with my config?

Thanks,

Malcolm
Re: Roads with cycleway=track not usable by cars Malcolm Morgan 8/11/19 12:30 AM
In fact, is seems that any cycleway tag closes the road to cars

Re: Roads with cycleway=track not usable by cars Tuukka Hastrup 8/11/19 5:39 AM

Indeed, this looks like a bug to me. highway=cycleway would mean that the path is not usable by cars, but cycleway=* just describes the (additional) bicycle lanes that are part of the path. https://wiki.openstreetmap.org/wiki/Key:cycleway

Quoting from https://github.com/opentripplanner/OpenTripPlanner/blob/master/src/main/java/org/opentripplanner/graph_builder/module/osm/DefaultWayPropertySetSource.java.

Unclassified roads should be permissible for all:

 props.setProperties("highway=unclassified", StreetTraversalPermission.ALL, 1, 1);

But then there's a variety of cycleway= values that remove the permission from cars:

props.setProperties("highway=*;cycleway=lane", StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 0.87, 0.87);

props.setProperties("highway=*;cycleway=share_busway", StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 0.92, 0.92);
props.setProperties("highway=*;cycleway=opposite_lane", StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 1.0, 0.87);
props.setProperties("highway=*;cycleway=track", StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 0.75, 0.75);
props.setProperties("highway=*;cycleway=opposite_track", StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 1.0, 0.75);
props.setProperties("highway=*;cycleway=shared_lane", StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 0.77, 0.77);
props.setProperties("highway=*;cycleway=opposite", StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 1.0, 1.4);
Then there's bicycle=designated, which is handled in a different way:
props.setProperties("highway=*;bicycle=designated", StreetTraversalPermission.ALL, 0.97, 0.97);
props.setProperties("highway=unclassified;bicycle=designated", StreetTraversalPermission.ALL, 0.95, 0.95);

Perhaps there are legacy or regional reasons for this handling of cycleway=*? (E.g. in Helsinki, I notice we use cycleway:right=* more.)

Regards,
Tuukka

--
You received this message because you are subscribed to the Google Groups "OpenTripPlanner Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opentripplanner-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/opentripplanner-users/336f5c36-db48-4315-9211-633f39244faf%40googlegroups.com.
Re: Roads with cycleway=track not usable by cars Nikhil VJ 10/25/19 12:45 AM
Hi, can anyone share what the two numbers at the end of these lines stand for?

Example: 
props.setProperties("highway=*;cycleway=share_busway", StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 0.92, 0.92);
Here, what does "0.92" mean? What effect does changing these numbers have? Is it some kind of weightage? 

Regards
Nikhil
Re: Roads with cycleway=track not usable by cars Nicolai Mogensen 10/25/19 7:49 AM
Hi Nikhil,

As i understand it the 0.92 is the "BikeSafety". It's a weighted number. There are two numbers, as the safety in direciton "To" or "From" can be different. How exactly the weighting works i will let others answer. Contradictionary, a low number here means high security.