Menu
▾
▴
Re: [Gramps-users] gramps testing with very large files
|
From: Alain A. <ala...@wa...> - 2014-04-14 19:18:42
|
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 14/04/2014 20:50, Enno Borgsteede a
écrit :<br>
</div>
<blockquote cite="mid:534...@gm..." type="cite">
<pre wrap="">Tim,
</pre>
<blockquote type="cite">
<pre wrap="">I suppose my next option would be to split the large gedcom into 3 or 4 geds (if that is
possible), and then import it using the ramdisk.
</pre>
</blockquote>
<pre wrap="">If the other tip doesn't help, splitting may indeed be an option, but
you can't just do that in an editor, because that is likely to break
lots of links, and kill your tree. And here again PAF can help. There's
a Windows program called GEDSplit that might do the same, but that does
not work well here. PAF does.
When you load your mega tree in that, PAF can select all persons that
are linked to a start person, and export those. How well that works
depends on the connectivity in your mega tree, but the nice thing about
PAF is that you can repeat the process for a another person that is not
selected, growing the selection till it's what you like. There's no need
to create filters for that, just point and click, and once they're safe
in Gramps, you can use the same technique to remove them from PAF, to
avoid duplicate exports.</pre>
</blockquote>
You can also use gWinTree, it exists for Windows and Linux.<br>
<br>
A+<br>
<div class="moz-signature">-- <br>
<hr>
Alain Aupeix<br>
<a class="moz-txt-link-freetext" href="http://jujuland.pagesperso-orange.fr/">http://jujuland.pagesperso-orange.fr/</a><br>
<a class="moz-txt-link-freetext" href="http://pissobi-lacassagne.pagesperso-orange.fr/">http://pissobi-lacassagne.pagesperso-orange.fr/</a><br>
<hr>
<small>U.buntu 12.04 | G.ramps 3.4.6-1 | H.arbour 3.2.0dev
(2014-04-03 12:26) | HbIDE (Rev.285) | Five.Linux (r138) |
Hw.Gui (2227)</small>
<hr></div>
</body>
</html>
|