what does wigle do with all the bluetooth data - Why is it not mapped?

Talk about whatever

5 posts • Page 1 of 1
as subject title>

Image
Hmmm... no answer? Interesting. I've wondered the same thing.
1. It's queryable and searchable via the search UIs and APIs, which is what people do to use it
2. If you want to see it on the map, you can check out the Basic Search UI, select the BT tab.

We don't put it on the main map because bluetooth data is often unreliable - BTLE in particular has a more sophisticated privacy model than WiFi that generates lots of "random" addresses.

-a
1. It's queryable and searchable via the search UIs and APIs, which is what people do to use it
2. If you want to see it on the map, you can check out the Basic Search UI, select the BT tab.

We don't put it on the main map because bluetooth data is often unreliable - BTLE in particular has a more sophisticated privacy model than WiFi that generates lots of "random" addresses.

-a


does wigle know which Bluetooth sources are BTLE ? Would be nice to be able to show on the map BT address's that are considered reliable. Mapping BT devices have static adresses the same way wifi is currently would be a great addition. Costly on server end perhaps?
There's more to it - some BTLE is more reliable than others. Some BT is unreliable!
We do some clustering analysis, both server-side, and client side in the search - if you have a specific set of criteria in mind, we urge you to play with the Basic Search BT system; it shows you what WiGLE knows, and you CAN get useful stuff from it. It's far from comprehensive, but you can still learn a lot!

-ark

5 posts • Page 1 of 1

Return to “General Grabbag”

Who is online

Users browsing this forum: No registered users and 16 guests