Geoff,
like you , I'm a fan of documenting the location at the time of event.
At the moment the only sure data of a place is the global position.
What I do at the moment is to use the "old name" and then in brackets the
"present name",
Eg. A place in present Poland at about 1940.
Wohlau (Wolów), Wohlau (Wolów), Breslau (Wroclaw), Deutsche Reich
(Polska) and add the global position.
BTW. In my case the notation in;
city, county, state, country
This notation workes in all countries I researched except for the
problem to note the country in a third
language eg. English = Poland.
When possible I try to transcribe the gobal positions to all of my events.
This way I have data which could be a basis for a historical database. Including
the same global position and the names of a location at the same place, with the
different historical data.
Looking at the place I live at the moment there are up to 10 different
desrcipition of the same place in the last 80 years and all have the same global
position.
As you propagate that it's best to document all sources of the information, in
my opinion the global positions belong to it too.
BTW. Your webinare about the cemetaries was great. Loved it.
What about one on locations.
Bernhard
-----Original Message-----
From: Geoff Rasmussen [mailto:[email protected]]
Sent: Thursday, November 17, 2011 1:39 AM
To: [email protected]
Subject: RE: [LegacyUG] Locations
Hey Tony,
I wish people would disagree with me more often - we all can learn from each
other.
However, understanding the location at the time of the event is crucial to
research success. Woodstock, Connecticut has always had the same
latitude/longitude. Today it resides in Windham County. If you look for records
in Woodstock, Windham County for an ancestor that lived in Woodstock in 1720,
you won't find what you are looking for because at that time it resided in
Suffolk County, Massachusetts. If I were to record the person's birth as 1720 in
Woodstock, Windham County, Connecticut, it would be false - the place simply did
not exist then. My recommendation then is to record the location as it existed
at the time of the event AND in the event's notes, record the name of the place
as it exists today to cross-reference each other.
Good luck,
Geoff
-----Original Message-----
From: Tony Rolfe [mailto:[email protected]]
Sent: Wednesday, November 16, 2011 5:10 PM
To: [email protected]
Subject: [LegacyUG] Locations
Paula wants me to change the thread title, so here goes.
Hi, Geoff
I have to disagree with your statement that "it's the location at the time of
the event that is important not the location as it is [or isn't] now."
Surely the whole point is that these two locations are the same location. The
names may have changed, the old location may now be in the middle of a motorway,
under a reservoir or have fallen off a crumbling cliff into the ocean. However,
where it was is where it is.
The latitude and longitude are still there.
Researching people is also about researching locations. Where they lived is
important. Where they lived often determined how they lived.
Sometimes reaearching the locations highlights problems. I have a grand uncle
and his wife who moved to Canada. His granddaughter contacted me and told me
that he told he that "he married his childhood sweetheart".
Fine, until you include location details. She was born and lived about 25
miles South of the wide part of the Thames Estuary. He was born and lived about
the same distance North. There is no obvious way from one place to the other in
a time when travel wan't as easy as it is today.
My research shows that they didn't meet until they both moved to a third
location. So what is wrong? Something doesn't add up. Is the childhood
sweetheart just a family story? Do I have the wrong wife?
The wrong grand uncle? Did they both travel to the coast and meet on holiday?
Without knowing the locations, I wouldn't know there was an issue. It's on my
to-do list.
Why do I prefer jpegs over PDF's? Partly because I don't like any of the PDF
readers and I can't afford (or be bothered) to buy a PDF editor.
Partly because I can use photoshop to make poor-quality jpeg images more
readable. Nothing really profound. Just a personal preference.
Cheers
Tony
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
