> ## Documentation Index
> Fetch the complete documentation index at: https://domoinc-openapi-sync-dataflows.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Directions Connector

## Intro

The Google Directions API is a service that calculates directions between locations using an HTTP request. You can search for directions for several modes of transportation, including transit, driving, walking, or cycling. Directions may specify origins, destinations, and waypoints either as text strings (e.g. Chicago, IL or Darwin, NT, Australia ) or as latitude/longitude coordinates. The Directions API can return multi-part directions using a series of waypoints.

You connect to Google Directions account in the Data Center. This topic discusses the fields and menus that are specific to the Google Directions connector user interface. General information for adding DataSets, setting update schedules, and editing DataSet information is discussed in [Adding a DataSet Using a Data Connector](/s/article/360042926274 "Adding a DataSet Using a Data Connector").

## Prerequisites

None

## Connecting to Google Directions

This section enumerates the options in the **Details** pane in the Google Directions Connector page. The components of the other panes in this page, **Scheduling** and **Name & Describe Your DataSet**, are universal across most connector types and are discussed in greater length in [Adding a DataSet Using a Data Connector](/s/article/360042926274 "Adding a DataSet Using a Data Connector").

### Details Pane

This pane contains a number of options for specifying the data you want to retrieve into Domo.

<table border="1" cellpadding="1" cellspacing="1" data-aura-rendered-by="33:195;a"><thead><tr><th colspan="1" rowspan="1"><p> Menu </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr></thead><tbody><tr><td colspan="1" rowspan="1"><p> Origin </p></td><td colspan="1" rowspan="1"><p> Enter the origin. This can be a place name or latitude and longitude coordinates. Ensure that no space exists between the latitude and longitude values. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Destination </p></td><td colspan="1" rowspan="1"><p> Enter the destination. This can be a place name or latitude and longitude coordinates. Ensure that no space exists between the latitude and longitude values. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Sensor </p></td><td colspan="1" rowspan="1"><p> Select <b> Yes </b> if the device has a location sensor. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Mode </p></td><td colspan="1" rowspan="1"><p> Select the travel mode you want to pull data for. If you select <b> Transit </b>, be sure to enter a time in either the <b> Departure Time </b> or <b> Arrival Time </b> field. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Alternatives </p></td><td colspan="1" rowspan="1"><p> Select whether you want your route to include alternate routes. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Waypoints (Optional) </p></td><td colspan="1" rowspan="1"><p> Enter waypoints you would like to appear in your route, separated by the pipe '|' character (for example: <span class="mt-font-courier-new"> Charlestown,MA|Lexington,MA </span> ). </p></td></tr><tr><td colspan="1" rowspan="1"><p> Avoid </p></td><td colspan="1" rowspan="1"><p> Select whether you want to avoid ferries, highways, or tolls in your route. You can also choose to select <b> All </b> or <b> None </b>. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Unit </p></td><td colspan="1" rowspan="1"><p> Select whether to show metric or imperial units in your report. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Departure Time (Optional) </p></td><td colspan="1" rowspan="1"><p> Enter the estimated departure time. The accepted format is <span class="mt-font-courier-new"> dd/MM/YYYY hh:mm AM/PM. </span> For example: <span class="mt-font-courier-new"> 01/09/2014 6:55 PM </span>. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Arrival Time (Optional) </p></td><td colspan="1" rowspan="1"><p> Enter the estimated arrival time. The accepted format is <span class="mt-font-courier-new"> dd/MM/YYYY hh:mm AM/PM. </span> For example: <span class="mt-font-courier-new"> 01/09/2014 6:55 PM </span>. </p></td></tr></tbody></table>

### Other Panes

For information about the remaining sections of the connector interface, including how to configure scheduling, retry, and update options, see [Adding a DataSet Using a Data Connector](/s/article/360042926274 "Adding a DataSet Using a Data Connector").
