oh hell - hit us up with a transaction ID in PM to reproduce, we'll get to the bottom of it!

Cheers, and thanks for the bug report.

good catch - boneheaded mistake by yours truly - OKHttp (the square-maintained HTTP library we use for API stuff) upgraded to min-SDK 21 / android 5, which broke our backward compatibility. I've reverted the change here , it will be fixed in the next release. in the meantime, just keep stumbling, th...

not sure where you found that old URL, but the new API and documentation are available here:

https://api.wigle.net/

happy hacking!

-Ark and the WiGLE team

kismet now has a built in tool to export to WiGLE!

https://www.kismetwireless.net/docs/readme/wigle/

sorry to hear that; we've had a few isolated reports like this, but never anything reproducible on a more than individual scale. Some things that would help: 1. Android version(s) 2. location settings - how did you verify app access 3. Testing location/local 4. carrier 5. devices 6. your location Ob...

Cell tower location accuracy depends on measurements for each tower. They tend to be reliable (vs. WiFi, which can move and vary more easily). The "API" menu item under tools has the programmatic access for data. There is no CSV mode. The WiGLE WiFi Wardriving android app allows you to acc...

in the beta channel now!

That's a good question, but there's a lot of nuance beyond a simple percentage answer; it depends on the location, when it was covered, and by whom. We've avoided making blanket statistics about it because it's so equipment-sensitive and because it would require significant work to figure out how to...

a lot of items to respond to here, so I'll keep this short - some of these are probably threads in their own right! 1. the graph certainly suggests multi-path propagation error *or* an external pattern of interference. It might be worth running that same experiment on different channels, as well us ...

certainly not opposed to it - we're big fans of OSM! a few questions, since we're not in-the-know on the terminology: 1. We're certainly usable as a "signal" - but it's important to know that our designation of "free" or "pay net" is pretty arbitrary. Is that ok? 2. is ...

fix coming in the next release!

we don't log previously-reported locations for things - the set shifts with each new observation, it would be too hard to do... what you can do though is look at the observations for a network either via the Basic Search page (select the network to see the "outlines"), the Advanced Search ...

it happens server-side - but it's not complicated! 1. filter out suspicious/garbage data. Locations that don't exist, GPS accuracy that might as well not have coordinates at all, timestamps that indicate the GPS clock was hosed, devices that can't exist.... (AND MANY MORE) 2. take a simple geospatia...

Two quick answers: - The convex hull algorithm is performed on your machine, the algorithm is JS we send you, so not in public github, however we intentionally serve our .js in non-minified format, so you can literally examine how we do it in the sources of the page in question! Look for "WiGLE...

we avoid doing this because phones are battery- and processor-constraint. Rendering the large pile of KML your trips would quickly become would result in warnings and the quick expenditure of your phone's battery. The "cheap" way is to request overlay images for your maps in the Settings p...