I was using the Mozilla Geolocation while working on Bug 985970. It had my location accurate to within 10m.
On 2014-03-27 06:20, B.J. Herbison wrote: > Three examples of bad results from the location button. > > 1: I've run MozScanner many times at my office--I scan driving to the parking > lot and then walking into the building. Recently pressed the find location > button inside my office (where my phone can't reach GPS). The service > couldn't find my location. Shouldn't it have been able to recognize some of > the wifi networks in the building and use the GPS position from outside? What kind of building, and how big? Do you have good coverage outside? How many networks and APs can you see? Is your phone dual band? It might be that you aren't getting enough APs. The geolocation service currently requires 3 mapped APs before returning a WiFi based location. > 2: I just pressed the location button at my well-scanned home, and the > location shown was over half a mile away. (If the location is intentionally > vague instead of precise the icon should be changed as the finger point > implies precision.) Again, how many APs are visible? Perhaps its using the cell tower instead. Do you have any mobile APs (trains/buses) nearby that aren't being filtered out? These can skew the results dramatically. > 3: After pressing the location button I noticed I was scanning. To test > whether asking for location turns on the scanner (it does) I tried asking for > location again. This time the location was in the next town over. It might > possibly be a location based on my IP address, but since I've scanned my home > with GPS and wifi signals many times why can't if find the correct location? If you are not sure how many APs are visible, try installing inSSIDer on your phone. It will give you a list of all visible APs. _______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
