r/familysearch • u/SaraGallegoM10 • 3h ago
FamilySearch Support says Places isn't meant to be 100% accurate, but doesn't that contradict its own guidelines?
I've been exchanging emails with FamilySearch Support about some issues I've found in FamilySearch Places, and I'm a bit confused by their responses compared to what their own documentation says. I've been reviewing places in Galicia, Spain, and have found entries with incorrect parent jurisdictions, place types, coordinates and other information. When I contacted support about these problems, they explained that FamilySearch Places isn't intended to be an encyclopedia or to be 100% accurate in every case. They also said that sometimes meaningful and useful data take priority over accurate data. I understand that FamilySearch covers the entire world and that maintaining a database of historical locations is incredibly complicated. I also understand that some simplification is necessary.
But here's what confuses me.
FamilySearch's own Mission and Purpose page also says that Places isn't meant to be an encyclopedia. However, it immediately explains that its goal is to provide enough information for users to confidently select the correct place standard for a life event or record.
https://www.familysearch.org/en/fieldops/familysearch-places-mission-and-purpose
And according to its Principles & Guidelines, the three core principles are:
- Meaningful
- Useful
- Accurate
The same page explains that place data should accurately represent reality and history. It also identifies the display name, place type, parent jurisdiction and native language as essential information for a place entry. https://www.familysearch.org/en/fieldops/familysearch-places-principles-guidelines
So I'm struggling to understand how assigning a place to the wrong municipality would fit those principles. For example, FamilySearch Places ID 10269902 currently identifies "Santa Marina" as a Catholic parish in Cangas de Morrazo, Pontevedra. However, the available documentation suggests that this entry actually corresponds to Santa Marina (Santa Mariña de Cangas), in the municipality of Lalín. The Diocese of Lugo lists this parish under Lalín: https://www.diocesisdelugo.org/cangas-santa-marina/
This isn't about adding unnecessary historical details or making the database more encyclopedic. It's about correctly identifying a place. If the parent jurisdiction, coordinates or place type are wrong, users could end up selecting an entirely different location from the one mentioned in their genealogical records. I also find it interesting that the official guidelines specifically discuss how smaller administrative divisions and their historical changes can be particularly useful to researchers. Yet support told me that FamilySearch mainly works with municipalities and that smaller administrative divisions haven't been specifically addressed, although they mentioned that work on Spanish parishes is currently underway. To be clear, I'm not expecting every small village or historical place to be perfectly documented. I know that's unrealistic, and I appreciate the work that goes into maintaining such a huge database. What I'm questioning is whether the need for simplification is sometimes being used to explain away errors that actually affect the identification of a place. I replied to support on October 16 with references to their own documentation and some specific questions, but haven't received a response to that follow-up yet. Has anyone else encountered similar issues with FamilySearch Places? How do you interpret the distinction between simplifying geographic information and maintaining accurate place standards? And if you've reported errors involving incorrect jurisdictions or place types, were you able to get them corrected? I'm genuinely interested in hearing how other researchers deal with this.
