oh, ok - that turns out to be really easy.

I'm going to include it using the action name: net.wigle.wigleandroid.END

just like with waze, it'll be that as the action name, and target will be: BroadcastReceiver

this will be in the next release.

not too familiar with Knoppix, but knowing your card chipset, checking knoppix support will be the first step!

I don't know that particular card, but this ID chart might help:



(via https://twitter.com/ve2lit/status/890843156509536257 )

no need to apologize - it's a good feature request. We'll start looking into it, post some options here!

Thanks for uploading! There are a lot of different ways to see the data through the site: 1.) on the general map: https://wigle.net/map you can scroll around a big graphical world with all the data and do some filtering. The individual points here don't have a ton of detail, because this is literall...

Find bobz or ark. Show us your WiGLE stats or give us a feature request, get a shirt. Know us by our lab coats. While supplies last. We'll also be at the wireless village WiGLE talk Saturday 16:00.

curious to know - whichever way you choose, please post your experiences!

is this in WiGLE WiFi Wardriving for Android? If so, "Run" is the number of networks you've seen since launch + scan. "New" is the number new to your local database (the app is designed to be self-contained) WiGLE's estimate of a network is updated with each uploaded observation,...

The issue with a public user ID token is that those can be mapped back to user name and location through correlation. it sounds to me like what you're interested in is the ratio between new:previously-seen over time; can you provide some use case information to help us think about creative solutions...

Because it could diminish user privacy, we decided to not publish this information. You can see how many networks a user has uploaded this month on the stats page (just click on the column headers for sorting), but we avoid presenting too much information that could be correlated with maps/searches ...

I've committed a first draft of full stream-parsed observation download as a candidate feature for 2.20. It's efficient enough that I can load my own observations on even more most limited testing devices. As always, feedback is greatly appreciated! https://github.com/wiglenet/wigle-wifi-wardriving/...

Well, that bumps a streaming import function up the priority list - thanks for letting us know!

Out of curiosity, if you access the SQLite file on a file system that supports large files, is the database intact?

Interesting - please do PM us the MAC address!

Some VFAT implementations apparently use an unsigned int, giving them a 4GB limit, but I can't find conclusive guides to this. We'll prioritize chunked handling of observation import; I've already done half of it here (streaming JSON parsing): https://github.com/wiglenet/wigle-wifi-wardriving/pull/1...

Hi Doc, Your query limit should have automatically updated since then - can you test and confirm? Re: KML: that output from that script is probably not compatible with the KML upload formats we do support - see the upload page for the list. The NetXML output should contain all the same data, so the ...