DOI: 10.21227/56xb-zg78
title: CRAWDAD rice/ad_hoc_city

description: Dataset 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. date/time of measurement start: 2001-10-30date/time of measurement end: 2001-12-02collection environment: We 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.network configuration: 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.data collection methodology: 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.Tracesetrice/ad_hoc_city/bus_mobilityTraceset of the movement of the fleet of city buses in Seattle.file: traces.tar.gzdescription: This traceset consists of several weeklong traces of the movement of the fleet of city buses in Seattle, Washington.measurement purpose: User Mobility Characterization, Routing Protocolmethodology: To 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.rice/ad_hoc_city/bus_mobility TraceTrace1 : Trace of the movement of the fleet of city buses in Seattle.configuration: The traces are based on location update messages sent by each bus.format: 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.Trace2 : Trace of the movement of the fleet of city buses in Seattle.configuration: The traces are based on location update messages sent by each bus.format: 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.Trace3 : Trace of the movement of the fleet of city buses in Seattle.configuration: The traces are based on location update messages sent by each bus.format: 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.Trace4 : Trace of the movement of the fleet of city buses in Seattle.configuration: The traces are based on location update messages sent by each bus.format: 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.Trace5 : Trace of the movement of the fleet of city buses in Seattle.configuration: The traces are based on location update messages sent by each bus.format: 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.