• 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

    marker

    The address and map coordinates of a physical location are represented by a marker object.

    Name Type Description
    country string Optional. The two-letter country code; for example, US. This field is used only by the UI.
    custom custom User-supplied custom fields that are returned unmodified in the response. These have no effect on optimization.
    formatted_address string Optional. The formatted address of the geocode. This should not include the country; for example, 4436 Delaware St, Denver, Colorado, 80216. This field is used only by the UI.
    id id A unique marker ID.
    intersection latlon Optional. The map coordinates of where the address intersects with the street.
    location_type path_request_location_type Optional Defines the type of location to support more accurate routing.
    is_depot boolean Optional. If set to true, the optimizer considers the marker location to be a depot that the driver can return to mid-route.
    attributes string[] Optional. The attributes provided by this depot (when is_depot is true). Use this with job.required_pre_job_depot_attributes and job.required_post_job_depot_attributes. See Routing with Attributes.
    location latlon The map coordinates of the marker.
    name string Optional. The name of the marker.

    Location and Intersection

    The Geocode call returns both an intersection and a location. The intersection is the point where the driveway meets the road. If location is used without intersection, the location can snap to a driveway on a different road when routing to the marker.

    Short Form

    For simplicity, a string can be specified instead of a marker object when making requests. This is a shorthand method for setting the location field directly. In the following example, job0 and job1 are at the same location:

    {
      "jobs": [
        {
          "id": "job0",
          "location": "33.584409,-117.730949",
        },
        {
          "id": "job1",
          "location": {
            "location": "33.584409,-117.730949"
    	  }
        }
      ]
    },
    

    Example

    Example marker object:

    {
      "location": "33.584362,-117.730968",
      "intersection": "33.584409,-117.730949",
      "formatted_address": "20 Enterprise, Aliso Viejo, California, 92656",
      "country": "US"
    }
    

    See Also

    • job.location, route.location.
    • The Geocode endpoint.
    • The Reverse Geocode endpoint.
    In this article
    Back to top
    © 2023 Verizon. All rights reserved. Verizon Privacy policy California Privacy Notice Your Privacy Choices Privacy request