Rewrite

[antoinebou12]

Description

This branch delivers a major rewrite of TrueMapData: reorganized packages, a clearer Typer-based CLI (tmd_cli.py entry point), and refactored surface and sequence pipelines. Surface work moves logic into tmd/surface/ (including transformations, terrain generation, filters, metadata, and processing) and drops the old monolithic tmd/utils/transformations.py / mesh_converter.py style layout in favor of a more cohesive module structure. Sequences are reworked around factory, GIF, video, and PowerPoint paths instead of the previous exporter/plotter split.

Additional scope includes 3D model export flows, alignment tooling, texture handling fixes, normal-related fixes, expanded maps support, documentation and GitHub workflow updates for deployment and docs generation, refreshed requirements, notebook tooling under tools/, and removal of stray sample assets (test.py, sample .tmd files). Legacy tmd2model.py is removed in favor of the new CLI-oriented layout.

Motivation: simplify maintenance, align the public API and CLI with current workflows, and make TMD processing, visualization, and export paths easier to extend and test.

Fixes # (add the issue number if one tracks this rewrite; otherwise remove this line)

---

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

(Breaking: import paths, removed tmd2model.py, and reshaped sequence/surface APIs will break consumers on the old layout.)

---

How Has This Been Tested?

From the repo root, with dev dependencies available:

python -m pytest tests -q

Result (this environment): 114 passed, 4 skipped; 5 warnings (mostly coverage/third-party noise in the tail of the run).

Reproduce: clone the branch, create/activate a venv, pip install -e ".[dev]" (or your usual install), then run the command above.

---

Checklist

• My code follows the style guidelines of this project (assumption—adjust after your own pass)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (per commits on docs/workflows)
• My changes generate no new warnings (pytest reported 5 warnings)
• I have added tests that prove my fix is effective or that my feature works (suite covers surface, CLI smoke, sequence alignment, etc.)
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules