I was more laughing that Tulsa’s cycleways with (incorrect) white centerline markings aren’t so weird now.

https://otc.org/wp-content/uploads/2023/01/OTM-Book-11-Pavement-Hazard-and-Delineation-Markings.pdf.pdf

Book 11 • Markings and Delineation Ontario Traffic Manual • March 2000104 • Blue [lines] must only be used for disabled parking spaces.

Oops, someone ignored the standard. blue lines indicate paths and spaces reserved for handicapped users in the US and Canada.

Correct. It really needs some quality of life improvements but otherwise it really helps.

I’m at a wait-and-see moment with connectivity relations to see what gets adopted and widespread editor support. Connectivity relations have some support in JOSM but none in Osmand, which tends to support the most tagging schemes. So far the one that looks most promising to me is the one that works complementary to turn lane tagging.

Also looking over the story again, looking at the Connecting the Lanes section, that one with the cycletrack and the road? I’d map those as two different parallel ways thanks to the buffer prohibiting crossing (even if they cheaped out and didn’t install physical barriers).

On that buffer with the orange hash marks, that should be turn:lanes:both_ways=none and access:lanes:both_ways=no

The country’s government and the people as a whole are unrelated for the purposes of this discussion.

You’d be correct on that, however, again, the way you phrased it suggests that 90% of people are homophobic, therefore it’s OK. Apologies if that’s not what you intended.

Khalid, the fact you entered this thread with a post that tries to promote homophobia as a valid viewpoint, then doubled down on it by trying to white knight Hungary’s homophobia as valid, really only leaves room for me to question if you’re even engaging with this subject in good faith.

You’re trying to excuse a genocide.

Homophobia is bigotry.

I think you improperly assume most people are bigots to come up with 90% on that one.

I don’t see explicit antifascism and antibigotry as being incompatible with the open definition, but an intrinsic component.

Australia’s idea and America’s idea of classification both differ from OSM’s idea, which is trying to have the same classification system globally. Trying to force Australian rules over actually bothering to conflate data into OSM rules is clownshoes thinking.

I think you’re the only one in disagreement on how this is mapped.

I’ve re-added the note contents at note/2060067 , but I suspect that it’s really a more general question (“how should we tag the destinations of individual lanes”). The answer to that is that there seems to be some usage of “destination:lanes” - see https://taginfo.openstreetmap.org/keys/destination:lanes#overview for the number in use around the world and way/375327794 for an example on the I5 South not far from you. What I don’t know is whether a Tesla will actually use that information (destination=*#destination:lanes.3D.2A_tagging asks that question more generally). You’d have to ask Tesla that question.

I do apologize for my rather aggressive tone in the note, I’ve been under a considerable amount of stress and it’s been affecting, probably most pronounced, my performance with OpenStreetMap of late.

I’m not convinced Tesla is actually smart, given the number of times I’ve seen ‘em drive headlong into trees, concrete barriers and pedestrians with the driver overtrusting the driver assistance in my city. Plus the hype surrounding electric vehicles and driver assistance technology overselling the benefits is creating a parasitic drag in many cities on adopting actually city-scalable infrastructure and highway safety in the urban context. I’d probably take a lot less dour view of the company and it’s products if they were honest about their product: “Look, it’s basically an GM EV1 with Cadillac’s supercruise and a higher price tag, and it’s never going to be as good as a sober and alert human driver except under ideal rural highway conditions.” They’ve chosen the opposite tack, thus Tesla considered harmful.

But more to the subject of the map itself, the way I’ve seen most data consumers actually work is to ignore destination:lanes and infer the destination from the destination= tags on the ramps, essentially using the turn:lanes=* tags to imply destination:lanes=* based off the destination. I think mkgmap does this, Magic Earth does this, Osmand does this. This is probably the better way forward from a human prospective, destination=, junction:ref=, destination:street=* destination:ref=, and the destination::to=* tags are all trivially straightforward. JOSM has a good turn lanes editor. Slap :forward or :backward to thee end if need be for two-way traffic flows. You could have some seriously Cities Skylines level absurdity with toll plazas in multilane cloverleaf lane drop split interchanges before you run into the risk of overrunning the size limit on values.

destination:lanes=* not so much. destination:lanes=* very rapidly runs into the problem of overflow. The 255 character value limit means destination:lanes=* can easily overrun the length limit where lanes have multiple destinations and there’s three or four lanes, with most of the information being redundant and long. It’s also way less effort to just remove destination:lanes=* when doing lane tagging than to update the values, even with an advanced editor.

I really wish id drew lanes and had an easy lane editor like JOSM does, however, as the lack of this functionality does tend to cause lane tagging to break with subtlety and silently without obvious feedback that this has happened

I think there’s a long stretch between the ignorant and minor scale bumbling of a new or student mapper that doesn’t have a proper grip on what they’re doing, and a corporation doing the same thing at a large scale, then running someone to an OSMF position.

No offense to migurski on this, and his extensive previous work with considerably better behaved corporate entities with interests in OSM. I have a hard time believing that he wouldn’t become a proxy for FB, to the detriment of OSM’s interests and his own personal interests. Especially fresh on the heels of the GlobalLogic debacle and FB’s involvement in severely and possibly irreparably harming humanitarian and political processes in entire sovereign countries.

@Kevin_Bullock: Really just sliding around Tulsa or along the length of US 412, US 169 or US 75 in Oklahoma, you can see it wobble substantially. I think I was looking up northwest of Cashion, OK when I saw it go totally off the rails.

Can we get some better alignment and resolution on the latest Maxar imagery? Not only is it not lined up, but the way that it’s out of alignment varies quite wildly over distances as short as 100m, and at resolutions that make it impossible to make out lanes.

Nice catch, Carnildo. “Speed limit” isn’t even the correct verbiage for those yellow signs, they’re Advisory Speeds in the US and Canada, and don’t have the force of law, just guidance of what the DOT can send a sedan around without passengers feeling uncomfortable.

So, I got a Waylens Horizon, now how do I use it for OSC?