Dataset: Taxi Routes Of Mexico City, Quito And More

About this Dataset

Taxi Routes Of Mexico City, Quito And More

Context

This dataset was collected using our App EC Taximeter.

An easy to use tool developed to compare fees, giving the user an accurate fee based on GPS to calculate a cost of the taxi ride. Due to the ability to verify that you are charged fairly, our App is very popular in several cities. We encourage our users to send us URLs with the taxi/transportation fees in their cities to keep growing our database.

★ Our App gets the available fares for your location based on your GPS, perfect when traveling and not getting scammed.

★ Users can start a taximeter in their own phone and check they are charged fairly

★ Several useful information is displayed to the user during the ride: Speed, Wait time, Distance, GPS update, GPS precision, Range of error.

★ Each fare has information available for reference like: Schedule, Minimum fee, Source, Last update.

★ It’s possible to surf through several cities and countries which fares are available for use. If a fare is not in the app, now it’s easier than ever to let us know thanks to Questbee Apps.

We invite users to contribute to our project and expect this data set to be useful, please don't hesitate to contact us to info@ashkadata.com to add your city or to contribute with this project.

Content

The data is collected from June 2016 until July 20th 2017. The data is not completely clean, many users forget to turn off the taximeter when done with the route. Hence, we encourage data scientist to explore it and trim the data a little bit

Acknowledgements

We have to acknowledge the valuable help of our users, who have contributed to generate this dataset and have push our growth by mouth to mouth recommendation.

Inspiration

Our first inspiration for the App was after being scammed in our home city Quito. We started it as a tool for people to be fairly charged when riding a taxi. Currently with other transportation options available, we also help user to compare fares in their cities or the cities which they are visiting.

File descriptions

mex_clean.csv - the dataset contains information of routes in Mexico City
uio_clean.csv - the dataset contains information of routes in Quito Ecuador
bog_clean.csv - the dataset contains information of routes in Bogota
all-data_clean.csv - the dataset contains information of routes in different cities

Tables

All Data Clean

@kaggle.mnavas_taxi_routes_for_mexico_city_and_quito.all_data_clean

6.29 MB
90287 rows
12 columns


CREATE TABLE all_data_clean (
  "id" BIGINT,
  "vendor_id" VARCHAR,
  "pickup_datetime" TIMESTAMP,
  "dropoff_datetime" TIMESTAMP,
  "pickup_longitude" DOUBLE,
  "pickup_latitude" DOUBLE,
  "dropoff_longitude" DOUBLE,
  "dropoff_latitude" DOUBLE,
  "store_and_fwd_flag" VARCHAR,
  "trip_duration" BIGINT,
  "dist_meters" BIGINT,
  "wait_sec" BIGINT
);

Bog Clean

@kaggle.mnavas_taxi_routes_for_mexico_city_and_quito.bog_clean

232.45 KB
3063 rows
12 columns


CREATE TABLE bog_clean (
  "id" BIGINT,
  "vendor_id" VARCHAR,
  "pickup_datetime" TIMESTAMP,
  "dropoff_datetime" TIMESTAMP,
  "pickup_longitude" DOUBLE,
  "pickup_latitude" DOUBLE,
  "dropoff_longitude" DOUBLE,
  "dropoff_latitude" DOUBLE,
  "store_and_fwd_flag" VARCHAR,
  "trip_duration" BIGINT,
  "dist_meters" BIGINT,
  "wait_sec" BIGINT
);

Mex Clean

@kaggle.mnavas_taxi_routes_for_mexico_city_and_quito.mex_clean

923.79 KB
12694 rows
12 columns


CREATE TABLE mex_clean (
  "id" BIGINT,
  "vendor_id" VARCHAR,
  "pickup_datetime" TIMESTAMP,
  "dropoff_datetime" TIMESTAMP,
  "pickup_longitude" DOUBLE,
  "pickup_latitude" DOUBLE,
  "dropoff_longitude" DOUBLE,
  "dropoff_latitude" DOUBLE,
  "store_and_fwd_flag" VARCHAR,
  "trip_duration" BIGINT,
  "dist_meters" BIGINT,
  "wait_sec" BIGINT
);

Uio Clean

@kaggle.mnavas_taxi_routes_for_mexico_city_and_quito.uio_clean

2.23 MB
32366 rows
12 columns


CREATE TABLE uio_clean (
  "id" BIGINT,
  "vendor_id" VARCHAR,
  "pickup_datetime" TIMESTAMP,
  "dropoff_datetime" TIMESTAMP,
  "pickup_longitude" DOUBLE,
  "pickup_latitude" DOUBLE,
  "dropoff_longitude" DOUBLE,
  "dropoff_latitude" DOUBLE,
  "store_and_fwd_flag" VARCHAR,
  "trip_duration" BIGINT,
  "dist_meters" BIGINT,
  "wait_sec" BIGINT
);