Resumo
- Sorting jurisdictions
- Inputing jusrisdictions
- Register the order of jurisdictions in your Gedcom file
- Globally change formuling of jurisditions
This is an important chapter. A close reading will avoid you some day, from having to rework all your genealogy. Adopting a universal and uniform jurisdictions order, compliant with the Gedcom standart, is mandatory to make easier your exchanges and make the geolocation of the events more accurate.
To create a place, you should classify the different
jurisdictions in growing order of importance, separating
each level with a comma. If a level is empty,
keep the comma.
Advise from Ancestris: unlike certain
practices, don't leave blank spaces between jurisdictions.
It's not mandatory to have them all but you should respect the hierarchy of this order.
|
If you chose ''Distinguish for editing the
jurisdictions for places'' (cf
First Settings) you don't need the following explanations, since you will be
inputing jurisdictions level by level.
For those who didn't choose this option, the easiest way to
explain is an example:
For an event happened in the hamlet of
"Mézin", at Allanche (INSEE code 15160),
Cantal department, Auvergne, France. You should
input:
Depending on the data you inputed, you will see a list that offers
the already known places starting with the same characters,
for you to choose from. → A left click over the suggested line,
click on OK to validate and that's it.
If you selected
"Preferences -
Distinguish jurisdictions...", this function is also present,
but line by line.
![]() Register in the Gedcom file, it is here you should respect the standart organization of the jurisdictions. Displaying places in views, it is the way you will see the jurisdictions in views (for example, choose to just see hamlet and country on tree view - cf Preferences). |
It is important that this places hierarchy (or jurisdictions
order) is described in the header of your Gedcom
file. It's the internal rule, established by the Gedcom file
that allows Ancestris e the other
users to reed the jurisdictions. This record
determines the format of all your "PLAC" tags.
This register should be made imediately whe creating
a genealogy or right after importing a
genealogy created with another programa
(many do not respect the standart).
0 HEAD 1 SOUR ANCESTRIS 2 VERS 0.10.0.1291 2 NAME Ancestris 2 CORP Ancestris Team 3 ADDR http://www.ancestris.org 1 DEST ANY 1 DATE 21 MAR 2011 <---- the date will be diferent 2 TIME 18:44:12 <---- the time will be diferent 1 SUBM @B1@ <---- you might not have this line 1 FILE john.ged <---- here is where your file name will be 1 GEDC 2 VERS 5.5 2 FORM Lineage-Linked 1 CHAR UTF-8 1 LANG English
It will suffice to add, right after the line ''1 LANG English'', the following two lines:
1 PLAC 2 FORM Hamlet,City,,Zip_Code,County,State,CountrySave your work, and that's it, job done!
If you
already have hundreds of places on your
file, the simple fact of adding these two lines to the header
of the Gedcom file, doesn't change anything in these already
registered places. The only alternate solution would be
go through all of them one by one.
|
You notice, after finishing, that you have
a typo on a place. Another possibility,
the same location was entered twice
in different ways.
With just a few clicks you can change every place involved:
|
|