OpenStreetMap標誌 OpenStreetMap

Oh TIGER...

於 22 八月 2014 由 mvexelEnglish發表。

Sometimes I wonder if those TIGER surveyors were just having a grand old time making up things as they drove past and casually looked out of the window of their cars…

TIGER...

This whole area needs lots of work - if you want to help out, that would be great!

(I have no personal or other connection to the area, but got dropped there by the MapRoulette ‘Ways Needing Smoothing’ challenge - freshly cleaned up, so most cases you get should now be real things to fix!

電郵圖示 Bluesky圖示 Facebook圖示 LinkedIn圖示 Mastodon圖示 Telegram圖示 X圖示

討論

Linutux2014年8月23日00:17發表的評論

I just read you blog post and looked at it myself. It’s just crazy! It’s not just one single street at one single place. The map in the whole area is crap. Oh my gosh!

aseerel4c262014年8月23日00:35發表的評論

or bing does not show reality! (in case you only rely on bing) ;-)

mvexel2014年8月23日00:46發表的評論

Bing may be out of date or misaligned, but in this case I’d wager a bet that TIGER is more wrong than Bing!

We also have the JOSM ‘TIGER 2012’ overlay as an additional reality check. This is also TIGER data but from after the big TIGER improvement program MFTAIP that ran between roughly 2004 and 2008:

TIGER 2012

jumbanho2014年8月23日00:46發表的評論

Yeah, sadly, the whole of Appalachia is like that, except for the few places where mappers live or visit.

Strava traces/slide, can help in the alignment if there are a lot of bikers in the area.

aseerel4c262014年8月23日01:45發表的評論

@mvexel: yeah, I just wanted to mention the possiblity (not more) of even a made-up bing aerial image.

robert2014年8月24日09:35發表的評論

Interesting thing is that it is actually topologically correct.

Pieren2014年8月26日12:38發表的評論

It’s seems the TIGER 2012 dataset is much better than first TIGER imported in OSM. Is something planned by the US community about this dataset ? a new import ? conflation ?

mvexel2014年8月26日22:00發表的評論

robert - that is what the T stands for in TIGER :)

Pieren - highly unlikely, for a number of reasons. The most important one is that the unique identifiers on the TIGER features have changed since the original import. Also, the original TIGER IDs have been removed from many objects in OSM. Both these things make it very hard to match newer TIGER to what is in OSM now reliably. Any re-import attempt would be far a smaller area, introducing its own set of challenges related to conflation and connecting up the newly imported data with the existing data at the boundaries of the import area. I think there is more to be gained from tools like the Battle Grid and the TIGER 2012/3 layers available in JOSM and iD.

Jonathan ZHAO2014年9月1日04:23發表的評論

I found it’s very common last year when we do battle grid. It’s very weird. The transformation has no obviously rule. I thought Navteq and TeleAtlas are also originated from Tiger. But there is no this kind of thing in Navteq or TeleAtlas.

nfgusedautoparts2014年9月7日00:55發表的評論

as near as i can tell, a lot of the early tiger stuff was hand drawn maps that was then entered in more-or-less the correct place without any reference to imagery. the stuff is topologically correct but off by large amounts in places. the worst i’ve seen is in WV which, of course, is part of Appalachia as jumbanho points out. best approach would be to use the tiger 2012/3 layers as reference for moving things to the right place. maybe we could find a way to load up maproulette with areas that have particularly bad correspondence?

登入以留言