CRAWDAD rice/ad_hoc_city

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. 

西雅图城市公交车队移动数据集。

我们获取了华盛顿州西雅图市城市公交车队在全市范围内提供客运服务的常规路线上的数周移动轨迹。

测量开始日期/时间：2001-10-30
测量结束日期/时间：2001-12-02

收集环境：
我们提出了一个名为Ad Hoc City的系统，它是一种适用于通用广域通信的多层无线自组织网络路由架构。为了通过仿真评估我们提出的设计，我们收集了华盛顿州西雅图大都市区城市公交车队在全市范围内提供客运服务的常规路线上的实际移动轨迹。西雅图的地形为路由带来了挑战，因其城市中央有一个面积达35平方英里的湖泊。该公交系统由超过1200辆公交车组成，覆盖面积达5100平方公里。

网络配置：
自动车辆定位（Automated Vehicle Location，AVL）系统通过里程计和路标发射器的组合跟踪每辆公交车。互联网用户可通过Busview软件实时监控每辆公交车的位置。

数据收集方法：
我们获取了华盛顿州西雅图市城市公交车队在全市范围内提供客运服务的常规路线上的数周移动轨迹。

轨迹集 rice/ad_hoc_city/bus_mobility
西雅图城市公交车队移动轨迹集。

测量目的：
用户移动特征分析、路由协议

方法：
为评估Ad Hoc City架构，我们使用了华盛顿州西雅图地区金县地铁公交系统的公交车实际移动轨迹。选择该系统的原因是其数据可在线获取，且公交车移动模式与其他车辆交通模式高度匹配。自动车辆定位（Automated Vehicle Location，AVL）系统通过里程计和路标发射器的组合跟踪每辆公交车。互联网用户可通过Busview软件实时监控每辆公交车的位置。我们开发了记录传递给Busview客户端的数据的机制，并将记录数据转换为适用于ns-2网络模拟器的移动模式，以评估我们的系统。

rice/ad_hoc_city/bus_mobility 轨迹

Trace1：西雅图城市公交车队移动轨迹。

配置：这些轨迹基于每辆公交车发送的位置更新消息。
格式：Trace1目录中的轨迹对应数周的数据。每一行格式如下：日-月:时间；公交车ID；路线ID；未知；x坐标；y坐标。路线ID表示公交车行驶的路线，任何时候可能有多辆公交车行驶同一条路线。x和y坐标以英尺为单位，由原始轨迹中报告的纬度和经度值计算得出。

Trace2：西雅图城市公交车队移动轨迹。

配置：这些轨迹基于每辆公交车发送的位置更新消息。
格式：Trace2目录中的轨迹对应数周的数据。每一行格式如下：日-月:时间；公交车ID；路线ID；未知；x坐标；y坐标。路线ID表示公交车行驶的路线，任何时候可能有多辆公交车行驶同一条路线。x和y坐标以英尺为单位，由原始轨迹中报告的纬度和经度值计算得出。

Trace3：西雅图城市公交车队移动轨迹。

配置：这些轨迹基于每辆公交车发送的位置更新消息。
格式：Trace3目录中的轨迹对应数周的数据。每一行格式如下：日-月:时间；公交车ID；路线ID；未知；x坐标；y坐标。路线ID表示公交车行驶的路线，任何时候可能有多辆公交车行驶同一条路线。x和y坐标以英尺为单位，由原始轨迹中报告的纬度和经度值计算得出。

Trace4：西雅图城市公交车队移动轨迹。

配置：这些轨迹基于每辆公交车发送的位置更新消息。
格式：Trace4目录中的轨迹对应数周的数据。每一行格式如下：日-月:时间；公交车ID；路线ID；未知；x坐标；y坐标。路线ID表示公交车行驶的路线，任何时候可能有多辆公交车行驶同一条路线。x和y坐标以英尺为单位，由原始轨迹中报告的纬度和经度值计算得出。

Trace5：西雅图城市公交车队移动轨迹。

配置：这些轨迹基于每辆公交车发送的位置更新消息。
格式：Trace5目录中的轨迹对应数周的数据。每一行格式如下：日-月:时间；公交车ID；路线ID；未知；x坐标；y坐标。路线ID表示公交车行驶的路线，任何时候可能有多辆公交车行驶同一条路线。x和y坐标以英尺为单位，由原始轨迹中报告的纬度和经度值计算得出。