[Mayukh-D]

Did you read the Contributor Guide?

• Yes, I have read the Contributor Rules and Contributor Development Guide

Is this PR related to a ticket?

• Yes, and the PR name follows the format [GH-XXX] my subject. Closes ST_Pixelize small polygon error #1272

What changes were proposed in this PR?

ST_Pixelize traces lines and polygon rings with Bresenham's algorithm, which draws a segment's start pixel but not its end. When every vertex of a geometry falls in the same pixel, every segment draws nothing and the expression fails on assert(pixels.size() > 0).

Now:

• a line or polygon that traces to no pixels returns the one pixel that contains it
• collections (including the Multi* types) are pixelized member by member, so a GeometryCollection no longer fails with a MatchError
• empty geometries return no pixels instead of failing

Geometries that span several pixels are traced exactly as before. VizTestBase now calls super.beforeAll(), so the viz suites register Sedona's SQL functions themselves instead of relying on another suite running first.

One visible change: a Multi* geometry with a member small enough to fit inside one pixel used to get no pixels for that member, and now gets that member's pixel. Geometries outside the boundary are not skipped; they keep their computed pixel, the same way ST_Pixelize already handles points.

How was this patch tested?

New cases in PixelizeTest for tiny lines and polygons, collections and empty geometries. Ran the viz tests on Spark 3.5 / Scala 2.12 and Spark 4.1 / Scala 2.13, and compared the old and new code on 3,000 random shapes: everything that pixelized before gives the same pixels, apart from the Multi* case above.

Did this PR include necessary documentation updates?

• Yes, I have updated the documentation.

Assisted by Claude Code
Generated-by: Claude Code (Claude Opus 5.5)

[Mayukh-D]

Hi @jiayuasu, when you get a chance, could you approve the CI workflows for this one? They're still waiting on maintainer approval. Happy to address any review comments once it's run. Thanks!

[Mayukh-D]

Hi @jiayuasu, whenever you have time, this one is ready for review. CI is green, and it follows your comment on #1272 that ST_Pixelize should always return at least one pixel. While fixing it I found a related rasterization bug, which is in #3485 (also green). Happy to make any changes to either, or to close them if they're not something you want right now. Thanks for merging #3503!