Intent of option BIKE/attribute BICYCLE_CARRIAGE?

[Holger Bruch]

Hi all,

what is the intention requesting a route with <code>Option</code> BIKE?
Should transit legs support taking bike along (what seems to be AbstractEfaProvider usage) or should biking be used as mode for first/last mile (instead of walking), as AbstractNavitionProvider seems to do?
And I guess for a line with bikes allowed, attribute BICYCLE_CARRIAGE should be set, correct?

Further, we'd like to introduce bike/park & ride into the PTE API. What would you recommend how to do this?

Thx,

Holger

[Andreas Schildbach]

> what is the intention requesting a route with <code>Option</code> BIKE?
> Should transit legs support taking bike along (what seems to be
> AbstractEfaProvider usage) or should biking be used as mode for
> first/last mile (instead of walking), as AbstractNavitionProvider seems
> to do?

The first meaning is the intended one. However that option kind of never
left the beta stage; needs implementation and testing thoughout all
providers.

> And I guess for a line with bikes allowed, attribute BICYCLE_CARRIAGE
> should be set, correct?

That's what I would expect the query system to do, yes.

> Further, we'd like to introduce bike/park & ride into the PTE API. What
> would you recommend how to do this?

I'm not sure, maybe we need mode options for the first and last legs, if
they are IT legs.