TBC Macros and Extensions

Hopefully @Bryce Haire can point you to a flag or something on a per linestring element basis.

Outside of that, I was going to suggest that there's a method to get a PolySeg from an element - that's how the Plan View mouse cursor is created in Edit Linestring.

But from your screenshot, it looks like you've already found that, great job!

So for non-straight elements, you can see if the PolySeg is just a straight segment, if so, the calculation must have bailed.

Interesting suggestion.

• Loop through the linestring elements
• if it contains arc elements check if the same chainage range in the PolySeg contains any PolySeg.Segment.Arc

will at least work for the arc types

I'll need to investigate the other element types, and which ones can potentially fail.

With PI arc I believe I need to check the radii against each other as well. My quick test line has a PI arc with set radius 50 m, but the solution on screen is less than 1 m.

Hopefully @Bryce Haire can point you to a flag or something on a per linestring element basis.

Outside of that, I was going to suggest that there's a method to get a PolySeg from an element - that's how the Plan View mouse cursor is created in Edit Linestring.

But from your screenshot, it looks like you've already found that, great job!

So for non-straight elements, you can see if the PolySeg is just a straight segment, if so, the calculation must have bailed.

If you are just looking for polyseg calculations that fail, I believe that the fallback to a failed calculation is a straight segment from the previous endpoint to the endpoint of the current element.

So if you get to an element that is not supposed to be a straight segment, but the PolySeg is just a straight segment, then you know that the calculation failed.

Now with your PI arc, you may have found an issue - or the logic for calculating the arc has a nuance you're not expecting...

Interesting suggestion.

• Loop through the linestring elements
• if it contains arc elements check if the same chainage range in the PolySeg contains any PolySeg.Segment.Arc

will at least work for the arc types

I'll need to investigate the other element types, and which ones can potentially fail.

With PI arc I believe I need to check the radii against each other as well. My quick test line has a PI arc with set radius 50 m, but the solution on screen is less than 1 m.

Hopefully @Bryce Haire can point you to a flag or something on a per linestring element basis.

Outside of that, I was going to suggest that there's a method to get a PolySeg from an element - that's how the Plan View mouse cursor is created in Edit Linestring.

But from your screenshot, it looks like you've already found that, great job!

So for non-straight elements, you can see if the PolySeg is just a straight segment, if so, the calculation must have bailed.