Motorway/trunk ways tagged only with lanes are excluded from the lane-tag shards. Where a merged Overture segment also lacks a primary Layercake lane count, missing per-way counts prevent the section splitter from preserving local lane changes. Junction inference or the default two-lane count then applies across the merged segment.
Keep plain lanes records for highway=motorway and highway=trunk in both the native OSM input key filter and lane_way(). Existing lane-detail and roundabout export behavior is preserved. No runtime splitting, junction inference, renderer, or shard-format changes.
Reproductions on the E40 near Leuven, Belgium:
| Location | OSM ways | Expected | Before |
|---|---|---|---|
| Kerspelstraat bridge, 50.84560 N, 4.70419 E | 15364879 / 15364866 | 3 westbound / 4 eastbound | 4 / 5 |
| Steenkruis area, 50.84285 N, 4.74060 E | 339911868 / 32601551 | 3 each direction | 2 each direction on the affected stretch |
Validation:
- Based on
v1.10.1-beta.dev.554(c12cabef); 145 lane/export/join/split/cache tests and 230 road/bridge/mesh tests passed. - New regression coverage exercises input filtering, gzip shard export, tag joining, section splitting and the bridge specifications, using simplified source-way sequences without a Layercake primary count. Both bridge cases fail with the original exporter.
- Reporter confirmed both locations corrected in-game using targeted regional test data generated from this exporter. Those test installers/data are not part of this PR.
- Additional plain-count coverage is limited to motorway/trunk roads. Existing shard format and compact tag storage are reused; full-planet data-size and memory impact has not been benchmarked.
Deployment: rebuild and publish the lane-tag dataset after merging. Updating the exporter alone does not change already published data. The corrected records work with the existing dev.554 lane loader, splitter and cache-version handling.