Why is my Percentage Quality Locations so low?
its like 23% or something like that... and the areas ive discovered havent been discovered by anyone before me... and they are all with GPS (with good signal)
now, could it be that my GPS is slow? it only updates once every 2 seconds or so, so its *possible* that more than one AP has the same location... but 77% loss is pretty damn high!
now, could it be that my GPS is slow? it only updates once every 2 seconds or so, so its *possible* that more than one AP has the same location... but 77% loss is pretty damn high!
heya, FLE...
your percentage quality locations is proportional to correlation of GPS signal to networks in your uploads; what kind of files are you submitting (from what stumbling package?), and what do they look like on your end, in terms of GPS?
-a
your percentage quality locations is proportional to correlation of GPS signal to networks in your uploads; what kind of files are you submitting (from what stumbling package?), and what do they look like on your end, in terms of GPS?
-a
err... forgot to login...
well the number of networks with gps / without gps is about 97.5%
User: FLECOM
Nets w/GPS: 2,100
Nets w/o GPS: 2,153
Percentage Quality Locations: 22.053%
well the number of networks with gps / without gps is about 97.5%
User: FLECOM
Nets w/GPS: 2,100
Nets w/o GPS: 2,153
Percentage Quality Locations: 22.053%
quality locations are ones not excluded by the filtering we do.
if you see an ap, and your gps or stumbling package is wonked out and reporting you somewhere you aren't, your observation of that ap will not agree with those who've seen it before. in such cases an observation may fall several standard deviations out from the previously averaged location of an AP. we keep all of the observations, so your percentage will change as we reapproximate the location of an AP over time, as its reported by more people.
so its not a "divide gps points by total" kind of number, sorry for the confusion.
if you see an ap, and your gps or stumbling package is wonked out and reporting you somewhere you aren't, your observation of that ap will not agree with those who've seen it before. in such cases an observation may fall several standard deviations out from the previously averaged location of an AP. we keep all of the observations, so your percentage will change as we reapproximate the location of an AP over time, as its reported by more people.
so its not a "divide gps points by total" kind of number, sorry for the confusion.
ok but what im wondering is that, all the AP's ive found in miami, are ALL The ap's you have for miami...
when i loaded the miami maps there were maybe a few in downtown but thats it...
i did all of the kendall/south miami/coconut grove area which were all new AP's for your database...
so what is there to compare them against?
when i loaded the miami maps there were maybe a few in downtown but thats it...
i did all of the kendall/south miami/coconut grove area which were all new AP's for your database...
so what is there to compare them against?
well, software being what it is: its possible your case has tripped an edge condition in the "goodness" detector.
we'll have a look, and let you know if we find something strange.
we'll have a look, and let you know if we find something strange.
coolwell, software being what it is: its possible your case has tripped an edge condition in the "goodness" detector.
we'll have a look, and let you know if we find something strange.
no hurry tho, im sure youve got all sorts of stuff to worry about, i was just wondering why i was getting "bad" data scores and what (if anything) i coudld do to improve them
webstumbler's slick, btw; you're gonna work maps in next, right?
*grin*
-a
*grin*
-a
Well, the reason is you've submitted over 11,000 observations with lat/long of zero, with different signal strengths, and roughly 3,000 observations with lat/long filled in. Given how our stats math is, it falls out that the percentage calculated of 'observations used for triangulation' is so low.
This stat is kind of a just-for-fun thing, doesn't count towards ranks or anything, so hopefully it won't bug you too much.
This stat is kind of a just-for-fun thing, doesn't count towards ranks or anything, so hopefully it won't bug you too much.
na its not that it bugs me, i just wanted to know if there was something i was doing wrongWell, the reason is you've submitted over 11,000 observations with lat/long of zero, with different signal strengths, and roughly 3,000 observations with lat/long filled in. Given how our stats math is, it falls out that the percentage calculated of 'observations used for triangulation' is so low.
This stat is kind of a just-for-fun thing, doesn't count towards ranks or anything, so hopefully it won't bug you too much.
but ya im sure i have different sighting of the same ap's since this machine is installed in my car its always running... and 90% of the time im driving to/from the same place through the same streets
thanks for everyones help tho
actually, im thinking about re-writing parts of it... it has some very nessicary things missing...webstumbler's slick, btw; you're gonna work maps in next, right?
*grin*
-a
i was thinking of GPL'ing it... but i dun really want to becuase then everyone will see what a shitty coder i am
Return to “WiGLE Project Suggestions”
Who is online
Users browsing this forum: Ahrefs [Bot] and 107 guests