How mhaln3mi/nyc-flights-eda works
Project type and purpose
• This is an Exploratory Data Analysis (EDA) pipeline built in R.
• Purpose: ingest raw flight/demographics data → perform data munging and visualization → produce a static HTML report, then host it as a GitHub Pages site.
File structure
• Top-level:
• data/ → raw CSV inputs
• src/ → R scripts and RMarkdown for analysis & report generation
• report.html (the generated output)
• NYC_Flights_Delays_EDA.Rproj → RStudio project file
• No separate “frontend” or “backend” folders—this is a single analytical pipeline.
README for additional insights
• Libraries: tidyverse, plotly, ggplot2, nycflights13, etc.
• Workflow: data munging → EDA → data viz → HTML report.
Main components & interactions
a. Data Layer
• airports_per_state.csv
• flights_data.csv
b. Processing Layer
1) Data Ingestion & Cleaning (src/EDA.R)
2) Exploratory Analysis & Visualization (src/report.Rmd invoking plotly, ggplot2, janitor, etc.)
3) Report Rendering (knitr renders .Rmd → report.html)
c. Hosting Layer
• GitHub Pages or static web server that serves report.html
d. User Layer
• Web browser that fetches report.html
• Raw CSV → Data Cleaning script
• Cleaning → EDA Visualizations
• Visualizations + Analysis → HTML Report
• HTML Report → Web Server
• User Browser ← HTML Report
Architectural patterns & tech
• “Pipeline” pattern: linear ETL (Extract, Transform, Load) + Reporting
• R packages as components: tidyverse for data wrangling, plotly/ggplot2 for viz, knitr for report
• Static-site hosting (GitHub Pages)