Ride icon

Ride

Interact with Ride service API
Join our community

Actions7

Overview

The "Get Trip" operation of this node retrieves detailed information about a specific trip from the Ride service API using the trip's unique ID. It supports multiple output formats and optional data processing steps to clean and optimize GPS track points.

This node is beneficial in scenarios where you want to analyze or visualize trip data, such as:

  • Mapping a trip route on geographic platforms.
  • Exporting trip data for use in GPS devices or mapping software.
  • Extracting key points of interest from a trip (start, end, stationary points).
  • Generating static map images for reports or presentations.
  • Cleaning and optimizing GPS data for better accuracy and efficiency.

Practical examples include:

  • A cycling app that fetches a user's trip and displays it on a map.
  • A logistics company exporting trip routes in GPX or KML format for fleet tracking.
  • An analyst extracting investigation points to study stops during a trip.
  • Creating visual summaries by generating static map images of trips.

Properties

Name Meaning
Trip ID The unique identifier of the trip to retrieve.
Output Formats Select one or more formats to output the trip data:
- GeoJSON: Geographic data format for mapping and analysis.
- GPX: GPS device compatible format.
- Image: Static map image generated via Google Maps (requires API key).
- Investigation Points: Key points like start, end, and stationary locations.
- KML: Format for GPS/mapping applications.
- Raw Data: Original trip data as received from the API.
Sanitize Track Points Whether to apply sanitization to GPS track points to remove anomalies and correct invalid coordinates.
Normalize Track Points Whether to normalize GPS track points by reducing redundant points for improved efficiency.
Collinear Removal Level When normalization is enabled, controls how aggressively collinear points are removed:
- Low (0.2%) - Keep More Points
- Medium (0.35%) - Balanced
- High (0.5%) - Remove More Points
Image Width Width in pixels of the generated static map image (only applicable if "Image" output format is selected).
Image Height Height in pixels of the generated static map image (only applicable if "Image" output format is selected).

Output

The node outputs an array of items corresponding to the selected output formats. Each item contains:

  • json: The main JSON data structure with fields depending on the output format:

    • For Raw Data: The full trip data object as returned by the API.
    • For GeoJSON: A GeoJSON representation of the trip route.
    • For GPX: Metadata including file name and MIME type; the actual GPX data is provided as binary.
    • For KML: Metadata including file name and MIME type; the actual KML data is provided as binary.
    • For Image: Metadata including file name and MIME type; the static map image is provided as binary.
    • For Investigation Points: JSON containing extracted key points like start, end, and stationary points.

  • binary (optional): Contains binary data for GPX, KML, and Image outputs, prepared for downstream nodes that handle files.

Each output item includes an output_format field indicating its format.

Dependencies

  • Requires an authenticated connection to the Ride service API via an API key credential.
  • For generating static map images, a valid Google Maps API key must be configured within the Ride API credentials.
  • Utilizes internal utility modules for data transformation, sanitization, normalization, and format conversion (KML, GPX, GeoJSON, etc.).

Troubleshooting

  • Missing or invalid Trip ID: The node requires a valid trip ID. Ensure the ID is correct and exists in the Ride service.
  • Google Maps API key missing: If "Image" output format is selected but no Google Maps API key is configured, the node will throw an error requesting the key.
  • Conversion failures: Errors may occur during format conversions (e.g., to KML, GPX, GeoJSON) due to malformed data. Check the trip data integrity.
  • Sanitization/Normalization issues: Applying these options on trips without track points or with corrupted GPS data might cause unexpected results.
  • API request errors: Network issues, invalid credentials, or API limits can cause HTTP errors. Verify API access and credentials.

To resolve errors:

  • Confirm all required parameters are set correctly.
  • Provide a valid Google Maps API key if generating images.
  • Check network connectivity and API credential validity.
  • Review error messages for specific conversion problems.

Links and References

Discussion