Wiglecsv
Wigle is a community for wardriving and mapping WiFi networks.
Kismet log files (kismetdb) can be converted to the Wigle CSV format, but Kismet can also directly log to the Wigle format with the wiglecsv log.
Wigle does not collect packet contents, so a wiglecsv log does not contain packets - it is a simplified CSV text file of WiFi Access Points and Bluetooth devices, and their locations. If you want to save packet contents, be sure to also turn on kismet or pcapng logs!
After 2026-10-R1, both the wiglecsv log and kismetdb_to_wiglecsv write Bluetooth LE devices seen by sniffers (nRF, TI, Ubertooth), and those from Bluetooth scan reports with a BTLE type such as BTLE Tracker or BTLE Device, as BLE, with only Wi-Fi written as WIFI, and Bluetooth rows in time order. Cell rows are written for GSM, WCDMA, LTE, and NR cells only, with the channel left blank as WiGLE expects; other phys, which WiGLE has no type for, are left out.
After 2026-10-R1, Wi-Fi networks an access point hosts in its multiple BSSID element (IE 71), which may never send beacons of their own, are written as WIFI rows too, with the SSID and encryption from the hosting access point’s beacon and its location. A hosted network which also sends its own beacons is written from those, as before.
After 2026-10-R1, the encryption column names WPA3 networks the way WiGLE expects: [WPA3-SAE-CCMP] for WPA3 personal, [WPA3-OWE-CCMP] for enhanced open, and [WPA3-EAP_SUITE_B_192-GCMP-256] for WPA3 enterprise suite B. A network in WPA3 transition mode, offering both, is written as [WPA2-PSK+SAE-CCMP], which WiGLE also counts as WPA3. Earlier versions wrote many of these as WPA2-UNKNOWN.
After 2026-10-R1, an SSID, Bluetooth name or cell operator name that begins with =, +, - or @ has that first character written as an octal escape (\075 for =), as commas and quotes already are, so a spreadsheet opening the file doesn’t read it as a formula. kismetdb_to_wiglecsv also skips records whose MAC address is malformed.
Since Wigle is designed for mapping wireless, Kismet will only create entries in the wiglecsv log when a GPS is connected and a location is available. If you have no GPS location, the wiglecsv will be empty.
Log type
log_types=wiglecsv
Kismet will automatically create a wiglecsv file while running. This can be combined with other log types like kismet and pcapng, but does not need to be. Remember you can’t recover packet data from a wiglecsv log, so if you want to process the packets later, be sure to log another format too!
Converting kismetdb to wiglecsv
The kismetdb log can be converted to Wigle format using the kismetdb_to_wiglecsv tool included as part of Kismet or in the kismet-logtools package.
The simplest way to convert a kismetdb log to a wiglecsv is to simply run the conversion tool:
kismetdb_to_wiglecsv --in some-kismet-log-file.kismet --out some-wigle-file.csv
Conversion options
Converting a kismetdb log can take a lot of space and time, because each packet is examined and the coordinates written to the CSV file. This can be sped up with various options to the kismetdb_to_wiglecsv tool:
--verbose
--skip-clean
kismetdb_to_wiglecsv performs a database cleanup and optimization stage (optimizing existing data, cleaning up stray journal files, etc). If you are running multiple passes on a file, or have already cleaned it using kismetdb_clean, you can save time by skipping this stage.--rate-limit={ limit-in-seconds }
By default, kismetdb_to_wiglecsv will only emit one record per second per access point. This prevents overloading the Wigle servers with insane quantities of data with no useful positional updates. If you find you are generating extremely large data sets, you can increase this time.
After 2026-10-R1, Wi-Fi rows are read in time order too, so a log from several sources keeps a record for every second a device was seen, instead of dropping the ones that were logged out of order.
--cache-limit={ number-of-devices }
kismetdb_to_wiglecsv will cache device information from the database to speed up looking up SSIDs and other device data. By default, the last 1000 devices are cached, but if you have a very large number of devices, or a very small amount of ram, increasing or decreasing this cache may speed up processing.--exclude={ lat,lon,distance }
distance meters of lat,lon, such as around your home. This option can be given more than once. After 2026-10-R1, exclusion zones apply to every record, Wi-Fi, Bluetooth and cell, and distances are measured correctly; earlier versions could write some records from inside a zone, and measured distances slightly too large.Uploading to Wigle
Once your log is converted, you can upload it to Wigle by creating an account there and choosing the file from your computer.