I would like to document a recurring routing behavior observed in Apple Maps involving Rue Beaunier (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 illustrates how a correctly mapped local street can be misused by a downstream routing engine, producing results that diverge from real-world urban logic.

On the ground, Rue Beaunier is a local street with a residential character, directly connected to Avenue du Général-Leclerc. It has a limited carriageway width, moderate traffic levels, and a clear function of local access rather than transit. Its physical configuration and urban context indicate that it is designed to serve nearby residences and local destinations, not to function as a substitute corridor for broader traffic flows. From an OpenStreetMap perspective, Rue Beaunier is correctly mapped and tagged as a low-hierarchy road, with no attributes suggesting an arterial or collector role.

Despite this, Apple Maps frequently routes traffic along Rue Beaunier as part of longer itineraries through the area. This behavior is typically observed when Avenue du Général-Leclerc, a nearby high-capacity arterial road, is algorithmically avoided. Rue Beaunier is then implicitly promoted to a transit function, even when the destination is not located on Rue Beaunier itself, when the detour offers no clear advantage in time or distance, and when higher-capacity roads remain directly accessible.

This routing pattern is consistent, reproducible, and independent of temporary disruptions. It points to a routing-model issue in which arterial roads appear to be over-penalized and adjacent local streets are inadvertently used as alternatives. As with similar cases in the area, this behavior does not stem from incorrect OpenStreetMap data, but from the way that data is interpreted and weighted by Apple