Next: 144487469

Next: 144487364

Previously: 144481130

Or maybe they're trying to match edges in a dataset like TIGER, but even then it would be easy to check if that thing already exists in OSM in a certain proximity...

These #MapWithAI changesets are something. They seem to be taking the name from the adjacent highways?

The ways here didn't even have a ref tag

MO A is a state-maintained asphalt road.

The bbox is large because of two north-south routes involved and east-west power lines

MO Z is secondary here, but bridge was accidentally left as tertiary

Brownington was untouched. The roads just don't even match with reality at this point.

I downgraded the way here labeled "State Highway F" to track because the concrete is completely torn up and interspersed with earth. There does not appear to be a crossing over the stream anymore, also.

Bounding box is large due to power lines as usual.

I also removed a duplicate label for Henderson, MO. I kept the older one.

Correction: the route relation was not removed, but the ref tag on the ways was. I will add the route relation.

This changeset also introduced some yield signs and dead ends.

U.S. 60 Bus., MO B, and CR 253 (in name only, as road is state owned) are all concurrent for a stretch in Rogersville.

This is being done in preparation for reworking the concurrencies here and addressing my note #3999754 about the route relation being removed last year for Route B.

This changeset adds ref tag to the way because I forgot it

There was also a segment in here accidentally tagged ref="MO E", so I changed that to ref="MO EE"

I also bumped T from unclassified to tertiary