Images
Image file exchange via agrirouter. BMP, JPEG, and PNG formats
Three image formats are supported for exchanging visual data between endpoints. All of them use binary encoding and follow the same transfer pattern.
| Property | Value |
|---|---|
| Technical Message Type | img:bmp |
| Information Type | Image |
| Format | Binary (BMP) |
| Protobuf Schema | None (binary format) |
Bitmap images in the standard BMP format. Uncompressed, so quality is preserved but file sizes are large.
| Property | Value |
|---|---|
| Technical Message Type | img:jpeg |
| Information Type | Image |
| Format | Binary (JPEG) |
| Protobuf Schema | None (binary format) |
JPEG images with lossy compression. Good for photographs and complex imagery when smaller file sizes are worth some quality loss.
| Property | Value |
|---|---|
| Technical Message Type | img:png |
| Information Type | Image |
| Format | Binary (PNG) |
| Protobuf Schema | None (binary format) |
PNG images with lossless compression. Good for screenshots, diagrams, and images that need transparency.
Data Format
Send the raw image 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
The API handles chunking for you. If an image 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 photos: documenting crop conditions, pest infestations, or weed pressure
- Crop documentation: growth stage records and visual monitoring
- Machine diagnostics: screenshots from machine terminals or diagnostic displays
- Scouting imagery: visual records from field scouting operations