So I stumbled (cough) around to a solution, and here are some details for anyone else who bumps into this.įirst, extract the gps trace-related fields from the Wigle csv file altitude is probably not necessary, but included anyway: It's apparently getting the 981.533 invalid longitude from numbers 98132 appended at the end of one of the SSIDs in the file (my guess). Realtime tracking (-T) is not suppored by this input type. XCSV attempt to read WigleWifi_20171231160828-excerpt.csv as a track or route, but this format only supports waypoints on read. I've got gpsbabel and a cornucopia of other gps, gpx, and openstreetmap related programs available on Debian Linux, but haven't yet, cough, stumbled onto a correct way of converting WigleWifi.csv files from the android client, into gpx files, using gpsbabel. Reconstruct the roads and other objects you visited from your tracks and/or upload them to the OSM projectpage. The best way (in my opinion -KH): convert the track to a gpx file, and import that file in 'josm', the java openstreetmap editor. If you're mapping wireless networks, you might consider mapping your routes and posting them to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |