How come these Swedes were born in Y, Somme, Picardie, France?

Question

Well there is already an answer in G2G: http://www.wikitree.com/g2g/20328/awake-thinking-about-somme-picardie-france-haunted-place-earth

But perhaps, since it is such a common error, it might be included in the database errors project? It should be possible to spot, no?

 

Comments

Feels like we should have some kind of validation of places people die in ;-) 

A search on Google site:wikitree.com Y, Somme, Picardie, France

gives us About 2 460 results 

http://ysommepicardiefrance.blogspot.se/

Internet makes genealogy easy ==> easy to make errors and copy errors....

---

I've seen that location many times in an obviously unlikely circumstance.

---

I feel sorry for anyone with ancestors who actually did die there!

---

I have seen some other similar location bloopers - but since I don't remember exactly what they were, I cannot search for them. Will have to note it down next time I stumble across one.

As for Y, Somme, Picardie it would be a kindness to the people who actually lived there to clean up the erroneous instances on wikitree. We cannot do much about the rest of the Internet ;-)

As for Sjulsson and a cluster of descendents with the same location error, there is an online tree in existence, showing a more appropriate location. One might even be able to source the family (in a while, when it won't confuse the readers of this thread).

Answer 1

New errors: 606, 636, 666 Bogus location

606, 636, 666 Bogus location: This location is inserted as location by autocomplete operations of some softwares or websites.

Errors	Total	0000-0000	0001-1499	1500-1699	1700-1799	1800-1899	1900-1999
606 Bogus birth location	58	10	4	31	5	8
636 Bogus death location	980	45	178	288	327	141	1

 

 

Answer 2

These locations were probably generated by a "smart" (ahem) genealogy software program that has a "sophisticated" (ahem) geo-database against which it checks what people enter manually. And that the person entering the data did not realize what happened. And then the gedcom got uploaded to wikitree, and this is the result.

Comments

Yup, that's a neat and short version of the longer (and more particular) explanation someone posted in the older thread.

Answer 3

And I thought WikiTree is very popular in France.

Well I chose Y as an obvious error in location field (See error 632). I thought it was GEDCOM import problem since it is often followed with /. Looks like it can be also Yes case.

I can make another error for "Y, Somme, Picardie", to find all occurrences of that town. If you want to make WikiTree free of Y.

I can make same also for other such places, if they exists and need reviewing.

Here is Wikitree Location summary for Y and Yes in location.

http://www.softdata.si/osebe_staro/Ales/WikiTree/Y-Yes.htm

Comments

Interesting. The welsh ones may be false errors - or perhaps they should not be using the definite article (Y) there.

"Yes, working on it" made me actually laugh out loud.

At Y Beach, Gallipoli I would be surprised if only one person died. The others must not be on wikitree yet http://battlefields1418.50megs.com/y_beach.htm

---

Also, I guess I have set myself up for reviewing the Swedish occurrences of Y, Somme, Picardie.

---

So do you need an error to find them in http://www.wikitree.com/wiki/Project:Database_Errors?

---

Well, maybe it is no hurry. Still plenty to do with the other types of error.

---

This one http://www.wikitree.com/wiki/Fouche-18 has Yes Date unknown in bitlh location. Good to know she was born.

---

Ah, but we have no source for that ;-)

---

Some others that are common and almost always wrong

Sea, Indonesia

Anjou, Rhône-Alpes

Richmond, Wise

---

I found an explanation for Sea Sulawesi Tengah Indonesia - posted at the Ancestry board in 2011!! - apparently it is what those "helpful" autosuggesting fields give you when you ar inattentious and wish to indicate that somebody was lost at sea. Full explanation here:

http://boards.ancestry.com/surnames.brumback/65.1/mb.ashx

---

I can prepare an error with custom locations, that Could be entered on some Free Space page, so any user could add a location, that would be shown on next recalculation. I would automatically use locations on the page.

Answer 4

I don't know how it happens, but I find this particular location showing up a lot on family tree at ancestry.com. it could be that there is something in their software that is triggering this location.