That, of course, is not the "standard" way to name historical places in genealogical research. The "standard" (recommended) method is to name the jurisdictions as they existed at the time of an Event (e.g., a birth, baptism, marriage, death, burial, will, residence, etc.). For instance, I have many Events that happened in Medfield, Massachusetts, which is currently in Norfolk County.
My "standard" location for this place is "Medfield, Norfolk, Massachusetts, United States." However, many records for my Medfield ancestors are in Suffolk County, Massachusetts, not Norfolk County. My preference is that the historical place names should be used depending on the time frame of the event, but I'm stymied by the limitations of the genealogy programs and my desire to have the historical place names associated with a map location.
As an example, here is my list of place name jurisdictions for Medfield (and I may have them wrong... this is just an example):
1649 to 1691: Medfield, Suffolk, Massachusetts Bay Colony, British America
1691-1777: Medfield, Suffolk, Massachusetts Bay Province, British America
1777-1793: Medfield, Suffolk, Massachusetts, United States
1793-present: Medfield, Norfolk, Massachusetts, United States.
Another example, this time for San Diego (city), California:
1769-1823: San Diego, Alta California, Spanish America
1823-1848: San Diego, Alta California, Mexico
1848-1850: San Diego, California Territory, United States
1850-present: San Diego, San Diego, California, United States
I described some of the historical place names I found in the RootsMagic 5 County Check system in my post "Exploring RootsMagic 5 New Features - Post 4: The CountyCheck Report."
There are at least two "standardized location databases" online for genealogists. The two I know about are:
1) The FamilySearch Standard Finder (https://labs.familysearch.org/stdfinder/PlaceStandardLookup.jsp). A user can input a place name and obtain place name variants. the place type, the place time period, standard text, culture, iso-code, geo-code (latitude and longitude) and an identification number for the place name.
This Standard Finder includes many variant names for the current place name. However, it does not include all historical place names as an entity (e.g., the name of Raby in New Hampshire Province changed to Brookline in 1788).
2) Dallan Quass has formed a standardized location database (see https://github.com/DallanQ/Places). He spoke about "An Open-Source Place-Finder for Genealogy" this at RootsTech 2012 (you can see his syllabus here) and says:
"The database contains over 400,000 current and historical populated places and higher-level political jurisdictions (districts, counties, provinces, states, etc.). It is based upon the place wiki pages at WeRelate.org. The database includes the place name, type (e.g., city, county, etc.) alternate names, the jurisdictional hierarchy that was in place in the early 1900's, earlier and later jurisdictional hierarchies, and geo-position coordinates."
Dallan's database has current place name locations, along with alternate place name(s), type of place, also located in, and geo-code latitude and longitude.
In order for genealogy software users like me to incorporate historical place names into their database, without going to every Fact in the database, while retaining the geo-coded information so that the map shows the correct location, my wish list for genealogy software includes:
A Historical Place Name Jurisdiction Catalog (HPNJC) feature that:
* Contains a table of the included years, historical place name and jurisdiction(s) for each year range, the current place name and jurisdiction, and the geo-coding that finds the place on the map. Simple examples of this would be my two lists above for Medfield and San Diego.
* Depending on the Date of the Event in the genealogy database, the program finds the correct historical place name and inserts it into the Event Place field (perhaps with a "current location is ..." in the Place Description field, or in a Place Note field).
* Of course, this feature would need to be incorporated into an updated GEDCOM system and the different genealogy software programs and online family trees would need to be able to read it and write it.
At present Legacy Family Tree has a "County Verifier" feature that, if activated, warns the user that the county did not exist before the formation date. RootsMagic 5 has a "County Check" feature that does a similar task, and offers a number of suggestions for the user to pick from. Other software programs may have similar features, and I may not be totally aware of the Legacy and RootsMagic capabilities.
I think that this can be accomplished at some point in time, but it requires a fully populated historical place name catalog that genealogy software creators can utilize to implement a Historical Place Name feature (which implies that it should be Open Source, like the FamilySearch Standard Finder and Dallan Quass's Place Finder).
What is your vision - your wish - for a Historical Place Name Jurisdiction Catalog (HPNJC)? Can it be implemented? Would you be willing to participate in the generation of an Open Source HPNJC?
The URL for this post is: http://www.geneamusings.com/2012/02/my-software-wish-list-historical-place.html
Copyright (c) Randall J. Seaver, 2012.









