Proper csv file output?

[RajunCajun]

I have been looking all over to find out what is correct way a .csv file should look for a correct submission.

The output my file shows now is:
MAC Address SSID Channel Signal WEP LAT LON

LAT and LON show up as for Ex. 3218.4369 N 09353.1464 W


I am using a OnCourse BT-339 that has protocal output of:
NMEA 0183 protocol, and supports command:
GGA, GSA, GSV, RMC ( VTG and GLL are optional)

The file I just uploaded transaction ID is 20070407-00030 showed 100% completion but did not add anything.

[Dutch]

I have been looking all over to find out what is correct way a .csv file should look for a correct submission.

The output my file shows now is:
MAC Address SSID Channel Signal WEP LAT LON

LAT and LON show up as for Ex. 3218.4369 N 09353.1464 W


I am using a OnCourse BT-339 that has protocal output of:
NMEA 0183 protocol, and supports command:
GGA, GSA, GSV, RMC ( VTG and GLL are optional)

The file I just uploaded transaction ID is 20070407-00030 showed 100% completion but did not add anything.

Wigle doesn't support generic csv formatted files.
Wigle supports Kismet's logfiles, including the csv version.
Delimiter is not a comma, but a semicolon.
The header for Kismet csv files are :
Network;NetType;ESSID;BSSID;Info;Channel;Cloaked;Encryption;Decrypted;MaxRate;MaxSeenRate;Beacon;LLC;Data;Crypt;Weak;Total;Carrier;Encoding;FirstTime;LastTime;BestQuality;BestSignal;BestNoise;GPSMinLat;GPSMinLon;GPSMinAlt;GPSMinSpd;GPSMaxLat;GPSMaxLon;GPSMaxAlt;GPSMaxSpd;GPSBestLat;GPSBestLon;GPSBestAlt;DataSize;IPType;IP;

Dutch

[RajunCajun]

Thanks.