Search for content in message boards

Data Structure for Place Names

Replies: 3

Re: Data Structure for Place Names

Posted: 21 Dec 2012 2:04PM GMT
Classification: Query
Edited: 21 Dec 2012 2:05PM GMT
First, FMT hasn't changed its "structure" for place name; rather it changed its structure for resolving place names. Place names can now be resolved with an address, or a cemetery or church, or village or hamlet - in the far left part of the name.

In turn, FTM did something which is bewildering to a lot of us: it then added a heirarchy feature; which means you can see a listing of states, then counties within a state, cities with a county, etc. This is bewildering to a lot of us because we wonder why ALL place names couldn't be placed in a heirarchical view. After all, the heirarchical view is nothing more than reading a location name from right to left, instead of left to right.

That said, these are the reasons for putting a cemetery, church name, local name in a city (any large city), village name, hamlet name (espeially New York):

1) You can see all the people that lived in that particular place in the Place Workspace, seleting the place name and look at the panel on the right side of the screen.

2) Maintain separate GPS of locations. Now that GPS devices can find a location to within 10 feet, or even closer - it is (or will be) necessary to have a specific GPS set of coordinates for either the front gate of a cemetery, or even a grave within the cemetery; specific GPS for a specific address of a house, etc. Not all of us are up to speed in this technology (I know I'm not), but the future is coming at us!





SubjectAuthorDate Posted
D. Shuler 21 Dec 2012 3:07PM GMT 
DavidNewton31 21 Dec 2012 3:45PM GMT 
Russ Worthing... 21 Dec 2012 7:24PM GMT 
silverfox3280 21 Dec 2012 9:04PM GMT 
per page

Find a board about a specific topic

  • Visit our other sites:

© 1997-2014 Ancestry.com | Corporate Information | New Privacy | Terms and Conditions