WiGLE CSV Format v1.6


WiGLE has adopted a simple modified comma-separated-value (CSV) format for wireless network observation upload through it's client as well as for a data interchange format. This is simple, mostly-human-readable format that allows us to reliably accept data from multiple software packages. The WiGLE CSV format adheres to UTF-8 encoded rfc4180 for the most part, however we require a pre-header row containing client specification before the CSV-standard header definition. The pre-header is also rfc4180 escaped. Most full-featured CSV generators/parsers can be set to prepend/ignore this row by default.

Pre-header (Device and planetary location)

Description

[Format version],appRelease=[version],model=[device model],release=[device release],device=[device name],display=[device display characteristics],board=[device board descriptor],brand=[device brand],star=[system star],body=[orbiting body index],subBody=[orbit index of sub-body]

Example

WigleWifi-1.6,appRelease=2.78,model=X-37B,release=11.0.0,device=felgercarb,display=OPSPLS1.76-1-S,board=snodgrass,"brand=Moog, LLC",star=Sol,body=4,subBody=0

Details

Field Name Description Example
Format version Current format - treat this as fixed for the version you've selected to implement WigleWifi-1.6
appRelease The current release of the application creating this CSV 2.53
model The device model measuring these signals X-37B
release The device OS version 11.0.0
device The device name/codename felgercarb
display The device display if present OPSPLS1.76-1-S
board The device core circuit board/processor version snodgrass
brand The device brand Moog, LLC
star The star around which these points were observed Sol(only ""Sol is supported)
body The body's orbit index about the star 4 (Sol 4,0 is Mars)
subBody The the satellite orbit index applicable, otherwise 0 1 (Sol 3,1 is the Earth's moon)

NOTE: While we're aware that star,body,subBody notation in the header prevents multiple bodies/subbodies per file, current positioning technology and travel speeds make this a reasonable assumption. We may revisit this in subsequent revisions.

Header

Description/Example

MAC,SSID,AuthMode,FirstSeen,Channel,Frequency,RSSI,CurrentLatitude,CurrentLongitude,AltitudeMeters,AccuracyMeters,RCOIs,MfgrId,Type

The header is a fixed ordered set describing the columns following. It is somewhat overloaded to accommodate cell (both CDMA and GSM variants) and Bluetooth, but has been maintained for purposes of backward compatibility.

WiFi Rows

Description

[BSSID],[SSID],[Capabilities],[First timestamp seen],[Channel],[Frequency],[RSSI],[Latitude],[Longitude],[Altitude],[Accuracy],[RCOIs],[MfgrId],[Type]

Example

1a:9f:ee:5c:71:c6,Scampoodle,[WPA2-EAP-CCMP][ESS],2018-08-01 13:08:27,161,5805,-43,37.76578028,-123.45919439,67,3.2160000801086426,5A03BA0000 BAA2D00000 BAA2D02000,,WIFI

Details

Field Name Description Example
BSSID Basic Service Set Identifier - hardware address 1a:9f:ee:5c:71:c6
SSID Service Set Identifier - the access point name Scampoodle
Capabilities Capabilities array as specified by package. Based on Android capabilities sets. [WPA2-EAP-CCMP][ESS]
First timestamp seen First timestamp seen in SQL seconds-precision time format (YYYY-MM-DD hh:mm:ss), assumes UTC 2018-08-01 13:08:27
Channel Integer channel value for the observed signal 161
Frequency Integer center frequency value in MHz for the observed signal 5805
RSSI Received Signal Strength Indicator (RSSI) as reported by the radio -43
Latitude Observed latitude in decimal (degrees.decimal degrees) format 37.76578028
Longitude Observed longitude in decimal (degrees.decimal degrees) format -123.45919439
Altitude Estimated position altitude in integer meters 67
Accuracy Estimated position accuracy in decimal meters 3.2160000801086426
RCOIs Roaming Consortium Organizational Identifiers, space delimited 5A03BA0000 BAA2D00000 BAA2D02000
MfgrId (left blank) (left blank)
Type The device type - always WIFI for WiFi networks currently WIFI

Cell Rows

Description

[Cell Key],[Network Name],[Capabilities],[First timestamp seen],[Channel],[Frequency],[RSSI],[Latitude],[Longitude],[Altitude],[Accuracy],[RCOIs],[MfgrId],[Type]

Example

310410_56967_4118917,AT&T Mobility,WCDMA;310410,2018-08-03 18:14:15,,4385,-81,37.72090053,-122.44579219,104,34.30400085449219,,,WCDMA

Details

Field Name Description Example
Cell Key Composite Identifier - depends on network type:
For CDMA:[System]_[Network]_[Base Station]
For GSM:[Operator*]_[LAC]_[Cell ID]
For WCDMA:[Operator*]_[LAC]_[Cell ID]
For LTE:[Operator*]_[LAC]_[Cell ID]
For NR:[Operator*]_[LAC]_[Cell ID]


*Operator: for GSM-derived networks this is MCCMNCconcatenated to a 6 digit format. MCC and MNC are searchable through the WiGLE API via the https://api.wigle.net/api/v2/cell/mccMnc endpoint. 		310410_56967_4118917
Network Name For GSM/WCDMA/LTE/NR: reported MCCMNC lookup value if available, otherwise reported network name from radio/SIM. For CDMA: reported network name from radio. AT&T Mobility
Capabilities For GSM/WCDMA/LTE/NR: Network type + ; + MCC+MNC (operator value)
For CDMA: Network type + ; + System		 WCDMA;310410
First timestamp seen First timestamp seen in SQL seconds-precision time format (YYYY-MM-DD hh:mm:ss), assumes UTC 2018-08-01 13:08:27
Channel (left blank) (left blank)
Frequency Integer center frequency value depending on network type:
For CDMA:0
For GSM:Observed ARFCN
For WCDMA:Observed UARFCN
For LTE:Observed EARFCN
For NR:Observed NRARFCN
 4385
RSSI Received Signal Strength Indicator (RSSI) as reported by the radio -81
Latitude Observed latitude in decimal (degrees.decimal degrees) format 37.72090053
Longitude Observed longitude in decimal (degrees.decimal degrees) format -122.44579219
Altitude Estimated position altitude in integer meters 104
Accuracy Estimated position accuracy in decimal meters 34.30400085449219
RCOIs (left blank) (left blank)
MfgrId (left blank) (left blank)
Type The device type - always one of CDMA, WCDMA, GSM, LTE, or NR. WCDMA

Bluetooth Rows

Description

[BD_ADDR],[Device Name],[Capabilities],[First timestamp seen],[Channel],[Frequency],[RSSI],[Latitude],[Longitude],[Altitude],[Accuracy],[RCOIs],[MfgrId],[Type]

Example

63:56:ac:c4:d4:30,,Misc [LE],2018-08-03 18:14:12,0,,-67,37.76090571,-122.44877987,104,49.3120002746582,,72,BLE

Details

Field Name Description Example
BD_ADDR Bluetooth Device Address - hardware address 1a:9f:ee:5c:71:c6
Device Name The published name of the Bluetooth device if available Jabra Headset
Capabilities List; includes the device type list if provided, and optionally [BT] or [BLE] enclosed in square brackets to describe the first scan type detecting the device. Misc [LE]
First timestamp seen First timestamp seen in SQL seconds-precision time format (YYYY-MM-DD hh:mm:ss), assumes UTC 2018-08-01 13:08:27
Channel 0 for Bluetooth devices 0
Frequency Bluetooth "Device Type" code 7936
RSSI Received Signal Strength Indicator (RSSI) as reported by the radio -67
Latitude Observed latitude in decimal (degrees.decimal degrees) format 37.73090571
Longitude Observed longitude in decimal (degrees.decimal degrees) format -122.42877987
Altitude Estimated position altitude in integer meters 104
Accuracy Estimated position accuracy in decimal meters 49.3120002746582
RCOIs (left blank) (left blank)
MfgrId The Bluetooth Manufacturer ID, if available. Otherwise blank. 72
Type The device type - always BT or BLE for Bluetooth or BTLE devices respectively BLE