Skip to content

Engine Validation: PathSweeper Against AutoTURN Online Reference Exports

Author

Founder & Developer · Published · Reading time: 8 min read

ValidationAutoTURN OnlineRBSV 2020Swept PathEngine
Two sheets of tracing film on a light table over a junction plan, each plotted with the same semi-trailer turning loop; the blue and grey swept-path bands lie on top of each other
Two sheets of tracing film on a light table over a junction plan, each plotted with the same semi-trailer turning loop; the blue and grey swept-path bands lie on top of each other · Illustrative image, AI-generated

Several pages on this site say that PathSweeper's swept-path engine agrees with AutoTURN Online reference exports to within 0.5 percent of envelope area. A sentence like that is only worth something if the numbers behind it can be inspected. This page is the record: what was compared, how, every per-vehicle result, and the cases where the two tools differ by design.

One thing up front: this is our own validation of our own product, run by us against exports from an AutoTURN Online subscription we hold. It is not a third-party audit. What it is, is reproducible: anyone with access to both tools can drive the same vehicles on the same paths and compare.

What was compared

Reference data. On 18 July 2026 we exported two drawings from AutoTURN Online, each containing all 13 German RBSV 2020 design vehicles driving the same set of manoeuvres: one with steering at standstill (RBSV Fahrweise 2, the wheels reach full lock instantly) and one with steering while moving (Fahrweise 1, the steering angle changes at a finite rate while the vehicle rolls). A third export, from August 2026, contains the semi-trailer reversing along a straight lead-in and a 6.76 m arc, guided on the trailer axle as AutoTURN does. The DWG files were converted to DXF with the open-source LibreDWG converter and the entities were read from the DXF: the body envelope, the wheel envelope, the body boxes at the end position and the drive line.

Same path, our engine. AutoTURN's drive line is the trace of the front-axle centre with that steering mode already baked in. We convert it to the rear-axle path by exact tractrix pursuit, then run it through PathSweeper's production engine and envelope pipeline, exactly as the app does when you draw a path. Nothing in the engine knows it is being tested.

Metrics. For each case we report:

  • Area difference: PathSweeper's envelope area minus the reference area, as a percentage of the reference. Negative means ours is smaller.
  • Mean boundary deviation: sample points along PathSweeper's envelope boundary, measure the distance from each to the nearest point of the reference boundary, average. Median likewise.
  • Maximum one-sided deviation, in both directions: the largest distance from a point on our boundary to the reference (ours → ref) and from a point on the reference boundary to ours (ref → ours). A large value in only one direction means one envelope has a lobe the other lacks.

The vehicle dimensions are the RBSV 2020 values in both tools. PathSweeper ships them with the permission of the FGSV Verlag.

Results

All 26 forward cases, 13 vehicles in each steering mode. Deviations in centimetres.

VehicleSteeringArea diff.Mean dev. (cm)Median (cm)Max ours → ref (cm)Max ref → ours (cm)
Passenger carwhile moving-0.08 %0.40.31.71.4
Passenger carat standstill+0.06 %0.30.20.80.8
Vanwhile moving-0.05 %0.30.31.41.2
Vanat standstill+0.04 %0.30.30.70.8
2-axle truckwhile moving+0.00 %0.40.32.01.9
2-axle truckat standstill+0.03 %0.40.30.90.9
3-axle truckwhile moving+0.02 %0.30.22.12.0
3-axle truckat standstill+0.04 %0.20.20.60.6
12 m buswhile moving-0.00 %0.40.32.01.9
12 m busat standstill+0.02 %0.30.20.80.8
13.7 m buswhile moving+0.02 %0.40.32.11.9
13.7 m busat standstill+0.02 %0.30.20.80.8
15 m buswhile moving+0.03 %0.40.21.91.8
15 m busat standstill+0.02 %0.30.20.80.8
Articulated buswhile moving-0.10 %0.90.32.93.0
Articulated busat standstill-0.02 %1.10.414.816.0
Refuse truck 3Müwhile moving+0.04 %0.40.22.11.9
Refuse truck 3Müat standstill+0.04 %0.20.30.70.7
Refuse truck 3MüNwhile moving+0.11 %0.50.42.92.4
Refuse truck 3MüNat standstill+0.03 %0.30.30.80.8
Truck with drawbar trailerwhile moving-0.04 %1.50.48.18.1
Truck with drawbar trailerat standstill+0.07 %2.20.69.815.6
Truck with centre-axle trailerwhile moving+0.46 %1.80.32.3127.1
Truck with centre-axle trailerat standstill+0.50 %1.50.23.0127.3
Semi-trailerwhile moving+0.09 %1.40.335.049.1
Semi-trailerat standstill+0.12 %1.50.435.549.8

