Video summary
Ola Data Analytics End to End Project | Data Analytics SQL, Excel & PowerBI Dashboard Project
Main summary
Key takeaways
Tech/Product/Project Summary (Ola Data Analytics end-to-end)
Project goal & dataset
- Builds an end-to-end data analytics project for Ola ride bookings to answer business-style questions, such as:
- Successful vs. cancelled rides
- Delays and cancellation reasons
- Driver and customer ratings
- Payment methods
- Revenue and booking values
- Uses an auto-generated bookings dataset with 19 columns.
- Dataset size is described as ~1 lakh+ rows per day; users can download it and adjust based on available capacity.
End-to-end workflow (SQL + Excel + Power BI)
1. Data cleaning in Excel
- Removes duplicate rows.
- Mentions additional cleanup steps such as:
- Trimming/cleaning whitespaces
- Using “AI suggestions” for cleanup
- Exports the cleaned dataset as CSV.
2. SQL setup and loading
- Uses SQL Workbench:
- Creates a database (e.g.,
Ola) - Imports the CSV into a SQL table (renames table to
bookingsor similar)
- Creates a database (e.g.,
- Creates SQL views for reusability, enabling faster retrieval and cleaner presentation in the project.
3. Core SQL queries (10-question set)
- Demonstrates writing multiple SQL queries and then wrapping them into
CREATE VIEWstatements. - Key query patterns shown:
- Filtering by
booking_status(e.g., successful, cancelled by customer/driver) GROUP BY+AVGfor averages by vehicle type (e.g., average right distance by vehicle type)COUNTfor cancellation counts (e.g., cancelled by customers; cancelled by drivers by reason)- Top-N ranking using:
COUNT(...)GROUP BY customer_idORDER BY ... DESCLIMIT 5
MIN/MAXfor driver ratings by vehicle type, including handling invalid/blank ratingsSUMfor total booking value totals (e.g., total ride value for successful bookings)- Selective filtering for payment method (e.g., rides paid via UPI)
- Extracting incomplete rides and their reasons (e.g.,
booking_id,incomplete_reason)
- Filtering by
4. Power BI dashboard design (visualization)
- After SQL, transitions to Power BI to build a multi-page dashboard (approximately 5 pages) with navigation buttons:
- Overall
- Ride volume over time
- Booking status breakdown
- Slicers
- Cards for total bookings and total booking value
- Vehicle Type
- Booking value by vehicle type
- Average right distance by vehicle type
- Revenue
- Revenue/payment method breakdown
- Average right distance vs. date
- Top 5 customers by booking value
- Cancellation
- Pie charts: cancellations by customer vs driver
- Cancellation counts and cancellation rate via a DAX measure
- Ratings
- Cards/visuals for driver and customer ratings by vehicle type
- Overall
- Uses common Power BI visuals:
- Line charts, pie charts, bar/column charts
- Tables and cards
- Slicers
- Power BI transformations described:
- Set first row as headers
- Convert timestamps to date
- Ensure numeric typing for columns such as booking value/distance/ratings
DAX concept: cancellation rate
- Introduces a DAX measure for cancellation rate:
- Cancellation rate ≈ (Cancelled bookings / Total bookings) * 100
- Includes supporting measures:
- Count of cancelled bookings
- Count of total bookings
- Percentage calculation using division and multiplication by 100
Resume positioning / deliverables emphasized
- The project is positioned as resume-ready by showcasing:
- SQL queries and views
- A complete Power BI end-to-end dashboard
- A promised downloadable repository/code link (as mentioned in the description)
- Encourages packaging deliverables for sharing (e.g., PDF/page, screenshots, and/or repo link).
Main speakers/sources (as mentioned/implied)
- “Ola” project (company domain used in the dataset)
- Main speaker: the YouTube presenter/creator (identity not explicitly named in subtitles)
- Mentions external platforms/content:
- Alice’s courses
- Unacademy
- FlatIcons
- A dataset blog/repository link (exact creator attribution not clearly identified in subtitles)