plan trip

This block is part of the NS group and was last modified in core v15.0.0.

plan trip v15.0.0

Plan a journey between an origin and a destination. Each endpoint accepts a station code, a UIC code, or a geo point.

In pins 15 + flow
  • flow
    flow
  • Connection required
    nsconnection

    The NS connection.

  • From station code required
    value

    Origin NS station code (e.g. asd for Amsterdam Centraal). • Hidden when other fields are filled

  • From UIC code
    value

    Origin UIC code. • Hidden when other fields are filled

  • From geo point
    geo_point

    Origin coordinate (for door-to-door planning). • Hidden when other fields are filled

  • From name
    value

    Optional label for the origin coordinate.

  • To station code required
    value

    Destination NS station code. • Hidden when other fields are filled

  • To UIC code
    value

    Destination UIC code. • Hidden when other fields are filled

  • To geo point
    geo_point

    Destination coordinate (for door-to-door planning). • Hidden when other fields are filled

  • To name
    value

    Optional label for the destination coordinate.

  • Via station code
    value

    Optional station code to route via.

  • Via UIC code
    value

    Optional UIC code to route via.

  • Via geo point
    geo_point

    Optional coordinate to route via.

  • Date / time
    date

    Departure (or arrival) moment for the trip. Defaults to now.

  • Search for arrival
    condition

    When true, the date/time is treated as the desired arrival time instead of departure.

    Default false

  • Language
    value

    Language for localized text (e.g. nl or en). Defaults to Dutch.

Out pins 5 + flow
  • flow
    flow
  • Connection
    nsconnection

    The NS connection.

  • Success
    condition

    True if the request succeeded.

  • Trips
    array

    The trip options, each with planned/actual departure and arrival as unix timestamps, transfers, delays and per-leg details.

  • Count
    number

    Number of trips returned.

  • Error
    value

    Error message if the request failed.

reisadvies
trips
journey
reisplanner

A typical wiring for plan trip: a function trigger starts the flow; open connection feeds the connection pin; value feeds the from_station pin; value feeds the to_station pin; the flow out pin feeds debug.

Studio canvas example for the plan trip block: typical wiring for plan trip.

Version history

Introduced in v15.0.0.


Back to NS Return to the main group to view all sub-groups Back to NS Return to the group to view all blocks within this group