Open DerekCaelin opened 2 months ago
At 44.04219, -107.7188
I don't have a 100% match of soils
44.16471, -107.33253
@CourtneyLee333 are there other locations where you're getting a 100% match?
@DerekCaelin on v1.0.2 (190) beta I no longer get 100% match on the original example coords or several other locations I tried.
OK! Closing this issue for now. I will continue to look out for instances of 100% matches
On iOS, I created a site at 41.7063, -72.63145
. In the temporary site I got 80% for Pootatuck. Upon becoming a permanent site, it becomes 100%.
@DerekCaelin This difference is due to the display of the location-score at a temporary site and the data-location-score once a site is created. This relates back to our discussion about the use of remotely sensed data to refine the data score without the user having to enter information. The reason it is reporting 100 is because it is being normalized. I have updated the code to remove the normalization step.
Pulling from Courtney's comment
On iOS, I created a site at
41.7063, -72.63145
. In the temporary site I got 80% for Pootatuck. Upon becoming a permanent site, it becomes 100%.Steps to reproduce
41.7063, -72.63145
Expected behavior
soils have location percentages other than 100%
Actual behavior
Some soils get 100% match
Additional context