Also not sure what was up retagging the ramps as motorway instead of motorway_link

Not quite sure what was going on with that toll=yes east of the east ramps of Memorial Drive, but that effectively blocked free navigation.

The expressway dumps off into a boulevard. That's a reduction.

With all due respect, I think folks need some perspective. What a few folks in a slack channel and who gatekeep on the wiki preventing folks from documenting how things actually get tagged in the real world say doesn't a consensus make. Haranguing people endlessly alienates people from the project and doesn't change the data consumers who have been, and still do, use the pre-NE2 idea of trunk in the US.

There's a substantial physical barrier separating the two sides going under the railroad.

Going from trunk to primary isn't a reduction in importance, it's a reduction in the road.

Yeah, I'm pretty sure that's not a consensus considering it doesn't work and only a few people seem to go with the wiki on this. Even data consumers like osmand and rand mcnally assume trunk is expressway.

Because they become a boulevard before returning to a larger highway again.

As for fixme=check lanes, it's to mark what highways haven't been checked yet. I've been working on getting the lanes done throughout Oklahoma as travel and time permits.

Thanks, mybad.

I'm not opposed to trunk, but, let's not smash everything to trunk when on the ground it's not really built as anything different than a primary. Let's wait until what's on the ground actually matches what's on the paper.

When it only exists on paper and there's nothing else that really brings it up to the level of a proto-motorway trunk, it's effectively the same as tagging the interstates in Alaska as motorway. It's overstating the character of the road based on a purely political process for funding.

Either way you want to cut it, most of America isn't connected *that* well. Let's avoid aspirationally tagging the wishful thinking of the HFCS.

That's clearly not a trunk, buddy. Let's not encourage upward priority creep.

OK Karen. Calm down. landuse=residential is absolutely incorrect in this case and landuse=residential should be smaller areas that actually fit the land use.

landuse=residential is only appropriate for areas where homes and apartments are. It's not appropriate where public roads are, for example.

No, they're not mutually exclusive but given the neighborhoods where it did get retagged, landuse=anything isn't an appropriate value ever for those polygons. Literally zero of them are purely residential landuse.

That said, landuse=highway and government land use outside of prisons and military bases doesn't currently have a good tagging, so AFAICT the best practice for landuse tagging on public commons is to not tag it at all.

Suggested iterative improvement would be to make sure these polygons actually fit the actual neighborhood boundaries (they're close but obviously not fully inclusive), and then tag groups of lots congruent to the boundaries with landuse=*. Outside of very limited edge cases, if your landuse=* polygon is crossing a highway=* line that isn't access=private, it's probably wrong.

landuse=* is lot-level tagging, not district level. A named landuse=residential area should be an apartment complex or a gated subdivision at most. Otherwise you definitely have a lot of space that definitely should be landuse=highway in the middle at every publicly owned street.

Large landuse gaps on the map is more accurate than overly inclusive landuse areas, so changing landuse=residential areas in this space to boundary=administrative admin_level=10 and place=neighborhood is a more accurate definition.

I'm not arguing against tagging things as landuse=residential, but what got retagged isn't even remotely congruent with landuse=residential by the broadest possible definition.

TLDR: No.

Problem is there's a lot in the middle that isn't actually residential. Landuses should be congruent with the actual landuse, not entire districts.

45 km/h?? I mean, I'd love it if we got on board with standard units here already but I didn't think we had any metric speed limits here yet.
---

Published using OSMCha: https://osmcha.org/changesets/110620424