Ride icon

Ride

Interact with Ride service API
Join our community

Actions7

Overview

The node interacts with the Ride service API to retrieve detailed information about cycling or outdoor routes. Specifically, the "Get Route" operation fetches a single route by its ID and optionally processes its GPS track points for improved data quality and efficiency.

This node is beneficial in scenarios where users want to:

  • Retrieve detailed route data from the Ride service.
  • Clean up GPS track points by removing anomalies or invalid coordinates.
  • Optimize GPS data by reducing redundant points to improve performance in downstream applications.

Practical examples include:

  • Importing a specific cycling route into a workflow for analysis or visualization.
  • Cleaning GPS data before feeding it into mapping or tracking systems.
  • Reducing data size of GPS tracks for storage or transmission efficiency.

Properties

Name Meaning
Route ID The unique identifier of the route to retrieve.
Sanitize Track Points Whether to apply sanitization to GPS track points, which removes anomalies and corrects invalid coordinates.
Normalize Track Points Whether to apply normalization to GPS track points, reducing redundant data points for efficiency.
Collinear Removal Level Controls how aggressively collinear points are removed during normalization. Options: Low, Medium, High.

Output

The output JSON contains the detailed route data under a route property. This includes all route metadata and an array of GPS track points (track_points). If sanitization or normalization is applied, the track_points array reflects the cleaned or optimized data accordingly.

No binary data output is produced by this operation.

Example structure (simplified):

{
  "route": {
    "id": "string",
    "name": "string",
    "description": "string",
    "track_points": [
      {
        "latitude": number,
        "longitude": number,
        "elevation": number,
        "timestamp": "ISO8601 string"
      },
      ...
    ],
    ...
  }
}

Dependencies

  • Requires an API key credential for authenticating requests to the Ride service API.
  • The node makes HTTP GET requests to endpoints like /api/v1/routes/{routeId}.json.
  • No additional external services or environment variables are required specifically for this operation.

Troubleshooting

  • Common issues:

    • Invalid or missing Route ID will cause the API request to fail.
    • Network connectivity problems can prevent successful API calls.
    • Applying sanitization or normalization on routes without track points will have no effect.

  • Error messages:

    • "Unknown routes operation: getRoute": Indicates an unsupported operation was requested; ensure the operation name is correct.
    • API errors returned from the Ride service (e.g., 404 Not Found) usually mean the route ID does not exist or is inaccessible.
    • If the node fails silently or returns empty data, verify that the API credentials are valid and have sufficient permissions.

Links and References

Discussion