Input - 23.1

Spectrum Dataflow Designer Guide

Version
23.1
Language
English
Product name
Spectrum Technology Platform
Title
Spectrum Dataflow Designer Guide
First publish date
2007
Last updated
2024-05-09
Published on
2024-05-09T23:01:03.226155

Get Travel Boundary takes cost, cost unit, point latitude, and point longitude as input. The following table provides information on the format and layout of the input.

Table 1. Get Travel Boundary Input Data

Field Name

Format

Description

Latitude

String

Latitude of the point. Specify latitude in the format chosen in the Coordinate format option.

Longitude

String

Longitude of the point. Specify longitude in the format chosen in the Coordinate format option.

TravelBoundaryCost

String

(Optional) The cost distance or time, in the units specified by either the TravelBoundaryCostUnits field or the Default cost units option. For example, if the unit specified is miles and you specify 10 in this field, the cost would be 10 miles.

Use this field to override the default travel boundary cost on a record-by-record basis.

You can also specify multiple costs by specifying the values as a ";" delimited string. It will return a separate Iso Route Response for every cost specified. If you specify multiple costs, every response will have cost and costUnits associated with that response.

TravelBoundaryCostUnits

String

(Optional) The type of metric used to calculate the travel boundary. One of the following:

  • Feet
  • Hours
  • Kilometers
  • Meters
  • Miles
  • Minutes
  • Seconds
  • Yards

Use this field to override the default travel boundary cost units on a record-by-record basis.