It looks like an attempt at making a relation for the highway. Which it probably should be. Should it? As i recall there was a recommendation for people not to be joining up the ways, just for the sake of joining them. But it never got materialized to the geobase2osm wiki page instructions. It's only the road name and the reference that should be part of that relation, as the physical road changes all along the #3 / #41
Check out Medicine Hat. http://www.openstreetmap.org/?lat=50.0311&lon=-110.6412&zoom=14&layers=B000FTF It renders all as little pieces of of the highway... ... BTW, im sure someone would fix that when they are physically in the area. I was just checking the GPS traces, and it looks like know one traced over my trail cycling yet. Cheers, Sam Twitter: @Acrosscanada Facebook: http://www.facebook.com/sam.vekemans On Sun, Jul 5, 2009 at 10:20 AM, Simon Wood <si...@mungewell.org> wrote: > Hi all, > I've messaged TheTom seperately, but thought best to post here as well. > > It looks like a script has gone wild. Down in the Crowsnest Pass highway 3 > has been corrupted with this change: > http://www.openstreetmap.org/browse/way/31475452/history > > It looks like an addition way has be superimposed on top of the original > nodes, which run in both directions. I'm worried that this problem is > duplicated in multiple places. > > Cheers, > Mungewell. > > _______________________________________________ > Talk-ca mailing list > talk...@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-ca >
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk