Seems like an oversight on the bike streets implementation side, shouldn’t have to alter the main database for it. Just don’t want to overly fragment things on OSM and slow down editing

I see, unfortunate that it has to be this way

What is the need for splitting all these ways without adding any differing tags on the new segments?

Whoops, the way was initially west to east and I must have reversed it and changed the incline direction instead of just doing one. Fixed now, thanks

Ah, my mistake. Yes that is the correct fix.

Got it, I can retag as disused. Thanks!

Mapping separately implies physical separation, which is not present here

A cycle path is typically only mapped separately if it is physically separated from the road itself. For a lane that’s just painted on, tag the road with cycleway:both=lane (or cycleway:right=lane and cycleway:left=lane where applicable)

More updates needed to add new city hall building and other features as construction finished

On the portion south of 28th St, I reconfirmed via survey that all signage shows "Blaisdell" and there is no sign of the Whittier/Lyndale name. Hennepin County lists this route as Blaisdell. While the initial construction project from Minneapolis (https://www.minneapolismn.gov/government/projects/whittier-lyndale-bikeway/) used the "Whittier/Lyndale" name it also used the names of the individual streets. Seems clear that the name was just used to indicate where the project is rather than assigning a name to the route.

For the purposes of navigation, Blaisdell is the more accurate term.

Sorry, didn’t realize! I am mainly relying on my own local knowledge for these updates, I will stop listing google products then.