It is true that you can manually shift the paternal tree...but the problem you are facing is solved in another way.
The issue is that in the paternal tree, you have termination at only the brother, ego, and sister nodes. But in the maternal tree, you have son, daughter, and niece/nephew nodes terminating. These lower-level nodes force more separation space between brother, ego, and sister -- this space is not required in the paternal tree, because those lower-level nodes don't exist.
All you need to do is mirror the entire child nodes structure from father and mother downward, like such:
EDIT:
The structure requires a very small tweak when you copy and paste. The first image shows what happens when you do not make the tweak. You'll need to flip the g and p in the father and mother nodes within the paternal tree.
\documentclass[a4paper,landscape]{article}
\usepackage[top=4.5cm, bottom=4.5cm, left=1cm, right=1cm]{geometry}
\usepackage[all]{genealogytree}
\begin{document}
\resizebox{\textwidth}{!}{
\begin{tikzpicture}
\genealogytree[template=signpost, id suffix=@p]
{
child{
g[male]{paternal grandfather}
p[female]{paternal grandmother}
child{
g[male]{paternal uncle}
c[male]{cousin}
child{
g[female]{cousin}
}
}
child{
g[female]{paternal aunt}
c[male]{cousin}
child{
g[female]{cousin}
}
}
%OLD WAY
%child[phantom*]{
%g[male,id=father]{father}
%p[female]{mother}
%c[male]{brother}
%c{\textsc{ego}}
%c[female]{sister}
%}
%MIRRORED FROM MATERNAL TREE (SEE FIRST IMAGE)
%child[phantom*]{
%p[male,id=father]{father}
%g[female]{mother}
%child{
%g[male]{brother}
%c[male]{nephew}
%child{
%g[female]{niece}
%}
%}
%child{
%g{\textsc{ego}}
%c[male]{son}
%child{
%g[female]{daughter}
%}
%}
%child{
%g[female]{sister}
%c[male]{nephew}
%child{
%g[female]{niece}
%}
%}
%}
%}
%MIRRORED FROM MATERNAL TREE WITH THE TWEAK (SEE SECOND IMAGE)
child[phantom*]{
g[male,id=father]{father}
p[female]{mother}
child{
g[male]{brother}
c[male]{nephew}
child{
g[female]{niece}
}
}
child{
g{\textsc{ego}}
c[male]{son}
child{
g[female]{daughter}
}
}
child{
g[female]{sister}
c[male]{nephew}
child{
g[female]{niece}
}
}
}
}
}
\genealogytree[template=signpost, id suffix=@m, set position=father@m at father@p]
{
child{
g[male]{maternal grandfather}
p[female]{maternal grandmother}
child{
p[male,id=father]{father}
g[female]{mother}
child{
g[male]{brother}
c[male]{nephew}
child{
g[female]{niece}
}
}
child{
g{\textsc{ego}}
c[male]{son}
child{
g[female]{daughter}
}
}
child{
g[female]{sister}
c[male]{nephew}
child{
g[female]{niece}
}
}
}
child{
g[male]{maternal uncle}
c[male]{cousin}
c[female]{cousin}
}
child{
g[female]{maternal aunt}
c[male]{cousin}
c[female]{cousin}
}
}
}
\end{tikzpicture}
}
\end{document}
(without the tweak - a pure copy-and-paste):
(copy-and-paste plus switching g and p on father and mother nodes):
I think this way is preferable because of the automatic spacing. The manual shift method should be reserved for what the genealogytree manual on page 44 refers to (which I think does not apply here):
Note that in a more complicated situation more manual intervention may
be necessary to avoid unwanted overlapping of other nodes.
Best Answer
Well, there is no program I know of that you could use (currently).
For private use, I do have a such a program which outputs
genealogytreecompatible code, but it is not based on GEDCOM and not suitable for publication. But you may take this information as proof of concept that an automatism could work, even if I know that this must be frustrating.I strongly believe that there should be some software in future that transforms a GEDCOM file (with some selected proband) into
genealogytreesource code. I see the following paths:Direct export out of a genealogy program. I had the (weak) hope that some author would implement such an export module into his/her software (hey, I can use this free tree drawing for my software), but I do not know of any yet.
Implementation of
gedcom2latexas student thesis. Well, I did not find a student yet who is willing to do it (and provide the result as freeware or open source).Implementation of
gedcom2latexby you or anybody else who thinks: why does this tool not exist?Implementation of
gedcom2latexby myself. Actually, I don't need it, because I have my private solution, but I'm tempted to do it for eternal glory ;-) I did not have enough time to follow this path yet...There in an open-source GEDCOM parser http://gedcom4j.org which could be used for
gedcom2latexto build an internal tree which is to be exported asgenealogytreesource...