Open pejacoby opened 12 months ago
Documented in #1 as well..
the /%s/
in the save line has trouble with punctuation and spaces.
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.
Also in ObservationUploader, they do nothing fancier that replacing a comma in an SSID with an "_".
This can be closed, was fixed in a previous release
Sanitized correctly: https://github.com/LyndLabs/Wardriver/blob/d6592d9f79394e645411a025fd570676b35ef299/src/Wardriver/src/Wardriver.cpp#L207
Encountered a glitch in the CSV file output:
SSID: LG_Speaker_S80QY7934.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 "_"