Contribute Power Lines to OpenStreetMap

…and help Gaggle improve low-level power-line warnings

Gaggle can play spoken power-line warnings when you are flying low and your projected path intersects a mapped line ahead. In the current implementation, the warning logic becomes relevant below 100 metres above ground, with a stronger critical threshold below 50 metres.

The better the underlying OpenStreetMap data is, the better these warnings work for pilots in that area.

How Your Edits Improve Safety in Gaggle

• Data source: Gaggle reads line data sourced from OpenStreetMap.
• In flight: Gaggle checks the path ahead against mapped line data when you are flying low.
• Warning levels: the current thresholds are based on metres above ground, not feet.
• Community impact: Each accurate line you add helps everyone who flies in your area.

Privacy & safety: Only map what you can see from public places or permitted imagery. Never trespass or approach electrical equipment.

What to Map (and the Tags You’ll Use)

Common line attributes (add only if you’re confident):
voltage=* (in volts, e.g. 110000, not “110 kV”), circuits=*, cables=*, operator=*

Before You Start

1. Create a free account at openstreetmap.org and click Edit (iD opens in your browser).
2. Use only permitted sources: built-in imagery layers in iD/JOSM (e.g., Bing/Esri/Maxar when available), your own ground survey, or openly-licensed local datasets that OSM allows.
3. Do not guess. If you don’t know the voltage/operator/design, leave it blank (your geometry is still incredibly valuable).

Quick Start: Map an Overhead Line in the iD Editor (Browser)

Step-by-step

1. Open iD where you want to map and pick a clear aerial imagery layer.
2. Add supports first
   • Click Point and place a node on each visible support.
   • Tag large ones as Power Tower (power=tower) and smaller ones as Power Pole (power=pole).
   • If you can tell, add material=* (wood/steel/concrete) and height=* (meters).
3. Draw the line between supports
   • Switch to Line, click your first support node, trace the span, and end on the next support.
   • Tag the way as Power Line (power=line) or Minor Power Line (power=minor_line) depending on size.
   • Add known attributes like voltage=* (in volts), circuits=*, cables=*, operator=*. Leave unknowns blank.
4. Transitions underground
   • If the line goes underground, split the line at the transition support and continue as power=cable + location=underground.
5. Avoid false connections
   • Let lines cross without a shared node unless they physically connect (e.g., inside a substation).
6. Save with a clear changeset comment
   • Example: “Added towers & 132 kV line from visible imagery/survey; split transitions; improved tagging.”

Advanced: Doing the Same in JOSM (Desktop)

1. Install JOSM and add the area/imagery you need.
2. Use presets: Power → Line / Tower / Pole / Substation for consistent tagging.
3. Split long lines at supports so each span can carry accurate attributes (voltage, circuits, design changes).
4. Run the JOSM Validator before uploading to catch geometry/tagging issues.
5. Upload with a descriptive changeset comment.

Tagging Cheat-Sheet (Copy/Paste Friendly)

# Lines (use one)
power=line                 # overhead transmission/distribution
power=minor_line           # smaller local distribution
power=cable                # underground/underwater segment

# Line attributes (add only when known)
voltage=110000             # in VOLTS, not "kV"
circuits=2                 # number of independent circuits
cables=3                   # number of physical conductors
operator=Your_Utility_Name

# Supports
power=tower                # large pylon (lattice/tubular)
power=pole                 # smaller support
material=steel|wood|concrete
height=25                  # meters (if you can estimate confidently)

# Substation (optional)
power=substation
substation=transmission|distribution|transition|traction

# Communication
communication=line         # telecom/telephone overhead lines
location=overhead         # for overhead lines

Quality Assurance (QA) — 5 Minutes Well Spent

• Check alignment: Towers/poles sit precisely under spans; lines don’t snake off imagery edges.
• No accidental joins: Only connect lines where they truly connect; remove stray shared nodes at crossings.
• Tag sanity: voltage values are numeric volts (110000), not “110 kV”; unknowns are left blank.
• Split for changes: If voltage/circuits/design changes, split the way at that support and update tags per segment.
• Avoid mis-tags: Do not use power=cable for overhead wires; use power=line/power=minor_line.
• A second look tomorrow: A fresh pass catches 90% of tiny geometry mistakes.

Optional Tools (Helpful, Not Required)

• Overpass Turbo (query the area to see what’s already mapped):

  [out:json][timeout:120];
  (
  // Overhead power lines (used in Gaggle)
  way["power"~"^(line|minor_line)$"]({{bbox}});
  
  // Underground/underwater power cables
  way["power"="cable"]({{bbox}});
  
  // Communication/telecom lines
  way["communication"="line"]({{bbox}});
  
  // Relations for complex power line groupings
  rel["power"~"^(line|minor_line)$"]({{bbox}})->.rels;
  way(r.rels);
  );
  out tags geom;

• Mapillary / KartaView (street-level imagery you or the community captured) to verify pole materials, labels, etc.

Common Pitfalls (and How to Avoid Them)

• Guessing voltage/operator: If you’re not certain, leave it blank. Geometry alone is extremely valuable for alerts.
• Connecting everything: Crossings are not connections; don’t share nodes unless the hardware connects.
• Using unpermitted sources: Only trace from imagery provided in iD/JOSM or from your own survey content that you’re allowed to share.
• Using power=cable for overhead: Don’t. Keep power=cable for underground/underwater; use power=line/power=minor_line for overhead.
• Confusing telecom with power: communication=line is not a power feature and won’t trigger Gaggle alerts.

When Will I See My Edits in Gaggle?

Gaggle uses refreshed map data rather than updating instantly from your edit session. Once your change is live in OpenStreetMap, it can appear in a later Gaggle data refresh.

Frequently Asked Questions

I mapped lines but didn’t get an alert in flight.

Alerts trigger when both conditions are true:

1. You are flying within the low-altitude warning thresholds used by the app, and
2. Your projected path intersects a mapped line ahead.
   If you’re higher, parallel but not intersecting, or the line is still missing/inaccurate, you won’t get an alert.

Should I tag voltage if I’m unsure?

No. Never guess. Leave it blank or add a note for future verification. The line geometry still improves safety.

Do I need to map every single pole?

Map supports that are visible. Towers/poles at reasonable spacing help others verify and maintain the line, and they improve quality checks.

Can I import my city’s utility data?

Possibly — but imports require discussion, licensing checks, and coordination with the OSM community. If you’re considering this, reach out first.

Safety & Responsibility Disclaimer

Gaggle’s Power Line Alerts are an aid to situational awareness, not a primary means of obstacle detection. Data quality varies by region and source. You are solely responsible for safe flight operations, see-and-avoid, and adherence to regulations. Always maintain appropriate clearances from obstacles and power lines.

Quick Checklist (Print Me)

• Supports mapped (power=tower / power=pole)
• Lines drawn and tagged (power=line / power=minor_line)
• Underground segments split & tagged (power=cable + location=underground)
• No accidental connections at crossings
• Optional: substation outlines, transformers if clearly known
• Clear changeset comment

Thank You ❤️

Every span you add makes Gaggle safer for you and your fellow pilots. If you improve a popular local route, let your community know — they’ll feel the difference on their very next flight.