You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SSID: LG_Speaker_S80QY_7934.l078_ (as captured by WiGle WiFi - they replace commas with _)
CSV output line -- note the comma in the SSID name has be included in the output. This leaves the "AuthMode" for this entry blank, and pushes the "[ESS]" value into "FirstSeen" column, and all subsequent fields only column to the right.
This has also been observed with the SSID "Bill Wi, The Science Fi" and similar naming where there is a comma at a word boundary. In Wigle-land, the comma is replaced by an underscore "_"
The text was updated successfully, but these errors were encountered:
Thanks for the pointer to #1 The pattern definitely holds, curious with the commonality to various "home speaker" SSIDs that have odd trailing characters.
Check out the code for the WigleWiFi app for a possible approach - this addresses various things that shouldn't be in a KML file.
Encountered a glitch in the CSV file output:
SSID: LG_Speaker_S80QY_7934.l078_ (as captured by WiGle WiFi - they replace commas with _)
CSV output line -- note the comma in the SSID name has be included in the output. This leaves the "AuthMode" for this entry blank, and pushes the "[ESS]" value into "FirstSeen" column, and all subsequent fields only column to the right.
FA:8F:CA:5D:71:B9,LG_Speaker_S80QY_7934.l078,,[ESS],2023-10-01 22:48:54,1,-91,44.885960,-92.903198,295,0.970000,WIFI
Here is the full output from a Wigle KML file export for comparison. Wigle replaces the comma with an underscore "_" to avoid the issue.
This has also been observed with the SSID "Bill Wi, The Science Fi" and similar naming where there is a comma at a word boundary. In Wigle-land, the comma is replaced by an underscore "_"
The text was updated successfully, but these errors were encountered: