advent, nickname, backup, .po, REFN, fact, Search and replace, Georgian, hover, descendant, close, shared note, follow, NCHI, individual resource, search, 3.0.0. setup, login upgrade, 500, release, 2.0, request, contact links, redirect, advanced, FAQ, webtrees, edit menu, dates, blank, simpl_research, Histo, survey, permissions, custom modules, 3.3.5, My Page, Support/Bug Reporting, links, icons, inactive, 5.6, type, googlemaps, gettext, Google Maps, age, roadmap, fancy tree view, notes, save settings, 3.2.0, click, source, defacto, footer, 3.0.0 widgets, events of close relatives, flags, feedback

Kiwitrees on Twitter

    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