Jump to content


Member Since 27 Oct 2018
Offline Last Active Feb 11 2020 12:28 PM

Topics I've Started

What Place fields are sent to FamilySearch?

05 February 2020 - 07:47 PM

Hello Renee,

I am interested in the use of the RootsMagic Places fields in the great RM feature "FamilySearch Person Tools." Specifically the interaction of RM & FS so I can make a decision on how I want to utilize the RM place fields.


I've been reading forum posts on how to use place names, the dilemmas, many ideas & opinions, good & bad, to the point of confusion. I don't want to rehash this topic. All I want to know is what the algorithms RM & FS software are actually expecting? How strict-forgiving or intelligent is the algorithm?


There are four RM place fields.

Which place fields does RM actually send to FSFT when trying to match individuals?
Does any API place conversion or filtering occur before the data is transmitted?

- Place

- Standardized place name (can be auto-populated by RM GeoCode)

- Latitude/Longitude (can be auto-populated by RM GeoCode)

- Abbreviated place name (if any)


What type of "ideal" place name does FSFT expect for optimized matching of RM individuals or will make matching worse?

- Modern names (Kansas) vs. Historical name (Kansas Territory)

- The English spelling of names in other countries vs. the native language vs. RM GeoCode mix

     English (North Rhine-Westphalia, Germany)

     German (Nordrhein-Westfalen, Deutschland)

     RM GeoCode (Nordrhein-Westfalen, Germany) mixed?

- Some countries have more than one official language (Switzerland officially has 4 languages)

- What about spellings with special characters like umlauts? German (ü) versus the English substitute (ue)

- What about when the place 4-comma format (city, county, state, country) contain qualifying words like "Smith Township" "Smith Twp." or "Jones County" "Jones Co." in the respective city or county position?

- Are the RM GeoCode database & FSFT equivalent place database the same database?


The same place questions if relevant for what is expected by Ancestry.com, MyHeritage, WebHints to optimize their algorithms?

Thank you very much. J

RM8 and Linux Wine/Crossover

14 August 2019 - 05:07 PM

Wish: I would like RM8 to work on a Linux OS using Wine or Crossover.


I know officially RootsMagic does not support Linux or Wine/Crossover, but if you could please provide some indication (even an educated guess) if the new RM8 rewrite & implementation is likely work with Linux & Wine/Crossover, or if its already known that Wine will have issues?


My concern is the (hopefully) soon to be released RM8 is a complete rewrite, RM8 is being designed for Win10, and RM8 does not need to support the soon to be obsolete Win7 I am currently using with RM7.


Why? In Jan 2020 Microsoft will discontinue support for Win7, afterwards it's a security risk; so I am currently analyzing my existing computer network, hardware and all software applications with respect to both my personal & professional computing needs, then develop a transition plan and implement it before Jan 2020. For various reason I am doing everything I can to avoid using Win10, and minimize buying new hardware. I have used both Windows & Linux for years, however, I have not used Wine or Crossover. Ideally I would like to go ALL Linux.

Thanks, John