Respect the timestamp!

[khmann]

Once upon a time, I uploaded an *old* consoldated.sqlite3 backup that included my AP from my OLD house, along with lots of other good data. Even though the file contained timestamps marking the data as several years old, it replaced the location of my AP at my NEW house (which has been consistently updated recently with kismet data). I understand making "correct" use of this data is difficult, I wonder if it makes sense to try and follow the timestamp (In my case it seems the number of seconds since y2k)... there would be a lot of potential issues with trusting timestamp data from capture sources (many of my drones don't have clocks).

I just hate to think of one ancient android cached location with signal=255 overriding REAL kismet upload data and corrupting computations.
Also I would like to see a webmaps filter for !SSID (ie: specifically no nodes without SSID)

[bobzilla]

Data tends to cluster, and newer larger clusters will override older and/or smaller ones. The !ssid is a good call, adding to todo list.