Split out of #43, where it was the question mark on "Map Panel rework — 3D view?". Everything else
in that issue is built and driven; this is a rework of every overlay rather than a next step, so it
gets its own.
What it would be
Tilt the map plane so it reads like the reference terminals (John Deere G5, Trimble GFX-750):
horizon-ish view down the field rather than straight down. In Compose this is
graphicsLayer { rotationX; cameraDistance } on the raster.
Why it isn't done yet
The tilt is the easy part. Every overlay — field labels, POI dots, vehicle arrows, the guidance
course, the coverage raster and its live trail — has to go through the same perspective projection
or it visibly detaches from the map underneath. Text also rasterizes badly inside a tilted layer, so
labels and readouts probably have to be projected as positions and drawn upright, the way the
course-up work already does.
What #43 left in place for it
MapProjection is now the single thing every overlay is projected through (toScreen / toNorm,
plus the rotation and pivot course-up added). That is exactly the seam a perspective transform would
go behind — which is the reason to do this after #43 rather than during it.
Course-up is worth judging against, not just north-up: the part of the reference photos that reads
as guidance — the map turning with the machine, the lightbar, coverage painted behind — is already
on screen. The open question is how much the tilt adds on top of that, and whether it survives
contact with a small tile on a grid page.
Worth deciding first
- Does the tilt earn its place at all once course-up and coverage are being driven? Judge it in the
seat before committing to the overlay work.
- If yes: a runtime toggle like course-up (a mode you flip while driving), or widget config?
- What happens to the overlays that cannot be perspective-projected sensibly — the ground-layer
legend, the field-info popup, the section strip. Probably screen-space chrome that never tilts.
Split out of #43, where it was the question mark on "Map Panel rework — 3D view?". Everything else
in that issue is built and driven; this is a rework of every overlay rather than a next step, so it
gets its own.
What it would be
Tilt the map plane so it reads like the reference terminals (John Deere G5, Trimble GFX-750):
horizon-ish view down the field rather than straight down. In Compose this is
graphicsLayer { rotationX; cameraDistance }on the raster.Why it isn't done yet
The tilt is the easy part. Every overlay — field labels, POI dots, vehicle arrows, the guidance
course, the coverage raster and its live trail — has to go through the same perspective projection
or it visibly detaches from the map underneath. Text also rasterizes badly inside a tilted layer, so
labels and readouts probably have to be projected as positions and drawn upright, the way the
course-up work already does.
What #43 left in place for it
MapProjectionis now the single thing every overlay is projected through (toScreen/toNorm,plus the rotation and pivot course-up added). That is exactly the seam a perspective transform would
go behind — which is the reason to do this after #43 rather than during it.
Course-up is worth judging against, not just north-up: the part of the reference photos that reads
as guidance — the map turning with the machine, the lightbar, coverage painted behind — is already
on screen. The open question is how much the tilt adds on top of that, and whether it survives
contact with a small tile on a grid page.
Worth deciding first
seat before committing to the overlay work.
legend, the field-info popup, the section strip. Probably screen-space chrome that never tilts.