Changes

Jump to: navigation, search

Places in Gramps

2,074 bytes added, 00:15, 20 December 2016
no edit summary
{{languages|Places in Gramps}}
 
An overview of countries with the relevant genealogical information about them:
* genealogical organisations with contact information
* digital archives you can consult online (free or fee based) with an appraisal
* location of archives, and how to consult sources there
* relevant history of the country viz-a-viz genealogy
* pointers to locations in the country, with details (as always, relevant to genealogy, eg an abbey of which many sources are available, ...)
== What is a Place? ==
 
A [[Gramps_Glossary#P|Place]] in Gramps generally refers to where an event occurred. This is different to an Address (see for example [[Why residence event and not Address%3F]]).
The {{icon|plac}} [[Gramps_3.4_Wiki_Manual_-_Main_Window#Places_Category|Places View]] lists all the places in your Gramps database, and A place is a handy spot geographical region of any size ranging from that of a country to make sure your places are named consistentlya burial plot. Boundaries of a place may vary over time. The latitude and longitude of an approximate centre point can be recorded.
== Organising your Places ==There are several ways you could organise your places. The concept of a place in genealogy is very complex, due both to the level of detail you wish to capture, A Gramps ID and the changes over time to the name of a place. Ultimately how much of this complexity you record in your database is up to you, but you will probably find it advantageous to consider your options before you have too many places in your datatype can be specified.
The summary below indicates some of the ways current Gramps users organise their placesNotes and media can also be attached to a place.
=== Place hierarchy =names ==Gramps stores places in a hierarchy. Places at the top of the hierarchy are usually countries. The level of detail increases the further the place is down the hierarchy. Places at the bottom of the hierarchy represent small areas such as individual houses or burial plots. The hierarchy can contain any number of levels.
For example, Hobart in Australia would be stored as three places: Australia, Tasmania, and Hobart. Australia would be at the top level of the hierarchy and have a A place type of ''Country''. Tasmania would be at the next level down and have is identified by a place type of ''State''. Hobart would have a place type of ''City'' name which may change over time and would can be stored entered in different languages. For example, the next level below ''State''. Any city of these three places Saint Petersburg in Russia could be referenced in an event.defined with the following names:
=== Level of detail ===* Санкт-Петербу́рг (1703-1914) [ru]The level of detail recorded for a place affects the number of places you have. One option is to not include detail finer than town or city in a place, in which case the ''Street'' field is always left empty. When further detail is to be recorded for an event, it can go in a note associated with that event. This has the advantage that your places are easier to manage, and can appear more consistent in reports. A disadvantage is that you may need to include the same note text against many events, for example if they all occurred at the one address. * Петрогра́д (1914-1924) [ru]In Gramps 3.0 you can have multiple notes, making copy/paste of this address in a note easier. You could also add the place ones to the source used for the event. Another possible disadvantage is that the place details may not be displayed in reports in the way you wish.* Ленингра́д (1924-1991) [ru]* Санкт-Петербу́рг (1991-) [ru]* Saint Petersburg (1703-1914) [en]* Petrograd (1914-1924) [en]* Leningrad (1924-1991) [en]* Saint Petersburg (1991-) [en]
The other extreme Assuming the default Places [[Gramps_4.2_Wiki_Manual_-_Settings#Places|Preferences]] settings of auto-generation of titles is to specify as fine detail as possibleenabled, automatic place title generation will choose the appropriate name, which may involve putting a lot given the date of information into an event and the language code specified in the preferences. Where there is no event date available, or if the place is displayed without reference to an event, then today''Street'' field. A drawback s date is that you will end up with a very large number of Place entriesused.
An approach that Each name is processed in turn. A name is matched if the date range contains the event date and the language code is between the above two involves treating a place same as a geographic location on the Earthlanguage preference setting. The land use (e An empty date range is interpreted as matching any date.g. St Luke's Church) would be If there is no language code match, names defined with an empty language code are used as a note. How you identify the geographic location may not always be obvious: a street address (e.g. 25 High St) will often be sufficientfallback.
=== Changes over time ===A given place can change its The main name over time. This change may be as minor as a change in street number or name, or a complete change in name of town and country. There are different ways of recording this, but most people seem to choose one name which they list on is processed before the Location tab, and the other alternative names go on the Alternate Locations tab.
Some put [[File:SaintPeterburgFullNames.png|600px|thumb|right|Fig. 1. Saint Petersburg Place example]]For example, Figure 1 shows the Place view for the above described Saint Petersburg. Note the order of the modern day details in entries, the Location tabdate ranges, and historical details under Alternate Locationsthe language codes. This has at least two drawbacks:{{-}}
# You may [[File:EventViewSaintPeterburgPlace.png|600px|thumb|right|Fig. 2. Saint Petersburg Event example]]Events can be created at specific dates for this place and the title generation will follow the rules above. In the first event in Figure 2, the title generated is '?' because the place has no entries for this date (1500 is not know between 1703 and today). In the second event in Figure 2, the generated title - Петрогра́д - corresponds to the first place that matches the date range since the language preference setting is blank. In the fourth event, again the generated title is the modern day details for a first place that matches the date range. Note that the order of the Alternate Names in Figure 1 is important in title generation when entering itthe default language is blank.If the Language is specified in the Places [[Gramps_4.2_Wiki_Manual_-_Settings# Places|Preferences]], then that language will be used if found. If the modern details changelanguage is not found, you have to remember to update everythingthe first date match will be used.
Other people prefer to put in the Location tab the details as they were The title generation is done at the time of the eventupdate, and it not refreshed if the modern details under Alternate LocationsPlace is edited. This also In the case where the Place is not perfectupdated, the event would have to be subsequently updated as you need well to decide what to do if you have two different events at regenerate the title with the same place, but separated corresponding change in time such that the place details differ. You would make two different places then, for the same placePlace.{{-}}
=== ''Place Name'' field hierarchy ===The first field in the Edit Place window is generally displayed where space is limited, such as in some graphical reports. Therefore some people like to put in here a short descriptive name.
Other people prefer this field [[File:SaintPeterburgPlaceHierarchy.png|600px|thumb|right|Fig. 3. Saint Petersburg Place Hierarchy example]]Places can be linked together to be form a repeat of all hierarchy. This enables different places with the fields in the location tab in the bottom of the window. It can same name to be listed either distinguished from the most specificeach other. For example, or the least.there are also places called Saint Petersburg outside of Russia:
For example, for a location of ''Street'': Rundle Mall, ''City:'' Adelaide, ''State:'' South Australia, ''Country:'' Australia, ''Postal Code:'' 5000, different people would set the ''Place Name'' field to one of:* Saint Petersburg --> Russia* Saint Petersburg --> Colorado --> USA* St. Petersburg --> Florida --> USA* St. Petersburg --> Pennsylvania --> USA
* Rundle Mall* Rundle MallA title can be generated by following the links. So "Saint Petersburg, Adelaide* Rundle Mall, Adelaide, South Australia, 5000, Australia* Australia, 5000, South Australia, Adelaide, Rundle MallRussia" would describe the city in Russia. Figure 3 illustrates the Place Editor view (with autogenerated titles) for these cities.
There are{{-}}[[File:AlsacePlaceHierarchy.png|600px|thumb|right|Fig. 4. Alsace Place Hierarchy example]]The place hierarchy can also be used in filters, of course, also minor variations on those listed aboveto find all places located in another place.
Some people ensure Multiple links with date ranges are allowed. This makes possible more complex cases where a place moves from being located within one place into another. Alsace makes a good example: * Alsace -(1618–1674)-> Holy Roman Empire* Alsace -(1674–1871)-> France* Alsace -(1871–1918)-> Germany* Alsace -(1919–1940)-> France* Alsace -(1940–1944)-> Germany* Alsace -(1945–)-> France {{-}}[[File:EventViewAlsacePlace.png|600px|thumb|right|Fig. 4. Events with different dates in Alsace example]]Figure 5 is the ''Event Editor view which illustrates that the generated title for an event is based on the date of the event when traversing the place hierarchy. {{-}} == Source description == Places in the hierarchy provide standardized titles. Event attributes with a key of "Place Name'' field has everything they want" can be used to record places as described in a source. This allows spelling variations to be recorded without the need to create extra places. It also allows more than one place to be recorded for an event. For example, an event in Saint Petersburg could have two citations. One may describe the place as "Saint Petersburg" and they leave the Location tab emptyother "St. Petersburg".
== Editing Places ==
[[Image:Edit-Place-1.png|300px|thumb|right|Fig. 1. Example Edit Place dialogue]]
The {{icon|plac}} [[Gramps_4.2_Wiki_Manual_-_Categories#Places_Category|Places Category View]] lists all the places in your Gramps database, and is a handy spot to make sure your places are named consistently. Gramps also provides a [[Gramps_4.2_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Place_Editor_dialog|window in which you can edit a place]]: [[File:Place editor 42.png|450px|thumb|right|Fig. 5. Example Edit Place dialogue]] Enter the ''Name'' and ''Type'' of the place in the fields provided. The ''ID'' field will be populated automatically by Gramps. The ''Code'' can be used to store a country code or postal code. The region in which the place belongs should be recorded in the ''Enclosed By'' tab. Every place except for countries should have at least one entry. Multiple entries are useful to record a place that has been part of different administrative regions over time. The first entry in the list will be used to construct default place titles. Variations of a place name over time or different language versions, can be recorded in the ''Alternative Names'' tab.{{-}} == Known Issues == * The place views and event editors always display the modern place title.* The mechanism for selecting an existing place or adding a new place needs improving.* The place tree view only displays each place once.* Using an empty language code for endonyms, makes entering some place names cumbersome. == Possible future enhancements ==
Use * Time dependent place types* Hierarchy types in links between places* Import from the [[Place completion tool]] to help automate the management of your places, as this allows you to edit several places in one go. It is also an easy way to determine and include [[GeoCodesGOV database (See {{bug|8974}})* Experimental place gazetteer (See: {{bug|latitude and longitude]] of cities and towns.8812}})
{{-}}
Retrieved from "https://gramps-project.org/wiki/index.php/Special:MobileDiff/49397...62385"

Navigation menu