I would like to document a recurring routing behavior observed in Apple Maps involving Avenue du Général-Leclerc (Paris 14ᵗʰ arrondissement), which appears to conflict with both ground truth and the functional road hierarchy represented in OpenStreetMap (OSM). This note is not intended as a critique of OpenStreetMap data quality. Rather, it highlights how a correctly mapped major urban arterial can be inadequately handled by a downstream routing engine, leading to results that diverge from real-world urban logic.

On the ground, Avenue du Général-Leclerc is a major north–south arterial road and the primary structuring axis of the southern part of the 14ᵗʰ arrondissement. It is a fully public, continuous avenue with multiple traffic lanes, bus lanes, protected cycling infrastructure, signalized intersections, and a clear role in carrying urban traffic. Its design, capacity, and function clearly identify it as a road intended to absorb traffic flows and serve as a backbone for local and district-level movement. From an OpenStreetMap perspective, the avenue is correctly mapped and tagged as a high-hierarchy road, with no access restrictions or discontinuities that would justify systematic avoidance.

Despite this, Apple Maps exhibits a consistent pattern in which Avenue du Général-Leclerc is used only when it is the final destination, but is frequently avoided when it should logically serve as a transit axis for destinations located on immediately adjacent streets. In such cases, routing is diverted onto smaller residential streets, even when the destination lies only a short distance from the avenue, when no clear time or distance benefit is achieved, and when the avenue remains fully available and connected.

This behavior is reproducible, independent of temporary disruptions, and indicative of a routing-model issue in which Avenue du Général-Leclerc appears to be globally penalized rather than contextually integrated into last-mile routing. The result is a mismatch 