• 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

    load_amount

    A load_amount object is a quantity of some user-defined metric that represents either a route's capacity or a job's load. Using load_amount enables the use of multiple capacity metrics. Note that this cannot be used in conjunction with route.load_capacity and job.load.

    Name Type Description
    amount float Required. The amount of the metric. Represents either a route's capacity or the job's load. When specifying a load for a job you may use a negative amount to represent a load needing to be picked up. A positive amount represents a delivery.
    metric capacity_metric or id Required. The metric the load is measured in. See Routing with Capacities. Up to four different metrics can be used in a single request.

    Example

    The following evaluate request demonstrates several details when using multiple load capacities with load_amount:

    {
      "routes": [
        {
          "id": "route0_route_with_several_load_capacities",
          "location": "39.718005, -104.969531",
          "load_capacities": [
            { "metric": "weight_kg", "amount": 200 },
            { "metric": "volume_liters", "amount": 500 }
          ],
          "jobs": [
            { "id": "job0", "location": "39.635928, -105.049219", "loads": [{ "metric": "weight_kg", "amount": 20 }, { "metric": "volume_liters", "amount": 60 }] },
            { "id": "job1", "location": "39.725375, -104.791080" },
            { "id": "job2", "location": "39.708990, -105.026954", "loads": [{ "metric": "volume_liters", "amount": 60 }, { "metric": "metric_without_a_limit", "amount": 1 }] },
            { "id": "job3", "location": "39.653975, -105.093750", "loads": [] }
          ]
        }
      ]
    }
    

    This request returns a result with no load violations. It uses three user-defined metrics (out of a maximum 4):

    • weight_kg.
    • volume_liters.
    • metric_without_a_limit.

    The route defines two limits: one for weight_kg and one for volume_liters. The load metric metric_without_a_limit is not specified on the route, so has no limit.

    The loads on the jobs may include fewer or more metrics than the routes that they can be routed on. If a particular metric is not specified on a job, it is taken to have an amount of 0.

    See Also

    • Routing with Capacities.
    • The route.load_capacities field.
    • The job.loads field.
    In this article
    Back to top
    © 2023 Verizon. All rights reserved. Verizon Privacy policy California Privacy Notice Your Privacy Choices Privacy request