National Irrigation Systems
Communal Irrigation Systems
1st Dry · 2nd Dry · Wet
Area Analytics
Digital Monitoring Platform for Region 10 Cropping Schedule, Program Area, and Irrigation System Planning
Planning Coverage
{{vm.kpi.records || 0 | number}} Filtered Records
Projected Production: {{vm.money(vm.calendarAnalytics.totalProduction)}} MT
Average Conservative Yield: {{vm.money(vm.calendarAnalytics.averageYield)}} MT/ha
Filters
Use filters to update all KPIs, charts, tables, and calendar listings.
Filtered Records
{{vm.kpi.records | number}}
NIS/CIS entries
Unique Systems
{{vm.kpi.systems | number}}
Distinct system names
FUSA
{{vm.money(vm.kpi.fusa)}}
Total service area
Operational
{{vm.money(vm.kpi.operational)}}
{{vm.percent(vm.kpi.operational, vm.kpi.fusa)}} of FUSA
{{vm.displaySeasonLabel()}}
{{vm.money(vm.kpi.selectedSeason)}}
Program area focus
Wet Season
{{vm.money(vm.kpi.wet)}}
Regular wet area
Program Area by Province
Program Area by Cropping Season
Commodity / Area Mix
Year and System Type Comparison
Cropping Schedule Records
Showing {{vm.pageItems().length}} of {{vm.filtered.length | number}} filtered records.
| Year | Type | System | Province | Municipality | Climate | FUSA | Operational | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| {{r.year}} | {{r.systemType}} | {{r.systemName}} {{r.systemTypeFull}} |
{{r.province}} | {{r.municipality}} | {{r.climateType}} | {{vm.money(r.fusa)}} | {{vm.money(r.operational)}} | {{vm.seasonRange(r.seasons.firstDry)}} | {{vm.money(r.seasons.firstDry.total)}} | {{vm.seasonRange(r.seasons.secondDry)}} | {{vm.money(r.seasons.secondDry.total)}} | {{vm.seasonRange(r.seasons.wet)}} | {{vm.money(r.seasons.wet.total)}} | |
| No matching records found. | ||||||||||||||
Page {{vm.page}} of {{vm.pageCount()}}
Cropping Calendar Focus
Schedule, area-per-hectare analytics, and conservative production projections update using the active filters.
Season Focus
{{vm.displaySeasonLabel()}}
Program Area: {{vm.money(vm.kpi.selectedSeason)}} ha
Conservative planning assumptions only. Adjust MT/ha values below based on validated local yield data.
Analyzed Area
{{vm.money(vm.calendarAnalytics.totalArea)}}
hectares
Projected Production
{{vm.money(vm.calendarAnalytics.totalProduction)}}
metric tons
Avg. Yield
{{vm.money(vm.calendarAnalytics.averageYield)}}
MT / hectare
Rice Projection
{{vm.money(vm.calendarAnalytics.riceProduction)}}
metric tons
Conservative Yield Assumptions
| Commodity / Land Use | MT per ha | Area | Projection |
|---|---|---|---|
| {{c.label}} | {{vm.money(c.area)}} ha | {{vm.money(c.production)}} MT |
Projected Production by Commodity
Upcoming / Scheduled Cropping Activities
{{t.earlyStart || t.lateStart || 'No Date'}} · {{t.seasonLabel}}
{{t.systemName}} {{t.type}}
{{t.province}} · {{t.municipality}} · {{t.climateType}}
Late Start: {{t.lateStart || '-'}} · Total Area: {{vm.money(t.total)}} ha · Rice: {{vm.money(t.rice)}} · Corn: {{vm.money(t.corn)}}
No schedule dates available for the selected filters.
Top Municipalities by Projected Production
Municipality Projection Summary
| Province | Municipality | Area | Projection | Avg MT/ha |
|---|---|---|---|---|
| {{m.province}} | {{m.municipality}} | {{vm.money(m.area)}} | {{vm.money(m.production)}} | {{vm.money(m.averageYield)}} |
| No projection data for the current filters. | ||||
Google Map Polygon Overlay
Polygons update from the active filters and summarize area plus projected production.
The included polygons are planning overlays for dashboard visualization. For official boundary/cadastral use, replace them with validated LGU/PSA/PSGC GeoJSON boundaries.
Current Map Summary
Polygon Level
{{vm.mapSummary.levelLabel}}
Polygons drawn: {{vm.mapSummary.count | number}}
Area
{{vm.money(vm.calendarAnalytics.totalArea)}}
ha
Projection
{{vm.money(vm.calendarAnalytics.totalProduction)}}
MT
Polygon Details
| Area | ha | MT |
|---|---|---|
| {{g.label}} {{g.records}} records |
{{vm.money(g.area)}} | {{vm.money(g.production)}} |
| No polygons for current filter. | ||
Firebase Realtime Database Tools
This module uses the Firebase configuration retained from the provided code. Writes depend on your Realtime Database security rules.
Firebase Status: {{vm.firebaseReady ? 'Ready' : 'Not Available'}}
Local Records: {{vm.records.length | number}}
Baseline Records: {{vm.baselineCount | number}}
{{vm.syncMessage}}
Recommended Data Path
- Use the embedded baseline dataset for initial review.
- Finalize security rules in Firebase.
- Import the baseline data to
croppingSchedule/records. - Let authorized encoders/admins update schedules through the Add/Edit module.