• Home
  • Guides
  • Reference
  • Support
Search Results for

    Show / Hide Table of Contents
    • API Overview
      • Overview
      • Authentication
      • Retrieving API Results
      • Referenced vs Inline Entities
      • Choosing API Response Data
      • Handling API Errors
    • separator
    • Vehicle Routing Endpoints
      • Path
    • Optimization Endpoints
      • Instantiate
      • Build
      • Assignment Restrictions
      • Optimize
      • Sequence
      • Evaluate
      • Recommend
      • Insert
      • Centroids
      • Zones
      • Consolidate By Job Restrictions
      • Consolidate By Route Assignments
    • Geocoding Endpoints
      • Geocode
      • Reverse Geocode
    • Task Endpoints
      • List
      • Status
      • Result
      • Cancel
    • Sandbox Endpoints
      • List
      • Create
      • Rename
      • Retrieve
      • Update
      • Delete
      • Revisions
      • Add Revision
      • Expiry
      • Permissions
    • Verizon Connect Fleet Integration Endpoints
      • Pull Platform Data
      • Sync Platform Data
      • List Platform Territories
    • Other Endpoints
      • Canonicalize
      • Route Cards
      • Validate
      • Version
    • separator
    • Request Types
      • problem
      • capacity_metric
      • depot
      • driver
      • driver_break
      • job
      • job_template
      • job_type
      • load_amount
      • marker
      • problem_defaults
      • route
      • schedule
      • settings
      • shift
      • shift_override
      • shift_pattern
      • shift_pattern_assignment
      • stop
      • vehicle
      • zone
      • variance
    • Response Types
      • instantiate_response
      • problem_response
      • problem_aggregates
      • driver_response
      • geocoded_location
      • recommend_option
      • route_response
      • schedule_response
      • schedule_instantiate_response
      • stop_response
      • violation
    • Meta Types
      • task_redirect_response
      • task_status_response
      • validate_response
    • Sandbox Types
      • delta
      • array_delta
      • dict_delta
      • keyed_array_delta
      • object_delta
      • set_delta
      • revision
      • revision_created_response
      • revision_response
      • sandbox_response
    • Common Types
      • date_range
      • day_of_week
      • hazmat_load_type
      • id
      • latlon
      • stop_type
      • time_window
      • custom
      • polygon
    • Primitive Types
      • boolean
      • date
      • datetime
      • float
      • integer
      • string
      • timespan

    driver_break

    A driver_break object represents a driver break that must be taken by the driver.

    RouteCloud can automatically insert driver breaks into routes. Breaks can be specified as non-relative or relative. Non-relative breaks always start at the same time each day. Relative breaks start at a time offset from the shift start time of the route.

    Breaks always happen at the specified break.start time. If a break occurs during a job the break object is placed on the route_response.stops list after the job.

    Breaks are created only for the duration of a route. For example, if a route starts at 11:00 AM and finishes at 2:00 PM, a 10:00 AM or 3:00 PM break is ignored.

    Name Type Description
    earliest_start timespan Used for flexible break scheduling. The break can start anytime between earliest_start and latest_start. Do not set "start" when using flexible scheduling. If route.breaks_relative_to_start is set, the earliest_start time is relative to the route start time.
    id string An ID assigned to the break. Can be used for integration with other systems.
    latest_start timespan Used for flexible break scheduling. The break can start anytime between earliest_start and latest_start. Do not set "start" when using flexible scheduling. If route.breaks_relative_to_start is set, the latest_start time is relative to the route start time.
    length timespan The duration of the break.
    name string The display name for the break. This must be unique among the breaks on each shift or route.
    start timespan The start time of the break. The break is placed at this time. If route.breaks_relative_to_start is set, the start time of the break is relative to the route start time.

    Example

    Sending the following build request to RouteCloud:

    {
      "routes": [
        {
          "id": "route0_route_with_relative_breaks",
          "location": "39.718005, -104.969531",
          "start_time": "09:00",
          "breaks": [
            { "id": "route0_morning_break", "start": "02:00", "length": "00:15" },
            { "id": "route0_lunch_break", "start": "04:00", "length": "00:30" },
            { "id": "route0_afternoon_break", "start": "06:00", "length": "00:15" }
          ],
          "breaks_relative_to_start": "true"
        }
      ],
      "jobs": [
        { "id": "job0", "location": "39.635928, -105.049219" },
        { "id": "job1", "time_on_site": "01:00", "location": "39.725375, -104.791080" },
        { "id": "job2", "time_on_site": "01:00", "location": "39.708990, -105.026954" },
        { "id": "job3", "time_on_site": "01:00", "location": "39.653975, -105.093750" }
      ]
    }
    

    Yields the following response:

    {
      "id": "route0_route_with_relative_breaks", ...
      "stops": [
        { "type": "depot", ...  },
        { "id": "job1", "arrival_time": "09:26:58", "time_on_site": "01:00:00", ...  },
        {
          "type": "break",
          "id": "route0_morning_break",
          "arrival_time": "11:00:00",
          "time_on_site": "00:15:00",
          "distance_to_meters": 0.0,
          "time_to": "00:00:00"
        },
        { "id": "job0", "arrival_time": "11:16:44", "time_on_site": "00:00:00", ... },
        { "id": "job3", "arrival_time": "11:26:12", "time_on_site": "01:00:00", ... },
        { "id": "job2", "arrival_time": "12:41:30", "time_on_site": "01:00:00", ... },
        {
          "type": "break",
          "id": "route0_lunch_break",
          "arrival_time": "13:00:00",
          "time_on_site": "00:30:00",
          "distance_to_meters": 0.0,
          "time_to": "00:00:00"
        },
        { "type": "depot", "arrival_time": "14:23:20", ...  }
      ]
    }
    

    See Also

    • Routing with Driver Breaks.
    • The route.breaks field.
    In this article
    Back to top
    © 2023 Verizon. All rights reserved. Verizon Privacy policy California Privacy Notice Your Privacy Choices Privacy request