Repository navigation
Ops Aerial Photo
MowDeck can lay an aerial photo under the mower map, so areas, no-go zones, the mower's track and the heat layers (coverage, RTK, WLAN, mobile) are seen on the real garden. It is off by default: nothing is requested from any third party until you configure a source. Design and reasons: ADR 0054.
Telemetry fetches the photo tiles itself and serves them to signed-in users at GET /api/v1/telemetry/mowers/{id}/aerial/{z}/{x}/{y}:
- only for users who may see that mower, and only for tiles around that mower's map (its outline plus 60 m); anything else is a 404, so the route is no open proxy,
- each tile is requested once from the source and cached on the
aerial-cachevolume (30 days, 256 MB by default, oldest deleted first), - new tiles are limited to 240 per minute and account,
- browsers never contact the source, so the web app's content security policy does not change.
The source learns your server's address and the tile coordinates around your garden, not who uses MowDeck.
While a theft tracking session exists, the same source also serves the "Luftbild" layer of the tracking map, around the tracked positions instead of the garden (2 km margin), for the owner and for a share link; see Theft tracking, base map.
Open data under CC BY 4.0, no registration, terms of use. In infra/compose/.env:
AERIAL_WMS_URL=https://geoservices.bayern.de/od/wms/dop/v1/dop40
AERIAL_WMS_LAYER=by_dop40c
AERIAL_IMAGE_FORMAT=image/jpeg
AERIAL_ATTRIBUTION=© Bayerische Vermessungsverwaltung – www.geodaten.bayern.de (CC BY 4.0)
AERIAL_MAX_ZOOM=19
then docker compose up -d telemetry. by_dop40g is the grey-scale layer. The photo is a tile mosaic of the service's image, scaled; the credit line below the map is the attribution the licence asks for and must stay. Other German states publish similar open orthophoto WMS; any WMS that answers GetMap in EPSG:3857 works, or set AERIAL_XYZ_URL to a Web Mercator tile template (https://…/{z}/{x}/{y}.jpg) that your licence allows you to use this way.
All are variables of Telemetry (MOWDECK_TELEMETRY_AERIAL_*); Compose passes the first seven from .env (AERIAL_*), Helm from config.AERIAL_*.
| Compose / Helm | Telemetry variable | Default | Meaning |
|---|---|---|---|
AERIAL_WMS_URL |
…_WMS_URL |
empty (off) | WMS base URL (https) |
AERIAL_WMS_LAYER |
…_WMS_LAYER |
empty | layer name |
AERIAL_IMAGE_FORMAT |
…_IMAGE_FORMAT |
image/jpeg |
image/jpeg or image/png
|
AERIAL_XYZ_URL |
…_XYZ_URL |
empty | XYZ template instead of the WMS |
AERIAL_ATTRIBUTION |
…_ATTRIBUTION |
empty | credit line shown on the map |
AERIAL_MAX_ZOOM |
…_MAX_ZOOM |
19 |
deepest level with detail; deeper zooms scale it |
AERIAL_CACHE_MAX_MB |
…_CACHE_MAX_MB |
256 |
cache size limit |
…_WMS_VERSION |
1.3.0 |
1.3.0 or 1.1.1
|
|
…_MIN_ZOOM |
14 |
lowest level served | |
…_TILE_SIZE |
256 |
pixels per WMS request | |
…_MARGIN_METERS |
60 |
tiles are served this far around the map | |
…_CACHE_TTL_DAYS |
30 |
a cached tile is fetched again after this | |
…_MISSES_PER_MINUTE |
240 |
new tiles per account and minute | |
…_TIMEOUT_SECONDS |
10 |
timeout per source request | |
…_CACHE_DIR |
/var/cache/mowdeck/aerial |
cache directory (a volume) |
Telemetry logs aerial photo layer on at startup when a source is set.
-
GET /api/v1/telemetry/mowers/{id}/aerial(with a token) answersenabled: truewith the credit line and the box where tiles are served. - No toggle "Luftbild" in the app means the source is not configured (or the mower has no map yet).
- A blank grey area on the map at high zoom is the source having no image there (outside its coverage).
Mirrored from docs/ops/aerial-photo.md at commit b52cccfea2503c98301131b99958abd10233e00a. Edit the file in the repository, not this wiki page.
Mirrored from the docs/ directory at commit b52cccfea2503c98301131b99958abd10233e00a. Edit the files in the repository, not this wiki.
MowDeck documentation
- Home
- Phases
- Architecture
-
Decisions (ADR)
- Architecture decisions
- ADR 0001: OpenFGA instead of self-built authorization
- ADR 0002: Self-built Identity service in FastAPI instead of Keycloak or Zitadel
- ADR 0003: SvelteKit for the web app
- ADR 0004: Monorepo with a uv workspace
- ADR 0005: AGPL-3.0 for services and apps, Apache-2.0 for libraries
- ADR 0006: PostgreSQL for all persistence, no SQLite
- ADR 0007: NATS JetStream as event bus
- ADR 0008: Traefik as gateway
- ADR 0009: Command and event envelopes, subject naming and de-duplication
- ADR 0010: Python 3.13 for all services and libraries
- ADR 0011: Separate GPL-3.0 package for the PyMammotion adapter
- ADR 0012: Mower control interface and safety rules
- ADR 0013: Device-Gateway registry, sharding and per-mower concurrency
- ADR 0014: Authorization model, tuple ownership and the mowdeck-authz client
- ADR 0015: Tokens, sessions and key rotation
- ADR 0016: Fleet commands and authorization per command kind
- ADR 0017: Telemetry storage and retention
- ADR 0018: Realtime WebSocket protocol
- ADR 0019: Mammotion adapter transports, manual drive and secrets
- ADR 0020: Web app architecture
- ADR 0021: Browser authentication flow
- ADR 0022: Notifications: rules, recipients and delivery
- ADR 0023: Map rendering and projection
- ADR 0024: Scheduler: recurrence, rain pause and command issuing
- ADR 0025: Home Assistant integration as a pure API client
- ADR 0026: Manual drive channel over the Realtime WebSocket
- ADR 0027: Health history and theft alarm
- ADR 0028: Entitlements: plans as data and enforcement
- ADR 0029: Helm chart and release pipeline
- ADR 0030: Mowing patterns as plug-ins and the Planner
- ADR 0031: Billing with a Stripe adapter
- ADR 0032: Live camera over Agora, joined directly by the browser
- ADR 0033: Vision-assisted recovery with human approval
- ADR 0034: Linked cloud accounts and device discovery
- ADR 0035: Server-side camera frames and automatic AI analysis on errors
- ADR 0036: Native app shells with Capacitor, loading the web app from the server
- ADR 0037: Camera panorama calibration in the browser, with the AI supplying points only
- ADR 0038: Dual link per mower and firmware updates
- ADR 0039: Spot mowing by MowDeck-driven paths
- ADR 0040: Link heartbeat for online status
- ADR 0041: Spot runs from the dock: undock, transit and return
- ADR 0042: Drive calibration
- ADR 0043: Turn styles
- ADR 0044: Drive view with camera
- ADR 0045: Camera relay
- ADR 0046: Device settings as capabilities
- ADR 0047: The RTK base station as a Fleet device
- ADR 0048: Maintenance commands
- ADR 0049: Manual driving over the Mammotion cloud
- ADR 0050: Passkeys and the app login hand-off
- ADR 0051: Sign in with GitHub
- ADR 0052: Sign in with Apple
- ADR 0053: Retention and downsampling of the position track
- ADR 0054: Aerial photo under the mower map
- ADR 0055: Deploy maintenance window
- ADR 0056: Camera photo in push notifications for errors and theft alarms
- ADR 0057: Step-up re-authentication for critical actions
- ADR 0058: Theft tracking mode
- ADR 0059: iOS widgets and the mowing Live Activity
- ADR 0060: Apple Watch app
- ADR 0061: Mowing angle rotation
- ADR 0062: Setup tour for new users
- ADR 0063: Matter server (mowers in Apple Home and Google Home)
- ADR 0064: Personal access tokens and the public API documentation
- ADR 0065: Security center and new-login alerts
- ADR 0066: Cloud provider plugins and adapters for more vendors
- ADR 0067: Error code lexicon, provider independent
- ADR 0068: Public demo mode
- ADR 0071: Capability matrix generated from the adapters
-
Development
- Getting started
- Service template
- Shared libraries
- Cloud providers: adding a vendor
- Adding an error lexicon for a vendor
- Design: identity and authorization
- Design: fleet, telemetry, realtime
- Design: web app
- Web app
- Home Assistant integration
- Camera source bridge protocol
- Fuzzing and property-based tests
- GitHub wiki mirror
-
Operations
- Operating the Compose stack
- Operating MowDeck on Kubernetes (Helm)
- Building the Bluetooth bridge (ESPHome on a XIAO ESP32-S3)
- Releases
- Vendor library updates
- Billing operations
- Telemetry: retention and position downsampling
- iPhone and Android apps
- Passkeys
- Sign in with GitHub
- Aerial photo under the map
- Sign in with Apple
- Theft tracking mode
- Matter server
- Source code offer (AGPL-3.0 section 13)
- Public demo
- Spikes
-
Guides
- Guides
- ESP32 bridge: purchase and setup
- Signing in with a passkey
- Signing in with GitHub
- Error codes in plain words
- Aerial photo under the map
- Signing in with Apple
- Confirming critical actions
- Your security page
- iPhone widgets and the mowing Live Activity
- Apple Watch
- The setup tour
- Apple Home and Google Home (Matter)
- Worx Landroid, Kress and LandXcape mowers
- Scripting MowDeck
- Capability matrix
- API reference
- Original plan (German)