http://www.manifestdensity.net/2009/07/01/gtfs-and-nextbus-dont-match-up/ Just another WordPress weblog Fri, 03 Feb 2012 18:04:33 +0000 hourly 1 http://wordpress.org/?v=3.3 http://www.manifestdensity.net/2009/07/01/gtfs-and-nextbus-dont-match-up/comment-page-1/#comment-42471 thiet ke website Wed, 27 Oct 2010 23:00:17 +0000 http://127.0.0.1:8888/?p=819#comment-42471 I love this post. I love this post.

]]> http://www.manifestdensity.net/2009/07/01/gtfs-and-nextbus-dont-match-up/comment-page-1/#comment-3976 NextBus = awesome Tue, 13 Oct 2009 21:32:44 +0000 http://127.0.0.1:8888/?p=819#comment-3976 LOL, you guys are funny. NextBus provides a feed in GTFS format for the real-time predictions...it's not out because Google Transit does not yet allow this type of data. No sense overanalyzing this. NextBus was here long before GTFS so I am not sure why you are surprised that they don't match up. LOL, you guys are funny. NextBus provides a feed in GTFS format for the real-time predictions…it’s not out because Google Transit does not yet allow this type of data. No sense overanalyzing this. NextBus was here long before GTFS so I am not sure why you are surprised that they don’t match up.

]]> http://www.manifestdensity.net/2009/07/01/gtfs-and-nextbus-dont-match-up/comment-page-1/#comment-1749 Tom Mon, 06 Jul 2009 17:14:45 +0000 http://127.0.0.1:8888/?p=819#comment-1749 That's a good suggestion, and one I'll have to investigate more thoroughly. But based on the one or two stops I've examined, I think the answer is "no". And worse, the distances make it look unlikely -- only a handful of the matches I generated (see <a href="http://www.manifestdensity.net/2009/07/02/some_nextbus_stats/" rel="nofollow">here</a> and <a href="http://www.manifestdensity.net/2009/07/06/more_nextbussery/" rel="nofollow">here</a>) are within 10m of the corresponding GTFS stops. It's weird -- right now my best guess is that NB may be using a different coordinate projection system (although the fact that I got these coordinates out of their google map system would make that very strange indeed). That’s a good suggestion, and one I’ll have to investigate more thoroughly. But based on the one or two stops I’ve examined, I think the answer is “no”. And worse, the distances make it look unlikely — only a handful of the matches I generated (see here and here) are within 10m of the corresponding GTFS stops. It’s weird — right now my best guess is that NB may be using a different coordinate projection system (although the fact that I got these coordinates out of their google map system would make that very strange indeed).

]]> http://www.manifestdensity.net/2009/07/01/gtfs-and-nextbus-dont-match-up/comment-page-1/#comment-1748 Wes Mon, 06 Jul 2009 16:59:17 +0000 http://127.0.0.1:8888/?p=819#comment-1748 Could the Lat and Long descrepancy be explained by NextBus putting the bus stop on the street (as that's where buses stop, and they're tracking buses) while WMATA puts the stop on the sidewalk, where the shelter or the flag goes? Could the Lat and Long descrepancy be explained by NextBus putting the bus stop on the street (as that’s where buses stop, and they’re tracking buses) while WMATA puts the stop on the sidewalk, where the shelter or the flag goes?

]]>