rice/ad_hoc_city2003091145200309112008-07-23rice/ad_hoc_cityDataset of the movement of the fleet of city buses in Seattle.We acquired several weeklong traces of the movement of the fleet of
city buses in Seattle, Washington, on their normal routes providing
passenger bus service throughout the city.the initial version2003-09-112001-10-302001-12-02jetcheva-metropolitanREADME174175176177178http://www.crawdad.org/rice/ad_hoc_cityhttp://www.crawdad.org/wiki/pmwiki.php?n=Main.Dataset.rice-ad_hoc_citylocationvehicular networkMANETUser Mobility CharacterizationRouting ProtocolVehicular networkWe propose a system, called Ad Hoc City, that is a multitier wireless
ad hoc network routing architecture for generalpurpose wide-area
communication. To evaluate our proposed design through simulation,
we collected traces of the actual movement of the fleet of city
buses in the Seattle, Washington metropolitan area, on their normal
routes providing passenger bus service throughout the city.
Seattle provides a topographically challenging routing
environment, created by a 35 square mile lake in the middle
of the city. The bus system is composed of over 1200
vehicles covering a 5100 square kilometer area.An Automated Vehicle Location (AVL) system tracks each bus
using a combination of odometry and signpost transmitters.
Internet users can monitor the location of each bus
in real-time using the Busview software.We acquired several weeklong traces of the movement of the fleet of
city buses in Seattle, Washington, on their normal routes providing
passenger bus service throughout the city.69200309112008-07-23the initial version.rice/ad_hoc_city/bus_mobilityTraceset of the movement of the fleet of city buses in Seattle.This traceset consists of several weeklong traces of the movement of
the fleet of city buses in Seattle, Washington.2003-09-112001-10-302001-12-02User Mobility CharacterizationRouting ProtocolTo evaluate the Ad Hoc City architecture, we used
traces of the actual movement of buses in the Seattle,
Washington area King County Metro bus system. We chose
the King County bus system because the data was available
on-line, and because bus movement patterns closely
match other vehicular traffic patterns.
An Automated Vehicle Location (AVL) system tracks each bus
using a combination of odometry and signpost transmitters.
Internet users can monitor the location of each bus
in real-time using the Busview software. We developed
mechanisms for recording the data being delivered to
Busview clients, and for converting the recorded data into
movement patterns suitable for use in the ns-2 network simulator,
which we use to evaluate our system./download/rice/ad_hoc_city/traces.tar.gzrice/ad_hoc_city214200309112008-07-23the initial versionrice/ad_hoc_city/bus_mobility/Trace1Trace of the movement of the fleet of city buses in Seattle.Trace of the movement of the fleet of city buses in Seattle.false2003-09-112001-10-302001-10-31The traces are based on location update messages sent
by each bus.The traces in Trace1 directory correspond to several weeks worth of data.
Each line in the traces is formatted as follows:
<day>-<month>:<time> <bus_id> <route_id> <unknown> <x_coord> <y_coord>
The route_id signifies the route followed by a bus. Multiple buses may follow a given
bus route at any time. The x and y coordinates are in feet and were computed from the
latitude and longitude values reported in the raw traces.rice/ad_hoc_city/bus_mobility215200309112008-07-23the initial versionrice/ad_hoc_city/bus_mobility/Trace2Trace of the movement of the fleet of city buses in Seattle.Trace of the movement of the fleet of city buses in Seattle.false2003-09-112001-11-012001-11-05The traces are based on location update messages sent
by each bus.The traces in Trace2 directory correspond to several weeks worth of data.
Each line in the traces is formatted as follows:
<day>-<month>:<time> <bus_id> <route_id> <unknown> <x_coord> <y_coord>
The route_id signifies the route followed by a bus. Multiple buses may follow a given
bus route at any time. The x and y coordinates are in feet and were computed from the
latitude and longitude values reported in the raw traces.rice/ad_hoc_city/bus_mobility216200309112008-07-23the initial versionrice/ad_hoc_city/bus_mobility/Trace3Trace of the movement of the fleet of city buses in Seattle.Trace of the movement of the fleet of city buses in Seattle.false2003-09-112001-11-072001-11-09The traces are based on location update messages sent
by each bus.The traces in Trace3 directory correspond to several weeks worth of data.
Each line in the traces is formatted as follows:
<day>-<month>:<time> <bus_id> <route_id> <unknown> <x_coord> <y_coord>
The route_id signifies the route followed by a bus. Multiple buses may follow a given
bus route at any time. The x and y coordinates are in feet and were computed from the
latitude and longitude values reported in the raw traces.rice/ad_hoc_city/bus_mobility217200309112008-07-23the initial versionrice/ad_hoc_city/bus_mobility/Trace4Trace of the movement of the fleet of city buses in Seattle.Trace of the movement of the fleet of city buses in Seattle.false2003-09-112001-11-132001-11-15The traces are based on location update messages sent
by each bus.The traces in Trace4 directory correspond to several weeks worth of data.
Each line in the traces is formatted as follows:
<day>-<month>:<time> <bus_id> <route_id> <unknown> <x_coord> <y_coord>
The route_id signifies the route followed by a bus. Multiple buses may follow a given
bus route at any time. The x and y coordinates are in feet and were computed from the
latitude and longitude values reported in the raw traces.rice/ad_hoc_city/bus_mobility218200309112008-07-23the initial versionrice/ad_hoc_city/bus_mobility/Trace5Trace of the movement of the fleet of city buses in Seattle.Trace of the movement of the fleet of city buses in Seattle.false2003-09-112001-11-162001-12-02The traces are based on location update messages sent
by each bus.The traces in Trace5 directory correspond to several weeks worth of data.
Each line in the traces is formatted as follows:
<day>-<month>:<time> <bus_id> <route_id> <unknown> <x_coord> <y_coord>
The route_id signifies the route followed by a bus. Multiple buses may follow a given
bus route at any time. The x and y coordinates are in feet and were computed from the
latitude and longitude values reported in the raw traces.rice/ad_hoc_city/bus_mobility174rice/ad_hoc_cityJorjeta G. Jetchevajorjeta@cs.cmu.eduCarnegie Mellon UniversityComputer Science713-348-2732http://www.cs.cmu.edu/~jorjeta/175rice/ad_hoc_cityYih-Chun HuUniversity of Illinois at Urbana-ChampaignDepartment of Electrical and Computer EngineeringAssistant ProfessorDepartment of Electrical and Computer Engineering
University of Illinois at Urbana-Champaign
1308 West Main Street
Urbana, Illinois 61801217-333-4220217-244-5685http://www.crhc.uiuc.edu/~yihchun/176rice/ad_hoc_citySantashil PalChaudhurisanta@alumni.rice.eduAruba Networks1322 Crossman Ave Sunnyvale, CA 94089408-754-8012http://www.cs.rice.edu/~santa/177rice/ad_hoc_cityAmit Kumar Sahaamsaha@cs.rice.eduTropos Networkshttp://www.cs.rice.edu/~amsaha/178rice/ad_hoc_cityDavid B. Johnsondbj@cs.rice.eduRice UniversityComputer ScienceProfessorDepartment of Computer Science
Rice University
6100 Main Street MS-132
Houston, TX 77005-1892
USA713 348-3063713 348-5930http://www.cs.rice.edu/~dbj/