Wrong State - Mississippi?

by **jasonh300** » Mon Nov 19, 2012 8:33 am

Guess we need a "Highlight by State" field in Colour Highlights then!

---------
Via my iPhone 3GS.

by **jasonh300** » Mon Nov 19, 2012 2:06 am

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?

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.

by **jasonh300** » Sun Nov 18, 2012 10:32 pm

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.

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.

by **CrackedLCD** » Mon Nov 19, 2012 7:09 am

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.

I'm deleting stuff like that, too, but some roads I'm finding are well trodden dirt roads or paved but I can't find a name for them… this is especially true in my home territory in Alabama. Some of them are trailer parks and parking lots that are better to be there than not. I've not been editing them beyond directionality no matter where I'm editing, but now I'm wondering if I should go back and change them all.

by **CrackedLCD** » Mon Nov 19, 2012 1:55 am

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.

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?

by **CrackedLCD** » Sun Nov 18, 2012 9:32 pm

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.

I work occasionally around Carroll, LeFlore and Grenada Counties so I see what the OP is talking about a lot. I just don't understand why the editor would even give us the option of multiple states when we're right smack dab in the middle, 80+ miles from any border. If I go more than 10-15 miles into Florida I tend to lose the ability select Alabama, for example. And I'm currently working the outskirts of Mobile and don't see Mississippi as a state option until I'm almost close enough to "see" the state line in the editor. It's a head scratcher.

by **Bigbear3764** » Mon Nov 19, 2012 3:43 pm

I have been hunting down some in my area and my drives north into Wisconsin where some are Michigan or Canada. I just pan the map and pull down the list of cities, if I get funky ones, I know they are in the area. Seek and destroy!

Sent from my iPhone using Tapatalk