On 2014-03-31 08:06, B.J. Herbison wrote: > Thanks for the responses. > > tl/dr: For my house, the issue is probably the requirement of three access > points. > > When scanning from my home I currently have 3 wifi access points visible, 5 > scanned. One of the three appears to be the phone itself, even though I have > the hotspot turned off. (I've never run MozStumbler while the phone was a > hotspot.) The other two are access points in my house. This is probably > typical in this area, houses are far enough apart that seeing a good > connection to a network from a neighbor is unusual. It was increased to 3 apparently because of an attack. https://github.com/mozilla/ichnaea/issues/126 is for reducing it back to 2. There is also https://github.com/mozilla/ichnaea/issues/23 for 1 WiFi + 1 Cell. Wifi geolocation isn't going to be particularly useful in rural areas. > > Assuming the phone's hotspot has been identified as mobile, that means only > two useful access points are visible. Requiring three access points will make > the service unusable for a large potion of the country. Why are three access > points required? > > Currently the phone GPS is showing a location about 100 meters east of my > house, but the location button shows a location about 1000 meters north. Most likely using the cell tower, not the WiFi. The Cell tower is probably towards the north. > > I've scanned driving away from my house to the north and south (and toward > from both directions). I've headed south more often, so any bias in the > locations of my house wifi should be toward the south. > > I am using MozStumbler version 0.17. >
_______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
