Hi @jordan​,

I think the NetworkCostCalculator will be the key transformer for a solution. It can calculate the distances from a Closure point to each vertex on the lines and store these as measures on the lines. We can then overlay the Risers on the lines to transfer the distance to each Riser. Next, we overlay the Risers on the Boundaries to transfer the Boundary IDs. Finally, we Sort the Risers by distance, then Sample to keep only the closest Riser to each Closure in each Boundary.

I am attaching a partial workspace illustrating the process:

Hey Dave,

Thanks for this, its absolutely amazing!

With the guidance of your explanation and Template I've been able to stuck much further along in the process 🙂 Hoping you can also help me out here again.

In the attached diagram Ive outlined a few different possibilities present in my dataset. The one I'm stuck on is when we have multiple Taps within the same boundary, along different branches (Left boundary on diagram). Using the sorter on the _distance is only yielding me a single feature in these branching scenarios.

Any tips would be greatly appreciated!

 Edit: For clarification, Taps as per this diagram is referring to the Risers from the above example, same things.

I added some modifications to the workspace to clip out a small section of the lines at the closures to turn them into separate networks, then use a NetworkTopologyCalculator to assign a network id to each. The Sampler then groups by the network id as well.