specifically, the filter tool was written to process the KML format generated by the "link" and "view" tools in the "Uploads" tab of the app, or by downloading using the transid link on the website uploads page; the export run as KML button on the database tab uses a di...

question: how are you accessing these KML files? (how/where are you downloading them?)

interesting - I gave it a try in my virtual environment and I get a successful run with your file! (yeah, I'm an admin, I can do that)

try blowing away your virtual environment/re-creating, and I'll do the same?

Cheers,

-ark

what's the filesize of the input file?

if you load it in google earth, what do you see?

Cheers, and thanks for your interest!

we'll look into it! short version: while we love data, we want to avoid any responsibility for packet data, because we take individual privacy very seriously. Unified SQLite file formats are something we're careful with, specifically because they frequently couple beacon/location and capture data (w...

Great idea!

We should do a survey of the most popular formats. A question about RaMBLE: does the SQLite database contain packet data, or just beacon/location data?

Cheers,

-ark

By popular demand, we are now vending bluetooth network data via the API and basic search pages. Please consider the detail results a non-final implementation, as bluetooth devices are highly mobile.

per the other post, the data is preserved!

The "switching" behavior isn't something we've encountered before, but tapping the notifications in the taskbar, lock screen, or custom dialog overlays (lost / acquired GPS, etc) will switch back to the app.

-ark

Thanks for the feedback. The data *is* saved to the phone on reboot, and will be included in the next transaction. The notion of "Runs" rely on in-memory state in order to keep a coherent portrait of a single execution of the program, but observations and networks are logged to the databas...

the scan throttling should not affect overall performance - we haven't seen or heard much about an interactivity problem in that respect (nor does the play store "app not responding" dashboard show an increase). Historically, slowness in interactivity has been commonly associated with: 1. ...

you'll still recieve discovery credit for any APs you're the first to find, and they'll still be geolocated - the timestamps-less locations will just be given lower weights than later observations with valid timestamps, and so long as you don't clear your DB, you'll be able to re-export these with v...

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.