Description
Integrate with CAL FIRE and NIFC (National Interagency Fire Center) dispatch systems to pull incident data and push observation reports. This would allow Firevector to auto-populate incident names, locations, and resource assignments from official dispatch databases.\n\n## Research Needed\n\n- CAL FIRE/ROSS (Resource Ordering and Status System) API availability\n- IRWIN (Integrated Reporting of Wildland-Fire Information) data feeds\n- InciWeb public incident data\n- NIFC SIT-209 report format\n- Data sharing agreements required\n\n## Potential Features\n\n- Auto-populate incident list from active CAL FIRE incidents\n- Push completed observations to incident management teams\n- Import resource assignments for observer identification\n- Sync with ICS-209 reporting requirements\n\n## Acceptance Criteria\n\n- [ ] Research document on available APIs and data feeds\n- [ ] At least one read-only integration working (e.g., active incident list from InciWeb)\n- [ ] Observation export in a format compatible with incident reporting\n- [ ] Data sharing/privacy considerations documented\n\n## Blockers\n\n- Requires understanding of CAL FIRE's technical infrastructure\n- May require government agency partnerships\n- Data format standards need investigation
Description
Integrate with CAL FIRE and NIFC (National Interagency Fire Center) dispatch systems to pull incident data and push observation reports. This would allow Firevector to auto-populate incident names, locations, and resource assignments from official dispatch databases.\n\n## Research Needed\n\n- CAL FIRE/ROSS (Resource Ordering and Status System) API availability\n- IRWIN (Integrated Reporting of Wildland-Fire Information) data feeds\n- InciWeb public incident data\n- NIFC SIT-209 report format\n- Data sharing agreements required\n\n## Potential Features\n\n- Auto-populate incident list from active CAL FIRE incidents\n- Push completed observations to incident management teams\n- Import resource assignments for observer identification\n- Sync with ICS-209 reporting requirements\n\n## Acceptance Criteria\n\n- [ ] Research document on available APIs and data feeds\n- [ ] At least one read-only integration working (e.g., active incident list from InciWeb)\n- [ ] Observation export in a format compatible with incident reporting\n- [ ] Data sharing/privacy considerations documented\n\n## Blockers\n\n- Requires understanding of CAL FIRE's technical infrastructure\n- May require government agency partnerships\n- Data format standards need investigation