Skip to main content

YardSpot

The YardSpot node integrates with the YardSpot yard management system to post asset location data, enabling real-time tracking and management of trailers, containers, and other assets within yard facilities.

Overview​

The YardSpot node is essential when you need to:

  • Asset tracking - Monitor trailer and container locations in real-time
  • Yard management - Maintain accurate asset positions within facilities
  • Gate operations - Record ingate and outgate events automatically
  • Location updates - Post GPS coordinates and timestamps for assets
  • Inventory management - Keep accurate counts of assets in the yard
  • Operational visibility - Provide real-time asset visibility to operations teams

Configuration​

Required Fields​

  • Asset ID - Unique identifier for the asset being tracked
  • Latitude - GPS latitude coordinate of asset location
  • Longitude - GPS longitude coordinate of asset location
  • Timestamp - Date and time of the location update
  • Source - System or device providing the location data

Optional Fields​

  • Type - Asset type classification (trailer, container, chassis, etc.)
  • Image - URL to asset image or photo
  • Event - Specific event type (ingate, outgate, move, etc.)

Authentication​

  • API credentials - YardSpot API key and authentication details

Operations​

Create Asset Location​

Add new asset location data to YardSpot:

  • Location posting - Submit GPS coordinates and timestamp
  • Asset identification - Link location to specific asset ID
  • Event classification - Specify the type of location event
  • Source tracking - Record the origin of location data

Example Usage & Common Use Cases​

Gate Event Processing​

Gate Operations:
  RFID scan at gate → Extract asset data → Post to YardSpot

Configuration:
  Action: Create Asset Location
  Asset ID: {{rfidData.trailerId}}
  Latitude: {{gateLocation.lat}}
  Longitude: {{gateLocation.lng}}
  Timestamp: {{currentTimestamp}}
  Source: "Gate Scanner"
  Event: "ingate"

Output: Asset location recorded in YardSpot system

GPS Tracker Integration​

Real-time Tracking:
  GPS device update → Process coordinates → Update YardSpot

Configuration:
  Asset ID: {{gpsData.deviceId}}
  Latitude: {{gpsData.latitude}}
  Longitude: {{gpsData.longitude}}
  Timestamp: {{gpsData.timestamp}}
  Source: "GPS Tracker"
  Type: "trailer"

Output: Continuous asset location updates in yard management system

Manual Location Updates​

Yard Operations:
  Operator input → Validate location → Post to YardSpot

Configuration:
  Asset ID: {{operatorInput.assetId}}
  Latitude: {{yardGrid.coordinates.lat}}
  Longitude: {{yardGrid.coordinates.lng}}
  Timestamp: {{currentTime}}
  Source: "Manual Entry"
  Event: "repositioned"

Output: Manual asset location update recorded

Batch Location Processing​

Bulk Updates:
  Process location file → Loop through assets → Update each in YardSpot

Loop Configuration:
  For each asset in file:
    Asset ID: {{asset.id}}
    Latitude: {{asset.location.lat}}
    Longitude: {{asset.location.lng}}
    Timestamp: {{asset.lastSeen}}
    Source: "Batch Import"
    Type: {{asset.type}}

Output: Multiple asset locations updated in batch

Automated Yard Sweeps​

Scheduled Inventory:
  Automated yard scan → Detect assets → Update all locations

Configuration:
  Trigger: Scheduled (daily)
  Process: Yard scanning system data
  
  For each detected asset:
    Asset ID: {{scanData.assetId}}
    Latitude: {{scanData.position.lat}}
    Longitude: {{scanData.position.lng}}
    Timestamp: {{scanData.scanTime}}
    Source: "Automated Scan"
    Image: {{scanData.photoUrl}}

Output: Complete yard inventory update

Exception Handling​

Asset Movement Alerts:
  Detect unexpected movement → Validate → Post alert location

Configuration:
  Asset ID: {{alert.assetId}}
  Latitude: {{alert.newLocation.lat}}
  Longitude: {{alert.newLocation.lng}}
  Timestamp: {{alert.detectionTime}}
  Source: "Security System"
  Event: "unauthorized_move"

Output: Security alert with location data posted to YardSpot

Data Format Requirements​

Coordinate Format​

  • Latitude - Decimal degrees format (e.g., 41.8781)
  • Longitude - Decimal degrees format (e.g., -87.6298)
  • Precision - Minimum 4 decimal places for accuracy
  • Range validation - Ensure coordinates are within valid ranges

Timestamp Format​

  • ISO 8601 - Standard timestamp format (2024-01-15T14:30:45Z)
  • Timezone - UTC preferred, local timezone acceptable with offset
  • Precision - Second-level precision minimum
  • Current time - Use current timestamp if not specified

Asset ID Format​

  • Unique identifier - Must be unique within YardSpot system
  • Consistent format - Use consistent ID format across all updates
  • Alphanumeric - Support for letters, numbers, and common symbols
  • Length limits - Respect YardSpot ID length requirements

Integration Features​

Real-time Updates​

  • Immediate posting - Location data sent to YardSpot in real-time
  • Event-driven - Trigger updates based on asset movements or events
  • Continuous tracking - Support for frequent location updates
  • Low latency - Minimize delay between detection and posting

Data Validation​

  • Coordinate validation - Verify GPS coordinates are valid
  • Timestamp validation - Ensure timestamps are reasonable
  • Asset ID verification - Validate asset exists in system
  • Required field checking - Ensure all mandatory fields are provided

Error Handling​

  • API error management - Handle YardSpot API errors gracefully
  • Retry logic - Automatic retry for transient failures
  • Data quality checks - Validate data before posting
  • Fallback procedures - Alternative actions when posting fails

Best Practices​

Data Quality​

  • Accurate coordinates - Ensure GPS data is precise and current
  • Consistent timestamps - Use synchronized time sources
  • Valid asset IDs - Verify asset identifiers before posting
  • Source identification - Always specify the data source

Performance​

  • Batch processing - Group multiple updates when possible
  • Rate limiting - Respect YardSpot API limits
  • Efficient updates - Only post when location significantly changes
  • Connection reuse - Maintain API connections efficiently

Security​

  • Credential protection - Secure YardSpot API credentials
  • Audit logging - Track all location updates for security

Operational​

  • Regular validation - Periodically verify posted data accuracy
  • Monitoring - Track posting success rates and errors
  • Backup procedures - Maintain local copies of location data
  • Documentation - Document asset ID conventions and procedures

Integration Patterns​

With IoT Devices​

GPS Tracker → Data Processing → YardSpot Node → Location Update

With Gate Systems​

RFID Scanner → Asset Identification → YardSpot Node → Gate Event

With Scheduling​

Cron Trigger → Yard Scan → Loop → YardSpot Node → Inventory Update

With Conditional Logic​

Location Change → If Node (significant move) → YardSpot Node → Update

Troubleshooting​

Common Issues​

  • Authentication failures - Verify YardSpot API credentials
  • Invalid coordinates - Check GPS data format and ranges
  • Missing required fields - Ensure all mandatory fields are provided
  • Rate limiting - Implement appropriate delays between requests

Debugging Tips​

  • Test with known coordinates - Use verified GPS coordinates for testing
  • Validate API access - Confirm YardSpot API connectivity
  • Check data formats - Verify all fields match expected formats
  • Monitor API responses - Review YardSpot API response messages

Performance Issues​

  • Slow API responses - Check network connectivity and YardSpot system status
  • High error rates - Review data quality and API usage patterns
  • Duplicate updates - Implement deduplication logic for repeated locations

The YardSpot node provides essential integration capabilities for yard management operations, enabling real-time asset tracking and location management within logistics facilities.