Hi everyone, I was able to identify the source of errors for these observations. Turns out, those were readings taken when my phone's clock was messed up. Date on my phone during that time was sometime in 1970. Those resulted in wacky computed GPS positions. What do I need to do to help you remove the erroneous data? Right now, it's making it rather hard to see which spots on the map are not yet covered in the Metro Manila area. Thanks!
*RK* On Thu, Jan 23, 2014 at 5:24 PM, <[email protected]> wrote: > Am Mittwoch, 22. Januar 2014 20:05:12 UTC+1 schrieb Chris Peterson: > > On 1/22/14, 6:47 AM, RK wrote: > > > > > Yup. That's low accuracy data from a WiGLe import(data's mine, WiGLe > kept > > > > > recording even when I'm indoors, hence the very low accuracies, in the > > > > > hundreds and sometimes thousands of meters range). > > > > > > > > I assumed those lines might be airplane routes, but low accuracy data > > > > makes more sense. :) > > > > > > > > You can also see off-road routes from devices that have GPS calibration > > > > problems. In San Francisco, you can see some stray lines (that are not a > > > > ferry) running parallel to the bridge: > > > > > > > > https://location.services.mozilla.com/map#15/37.7963/-122.3750 > > > > > > > > > > > > chris > > air planes shortly crossed my mind too, but all those pilots would have > had to fly in remarkably straight lines & land in rather built-up areas ;-) > > but thanks for the clarification RK > _______________________________________________ > dev-geolocation mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-geolocation > _______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
