Location Algorithm Does Not Work, Period
Is anyone in FS organization ever going to either
A. turn OFF algorithm which continues to degrade and worsen location info
Or
B. Put it back to original data which for the most part was correct PLEASE
Or
C. Fix it
Sorry for the rant but it is a real mess now and seems to be worse every time. Location is the most key data point and now is becoming useless.
Comments
-
@SerraNola FYI and thanks.
0 -
I agree, several census records come up in totally different states of the US. But when you pull up the record, it was put into the right place to begin with. Definitely needs to be addressed.
1 -
It is being addressed - albeit more slowly than most of us would like. It's an enormous project.
1 -
To clarify, this impacts ALL records for all of Ontario, Canada (not just my one example) and from other comments seems widespread across all locations oh my! All incorrect. Initially earlier algorithms changed the location that returned in a search, but often when adding the location to a record the older correct location fed over, but not any more - all must be manually corrected. Not sure how such a beast (algorithm) was released across all records everywhere without better testing. If ain’t broke, which it was not, what is being ‘fixed’. So many records and family groups will be wrong in FS as location is the main thing for majority of research. Are we to be sending every concern individually?
0 -
here is another, 1871 Census - Clinton, Huron, Ontario, Canada now showing Lambton County
0 -
We have updated the case owner with this latest example. It is still being worked on.
0
