fix: fill junction core and connect cluster lane trajectories
This commit is contained in:
1 parent
695bf21a84
commit
6a8f026d12
12 files changed
+527
-83
No files matched your search
+5
-11
@@ -113,17 +113,11 @@ const complexGeometry = compiler.nativeRoad.compileGeometry(
|
||||
const complexCore = complexGeometry.roadSurface.features.find(
|
||||
(feature) => feature.properties?.kind === 'complex-core' && feature.properties?.cluster_id === 'fixture-five-arm',
|
||||
);
|
||||
// This fixture contains multiple source carriageways within several arms. The
|
||||
// compiler must retain those independent sections rather than filling their
|
||||
// unknown interstitial areas with a synthetic core.
|
||||
assert.equal(complexCore, undefined);
|
||||
assert.ok(
|
||||
complexGeometry.diagnostics.some(
|
||||
(item) =>
|
||||
item.rule === 'complex-junction-core-closure-unsupported' &&
|
||||
item.subjectId === 'junction-cluster:fixture-five-arm',
|
||||
),
|
||||
);
|
||||
// Every valid carriageway must participate in the continuous center region.
|
||||
assert.ok(complexCore);
|
||||
assert.equal(complexCore.properties.required_pavement_connected, true);
|
||||
assert.equal(complexCore.properties.shared_seam_error_m, 0);
|
||||
assert.equal(complexCore.properties.core_ring_self_intersects, false);
|
||||
assert.ok(complexGeometry.roadSurface.features.some((feature) => feature.properties?.kind === 'complex-approach'));
|
||||
const compiledApproach = complexGeometry.roadSurface.features.find(
|
||||
(feature) => feature.properties?.kind === 'complex-approach',
|
||||
|
||||
Reference in new issue
Block a user