No. Officially you’re not supposed to bicycle in transit lanes, but in practice it’s well tolerated on 1st Avenue, Yamhill Street and Morrison Street from experience.
Another example just a few blocks away, even where the Brooklyn Subdivision replaced it over a century ago, the railroad tracks that replaced the street are still referred to as 1st Avenue by locals (moot in that the 1st Avenue corridor is railroad property with no legal public access).
You’re welcome. This may have made me think about subject matter a bit differently. What if this topic here was less about naming and more about labelling? The left hand side it is easy, put the label (sourced from the name) onto the centreline (which is an abstraction of the whole of the street.) The right hand side no longer maps an abstraction of the street (understood as a multimodal right of way.) So where to put the label? On the centreline of course, where the cars drive ;)
Said that, I think that is a choice consumers have to make. Renderers may have different prerogatives than voice navigation for pedestrians…
Focusing on the ”it will look messy” argument for a moment, would’t it be absolutely trivial for a car centric renderer to ignore name tags on sidewalks?
And just as easily, a ”general purpose” purpose renderer could do the same if they wanted couldn’t they? Is not tagging sidewalks with a name just saving them from making an awkward choice? Or is this because of an assumption that Carto specifically won’t do anything?
How to do it would depend on the technology used, but basically “yes, it would be absolutely trivial” (raster example using osm2pgsql with pgsql backend + lua + CartoCSS/Mapnik, vector example using tilemaker + mostly the same lua, MapLibre).
In both cases, but especially MapLibre, you have a lot of control over when to show names (e.g. to avoid overlaps), so “removing the name in lua” is arguably unnecessary in that style (have a look at the way that the railway line names disappear here as you zoom out to see that).