Skip to content

Phase 6: MapPhase - Refactor to Polars #500

@mattsan-dev

Description

@mattsan-dev

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

  • MapPhase phase accepts the normalise phase LazyFrame without errors.
  • Legacy MapPhase behaviour is reproduced using Polars.
  • Outputs match the legacy MapPhase phase (apart from expected improvements).
  • No Pandas or row‑based Python operations are used.
  • Add test cases
  • Refactored code complies with project formatting and style standards (black/flake8/pep)

Resourcing & Dependencies
Depends on ConcatField phase, no external teams.

Metadata

Metadata

Labels

No labels
No labels

Type

Projects

Status

In Review / QA 🔎

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions