Loading…
Upload Digitized Parcels
Digitize in QGIS or ArcGIS — the tools your team already knows — then bring the result in here. In QGIS: Layer → Save Features As → GeoJSON, keeping the layer's own CRS. Each feature needs a field holding the farmer's Control_No; that is what joins the polygon to the right farm and lets FPS check the area against what was declared.
1 · File
2 · Match & CRS
4326 for plain GeoJSON; 32651 if you exported in UTM 51N. Wrong here means every parcel lands in the wrong place.
3 · Orthomosaic (optional)
Branch Masterlist
1 · Upload a list
Use this template. Its column headings are what the importer reads to work out which column is which, and it carries the exact PSGC spelling of all 104 municipalities and 2,204 barangays across the five branches. A barangay spelled any other way loses its code, and every farmer in it gets a Control No. with the barangay missing — permanently, and with nothing to warn you.
NTA_FPS_Masterlist_Template.xlsx · Farmers, How to Use, and two PSGC reference sheets
Your own file will still work if it has at least a surname and a first-name column, and barangay, municipality, NTA ID, RSBSA, birthdate, suffix and mother’s maiden name are used when present. The template is strongly preferred: every heading in it is one the importer already knows, so nothing is silently dropped.
EW areas of responsibility
Routing depends on this. A barangay rule beats a municipality-wide one; rows with no match land with you to assign by hand.
2 · Batches
Loading…
Messages
Not instant. Field staff are offline most of the day and receive messages when they next sync — each thread shows when the other person last synced. For anything urgent, phone them. Messages are deleted automatically after 60 days; decisions, remarks and amendment outcomes are kept permanently in the record.
Loading…
EW Recommendations
Add a rule
Any condition here makes the rule apply only to parcels that have a soil test.
Rules in force
Loading…
Suitability map in use
Loading…
Parcel Amendments
Reported from the field. Approving a withdrawal removes the area from the season's reportable hectarage; nothing changes until you decide.
Loading…
Production Analytics
| Class | Farmers | Parcels | Avg ha |
|---|
Suitability from the 2021 NTA Soil and Water Technical Report. Hectarage planted outside a suitable class is where extension effort earns the most.
| Municipality | Suitability | Farmers | Active | Parcels | Geotagged | Contracted | Tobacco ha |
|---|
Call for geotagging
Parcels consolidated in phase 1 that have no GPS pin yet.
| Municipality | Province | Parcels | Farmers | Declared ha | EWs |
|---|
Pin integrity
Quarantined pins are recorded but do not count as geotagged, so their hectarage stays out of the reportable figures until someone clears them. Android reports mock providers definitively; iOS and the browser cannot, so those rely on the server-side checks — pin outside the municipality, identical coordinates to another parcel, or impossible travel between captures.
Routing by submitting device
The locked Geotag queue relies on the phone holding a frozen record across a field visit. iOS Safari cannot be relied on to do that — it evicts storage and suspends background GPS — so iOS submissions are returned for correction instead: the profile reopens, the EW adds the pin in the normal edit screen and resubmits. Android and web are unchanged.
Open calls
Progress since the call was issued.
Cancel a call
Withdraws the call and unfreezes those profiles.
Review Queue
to| Control No. | Farmer | Municipality | Branch | Assigned EW | Parcels | Status | Updated |
|---|
Area Reconciliation — PY2026-2027
Declared (RO606) vs validated (orthomosaic digitization). Flag = variance beyond 10%.
| Farmer | Municipality | Declared | Validated | Var % | Flags |
|---|
Unmatched Planted Parcels
Confirmed tobacco on imagery with NO profiled farmer — the unprofiled/uncontracted growers evidence layer for Branch Office follow-up.
| Municipality | Area (ha) | Orthomosaic | Source |
|---|
Consolidated Excel export
The workbook contains personal data under RA 10173. Store it on NTA-controlled storage and dispose of it per policy.
1 · Publish a build
Upload the APK from eas build. It is stored on the NAS and
served to phones over Tailscale — no Play Store, no public CDN.
2 · Set the policy
Latest = what's available (a gentle prompt).
Minimum = anything older is blocked from running.
3 · Who is on what
Check this before raising the minimum — blocking a device with unsynced profiles keeps that work off the server until the EW updates.
Published builds
eas update — phones pick them up on next launch,
nobody reinstalls anything. A change that adds a native capability (camera, biometrics, GPS libraries)
needs a new APK: publish it here and raise the minimum.
Create account
Accounts
| Username | Name | Role | Branch | Pest Clinic | Active | Actions |
|---|
Locked accounts
An account locks after 10 consecutive failed sign-ins and unlocks itself — 5 minutes the first time, longer on repeat. Only unlock manually when someone is in the field and cannot wait. A rising lockout count on one account may mean someone is guessing at it, so check before clearing.
Pending account requests
Applicants request a role; you assign it. Approving with a lower role than
requested is normal and expected. An approving officer cannot grant
Administrator or Approving Officer — those must go to FTSD,
otherwise one officer account could create more of its own kind.
Share the signup link: /signup.html