Twelve of the thirteen vehicles agree within 0.13 percent of area in both steering modes, with a mean boundary deviation of 2.2 cm or less. The truck with centre-axle trailer sits at 0.5 percent because of one documented modelling difference, explained below.

The one reverse case:

VehicleSteeringArea diff.Mean dev. (cm)Median (cm)Max ours → ref (cm)Max ref → ours (cm)
Semi-trailerreverse, guided on trailer axle-2.45 %9.91.8139.3126.2

Known differences

Two cases differ by more than the rest, and in both the cause is a modelling decision rather than a numerical error.

Centre-axle trailer: the towbar corridor. AutoTURN sweeps the drawbar between the truck and the centre-axle trailer as part of the envelope. PathSweeper sweeps vehicle bodies, not the towbar, so at full articulation the reference shows a one-sided lobe of up to 1.27 m between the units that ours lacks. That lobe is the whole 0.5 percent area difference; outside it the two boundaries agree to 3 cm. We reviewed the overlaid envelopes and kept our modelling: the towbar is not body envelope, and a corridor that only exists between the units does not change clearance to anything outside the combination.

Semi-trailer reversing: when the tractor starts to swing. In the reverse export the reference begins the tractor's swing during the straight lead-in, before the arc; PathSweeper starts it at the junction. The result is a one-sided fan of about 1.2 to 1.4 m at the start of the arc and an envelope 2.5 percent smaller than the reference. Reverse manoeuvres with articulated vehicles depend on how the driver is assumed to anticipate the turn, and the two tools make different assumptions. We document this rather than tune our model to match.

What this shows, and what it does not

It shows that, on identical paths with identical vehicle dimensions, PathSweeper's forward swept envelopes are the same as AutoTURN Online's to within the width of a pencil line at plan scale. It does not prove either tool correct: two implementations can agree and both be wrong. For that reason the engine is also audited against the analytic tractrix solution of the vehicle model, independent of any other software.

The table covers the German RBSV 2020 vehicles only. A similar comparison was run for the Australian Austroads library in July 2026 and is not yet tabulated here. Reverse manoeuvres are covered by a single case. Both are gaps we intend to close as further reference exports become available.

How this is maintained

The comparison is a regression suite inside the PathSweeper repository and runs on every change to the geometry engine. Each case carries a tolerance; a tolerance is never loosened to make a failing engine change pass, and the two cases with documented differences carry notes naming the difference they cover. The numbers on this page are the suite's output on 9 October 2026 and will be refreshed when the engine changes.

We do not publish Transoft's export files themselves, which are their intellectual property. The numbers in the table are our own measurements. Overlay drawings of the two envelopes exist for every case and can be shown on request.

AutoTURN, AutoTURN Online and InSTRATO are trademarks of Transoft Solutions Inc. They are named here only to identify the reference software; PathSweeper is not affiliated with or endorsed by Transoft Solutions, and Transoft has not reviewed this comparison.

For how the swept path itself is computed, see the swept path analysis guide. For how the two products compare on features and price, see PathSweeper vs AutoTURN Online.

Frequently Asked Questions

For each of the 13 German RBSV 2020 design vehicles we drove the same path in PathSweeper that AutoTURN Online had driven in its reference export, then compared the two swept envelopes. The area of PathSweeper's envelope differs from the reference by at most 0.13 percent for 12 vehicles and by 0.5 percent for the truck with centre-axle trailer, in both steering modes. The mean distance between the two envelope boundaries is 2.2 cm or less in every forward case.

No. We ran the comparison ourselves, against exports from an AutoTURN Online subscription we hold. This page publishes the method and every per-vehicle number so that anyone with access to either tool can repeat it. Agreement between two tools is a compatibility check, not a proof of correctness; the engine is separately checked against the exact tractrix solution of the vehicle model.

This table covers the 13 German RBSV 2020 design vehicles in forward manoeuvres with both steering modes, plus one reverse manoeuvre of the semi-trailer. Vehicles from the other national libraries and further reverse manoeuvres are not in this table. Where PathSweeper and the reference differ by design, the difference is documented in the known-differences section rather than tuned away.

Sources & References

  1. AutoTURN Online product page — Transoft Solutions
  2. RBSV 2020, Richtlinien für Bemessungsfahrzeuge und Schleppkurven (FGSV No. 287) — FGSV Verlag

Was this article helpful?

Try it now

Try PathSweeper for free and calculate swept paths directly in your browser.