Overview
The FilterPhase step now produces data using Polars LazyFrames, but the MapPhase step still uses the legacy implementation and cannot process this new output. To keep the pipeline consistent and efficient, the MapPhase phase must be updated to use the Polars version. This will keep existing behaviour while modernising the underlying process.
Tech Approach
- Update digital_land/phase/MapPhase.py so it delegates to the Polars parse implementation.
- Implement the full MapPhase logic inside digital_land/phase_polars/transform/MapPhase.py.
- Convert existing MapPhase rules into Polars lazy transformations.
- Ensure the MapPhase phase accepts the LazyFrame produced by the new normalise step.
- Keep the same public interface so no downstream code needs changing.
Acceptance Criteria/Tests
Resourcing & Dependencies
Depends on ConcatField phase, no external teams.
Overview
The FilterPhase step now produces data using Polars LazyFrames, but the MapPhase step still uses the legacy implementation and cannot process this new output. To keep the pipeline consistent and efficient, the MapPhase phase must be updated to use the Polars version. This will keep existing behaviour while modernising the underlying process.
Tech Approach
Acceptance Criteria/Tests
Resourcing & Dependencies
Depends on ConcatField phase, no external teams.