WiFiFoFum? File formats accepted by WiGLE?

[pejacoby]

I know the Post File page shows which file formats WiGLE accepts, but I can't find a concise reference to what each format looks like.

The reason I ask is that I've been using WiFiFoFum (http://www.wififofum.org/), which has a pure text csv format for it's log files. To wit:

WEP?,Type,SSID,MAC,Signal,Channel,First Seen,Last Seen,Lat,Long

Does this match anything useful such that I can upload my WFFF stumbles? I'm loathe to just toss a file up and tempt the wrath of the uberlords....

[uhtu]

the ueberlords are displeased with your belief in the existance of ueberlords.
er.

i've never heard of that before. go ahead and post one and let us know the transid and we'll have a look if they didn't work.

basicly if you can find a "wi-scan" or "wi-scan plus" export option, that should work.

[pejacoby]

File trans-id 20040702-00049

Status indicates it wasn't well liked

I did manage to find a NetStumbler wi-scan file so I can see the format a bit. Might try to massage the WFFF file, if this would please the uberlords.

The author of WFFF has been collecting suggestions and is indicating version 0.4 coming soon...I know 'compatible log formats' has been a request made by many folks.

[pejacoby]

Malcom is working on wi-scan format is the latest version of WiFiFoFum, but it doesn't appear to be quite right. I've sent up two files 20040806-00036 and 20040804-00016, but neither grok'ed well.

Any pointers on the best reference for the wi-scan format?

Or perhaps the ubergods can elucidate the error logs for these particular files?

[bobzilla]

There are '-' signs on the longitudes. wi-scan doesn't have a dash, it uses the N,E,S,W to indicate what hemesphere. A -92 should be west, IE: 'W 92.9561400'. Also note that wi-scan uses sexigesimal, not decimal lat/longs (which is a bit silly, but it's what we're stuck with). 'wi-scan with extensions' does not use sexigesimal, it uses regular decimal degrees, so you may want to use that as your export format instead.

[pejacoby]

Thanks Bobzilla, doing some manual tweakage on WFFF's wi-scan files creates readable content, I uploaded a bunch of files this evening with grand success. Converting the header to "wi-scan with extensions", fixing the Date line, and converting "E -92" into "W 92" was the magic.

[bobzilla]

Excellant, glad it's workin.

[brentw]

I am also using wfff and trying to upload files what is the proper format and what do I need to do exactly to get the files to upload properly. I don't have a problem editing them around just tell me how please. I have some 1500 + points gpsed and want to upload them.

[pejacoby]

The author of WFFF is aware of the format issues, and is working on improvements for the next version. Check out the forums on www.aspecto-software.com, maybe chime in with your yearnings for a compatible wiscan file

In the meantime, I built myself a spreadsheet that appeases the WiGLE.net uberlords and allows WiGLE to digest WFFF files

Drop me a private note with your email address and I'll send it to you.

[stavr0]

1. Find a binary of GNU awk for your platform: ( for Windows http://unxutils.sourceforge.net )

2.Save this to fixwis.awk:

Code: Select all

BEGIN { RS = "\n" FS = "\t" OFS=FS } # Fix minutes instead of months in header (configured with 'gawk -v month=mm ...' ) $1 ~ /^# \$DateGMT\:/ { if (month>0) { $0 = substr($0,1,15) substr(100+month,2) substr($0,18) } } # Fix NE/SW negative coordinates problem { sub(/N -/,"S ",$1) # fix southern hemi sub(/E -/,"W ",$2) # fix western hemi print }

3. massage broken WIS file:

Code: Select all

gawk -v month={month number} -f fixwis.awk < bad.wis > good.wis

4. Upload to WIGLE

5. Überlords appeased.

The date problem can be fixed once and for all by editing the WIFIFOFUM.EXE find hex string
00 79 00 79 00 2D 00 6D 00 6D 00 2D 00 64 00 64
and replace with
00 79 00 79 00 2D 00 4D 00 4D 00 2D 00 64 00 64
Unicode yy-mm-dd -> yy-MM-dd

Last edited by stavr0 on Tue Feb 15, 2005 2:24 pm, edited 3 times in total.

[stavr0]

This one converts the WiFiFoFum TXT format into KISMET CSV which has more information than the WIS (channel, proper first and last seen date)

Run with

Code: Select all

gawk -f txt2csv.awk {wififofum.txt}

Save as txt2csv.awk

Code: Select all

BEGIN { RS = "\n" FS = "," OFS=";" # or , ? ORS = "\n" # wfff .txt is # $1 $2 $3 $4 $5 $6 $7 $8 $9 $10 # wep,nettype,ssid,bssid,signal,channel,firstseen,lastseen,latitude,longitude # WEP,Infrastructure,edetc,00:00:00:00:00:00,-30,10,05-02-09 17:15:33,05-02-09 17:19:45,45.123456,-45.123456 # kismet .csv # 1,infrastructure,wmaaa2123,00:10:E7:F5:54:E9,None,01,11.0,Yes,218,0,0,0,218,Thu Oct 31 12:14:13 2002,Thu Oct 31 13:01:30 2002,0,56,49,44.105885,-70.226585,171.929993,0.000000,44.105953,-70.226524,251.459991,0.000000,,,,,,, }#### FNR==1 { fout = FILENAME sub(/\.[Tt][Xx][Tt]$/,"",fout) fout = fout ".csv" print "Converting WFFF \"" FILENAME "\" to Kismet \"" fout "\"" network = 0 print "Network","NetType","ESSID","BSSID","Info","Channel","Maxrate","WEP","LLC","Data","Crypt","Weak","Total","First","Last","BestQuality","BestSignal","BestNoise","GPSMinLat","GPSMinLon","GPSMinAlt","GPSMinSpd","GPSMaxLat","GPSMaxLon","GPSMaxAlt","GPSMaxSpd","DHCP","ARP","UDP","TCP","" > fout }#### $9+0!=0 || $10+0!=0 { network++ First = "20" $7 Last = "20 "$8 # Network,NetType,ESSID,BSSID,Info, Channel,Maxrate,WEP, LLC,Data,Crypt,Weak,Total,First, Last, BestQuality,BestSignal, BestNoise,GPSMinLat,GPSMinLon,GPSMinAlt,GPSMinSpd,GPSMaxLat,GPSMaxLon,GPSMaxAlt,GPSMaxSpd,DHCP,ARP,UDP,TCP, print network,$2, $3, $4, "None",$6, 0, ($1=="None")?"No":"Yes", 1, 0, 0, 0, 1, First, Last, 0, ($5>0)?$5:-$5, 0, $9, $10, 0, 0, $9, $10, 0, 0, "", "", "", "", "", "", "" >> fout }#### $9+0==0 && $10+0==0 { print "Dropped zero coordinates for " $3 }

Last edited by stavr0 on Fri Feb 18, 2005 1:52 pm, edited 1 time in total.

[pejacoby]

stavr0, that's awesome, thanks for the converter. You should post this over on the aspecto-software forums for Malcolm to see.

[bobzilla]

most impressive