A municipal water-taxi farebox extract double-wrote the same tap when a job retried. Training row counts jumped but unique riders did not. Which cleaning step should run before feature builds?

Short Explanation

Think of a farebox retry that double-wrote the same tap. Row counts jumped, unique riders did not. Deduplicate on a stable key before you build features. Extra rows are not extra riders.

Full Explanation

Remove duplicate records as a cleaning step so later features are not double-counted. A stable tap key is that transform. Leaving duplicates, adding a Region, and Firehose do not dedupe.

×