Bug filter
Topic Information
ForumSupport for kiwitrees
Last activity6 years, 8 months ago
ParticipantsGrimpel, kiwi

UID, click, cookie, mobile, emigration, reports, events of close relatives, 3.0.0. setup, fact, burial, F.A.B., inactive, relationships, Search and replace, error, fatal error, margin, MYSQL, 3.3.0, Favourites, not married, children, dropbox. token, source, I18N, places, xmas, statistics, Google Maps, cousin tab, blank, progress, last change date, missing data, GEDCOM errors, GEDCOM, search, lists individuals families, census, footer, ckeditor, performance, IE problem, NCHI, date, batch update, Themes change, dead, resources, administration pages, sidebar, lists, individuals, Georgian, sanity, blank screem, logout, responsive menus, zend, drag

Kiwitrees on Twitter

    Topic:   Autocomplete on places  

    Viewing 3 posts - 1 through 3 (of 3 total)
    • Author
    • #1703

      49 posts

      Hi everybody!
      I would like to guide my users to enter places orderly. As I understand autocomplete on places searches only the genealogical database. Optional GeoNames, too. (GeoNames doesn’t work well on german places…)
      In my point of view it would make more sense to search the google maps (wt-)database. (There I could easily import proper hierarchical place names and coords.)
      Did I miss a configuration option or is this just not implented?
      Toodle-oo! Grimpel


      1894 posts

      No, you didn’t miss anything. It is a question asked a few times before, with a complex answer.

      While I don’t entirely disagree with your expectation, there are reasons why autocomplete is only linked to the GEDCOM PLAC data (wt_places table) not the Google Maps data (wt_placelocations).

      1. Not everyone use the Google Maps module, so at the very least the code would need to identify that.
      2. Among those who have it enabled, many still don’t really use it, so have many places missing.
      3. The GEDCOM data is specific to a single family tree, but the GM table is site-wide. It has no tree identifier attached. So a single place might have multiple different spellings, depending on the tree it came from. That could be very confusing for users.
      4. The GM module is secondary to the GEDCOM data. The GEDCOM should be correct first, then the GM data can be created properly to match and supply coordinates.

      I’m sure some of these points could be changed (fixed), but it was always planned that the entire place-handling code would be re-written, though little progress was ever made. It is a VERY complex area.

      My personal kiwitrees site is

      49 posts

      Thank you Nigel for your answer.
      Hmm… I see the complexity (historical place names, translation, defining of areas using coords …) and I haven’t seen a convincing approach at all. In my point of view geotagging entrapped many genealogists to deform their place data by “normalizing”.
      As a newbie it’s sometimes hard to figure out if something is not working well because of my ignorance or a half-baked module 🙂

    Viewing 3 posts - 1 through 3 (of 3 total)
    • The topic ‘Autocomplete on places’ is closed to new replies.