Many mapping jobs are not a single orthomosaic. Progress flights, RGB vs thermal, or alternate processing runs often arrive as separate georeferenced TIFFs. Version 2 puts those layers into one map room instead of forcing operators to bounce between projects or external viewers.

What you can do

• Switch among hosted GeoTIFF layers from a compact layer control in the map room
• Add another orthomosaic layer to the same room without replacing the primary deliverable
• Keep map annotations scoped to the active layer so notes stay attached to the right surface
• Present a clearer client Review rail—active layer without technical clutter

Why it matters for delivery

Clients reviewing progress or dual-sensor work should not have to reconstruct context from filenames. Layered orthos keep comparison inside the same mission handoff—closer to how the field work was actually flown.

Layer labels are derived for clarity; optional local rename helps operators tidy presentation in their own browser. Server-side rename and broader CRS coverage remain ongoing work—see the Looking ahead note in this journal.