Feature request: simple “Reference Layer” (show KML/GeoJSON as overlay) + batch-import UX

bruna pelloia

Hi Dronelink team,

Context
I’m using Dronelink (Hobbyist Elite) with a DJI Mini 4 Pro (RC-N2 + Android). My goal is simple: while flying manually, see my live position on top of all past flight tracks (KML/GeoJSON) so I don’t re-cover the same area.

Pain points

  • The Create → Import flow tries to convert each KML LineString into a mission (Waypoints/Map). With multiple lines and many vertices the UI can freeze, even if I just need a visual overlay.

  • Changing “Import As” from Waypoints to Map for every single line is slow (no “apply to all”).

  • The path that actually works—Plan → +Add → Map → Advanced → Features → Upload—is not obvious/discoverable.

  • GeoJSON is rejected by Import (even though it works fine as a Map/Features overlay).

  • Small UI details (e.g., seeing speed/RTH params in a plan used only as a reference map) create confusion when you’re not running missions.

What would solve it (minimal changes)

  1. One-click option: “Show KML/GeoJSON as Reference Layer (no mission)”.

    • Always treat the file as a passive overlay (no waypoint generation, no gridding).

  2. Batch choice: when a file has multiple items, allow “Set Import As = Map for all” (or “Reference Layer for all”).

  3. Safer defaults: if a KML/GeoJSON has >N vertices or multiple LineStrings, default to Map/Reference instead of Waypoints.

  4. Accept GeoJSON in Import (same as KML) or provide a visible link to “Import as Reference Layer”.

  5. Discoverability: a small tooltip/help link in Import and in Map pointing to “How to add a KML/GeoJSON as overlay only”.

  6. Quality-of-life: in a plan with only reference layers, optionally hide mission-only fields (RTH, speed, overlap) to reduce confusion.

Why this matters
This is a very common workflow for survey/inspection: a live breadcrumb over historical coverage. Google Earth loads the file instantly because it just draws it; Dronelink’s Import currently tries to convert it. A first-class “Reference Layer” would make this trivial, keep users inside Dronelink, and avoid UI stalls.

Happy to share a sample KML (14 LineStrings, ~1k simplified points) or screen captures if helpful. Thanks for considering!

Best, Bruna

2

Comments

2 comments

Date Votes
  • Comment author
    bruna pelloia

    UX detail: when importing KML only as a visual reference, users must manually raise “Merge points closer than” to ~8–10 m to avoid freezes. That behavior isn’t obvious.
    Suggestion: if the file has many vertices or multiple LineStrings, default the merge to ~10 m, or show a prompt: “Treat as Reference Layer and simplify to 5–10 m?” Also remember the last value per user.

    0
  • Comment author
    bruna pelloia

    Addendum: “Coverage Layer” (single-user) like the Aloft integration

    For my use case (single pilot), the perfect solution would be built-in:

    1. Coverage Layer per plan

      • A toggle: “Record breadcrumb to Coverage Layer while flying.”

      • During flight, append the live breadcrumb (1–5 s) to a server-side KML/GeoJSON tied to the plan.

      • Auto-simplify (~8–10 m), clampToGround, color by date/session.

    2. Always-on overlay

      • The Coverage Layer is shown by default in the plan (no mission generation).

      • One click Download / Replace if I want to manage it manually.

    3. Single-user friendly

      • No enterprise “Connections” needed: just my account.

      • Option to pause/resume and clear last session.

      • Remember last simplification value.

    4. (Optional) URL layer

      • Allow adding a public KML/GeoJSON URL (like a NetworkLink) with periodic refresh (2–5 s).

    This would replicate what I needed from the Aloft integration but inside Dronelink, making the “live over historical tracks” workflow trivial for single users as well.

    0

Please sign in to leave a comment.