Videos
Video file exchange via agrirouter. AVI, WMV, and MP4 formats
Three video formats are supported for exchanging recorded video between endpoints. All of them use binary encoding and follow the same transfer pattern.
| Property | Value |
|---|---|
| Technical Message Type | vid:avi |
| Information Type | Video |
| Format | Binary (AVI) |
| Protobuf Schema | None (binary format) |
AVI (Audio Video Interleave) container format. A widely-supported legacy format for uncompressed or lightly compressed video.
| Property | Value |
|---|---|
| Technical Message Type | vid:mp4 |
| Information Type | Video |
| Format | Binary (MP4) |
| Protobuf Schema | None (binary format) |
MPEG4 container format. The common modern choice: efficient compression at good quality. Recommended for most use cases.
| Property | Value |
|---|---|
| Technical Message Type | vid:wmv |
| Information Type | Video |
| Format | Binary (WMV) |
| Protobuf Schema | None (binary format) |
Windows Media Video format. Occasionally seen on agricultural equipment with Windows-based terminals.
Data Format
Send the raw video bytes as the request body with Content-Type: application/octet-stream. Do not Base64-encode the payload yourself; agrirouter applies transport encoding internally for chunked message types.
Chunking
Video files are typically large, so chunking is common. The API handles it for you: if a video exceeds the internal chunk size, the API splits it on the way out and the recipient gets the reassembled file as a single FILE_RECEIVED event. No manual chunking or reassembly on your side.
Use Cases
- Field operation recordings: video documentation of planting, spraying, or harvesting operations
- Machine operation documentation: recording machine behavior for maintenance or training
- Quality assurance: visual records of crop handling and processing
- Incident documentation: recording equipment issues or field conditions for later review