Pr 62

[danielnovais-tech]

Description

Impact

User Benefit

Business Value

Roadmap Alignment

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Performance improvement
• Code refactoring
• Test coverage improvement
• Dependency update

Testing

• I have run existing tests (pytest tests/ -v)
• I have added new tests for my changes
• All tests pass locally

Checklist

• My code follows the PEP 8 style guidelines
• I have added docstrings (Google-style) to new functions/classes
• I have updated the documentation (README, API.md, etc.)
• My changes generate no new warnings or errors
• I have checked my code for potential security vulnerabilities
• I have verified that my changes work as expected

Related Issues

Closes #

Screenshots (if applicable)

Additional Context

[Copilot]

Pull request overview

Adds README documentation to help users prepare CSV inputs for the Manual CSV Pipeline portion of the Rural Connectivity Mapper.

Changes:

• Added a “CSV templates” section with a basic and a complete example CSV snippet.
• Linked readers to the full Manual CSV Pipeline guide for more details.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The templates include jitter and packet_loss as if they are first-class measurement metrics, but the Manual CSV pipeline currently only preserves these columns as string metadata (see src/sources/manual_csv.py where they are copied into measurement.metadata), and they are not part of the canonical MeasurementSchema. This is likely to mislead users into thinking those values will be validated/used in scoring/analysis; either clarify here that these fields are stored as metadata only for Manual CSV ingestion, or remove them from the Manual CSV templates / link to the upload_csv.py template docs instead.

Suggested change

	Note: in the Manual CSV pipeline, the `jitter` and `packet_loss` columns are preserved as string metadata only and are **not** part of the canonical `MeasurementSchema` or used directly in scoring/analysis.