You are right.
If you look at the standard:
you see that a date is or approximated or a range, but not both.

So it is a bug in GRAMPS on GEDCOM export.
This is then one more thing that would get lost if people export to GEDCOM then import back in GRAMPS.

Please, post a bug on the bug tracker, adding all info. I would suggest to indeed have the range identifiers take precedence on approximated qualifiers.
We could however also export this as a text field in Date gramps can parse back in ....


2009/3/2 Christian Möller <>

I've a question (or feature request) regarding GEDCOM export of certain
date field content. Sometimes I'm using estimated date information like
"estimated before 1750" to distinguish persons having the same name but
living at different times. If I know that one of them married in 1765, I
estimate his unknown birth year to be before 1750.

Exporting this data as GEDCOM yields "EST BEF 1750" in the appropriate
line which looks fine at first. But importing the GEDCOM file with some
other program I get "estimated 1750". I've asked on the forum of the
other program and they told me that GEDCOM standard does not support
more than one modifier like "BEF", "EST" and so on: They simply ignore
the second one. Hence "EST BEF 1750" becomes "EST 1750".

So here my question: Is it possible to export "Estimated before 1750" as
"BEF 1750"? I think this would be more adequate compared with "EST 1750".

What do you think?


Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
Gramps-users mailing list