Geoprocessing is complete only when the output is verified.

Validate before processing.

Start by reading the data rights, location and observation date for each layer. The coordinate reference system determines whether distance and area operations are meaningful. Use an appropriate projected CRS for metres or square metres and retain the original datasets.

• Coordinate systems: document CRS/EPSG, axis order, units and any transformation.
• Geometries: count input features, check types and identify invalid or empty geometry.
• Attributes: preserve stable IDs, timestamps, expected fields and relevant source metadata.
• Authority: know whether the layer is official, user-drawn, illustrative or simulated.

Specify the actual GIS operation.

A buffer depends on distance units, cap or join policy and whether overlaps should dissolve. Intersection depends on both geometries, selected fields and topology. Clipping depends on a valid boundary and output geometry expectations. A run should record exact parameters and distinguish rejected requests, empty outputs and successful operations.

• Buffer: choose the correct metric CRS, distance, geometry treatment and dissolve option.
• Intersection: check both layers, overlapping extent, output schema and feature count.
• Clip: verify the clipping polygon, coordinate systems, output area and source lineage.
• Avoid conflating straight-line proximity with travel distances through a road network.

Reopen the artifact in a second GIS reader.

A credible analysis produces a spatial file or database table that another analyst can independently inspect. Record exact input versions, tool parameters, time, output location, warnings and validation outcomes. If a model asked for the task, distinguish its request from the actual native GIS execution receipt.