Managing places


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.



CAUTION : before any modifications, make a backup of your gedcom file.

Sorting the jurisdictions

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.

Seven levels of jurisdiction are possible:
Hamlet,City,,ZIP_Code,County,State,Country

It's not mandatory to have them all but you should respect the hierarchy of this order.

Although Ancestris allows to input the ZIP code, it is preferable to use the INSEE code. As a matter of fact, a ZIP code can group more cities while the INSEE code (geographic codding system created in 1943), is unic for each city (only valid in France).


Inputing jurisdictions

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:

Jurisdictions input screen.

It's simple, to remember: ''From the smalest to the greates and each term is comma separated''.

Auto-complete field

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.


Do not confuse registering to the Gedcom file with displaying on the views.

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).

Register jurisdctions order in the Gedcom file

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).


Global change of the formulation of jurisdictions

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:



Previous page

 

Next page