Import wardriving data (Wigle CSV, Kismet exports)

[dougborg]

Idea

Allow users to import wardriving session data from Wigle CSV exports and Kismet exports. Filter imported data through the surveillance device OUI/SSID watchlist to surface camera-related networks and add them to DeFlock's detection database.

This issue is a proposal/placeholder to gather community feedback, ideas, and suggestions — not a prescriptive spec.

Why

Many users already do wardriving with tools like the Wigle app or Kismet. Rather than requiring them to use DeFlock-specific hardware, let them import their existing session data. This makes DeFlock immediately useful for anyone who already wardrive — they can retroactively find surveillance cameras in data they've already collected.

How it might work

1. User exports their wardriving session from Wigle app or Kismet
2. Shares/opens the file with DeFlock (Android share intent / iOS share sheet, or file picker)
3. App parses the file, filters through OUI/SSID watchlist
4. Matching devices are added to rf_devices/rf_sightings tables
5. Non-matching devices are discarded (or optionally kept for manual review)

Formats to support

• Wigle CSV — UTF-8, RFC4180 format with a pre-header row containing metadata
• Kismet CSV — exported via kismet_log_to_csv from .kismet database files
• Kismet JSON — device export format

Considerations

• Large files — wardriving sessions can contain tens of thousands of networks. Need a streaming parser, not load-everything-into-memory
• GPS accuracy — wardriving GPS accuracy varies; could show a confidence radius on imported detections
• Export support — could also support exporting DeFlock RF data to Wigle CSV/Kismet formats for interoperability
• Duplicate detection — need to handle re-importing the same session or overlapping sessions gracefully
• Progress UI — large imports should show a progress indicator

Open Questions

• Should we keep non-matching devices for optional manual review, or discard immediately?
• What's the UX for triggering an import — file picker, share intent, both?
• Should we support Wigle's KML/KMZ exports as well?
• Is there demand for exporting DeFlock data to these formats?

Effort Estimate

Medium

Dependencies

• Curated surveillance device OUI + SSID watchlist (the watchlist issue)

Related

• PR Add FlockSquawk scanner integration (USB + BLE) #37 — FlockSquawk scanner integration (rf_devices/rf_sightings data model)
• Part of the Wardriving & Surveillance Detection epic