Provider Priority?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I do not know if this is already implemented and it is hard to test, so I just write my suggestion here. Ignore it if you wish.
What I would like is to have some less accurate providers still be able to cancel more accurate ones if the data differs.
I had the problem with the Google provider, that someone in the Netherlands used the same MAC as my router.
Google would always place me in the Netherlands when I was at home and had no GPS signal.
But I am in Austria and had GSM reception.
There just is no way to be connected to an Austrian GPS network and be in the Netherlands.
So in my opinion, while the exact location of the GSM provider is less accurate, at least the country is more accurate and it would be great to use this to filter wrong results.
This wrong data can not only happen with cloned MAC but also when wifi aps are moved which is not uncommon today,
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the provider interface and location-priority handling in UnifiedNlp, then trace how Google, GSM, and GPS results are combined. Reproduce the Netherlands-versus-Austria case if possible and define how conflicting provider data should be resolved before changing the implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100