Quote:
|
Originally Posted by Dutch
If ksngem parses the .gps file for any BSSID's there, then the CSV and .XML for any missing BSSID's before outputting the new .csv file, you should have them all.
Dutch
|
Yep it does
Knsgem parses both of these fields into the master data base from gps file.
bssid="00:11:95:4C:3F:73" source="00:11:95:4C:3F:73"
The area of concern is when its producing the output kml files for GE, which is the same time its producing the Wigle CSV files. I have several filters that keep "0" lat/long or bogus gps data from being written to KML. I just want to make sure the filter isn't interfering with the Wigle CSV output.
Is supposed to write all nets detected to CSV and only nets with good gps data to kml.