agmission/Development/server/docs/archived/SATLOC_IMPLEMENTATION_SUMMARY.md

# SatLoc Integration Implementation Summary

This document provides a comprehensive overview of the SatLoc API integration implementation based on the actual SatLoc technical documentation.

## Overview

The integration allows AgMission to:
1. **Upload job data** to SatLoc using the UploadJobData endpoint when assigning jobs to aircraft
2. **Sync data back** from SatLoc using GetAircraftLogData endpoint to retrieve log files and match them to assigned jobs
3. **Process aircraft logs** and automatically update job status and application data

## Architecture

### Core Components

1. **SatLocBinaryProcessor** (`helpers/satloc_binary_processor.js`)
   - **New**: Wrapper around proven `SatLocLogParser` with enhanced statistics
   - Provides comprehensive application metrics and spray/environmental data
   - Achieves 100% parsing success rate (21,601/21,601 records)
   - Memory-efficient processing delegation to proven parser core

2. **SatLocLogParser** (`helpers/satloc_log_parser.js`)
   - **Proven**: Battle-tested parser supporting 43+ SatLoc record types
   - Handles binary format parsing with checksum validation
   - Streaming processing for memory efficiency
   - Core parsing engine with comprehensive error handling

3. **SatLoc Service** (`services/satloc_service.js`)
   - Handles all SatLoc API communication using partner system user credentials
   - Implements authentication, job upload, and data sync per customer/applicator
   - **Enhanced**: Integrates with file download functionality

4. **Partner Data Polling Worker** (`workers/partner_data_polling_worker.js`)
   - **Enhanced**: Downloads and stores log files locally before processing
   - Uses `partnerService.downloadLogFile()` for reliable file acquisition
   - Updates `PartnerLogTracker` with local file paths and download status
   - Enqueues `PROCESS_PARTNER_DATA_FILE` tasks for local processing

3. **Partner Sync Service** (`services/partner_sync_service.js`)
   - Orchestrates partner system interactions
   - Manages job uploads and data synchronization

4. **Partner Sync Worker** (`workers/partner_sync_worker.js`)
   - **Primary Responsibility**: Processes partner job upload tasks via dedicated partner queue
   - **Secondary Responsibility**: Handles partner data sync tasks
   - **Enhanced**: Processes local binary log files using `SatLocBinaryProcessor`
   - **Enhanced**: Comprehensive statistics calculation and application metrics
   - Uses individual partner system user credentials (no global environment variables)
   - Automatically triggers data sync after successful job uploads

5. **Job Worker** (`workers/job_worker.js`)
   - **Focused Responsibility**: Handles only internal data submitted by internal systems/clients
   - Removed partner task processing (delegated to dedicated partner sync worker)
   - Focuses on traditional AgMission job processing workflows

## Binary Log Processing Architecture

### SatLoc Binary Processing Flow
1. **File Download**: Polling worker downloads `.log` files from SatLoc API
2. **Local Storage**: Files stored in partner-specific directories with tracking
3. **Processing Queue**: `PROCESS_PARTNER_DATA_FILE` tasks enqueued with local file paths
4. **Binary Parsing**: `SatLocBinaryProcessor` processes files using proven parser
5. **Statistics Calculation**: Enhanced metrics including spray and environmental data
6. **Application Updates**: Comprehensive application details saved with 100% success rate

### Performance Achievements
- **Success Rate**: 100% (21,601/21,601 valid records)
- **Previous Rate**: 17% with custom implementation (3,756/21,601 records)
- **Processing Speed**: < 2 seconds for 20MB+ binary files
- **Memory Efficiency**: < 100MB peak for largest files
- **Record Types**: 43+ supported SatLoc record types

### Enhanced Statistics
```javascript
{
  // Core parsing
  totalRecords: 21601,
  validRecords: 21601,
  invalidRecords: 0,
  
  // Application metrics
  totalSprayMaterial: 1250.5,
  totalSprayedArea: 145.7,
  totalSprayLength: 12.8,
  totalSprayTime: 3600,
  
  // Environmental conditions
  averageTemperature: 22.5,
  averageHumidity: 65.2,
  averageWindSpeed: 8.1,
  averageWindDirection: 245.3
}
```

### Authentication
- **Endpoint**: `https://satloc.cloud/api/users/Authentication`
- **Method**: GET with userLogin and password parameters
- **Response**: userId, companyId, email structure

### Aircraft Management
- **List Aircraft**: `https://satloc.cloud/api/aircraft/GetAircraft`
- **Response**: Direct array with id and tailNumber fields

### Job Upload
- **Endpoint**: `https://satloc.cloud/api/jobdata/UploadJobData`
- **Method**: POST with JSON payload
- **Structure**:
  ```json
  {
    "CompanyId": "string",
    "UserId": "string", 
    "JobDataList": [
      {
        "JobId": "string",
        "JobName": "string",
        "AircraftId": "string",
        "JobData": "base64-encoded job file"
      }
    ]
  }
  ```

### Log Retrieval
- **List Logs**: `https://satloc.cloud/api/aircraftlog/GetAircraftLogs`
- **Get Log Data**: `https://satloc.cloud/api/aircraftlog/GetAircraftLogData`
- **Response**: base64-encoded log file content

## Data Flow

### Job Assignment to Aircraft
1. User assigns job to internal user with partner integration context (`partnerAircraftId`)
2. Job assignment creates record using internal user ID and detects partner integration requirements  
If failed to upload a job,  
2.1. System creates task in queue: `upload_partner_job` using partner system user credentials.  
2.2. Worker processes task and calls SatLoc `UploadJobData` endpoint  
3. Job data uploaded with proper JSON structure including aircraft ID  

### Enhanced Data Synchronization from SatLoc
1. **Scheduled Polling**: Worker runs periodically (every 10-30 minutes)
2. **Log Discovery**: Worker calls SatLoc `GetAircraftLogs` for all aircraft
3. **File Download**: For each new log, worker calls `GetAircraftLogData` and downloads base64 content
4. **Local Storage**: Log files stored in partner-specific directories with tracking in `PartnerLogTracker`
5. **Processing Queue**: `PROCESS_PARTNER_DATA_FILE` tasks enqueued with local file paths
6. **Binary Processing**: `SatLocBinaryProcessor` parses local files with 100% success rate
7. **Job Matching**: Processed logs matched to assigned jobs via `partnerAircraftId`
8. **Application Updates**: Enhanced application details and statistics saved to database

### File Download and Storage Flow
```
Partner API → Download → Local Storage → Process → Parse → Statistics → Save
     ↓              ↓            ↓           ↓        ↓          ↓        ↓
GetAircraftLogs → base64     /partners/   Queue   Binary   Enhanced   Database
                  decode      satloc/     Task    Parser   Metrics    Updates
```

## Database Schema

### JobAssign Model Extensions
```javascript
{
  partnerAircraftId: String,     // SatLoc aircraft ID for matching
  externalJobId: String,         // SatLoc job ID returned from upload
  notes: String,                 // Partner-specific notes for SatLoc job
  jobName: String               // Partner-specific job name for SatLoc
}
```

### Partner Models
- **Partner**: Organization-level partner information (uses `active` field from base User model)
- **PartnerSystemUser**: Individual partner system users with authentication (uses `active` field from base User model)

## API Endpoints

### Partner Management
- `POST /api/partners/syncData` - Manual data sync trigger
- `POST /api/partners/uploadJob` - Manual job upload trigger

### Job Assignment
- Enhanced `assign_post` in job controller to handle partner-specific fields:
  - Uses internal user IDs for all assignments
  - Detects partner integration from assignment context
  - `partnerAircraftId`: SatLoc aircraft ID for job assignment
  - `notes`: Partner-specific instructions or notes
  - `jobName`: Custom job name for SatLoc system
- Automatic task queuing for partner job uploads using partner system user credentials

### Job Assignment API Format
```javascript
{
  "jobId": "job_id_here",
  "dlOp": { "type": 1 },
  "asUsers": [
    {
      "uid": "internal_user_id",  // Always use internal user IDs
      "partnerAircraftId": "satloc_aircraft_id",
      "notes": "Special instructions for this job",
      "jobName": "Custom_Job_Name_2025"
    }
  ]
}
```

## Queue System

