Another free service,, also accepts GEDCOM-uploads, but I have no experience with that (Only because I would rather that they spend their limited CPU power on analysing DNA-data). So I will boldly point to my above link regarding GEDCOM comparison. So it appears the FTDNA does not actually have a procedure for testing their software changes but that they just try out their changes directly on the production system. The above example dates are all of type DATE_JULN, and after limiting myself to those I was able to import.īut: Since last night something else has stopped working at FTDNA:ġ) The attempt to render an already imported GEDCOM hangs (or takes more than 6 hours).Ģ) Consequently, GEDCOM upload is currently not possible.ģ) The attempt render to render a GEDCOM from a match returns a HTTP error 500 (Internal Server Error) along with the text 'The wait operation timed out'. Just sitting there telling us to wait while it processes. I don't have any dates in my gedcom other then simply "DATE".įor example, they all look something like: I’ve identified the following problem but don’t know what is the next step to solve it. But my use of Other sources or Web links is generating meny errors. My problem by the way prevents upload of GEDCOM from the open-source gramps (version 4.2.2). hogenf October 1, 2023, 1:20pm 1 Im trying to get Gramps to import Ancestry’s export with as few errors as possible. GEDCOM, complete name FamilySearch GEDCOM, is a de facto open file format specification to store genealogical data, and import or export it between. Your upload problem must have been different from mine, since mine only appeared about 6 weeks ago. The upload would also fail on individuals without both a first and last name, although that is entirely permitted by the standard. Instead, what appeared to be a usable but non-standard work-around was to use a HTML character-encoding. When I was last able to check, they did not even have support for the ANSEL-character encoding, which is the one actual GEDCOM-encoding that supports non-English characters. However, I finally tried creating a gedcom directly from and that loaded.Well, before it even makes sense for FTDNA to think about supporting the idiosyncrasies of the GEDCOM export of various genealogy software, FTDNA would need to first have basic support for the GEDCOM standard.Īnd they don't have that. When moving to Gramps Web from a different genalogy program including media files, it is recommended to first import everything into Gramps Desktop, which has more options to associate existing media files with an imported tree.I had problems for years uploading a gedcom created from Family Tree Maker. Note that this feature only works for files that have the correct checksum in the Gramps database (which should be ensured by running the check and repair tool in the first step). The folder structure in the ZIP file does not have to be the same as the folder structure inside the Gramps media folder as the files are matched to media objects by their checksum. It expects a ZIP file with the missing media files inside. If you have uploaded a family tree and need to upload the corresponding media files, you can use the "import media archive" button on the "Import" page. To import the media files belonging to an imported. This is because the import and export routines for media files are not suited for use on a web server. gramps) is the preferred format for importing data, Gramps XML package (. gramps) format to ensure your online and offline trees use the same identifiers and can be synchronized. If you already use Gramps Desktop, it is strongly recommended to use the Gramps XML (. To import an existing family tree, use the "Import" page and upload a file in any of the file formats supported by Gramps – see Import from another genealogy program in the Gramps Wiki. Note that even with relative paths, any media files outside of your Gramps media directory will not work properly when synchronized with Gramps Web. Use the Gramps Media Manager to convert all media paths from absolute to relative.This fixes some internal inconsistencies that could lead to problems in Gramps Web. Run the Check and repair database tool.Optional: create a database backup by exporting to Gramps XML.If you are migrating from a different genealogy program, you can skip this step. If you are using Gramps Desktop, there are two steps to prepare your database to make sure everything will run smoothly in the following.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |