-Agreed, if there's a way to tell which is less accurate. We record what accuracy is reported Oh I must be totally blind to oversee that column /facepalm. I surely don't want to bash you or otherway say this system is bad, I just want to point out that there may be some problems somewhere else than ...

-But even a somewhat inaccurate location is at least more data then no location at all. sure, but when more accurate observation is available the less accurate should be ignored, shouldn't they? IMO when doing any kind of statistics the extremes (values very different from median) tend to be ignored...

my observations weren't just uploaded so I uploaded them ( https://wigle.net/gps/gps/main/confirmlocquery/?netid=00:50:7f:b7:d1:98 ) and: -I see many very inacurate observations (position probably not via gps) - why are these even counted? (it's a bar and I've been sitting inside so yea, no gps sign...

good to know. btw thanks for the link so I can check how it works without further questions

How can I get the BSSID and the wigle transaction id? But if you'd look at this map: https://wigle.net/gps/gps/Map/onlinemap2/?maplat=48.71915783585631&maplon=21.257364749908447&mapzoom=18 the wifi with SSID "BlueBell" should be in the center of the map yet it it still far too righ...

I've just checked and it looks like that for each run just one observation is uploaded and it just isn't right. The wifi is first seen very far from real position, this very-far position is reported as HERE IS THE WIFI!!! but even walking towards the hotspot itself won't change what will be uploaded...

so when I do upload the new run will it change the older wifis?

Hello,
would it be possible to use triangulation to count position of hotspots as https://market.android.com/details?id=h ... iscannkeep this app does?

Thank you!