Hi Robert,
Thank you for pointing out this very interesting video. Unfortunately, it didn't help me with my problem. Although it is explained at the end of the video that, as I had assumed, in order to be able to identify the exact distance position X, the “Aggregated Geometry” option must be used as the Result Type, this has not worked so far in my attempts. (However, thanks to the video, I have not received any further error messages when trying again).
My test case looks like this: I select any mid-voltage transformer (of the Electric Utility Network Foundation Solution) and define the primary terminal as the trace location. Then I execute an upstream trace in the distribution tier with the following filter function barrier: Add - Shape length - Is greater than or equal to - 20 (so my distance position is 20 units). Before running the trace I have deleted the traversability barriers of the trace configuration. My output options are “Aggregated Geometry” and “Selection”.
In fact, the trace delivers a result - it selects the line connected upstream to the transformer and generates an aggregated line geometry. However, this is not 20 units long, but goes as far as the vertex of the line that most closely fulfills the function barrier condition. However, I would have expected the aggregated geometry to be exactly 20 units long.
On further attempts with other X values (50, 100, 200), it can be seen that the aggregated geometry always runs up to a vertex of the line, but never ends at the exact X value.
I am now wondering whether I am doing something wrong here, or whether it generally does not work to determine the exact distance position.
I would be happy to demonstrate my test case in a web session.
Best regards, Jürgen
