Search Forums
Kiwitrees on Twitter

    index, php 7, cookie, design, Batch Updates, FAQ, 3.0.0 widgets, version, survey, IE11, chart, Georgian, default individual, notes, xenea, latest version, permissions, clippings cart, future, set link, locked out, icons, add_asso_facts, 3.3.3, blank screem, library, illegitimate, statistics, 1939 Register, MYSQL, html, styles, webtrees, users, style, colors theme, help, datatables, calendar.php issue, 3.2.3, feedback, 2.0.2, place, tab, defacto, menu, upgrade, gender change, follow, abbreviate, burial, My Page, pop-ups, fancy image bar, watermark, progress, editor, tree, beta, census assistant


    110 posts


    This question sent me back to look at the GEDCOM standard. It parallels my personal thought.

    I consider BAPM and CHR the same event and on the occasion of a merge, convert CHR events to BAPM as my personal choice as the default event.

    I treat BURI and CREM as two distinct events generally for the reason you stated. I think some religions and other traditions only allow cremation when burial or placement in a Columbarium follow. I currently report placement in a Columbarium as a burial.

    Dealing with these two events, really hasn’t been a big issue for me. It is just another challenge of trying to standardize/simplify reporting how the peoples in a diverse world lived and died.



    Apache 2.4.27  PHP 7.19 MariaDB 10.2.8