Add "MissingCount" attribute to groups to address data quality issues about mapswipe HOT 4 CLOSED

Maybe I could have a look at that issue. But couldn't we just calculate the missing-count instead of storing it, like:
missing.count = group.count - group.completedCount
or is it because of database accessibility that we need to store it?

from mapswipe.

@gkeller26 Nice! So to give a little background on what we're trying to solve here. Right now, for each tile (each square on the map), we store the following:

• # of tiles with buildings
• # of tiles with "maybe"
• # of tiles with bad imagery

Here, the counts that we have are the sum of the counts above. We don't happen to have counts for cases where there were no buildings. Another way to say that is we don't have counts for cases where someone looked at a tile and didn't tap it.

You're right that one way to implement that would be to go ahead and count how many times someone saw a tile and that might be a better implementation here.

from mapswipe.

I think this is out of date now with v2.0. @Hagellach37 can you take a quick look, and close this ticket if it makes sense? If not, it might need updating to match the current database format...

from mapswipe.

I'm going to close this, as v2.0 now implements the storage of results differently, and specifically, we store a result object even when there are no buildings, which allows much more detailed stats. The changes proposed here are not relevant anymore.

from mapswipe.