I certainly agree with the points of this program, both having data where e.g. radiocells does not, and the privacy issue. But, it would be great to be able to have the data avoid lots of overlap with a backend that uses a downloaded database, to avoid recording things that are a) known and b) not incrementally useful given the values in the other database.
The idea would be to have a side channel to query the other provider, and if recording the emitter is not useful given that it's in the other db, skip it.
Obviously this needs to be configurable and default to off.
It could be that the savings in the database is small, but my LocalWifi backend now has 300K wifis in it, and I suspect a fair number of those are in radiocells.
I certainly agree with the points of this program, both having data where e.g. radiocells does not, and the privacy issue. But, it would be great to be able to have the data avoid lots of overlap with a backend that uses a downloaded database, to avoid recording things that are a) known and b) not incrementally useful given the values in the other database.
The idea would be to have a side channel to query the other provider, and if recording the emitter is not useful given that it's in the other db, skip it.
Obviously this needs to be configurable and default to off.
It could be that the savings in the database is small, but my LocalWifi backend now has 300K wifis in it, and I suspect a fair number of those are in radiocells.