You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if it would be more efficient than the Open Cell ID data, but have you looked at Wigle.net's Magic 8 ball positioning data? Would be interesting to use the data we contribute to back into the system.
I've only quickly read through the implementation, but this seems limited to 1km square precision (2 decimals of precision on coordinates):
This specification covers the use of 9-byte string form of 1km squares in the UTM space (two digits of precision.)
If that's the case, it probably isn't any more accurate than the current cell tower implementation. In my own tests, I have often seen sub-200m accuracy on the current cell tower feature.
Also it seems a .m8b file is ~500MB which probably can't be efficiently read on the wardriver (read operations are very expensive). This is a problem I was able to mitigate with the cell tower feature by chunking the data in a way which the wardriver can efficiently read and lookup, but the m8b implementation doesn't appear to have something similar.
I still need to read more into this, but at a first glance I don't think this is something that can be nicely integrated into the wardriver.
Not sure if it would be more efficient than the Open Cell ID data, but have you looked at Wigle.net's Magic 8 ball positioning data? Would be interesting to use the data we contribute to back into the system.
https://github.com/wiglenet/m8b
The text was updated successfully, but these errors were encountered: