Split Coords (from COORDS)

Split Coords (from COORDS) (class SplitCoords) is the inverse of CombineCoords: it takes this pack's COORDS value and unpacks it into two plain INTS lists - one of x coordinates, one of y coordinates. If CombineCoords is the constructor for the coordinate type, this is the destructor, and it exists so you can get the raw numbers back out when you need them.

When is that useful? A few honest cases. You might have a COORDS value (from CombineCoords, or passed through a workflow) and want to display or log the positions, or hand individual x/y lists to something that only accepts INTS. It's also handy for editing: split, tweak one list, re-combine with CombineCoords - a cheap way to "map" a coordinate set without writing a custom node. And if you're learning what COORDS actually contains, this node is the fastest way to see it.

How it works. No math, just structure: it iterates the coordinate pairs and collects every first element into x_coords and every second into y_coords, preserving order. Pair (10, 50) and (200, 300) becomes [10, 200] and [50, 300] - exactly the values that went in. Defensively, an empty or malformed COORDS input returns [0] for both lists rather than crashing, in keeping with the rest of the pack's "don't blow up the graph" philosophy.

The inputs and outputs that matter. One input: coords (the COORDS value). Two outputs: x_coords and y_coords, both INTS. That's the entire interface - there isn't a setting to get wrong.

Because it's a pure structural pass-through, the usual caveat applies: COORDS is a pack-defined type, so this node only accepts the value from nodes that emit it (chiefly CombineCoords). Feed it anything else and the wire simply won't connect.

Install. Standard for this pack - no dependencies, no model files:

cd ComfyUI/custom_nodes
git clone https://github.com/einhorn13/ComfyUI-ImageProcessUtilities

Restart ComfyUI. Manager search may not surface it (the pack isn't on the official Comfy Registry as of writing), so the clone is the dependable route.

Common issues. There's not much to break. The one trap: order. SplitCoords preserves the order it was given, and so does the pair-zip, so round-tripping through SplitCoords → CombineCoords reproduces your coordinates exactly - as long as you don't reorder a list in between and expect the pairing to follow. If your x and y get misaligned after a round trip, check whether you sorted or shuffled one list on the way.