Search for content in message boards

Data Structure for Place Names

Data Structure for Place Names

Posted: 1356102423000
Classification: Query
I'm glad FTM is creating a better structure to better handle places though I have a few questions on long term strategy.

I currently create my places using {city},{county},{state},{country} with the comma being the delimiter. I include churches, hospitals, schools, etc in the description field for event like burial and birth.

Rather than just listing all the people associated with a location, will FTM list locations under a place, ie churches in a county? Do I need to redo all my places and put non-political locations in the place field with a comma or keep them in the Description field.

I'm also redoing some of my locations to include names at the time of a record, ie a District vs present County.

Basically, how do we need to structure our place data to best take advantage of upgrades in FTM, especially if they start allowing search based on location, and listing places on the mobile app based on your current location.

Re: Data Structure for Place Names

Posted: 1356104704000
Classification: Query
Does the heirarchical view of places help here? I always included addresses in my places and the heirarchy allows me to drill down to whatever level I want. So for example, I can go to England, Yorkshire, Halifax and get a list of all the addresses used in Halifax and clicking Halifax gives me a combined list of all the people who lived in Halifax etc.

Re: Data Structure for Place Names

Posted: 1356117852000
Classification: Query
D. Shuler,

I did a blog post on this topic, in fact there are a couple.

With FTM2012, and the new way of handling place names, I use Address, City, County, State, Country; Cemetery, City.....; Church, City ....; AND Historical Place names.

Hope that helps,


Re: Data Structure for Place Names

Posted: 1356123875000
Classification: Query
Edited: 1356123954000
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!

per page

Find a board about a specific topic