This node uses the Google Distance Matrix API to create a distance matrix for the provided origins and destinations. The matrix is created by pairing each input origin with each input destination and will contain the travel distance and duration for each pair. The distance unit is meter and the duration is returned in minutes.
If the input geometry is not a point geometry, the centroids will be automatically computed and used.
Select the geometry column that describes the origins.
Select the column which contains for each origin a unique ID. The selected column will be returned in the result table and can be used to link back to the original data.
Select the geometry column that describes the destinations.
Select the column which contains for each destination a unique ID. The selected column will be returned in the result table and can be used to link back to the original data.
Click here for details on how to obtain and use a Google API key for the Distance Matrix API.
The following travel modes are supported:
Available options:
If checked, the travel time and distance will be computed considering the traffic conditions. If unchecked, the travel time and distance will be computed without considering the traffic conditions.
The traffic model specifies the assumptions to use when calculating time in traffic.
Available options:
The departure time may be specified in two cases: - For requests where the travel mode is transit: You can optionally specify departure_time or arrival_time. If None the departure_time defaults to now (that is, the departure time defaults to the current time). - For requests where the travel mode is driving: You can specify the departure_time to receive a route and trip duration (response field: duration_in_traffic) that take traffic conditions into account. The departure_time must be set to the current time or some time in the future. It cannot be in the past.
Note: If departure time is not specified, choice of route and duration are based on road network and average time-independent traffic conditions. Results for a given request may vary over time due to changes in the road network, updated average traffic conditions, and the distributed nature of the service. Results may also vary between nearly-equivalent routes at any time or frequency.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension Geospatial Analytics Extension for KNIME from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.