Rice lodging after storms: separate visible change and loss

Start with the operational question

Collect geolocated observations of crop orientation and affected extent after a storm, together with growth stage and safe access information. Preserve a suitable pre-event reference where available.

Separate observation from explanation

Lodged appearance does not directly quantify harvest loss. Wetness, shadows, crop variety, recovery, and the available harvesting method can influence both the image and the eventual outcome.

Design a field visit that produces comparable observations

Define the sampling unit and the meaning of every response before building the form. Use a short list of clear categories, allow an explicit unknown response, and distinguish a measured value from an observer assessment. Test the questions with the intended field team; a compulsory answer should never force someone to guess information that the visit cannot establish.

Record field identifier, observation date, location, method, and enough photographic context to interpret the observation later. Check device permissions, location quality, battery use, and the actual collection route. If offline collection is expected, test saving, closing, reopening, and synchronising with the intended browser or application. Document which steps depend on connectivity.

Review responses soon after collection while clarification is still possible. Keep the original observation and append a correction with its reason rather than silently replacing the source. Mark incomplete, contradictory, or poorly located records for follow-up. A smaller dataset with consistent definitions can support better analysis than a large collection of records whose sampling and terminology changed between observers.

Use the establishment date and water regime together

A paddy map needs to identify the actual field or irrigation unit, its establishment method, establishment date and observed crop stage. Transplanted and direct-seeded fields may follow different early-season patterns. Keep the crop season separate from a permanent field identifier, because a field can carry several crop cycles and a fallow period. A recent change in reflectance may indicate flooding, drainage or harvest rather than a sudden deterioration in the crop.

Water and young plants can contribute to the same pixel while the canopy is still open. Later, the developed canopy changes what the sensor observes. Compare fields at similar stages and inspect the water-management record before interpreting their vegetation values. Where water is delivered by a shared canal or scheme, keep that relationship in the map. A field's response may depend on supply conditions outside its own boundary, which a field-only analysis could overlook.

Keep abandoned, temporarily uncultivated and inaccessible paddies as explicit classes in seasonal records. Their absence from a survey should not automatically be interpreted as a failed crop or a missing planting event.

Observe water rather than guessing it from greenness

IRRI describes alternate wetting and drying as a controlled water-management practice that uses a field water-level tube to support irrigation decisions. Its suitability and operating procedure depend on field conditions and local guidance. A remote-sensing indicator is not a substitute for the water-level observation that a prescribed protocol requires. If the team is evaluating a water practice, retain the measurement method, reading date, crop stage and management action together in the field record.

During a scouting visit, examine the inlet, outlet, bunds and the distribution of water across the field. Record an observation of standing water separately from a conclusion about root-zone water availability. If a crop patch appears different, inspect neighbouring normal plants under comparable conditions and note pests, weeds, leaf symptoms and recent operations. Some problems can share an overhead appearance, so the first purpose of the map is to direct a well-designed inspection.

Validate crop-stage and harvest interpretations locally

Rice water requirements and sensitivity to stress vary through development, as the Sri Lankan Department of Agriculture explains in its stage-based guidance. A monitoring report should therefore show the observed growth stage rather than rely only on days after planting. When stage is uncertain, mark it as unverified and organise a check. Do not create a precise maturity or yield prediction from a greenness value without suitable local calibration and independent validation.

At harvest, link measured production to the harvested area, date and moisture basis used in the records. Keep lost, damaged or unharvested portions explicit instead of dividing every load by the whole field polygon. When reviewing a season, compare the image sequence, water observations, management events and measured outcomes together. State where cloud gaps or missing field visits prevent a firm conclusion. That transparent sequence is more useful for planning the next season than a single map presented as a complete diagnosis.

Design reference observations that represent the field

State the population that the sample should represent and the question it must answer. Select locations across relevant crop stages, terrain, management, and image conditions. Include ordinary areas and difficult cases, not only conspicuous anomalies or convenient roadside stops. Record selection rules so that later users understand where the reference is representative.

Define the observation unit, area or depth, timing, instrument or laboratory method, and required replicates using the appropriate discipline's protocol. A point observation and a satellite pixel have different spatial support. Record enough context to evaluate that mismatch. Keep inaccessible sites in the sampling log and explain any replacement rather than silently dropping them.

Separate reference collection from the result being evaluated when feasible. Review observer consistency and missing data before calculating agreement or error. Retain raw observations, corrections, and exclusions with their reasons. More samples can improve precision, but a large biased sample still fails to represent excluded conditions. Use the results within the population and period that the sampling design supports.

Keep identifiers, history, and evidence connected

Use a stable identifier for each field or asset and store its descriptive name separately. The identifier should remain useful when a crop changes, staff move, or an operational unit is subdivided. Define relationships explicitly: one field may have many visits, one visit may have several photographs, and one harvest lot may refer to several fields. Document those relationships before combining spreadsheets or map layers.

Changes need an effective date and a reason. Preserve earlier geometry or attribute versions when a correction affects historical reports. Record who approved the change and which source supported it. Correcting a boundary should not silently rewrite the area that was used for a previous season unless the report is intentionally revised and the revision is explained.

Test an export by bringing representative records back into the receiving workflow. Check that identifiers, dates, units, text encoding, coordinate interpretation, and missing values survive. Keep an unaltered source copy and a transformation note. A simple data dictionary and a named owner for each dataset often prevent more errors than an elaborate visual interface without clear responsibilities.

Define the deliverable and approval

Prepare a reviewed lodging map with photographs, severity definitions, unvisited areas, and a later reconciliation with actual harvesting records.

A practical review before sharing the result

Check the observation against its source and make sure the field identifier is correct. Review dates, units, missing values, quality exclusions, and geometry versions. Ask a colleague to reproduce one representative result from the recorded inputs. This small independent check often exposes a misunderstood field code or a processing assumption before it affects an entire report.

Write down the alternative explanations for the mapped pattern and identify what evidence would distinguish them. Keep a measured observation separate from the interpretation and from any treatment or management instruction. A decision should name its responsible reviewer and account for local operating procedures. If the evidence is insufficient, the appropriate output is a targeted inspection rather than a confident claim.

Keep the original result, any reviewed version, and a short change log. State which locations and periods the output can reasonably describe. When sharing a map, provide a clear legend, source dates, and an accessible explanation of uncertainty. The recipient should know whether a feature is a confirmed observation, a candidate awaiting inspection, or a model-based estimate.

Turn the investigation into a repeatable field cycle

Prepare the visit with a map that can be used at the intended location and a concise list of questions. Confirm access, permissions, equipment, and the availability of a person familiar with the field. Choose representative stops as well as unusual areas. Record where the planned route could not be followed, because missing observations can change how the result should be interpreted.

After the visit, review the observations while the team can still clarify them. Connect photographs, measurements, and comments to the same field and visit identifiers. Assign a follow-up status and preserve unresolved cases. A correction should explain what changed and why; it should not erase the original evidence or make an earlier interpretation appear to have been certain.

At the next suitable observation date, compare conditions using the same definitions and review any management or weather events that occurred between visits. Record the action actually completed and its operational outcome. This creates an evidence trail from an initial pattern to field confirmation and later review, making the mapping process easier to improve over successive seasons.