Question option to add data in entire tree

I want to have an option to add data in the entire tree in Gedcom mode.
E.g. in my Gedcom file:
2 PLAC Amsterdam, NH, NLD
should be:
2 PLAC Amsterdam
3 _LOC @L3120@

I know I can download the file, make changes to the downloaded file and upload it again.

Best regards,
Marianne

Interesting question!

I suspect you could use a "regular expression" search.

But I would not know how!

Use regular expression search&Replace for individuals and families (and others if relevant):

Search: 2 PLAC Amsterdam, NH, NLD\n
Replace: 2 PLAC Amsterdam\n3 _LOC @L3120@\n

Check it before applying it to all records. And you lose the place hierarchy using PLAC. Why do you do it? I do not recommend that.

mariannevanharten wrote:

I want to have an option to add data in the entire tree in Gedcom mode.
E.g. in my Gedcom file:
2 PLAC Amsterdam, NH, NLD
should be:
2 PLAC Amsterdam
3 _LOC @L3120@

If I had the above, I would first use search/replace to change it to then I would use the Vesta data fixes to complete the _LOC records and sub-records.

I have never really understood this aspect of the _LOC record design.

There seems to be a one-to-one mapping from PLAC to _LOC.
So why does it need to be copied everywhere?

A simpler and more reliable design might be to map the place name to the corresponding location name.
i.e. if you have PLAC Amsterdam, you display data from the _LOC record with the name Amsterdam.

The links seem pointless and redundant...

fisharebest wrote:

There seems to be a one-to-one mapping from PLAC to _LOC.
So why does it need to be copied everywhere?

A simpler and more reliable design might be to map the place name to the corresponding location name.
i.e. if you have PLAC Amsterdam, you display data from the _LOC record with the name Amsterdam.

Initially I thought so as well. Therefore, there is an option in the Vesta Shared Places module to handle it just like this, i.e. link to the _LOC-records via place name, without having to enter the link explicitly. I wouldn't recommend to use it like that though:

The Gedcom-L addendum specifies otherwise, and having explicit links is anyway more efficient for calculations (list of individuals related to a _LOC etc) because the respective database table wt_link can be used. Note that when entering new events, you only have to select the _LOC link, from which the place name will be filled in automatically, so you usually do not have to copy it manually.

There is another advantage when using explicit links to _LOC-records: You can now use the proper historic place name and hierarchy for events at different times at the same actual place, while still linking to a single _LOC.

Greg,

I don’t know how other people do it, but my “Location” place records are for very place in the hierarchy.

So I have a location record for all the farms in Norway my family lived, and separate location records for the kommune, Fylke, and Norway itself. Same for USA, Germany, and the place hierarchy of each country.

I’m not sure how I did this, it was automatic I think. I’m also on an early version of Vesta in v2.0 of webtrees.

I use the most specific location record to detail with pictures and words the farm, city, or business, but also sometimes write up stuff about the other levels as well to support my family that don’t know about locations or regions in Norway, Germany, USA.

It was my hope to use this detail (extract it out of the database) for use in books and other documents to tell the story of the places, countries our ancestors lived or worked.

My greater hope was the we did not use _LOC links to LOCATION records, but have created the same data in the webtrees place hierarchy, but this will work too!

Correction:

Not all PLACes in my hierarchy have corresponding _LOC records, I guess it was not automagically done.

I’ll have to review how I did it! But never the less I still have _LOC records for each of the levels I did create!

Personally, I think PLAC should have been treated like NOTE—either inline, or an xref to a shared PLAC. Doesn't make sense to me to repeat coordinates and such in so many records.
Would still be reasonable to have with a in the other one

norwegian_sardines wrote:

… Not all PLACes in my hierarchy have corresponding _LOC records, I guess it was not automagically done. …

These can be automatically created by the data fixes that Vesta installs.