Absolutely; the KML export just disqualifies those because broken time stamps are often a proxy sign of bad GPS signal. You can gather data and export upload once the patch is in. You can also upload on a rolling basis and re upload when the date stamps are fixed

documented issue here:
https://github.com/kismetwireless/kismet/issues/122


proposed a patch here:
https://github.com/kismetwireless/kismet/pull/123

happy to hear if i've made a mistake - it's been a long time since i've used

ah, kismet is inserting "Mar" instead of "03" in the date stamps, which doesn't match our format.

ah, I've found the problem - the time value we populate in that table isn't getting set correctly on the observations. watch this space for details.

looking through the logs, I get: No locations results for transid 20190305-0008 - if the file doesn't contain coordinates, wigle doesn't attempt to build KML. since the link is a direct download, there isn't a good channel to provide an error message. feel free to post transids here, I can check the...

oh interesting - we'll check it out.

As a reminder, those KML files are just about your uploads, not a good way of evaluating the WiGLE trilateration tech.

Indeed, we're looking into whether or not the Lineage folks would consider a patch to remedy this!
If anyone has connections there, we'd love to get a read on what the criteria are, whether they'd consider it!

Cheers,

wow, yeah, the images make that easier to spot; they've been there all along, but only if you were using a screenreader or viewing source. They started out as a riff on Prince's spoken word stuff from Graffiti Bridge, if that tells you how old they are. Good spot. We owe you stickers, if you want 'em!

We use a wide range of technology, much of it is hand-rolled (since we've been around a while, a lot of new cool stuff has arrived, and we haven't always incorporated it). A few elements of our tech stack we're really happy with: - MySQL / MariaDB have worked for us since the start - ElasticSearch i...

Right now, we don't back-up your observation data for you; only the list of APs you have seen.

You can use the map tile overlays ("Mine" in settings) and search function to view your previously located APs.

Pretty sure we'd have been kicked out of the Play store if we didn't exit correctly!
Can you tell us what you mean by the "app list?"

Cheers,

-ark

there are actually a number of states - you can check out the list here: https://github.com/wiglenet/wigle-wifi-wardriving/blob/ec08365dc29aaebc9cb812b8b6b60566c62ca09b/wiglewifiwardriving/src/main/java/net/wigle/wigleandroid/UploadsFragment.java#L102 the reason you see queued and geocoding for exte...

It's a consequence of the reprocessing we're doing - we're throwing old files back into the queue in order to fix some data we didn't process or process correctly the first time around.
This will stop happening once we complete our bluetooth infra!

the real problem is that we're getting some serious kitten-crowding on our tables now. (Uploads are already a wreck even without adding BT).

Great idea. Implemented as requested on Stats and Uploads.
Let me know if you have questions, or if I made any mistakes.