rjh
May 24, 08, 9:33 am
It looks as if one can consider using twitter (http://twitter.com/commuter) to report near real time tactics for finding shortest security checkpoint lines.
The method would require prior reporting travelers, similar to the logic of Dash Express (http://dash.net/product/traffic.php), without the historical component. Yeah, a certain critical mass of reporting travelers would be required, twitter would have to have better service availability, filtering of the feed for specific sites would have to be implemented/improved...
For instance, a simple case would be OAK, where the Terminal 2 checkpoint can be a zoo. If T1 checkpoint wasn't similarly a disaster, one could get a report from an earlier traveler through T1 and choose the T1 checkpoint, then walk airside to T2.
Of course, this method could also be used for early warning about expert/casual/family lane issues, doing time and motion studies of ID checkers, avoiding checkpoint closure because of pepper spray discharge, etc.
The method would require prior reporting travelers, similar to the logic of Dash Express (http://dash.net/product/traffic.php), without the historical component. Yeah, a certain critical mass of reporting travelers would be required, twitter would have to have better service availability, filtering of the feed for specific sites would have to be implemented/improved...
For instance, a simple case would be OAK, where the Terminal 2 checkpoint can be a zoo. If T1 checkpoint wasn't similarly a disaster, one could get a report from an earlier traveler through T1 and choose the T1 checkpoint, then walk airside to T2.
Of course, this method could also be used for early warning about expert/casual/family lane issues, doing time and motion studies of ID checkers, avoiding checkpoint closure because of pepper spray discharge, etc.