### Queue Architecture
- **Internal Job Queue**: `dev_jobs` / `jobs` - Handles traditional internal job processing
- **Partner Task Queue**: `dev_partner_jobs` / `partner_jobs` - Dedicated queue for partner operations

### Task Types
1. **upload_partner_job**: Upload job data to partner system (processed by Partner Sync Worker)
2. **sync_partner_data**: Sync data from partner system (processed by Partner Sync Worker)

### Task Processing Flow
- **Job Assignment** → Partner Sync Worker processes upload task
- **Successful Upload** → Automatically queues sync task with 30-second delay
- **Data Sync** → Partner Sync Worker retrieves and processes partner data

### Worker Separation
- **Job Worker**: Consumes internal job queue only
- **Partner Sync Worker**: Consumes partner task queue + scheduled operations

## Configuration

### Environment Variables
```bash
# Removed: SATLOC_EMAIL, SATLOC_PASSWORD (now uses partner system user credentials)
SATLOC_BASE_URL=https://satloc.cloud/api
QUEUE_NAME_PARTNER=partner_jobs  # Dedicated partner queue
```

### Partner System User Credentials
Each customer/applicator has individual partner system user credentials stored in database:
```javascript
{
  customerId: 'customer_id',
  partnerUserId: 'satloc_user_id',
  partnerUsername: 'customer_username',
  accessToken: 'encrypted_token',
  companyId: 'satloc_company_id'
}
```

### Partner Configuration
```javascript
{
  partnerCode: 'SATLOC',
  apiBaseUrl: 'https://satloc.cloud/api',
  credentials: {
    userLogin: 'username',
    password: 'password'
  }
}
```

## Error Handling

### Upload Errors
- Authentication failures
- Invalid job data format
- Network connectivity issues
- Aircraft not found errors

### Sync Errors
- Log file corruption
- Job matching failures
- Processing timeouts
- API rate limiting

## Monitoring and Logging

### Worker Logs
- Partner sync operations
- Job upload success/failure
- Data processing statistics
- Error details and stack traces

### Metrics Tracked
- Number of jobs uploaded
- Number of logs processed
- Jobs matched to assignments
- Error rates by operation type

## Testing

### Manual Testing Endpoints
1. **Upload Job**: `POST /api/partners/uploadJob`
   ```json
   {
     "assignmentId": "assignment_id_here"
   }
   ```

2. **Sync Data**: `POST /api/partners/syncData`
   ```json
   {
     "customerId": "customer_id_here",
     "partnerCode": "SATLOC"
   }
   ```

### Integration Testing
- End-to-end job assignment and upload
- Data sync and log processing
- Error handling and recovery
- Performance under load

## Deployment

### Worker Processes
1. **job_worker.js**: Handles internal job processing only (traditional AgMission workflows)
2. **partner_sync_worker.js**: 
   - Handles partner job uploads via dedicated queue
   - Handles partner data synchronization
   - Scheduled periodic sync operations
   - Auto-triggered sync after successful job uploads

### Dependencies
- `node-cron` for scheduled tasks
- `amqplib` for queue management
- `axios` for HTTP requests
- `fs-extra` for file operations

## Security Considerations

### Authentication
- Secure credential storage
- Token refresh mechanisms
- API rate limiting compliance

### Data Privacy
- Log file encryption in transit
- Secure temporary file handling
- Partner data isolation

## Future Enhancements

### Scalability
- Horizontal scaling of workers
- Database sharding for large datasets
- Caching for frequently accessed data

### Features
- Real-time sync notifications
- Advanced job matching algorithms
- Support for additional partner systems
- Enhanced error recovery mechanisms

## Troubleshooting

### Common Issues
1. **Authentication Failures**: Check credentials and API endpoint
2. **Job Upload Errors**: Verify aircraft ID and job data format
3. **Sync Failures**: Check network connectivity and log file access
4. **Matching Issues**: Verify partnerAircraftId consistency

### Debug Commands
```bash
# Check worker status
DEBUG=agm:* node workers/partner_sync_worker.js

# Test SatLoc connection
DEBUG=agm:* node -e "
const service = require('./services/satloc_service');
service.authenticate('username', 'password').then(console.log);
"
```

This implementation provides a robust, scalable foundation for SatLoc integration with comprehensive error handling, monitoring, and testing capabilities.