Soil ID is returning 100% in some locations

[DerekCaelin]

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

1. Create a temporary pin at 41.7063, -72.63145
2. Look at soils list
3. Convert into a permanent site
4. look st soils list
5. See issue

Expected behavior

soils have location percentages other than 100%

Actual behavior

Some soils get 100% match

Additional context

[DerekCaelin]

At 44.04219, -107.7188 I don't have a 100% match of soils

44.16471, -107.33253

[DerekCaelin]

@CourtneyLee333 are there other locations where you're getting a 100% match?

[CourtneyLee333]

@DerekCaelin on v1.0.2 (190) beta I no longer get 100% match on the original example coords or several other locations I tried.

[DerekCaelin]

OK! Closing this issue for now. I will continue to look out for instances of 100% matches

[DerekCaelin]

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%.

[jjmaynard]

@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.

[DerekCaelin]

@CourtneyLee333 found that at 38.50193, -80.64322, returned list of sites will have a 100% match for the site, but not the temporary location.

Temporary location

Site (after list_soils called?)

[DerekCaelin]

From @ssfrancis :
Created a site at Paicines Ranch (36.72538, -121.30373)

Top Soil Matches:
100% Pleasanton
66% Cropley
64% Soper
52% Antioch
52% Rincon