You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I create a link to a specific place, the next GEDCOM import will just continue the numbering, thus invalidating the link and redirecting to location 0 - World. For example if I create the following link to London in my tree
link to London
On the next GEDCOM import, the links probably start at the max of the previous import.
Since webtrees has a table of all locations (optionally with latitude and longitudes for maps), can't the link reference the actual location name and not an ID? At the least, if that table has IDs, it can reference the IDs in that table, something that seemingly does not change (since I see that the maps do not lose their latitude and longitude with every import).
Thanks
The text was updated successfully, but these errors were encountered:
What do you mean by: "If I create a link to a specific place". What kind of "link" are you creating? Can you supply GEDCOM code? Where does this "Link" get added? Normally when we add a place to a fact we add it in the PLAC tag which will give you a dropdown of all the current "Places" in the database.
If I create a link to a specific place, the next GEDCOM import will just continue the numbering, thus invalidating the link and redirecting to location 0 - World. For example if I create the following link to London in my tree
link to London
On the next GEDCOM import, the links probably start at the max of the previous import.
Since webtrees has a table of all locations (optionally with latitude and longitudes for maps), can't the link reference the actual location name and not an ID? At the least, if that table has IDs, it can reference the IDs in that table, something that seemingly does not change (since I see that the maps do not lose their latitude and longitude with every import).
Thanks
The text was updated successfully, but these errors were encountered: