You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the JSON response for the API call /api/v2/challenge/{id} the keys .tasksRemaining and .completionPercentage sometimes show slightly wrong values. The correct values can be seen in the challenge web page (e.g. https://maproulette.org/browse/challenges/{id}) or by making a request at /api/v2/challenge/view/{id} and doing the math.
Here is a bunch of examples:
Challenge 5556 (both values are wrong, 3% difference of completion):
I suppose that when .tasksRemaining contains the correct value it's just a problem of rounding to the nearest integer (because the .completionPercentage seems to be offset to just 1%), but what about the case where the difference is greater than 1%?
Kind regards,
Marco.
The text was updated successfully, but these errors were encountered:
In the JSON response for the API call /api/v2/challenge/{id} the keys .tasksRemaining and .completionPercentage sometimes show slightly wrong values. The correct values can be seen in the challenge web page (e.g. https://maproulette.org/browse/challenges/{id}) or by making a request at /api/v2/challenge/view/{id} and doing the math.
Here is a bunch of examples:
Web page https://maproulette.org/browse/challenges/5556 shows 79% and 118
Web page https://maproulette.org/browse/challenges/43716 shows 39% and 282
Web page https://maproulette.org/browse/challenges/28186 shows 20% and 5598
Web page https://maproulette.org/browse/challenges/42381 shows 4% and 26193
Web page https://maproulette.org/browse/challenges/48926 shows 49% and 11510
I suppose that when .tasksRemaining contains the correct value it's just a problem of rounding to the nearest integer (because the .completionPercentage seems to be offset to just 1%), but what about the case where the difference is greater than 1%?
Kind regards,
Marco.
The text was updated successfully, but these errors were encountered: