import streamlit as st

st.markdown(
    """
# Traffic Analysis Documentation

## 1. Objective
Analyze and compare 2G/3G/LTE traffic behavior across pre/post periods and visualize trends, top sites, and maps.

## 2. When to use this tool
Use this page when you need:
- pre/post traffic comparison
- top traffic site ranking
- trend visualization over time
- map-based traffic review
- exportable summary outputs

## 3. Input files and accepted formats
Typical inputs are KPI traffic exports in `.csv` (or zip containing CSV, depending on source export).
You usually provide one report per RAT:
- 2G traffic report
- 3G traffic report
- LTE traffic report

## 4. Required fields (typical)
Required columns depend on RAT and source report format. Common fields include:
- site/cell identifiers (`BCF name`, `WBTS name`, `LNBTS name`)
- timestamp/date (`PERIOD_START_TIME`)
- traffic metrics (voice/data indicators by RAT)

## 5. Step-by-step usage
1. Open `KPI Analysis > Trafic Analysis`.
2. Upload available traffic reports (2G/3G/LTE).
3. Configure period filters (pre/post/last period).
4. Choose analysis options (top N, thresholds, drill-down filters).
5. Review tables, charts, and maps.
6. Download generated report when available.

## 6. Outputs generated
- comparative summary tables
- top sites by voice/data traffic
- trend charts
- map visualizations
- downloadable report (Excel) when generated

## 7. Frequent errors and fixes
- Empty charts or missing KPIs.
  - Fix: verify required traffic columns exist and are numeric.
- Date filtering produces no data.
  - Fix: confirm date format and selected ranges.
- Unexpected aggregation result.
  - Fix: check identifier consistency (site/cell naming between reports).

## 8. Minimal reproducible example
- Input: one valid 2G, one valid 3G, one valid LTE traffic CSV covering overlapping dates.
- Action: select pre/post periods and run analysis.
- Expected result: non-empty summary tables and top-sites charts.

## 9. Known limitations
- Results depend on source export quality and naming consistency.
- Very large reports can increase rendering time.
- Mixed naming standards across RATs can reduce merge quality.

## 10. Version and update date
- Documentation version: 1.0
- Last update: 2026-02-23
"""
)