Search Forums
Kiwitrees on Twitter

    mystyle, last change date, logs, source, events of close relatives, fancy tree view, version, search, 7.2, Search and replace, add, 3.1.1, Relationship, block, calendar.php issue, access level, upgrade, links, login, clippings cart, edit, BURI, media_links, performance, special character, footer, illegitimate, message, error, immigration, session, message contactform, descendant, database, Default record, family, slideshow, type, age, PHP, survey, support, BAPM, 3.0.0, ID notes, tab, flags, clipboard, admin, Favourites 3.0.0, edit menu, ASSO, beta, date, ckeditor, login failure, dropbox. token, contact, pop-ups, bug



    42 posts

    I presume you realise you have to enter the coordinates for each place EVERY TIME it is used in your data with this old method?

    Yes. GM module kept me occupied for a long time.

    The benefit of the GM module is that each place only needs to be added once – EVER.

    No. Due to the specific german history place names changed very often. GM module can’t handle that complexity. Even “normalizing” is not a solution if borders changed a lot.

    So for me it is just the other way around: The “old” code is a time-safer for me!
    😉 Grimpel