jasonh300 wrote:It doesn't have anything to do with the number of editors in Mississippi (there are 3 heavily active MS editors other than myself). It's because the geometry of Mississippi was incorrect in the basemap, on a layer that we can't edit. You can see this by checking unnamed roads to see what state they're labeled with. If a street came from the basemap with a name, it also had the city and state attached to it. If the street had no name, then some automatic process pulled the state from a geometric outline in an invisible layer, and that layer was wrong. You get similar results by creating a new road, except now, you get an error that you're too far from the state you selected. (Prior to a few months ago, it'd let you save and contribute to the smear.)
Close to the coast, it stops around Gulfport, but if you get 30 or 40 miles inland, I see unnamed roads in Mississippi with Louisiana on them almost to the Alabama line.
jasonh300 wrote:As I go through coastal Mississippi doing cleanup, I delete the vast majority of them unless I can clearly see a road in the aerial, or there's some evidence of construction. They *never* have GPS tracks on them. A lot of them appear to be overgrown dirt paths, and some of them are creeks and small rivers. And the ones that seem to be legitimate roads usually have the correct state for some reason...maybe some of the no-name roads were flagged as no-name in the basemap and had a city/state attached to them.
I figure if I delete something that needs to be there, I keep a close enough eye on that area that I'll see a pave or a UR complaining about it.
CrackedLCD wrote:Maybe it's because there are fewer editors overseeing Mississippi, but my experience has been that the Magnolia State has a serious problem with state-smear. At least compared to the little editing I've done in TN, AL and FL.
CrackedLCD wrote:Ah, OK. How much of a priority should it be for us to go around and fix the state names on unnamed roads? Is it going to adversely affect routing?