Baselight

Traffic Flow Data In Ho Chi Minh City, Viet Nam

Historical data of traffic condition (speed, level of service, etc.)

@kaggle.thanhnguyen2612_traffic_flow_data_in_ho_chi_minh_city_viet_nam

Loading...
Loading...

About this Dataset

Traffic Flow Data In Ho Chi Minh City, Viet Nam

Context

Mining historical data from local traffic condition to learn/predict/analyze how traffic flow could be at different times of the day.

Content

The main file is train.csv: built from segments.csv and segment_status.csv. A day is split into 48 periods of 30 minutes, the first period is period_0_00 corresponding to 00:00 and the last one is period_23_30 corresponding to 23:30, each period is labeled by Level of Service (LOS - assessed by velocity at the time and the maximum velocity allowed.)
The original dataset provided and minimized for analytical purposes contains 4 tables only:

  • segment_status.csv: traffic status for a segment reported at different date and time.
  • segments.csv: detail information about a segment including start node, end node, length of the segment and its belonging street.
  • nodes.csv: a node is a point on Earth specified by longitude and latitude positions, it connects segments together.
  • streets.csv: many segments together form a street in real-world, the table contains details about street name, level, type of street and its maximum velocity when free flow.

Acknowledgements

Data provided: Research group from HCM University of Technology (website)
Banner image by Denys Nevozhai

Inspirations

Research motivation?

Tables

Nodes

@kaggle.thanhnguyen2612_traffic_flow_data_in_ho_chi_minh_city_viet_nam.nodes
  • 11.5 MB
  • 577967 rows
  • 3 columns
Loading...

CREATE TABLE nodes (
  "n__id" BIGINT,
  "long" DOUBLE,
  "lat" DOUBLE
);

Segments

@kaggle.thanhnguyen2612_traffic_flow_data_in_ho_chi_minh_city_viet_nam.segments
  • 2.49 MB
  • 84633 rows
  • 11 columns
Loading...

CREATE TABLE segments (
  "n__id" BIGINT,
  "created_at" VARCHAR,
  "updated_at" VARCHAR,
  "s_node_id" BIGINT,
  "e_node_id" BIGINT,
  "length" BIGINT,
  "street_id" BIGINT,
  "max_velocity" DOUBLE,
  "street_level" BIGINT,
  "street_name" VARCHAR,
  "street_type" VARCHAR
);

Segment Status

@kaggle.thanhnguyen2612_traffic_flow_data_in_ho_chi_minh_city_viet_nam.segment_status
  • 1.33 MB
  • 90938 rows
  • 4 columns
Loading...

CREATE TABLE segment_status (
  "n__id" BIGINT,
  "updated_at" VARCHAR,
  "segment_id" BIGINT,
  "velocity" BIGINT
);

Streets

@kaggle.thanhnguyen2612_traffic_flow_data_in_ho_chi_minh_city_viet_nam.streets
  • 61.32 KB
  • 5553 rows
  • 5 columns
Loading...

CREATE TABLE streets (
  "n__id" BIGINT,
  "level" BIGINT,
  "max_velocity" DOUBLE,
  "name" VARCHAR,
  "type" VARCHAR
);

Train

@kaggle.thanhnguyen2612_traffic_flow_data_in_ho_chi_minh_city_viet_nam.train
  • 983.08 KB
  • 33441 rows
  • 18 columns
Loading...

CREATE TABLE train (
  "n__id" BIGINT,
  "segment_id" BIGINT,
  "date" TIMESTAMP,
  "weekday" BIGINT,
  "period" VARCHAR,
  "los" VARCHAR,
  "s_node_id" BIGINT,
  "e_node_id" BIGINT,
  "length" BIGINT,
  "street_id" BIGINT,
  "max_velocity" DOUBLE,
  "street_level" BIGINT,
  "street_name" VARCHAR,
  "street_type" VARCHAR,
  "long_snode" DOUBLE,
  "lat_snode" DOUBLE,
  "long_enode" DOUBLE,
  "lat_enode" DOUBLE
);

Share link

Anyone who has the link will be able to view this.