GSoC 2026 Week 11 Report: Implementation of Maximum Weighted Matching Algorithm to pgRouting

Initiatives Google Summer of Code
1

Mayur Galhate
Github id: mayurgalhate

Mentors: @cvvergara, @robe
Organization: OSGeo / pgRouting
OSGeo Profile: OSGeo Profile Link
Project Wiki: Github Wiki Link
Repository: Repo Link

Hello everyone,

This is my eleventh weekly report of Official coding period for GSoC 2026

Week 11 Report (10 august ~ 16 august)

What did I get done this week?

  1. Applied the same consolidation approach demonstrated by @cvvergara for pgr_coreNumbers, this time to pgr_maxWeightedMatching. Since pgr_maxWeightedMatching returns IID_t_rt (from_vid, to_vid, cost), coloring_process.h could not be reused because it supports II_t_rt.
  2. Switched pgr_maxWeightedMatching to the appropriate shared IID_t_rt process/driver architecture and removed the function-specific process/driver implementation where it was no longer needed.
  3. Since no existing process/driver pair was suitable for IID_t_rt and maximum weighted matching, added the required process/driver integration with a Which switch and a MAXWEIGHTEDMATCHING case, following the existing pgRouting driver structure.
  4. Added MAXWEIGHTEDMATCHING to the enumeration and get_name(), and repointed pgr_maxWeightedMatching.c to call the new process function.
  5. Updated pgRouting-introduction.rst and release_notes.rst with pgr_maxWeightedMatching.
  6. Resolved merge conflicts and synchronized the changes with the latest branch.

Boost Proof of Concept – PR #634

  • Opened the first Boost version PoC branch for pgr_maxWeightedMatching to start testing Boost version compatibility in CI.

  • Updated wiki page can be found in [1]

  • The pull request can be found in [2]

  • The pull request can be found in [3]

Am I blocked on anything?

  • No

References:

Thank you,
Mayur Galhate