How enochemerald/nigerian_aircraft_accident works
Project type and purpose
• This is a data‐analysis and reporting project (not a typical full‐stack app). Its purpose is to ingest historical aircraft accident data for Nigeria, compute trends and summary statistics, then produce deliverables in Excel, PowerPoint and PDF form for stakeholders.
File structure
• Top-level files:
• Nigerian_air_accidents.xlsx – the primary data table
• Nigerian_air_accidents.pptx – the slide deck of findings
• Nigerian_air_accidents.pdf – a printable report
• README.md – explanation of scope, source, insights
• There are no code or service directories; the “runtime” is an ad-hoc data pipeline likely implemented offline (e.g., Python/R scripts or manual steps).
README for additional insights
• Data source: Aviation Safety Network
• Key outputs: Trends by year, operator, severity, fatalities
a. Main components
1. External Data Source (ASN online database)
2. Data Ingestion Layer (download / API client / scraper)
3. Raw Data Storage (Excel file, CSV intermediate)
4. Processing & Analysis Engine (e.g., Python scripts, R scripts, Jupyter notebooks)
5. Visualization & Reporting Module (charting libraries, PPTX generator, PDF exporter)
6. Final Deliverables (Nigerian_air_accidents.xlsx/.pptx/.pdf)
b. Relationships & interactions
• Ingestion → Raw Storage
• Raw Storage → Analysis Engine
• Analysis Engine → Visualization Module
• Visualization Module → Final Deliverables
c. Architectural patterns / design principles
• ETL (Extract → Transform → Load) pipeline
• Separation of concerns: ingestion, storage, analysis, reporting
• Modularity: each step can be automated or run manually
d. Key technologies / libraries (hypothetical based on deliverables)
• Data Ingestion: requests / BeautifulSoup (Python) or API client
• Storage: pandas (read/write Excel/CSV)
• Processing: pandas, numpy, scipy
• Visualization: matplotlib / seaborn, python-pptx
• Reporting: ReportLab or LaTeX → PDF, python-pptx
Be comprehensive but focused
• Discrete step in the pipeline as a separate component
• Don’t over-fragment—show logical groupings (e.g., “Processing & Analysis Engine” can contain multiple scripts)