More examples of the search results display pulling places out of thin air

Julia Szent-Györgyi

This is that weird not-quite-autostandardization error, or autostandardization on the fly, or whatever the heck it is: the search results list picks a place more-or-less at random to display in place of the indexed text that shows if you actually look at an individual result. In this case, we have an indexed "Vigo" as the departure place of a bunch of Spaniards immigrating to Uruguay, which shows up in the search results list as "Vigø, Fyn, Denmark".

There are also some actual autostandardization errors mixed in with those results: if the Immigration Place (Original) is "Vigo", it has been autocorrupted to "Vigø, Svanninge, Sallinge, Svendborg, Denmark" as the "Immigration Place" -- never mind that the nationality is "Uruguaya" (https://www.familysearch.org/ark:/61903/1:1:Z7X6-5V2M).

Julia Szent-Györgyi

And Find is doing it, too: it's apparently randomly picking a place, totally ignoring what has actually been chosen as the standard.

https://www.familysearch.org/search/tree/results?count=100&q.birthLikeDate.from=1855&q.birthLikeDate.to=1855&q.birthLikePlace=Wennington%2A&q.givenName=Susan%20Ann&q.givenName.exact=on&q.surname=Hill&q.surname.exact=on

The birthplace shows in the Find results as "Conington, Huntingdonshire, England".

https://www.familysearch.org/tree/person/details/9XNH-2LF

The display value for the birthplace is "Wennington, Huntingdon, England". (Google Maps says there is/was a Wennington in Huntingdonshire, in between Woodwalton, Little Raveley, and Abbots Ripton, but it's apparently not in FS's database.)

The Standardized Event Place for the birth was (incorrectly) chosen as "Wennington, Essex, England, United Kingdom". "Conington" is not in the drop-down list, that I can find, so I really have no clue where it's coming from, besides right out of thin air.