https://blog.gramps-project.org/wiki/api.php?action=feedcontributions&user=Nomeata&feedformat=atomGramps - User contributions [en]2024-03-29T15:19:30ZUser contributionsMediaWiki 1.31.3https://blog.gramps-project.org/wiki/index.php?title=Gramps_3.0_Wiki_Manual_-_Main_Window&diff=5723Gramps 3.0 Wiki Manual - Main Window2008-03-26T11:04:16Z<p>Nomeata: /* Notes View */</p>
<hr />
<div>{{grampsmanualcopyright}}<br />
<br />
<br />
{{languages}}<br />
<br />
<br />
== Introduction ==<br />
<br />
When you open a database (either existing or new), the following window is displayed:<br />
[[Image:Mainwin.png|right|thumb|200px|Fig. 2.1 GRAMPS Main Window]]<br />
<br />
The main GRAMPS window contains the following elements:<br />
<br />
*Menubar: The menubar is located at the very top of the window (right below the window title) and provides access to all the features of GRAMPS.<br />
<br />
*Toolbar: The toolbar is located right below the menubar. It gives you access to the most frequently used functions of GRAMPS. You can set options that control how it appears by going to ''' Edit ->Preferences ''' . You can also hide it entirely by going to ''' View ->Toolbar ''' .<br />
<br />
*Progress Bar: The Progress Bar is located in the lower left corner of the GRAMPS window. It displays the progress of time consuming operations, such as opening and saving large databases, importing and exporting to other formats, generating web sites, etc. When you are not doing these types of operations, the Progress Bar is not shown.<br />
<br />
*Status Bar: The Status Bar is located to the right of the Progress Bar, on the very bottom of the GRAMPS window. It displays information about current GRAMPS activity and contextual information about the selected items.<br />
<br />
*Display area: The largest area in the center of the GRAMPS window is the display area. What it displays depends on the currently selected View. We'll discuss Views in detail below.<br />
<br />
== The Different Views ==<br />
<br />
Genealogical information is very broad and can be extremely detailed. Displaying it poses a challenge that GRAMPS takes on by dividing and organizing the information into a series of Views. Each View displays a portion of the total information, selected according to a particular category. This will become clearer as we explore the different Views, listed below:<br />
<br />
*Gramplet View: Displays different Gramplets, small widgets that can help in your genealogical research.<br />
<br />
*People View: Displays the list of people in the family tree<br />
<br />
*Relationships View: Shows the relationships between the Active Person and other people. This includes parents, spouses, and children<br />
<br />
*Family List View: Shows the list of families in the family tree<br />
<br />
*Pedigree View: Displays a graphical ancestor tree for the selected person<br />
<br />
*Events View: Displays the list of events in the family tree<br />
<br />
*Sources View: Displays the list of sources in the family tree<br />
<br />
*Places View: Displays the list of places in the family tree<br />
<br />
*Media View: Displays the list of media objects in the family tree<br />
<br />
*Repositories View: Displays the list of repositories in the family tree.<br />
<br />
*Notes View: Displays the list of notes in the family tree.<br />
<br />
Before we launch into a description of each View, let's first explain how to switch between Views.<br />
<br />
== Switching Views and Viewing Modes ==<br />
[[Image:Mainwin.png|right|thumb|150px|Fig. 2.1. Sidebar view mode]]<br />
[[Image:Noside-nofilt.png|left|thumb|150px|Fig. 2.2. Tabbed Viewing Mode]]<br />
<br />
<br />
<br />
As mentioned above there are nine different Views. In addition, there are two different Viewing Modes. You can tell at a glance which Viewing Mode you are in: If you see icons listed vertically in a sidebar at the left of the window, you are in the Sidebar Viewing Mode.<br />
.<br />
<br />
If instead you see a series of "notebook tabs" (labeled People, Relationships, Family List, Pedigree, Events, Sources, Places, Media and Repositories) that run horizontally across the window, then you are in the Tabbed Viewing Mode. You can switch from one Viewing Mode to another by selecting ''' View ->Sidebar ''' from the Sidebar menu item.<br />
<br />
If you're in the Sidebar Viewing Mode, you can select the View you want by clicking one of the sidebar icons.<br />
<br />
<br />
If you're in the Tabbed Viewing Mode, you can select the View you want by clicking the corresponding notebook tab.<br />
<br />
== Gramplets View ==<br />
[[Image:Grampletsview.png|right|thumb|200px|Fig.2.z Gramplets view]]<br />
<br />
The Gramplets view shows a number of widgets, called Gramplets, that can help you in your research. Two Gramplets are shown on start-up (the Welcome and Top Surname Gramplets), but by right-clicking on the view, a popup comes up with the possibility of adding other Gramplets. <br />
<br />
For more detailed information see [[Gramps 3.0 Wiki Manual - Gramplets|Gramplets]]. Here we give an overview of the functionalities.<br />
<br />
*Age on Date Gramplet: This gramplet computes the ages for everyone in your Family Tree on a given date<br />
*Calendar Gramplet: Shows events on particular days and years<br />
*News Gramplet: Retrieves the News page from the GRAMPS wiki<br />
*Pedigree Gramplet: Shows a compressed Pedigree Chart of past direct ancestors. Also gives a breakdown by generation. Click the links to see matching entries<br />
*Python Gramplet: Shows a window with a Python Shell. This is especially handy as a Date calculator, or for a quick access to Python<br />
*Session Log Gramplet: Shows a log of entries accessed, edited, for deleted for this session.<br />
*Statistics Gramplet: Shows a window with summary statistics of the current {{man label|Family Tree}}: number of individuals, males and females, number of families, media objects, etc. <br />
*Surname Cloud Gramplet: Shows a window with a '''cloud''' of the most common {{man label|Surnames}}. <br />
*TODO Gramplet: In this window you can add yout TODO list, or any notes. Several TODO gramplets can be made to help organize your research<br />
*Top Surnames Gramplet: Shows your '''top 10''' Surnames<br />
*Welcome Gramplet: A '''Welcome to GRAMPS''' window<br />
<br />
== People View ==<br />
[[Image:Column-editor.png|right|thumb|150px|Fig. 2.3. Column Editor Dialog ]]<br />
The People View lists the people stored in the database. You'll note that people are grouped according to their family names. To the left of each family name is typically either an arrow or some other type of indicator. Clicking it once will reveal the entire list of people sharing that name. Clicking the indicator again will "roll up" the list and show only the family name.<br />
<br />
By default, the People View, displays the several columns of information about each person. You can add or remove columns to and from the display by calling up the '''Column Editor''' dialog ( ''' Edit ->Column Editor ''' ) and checking or unchecking the boxes listed. You can also change the position of a column in People View by clicking and dragging it to a new position in the Editor. Once you have made the changes you want, click '''OK''' to exit the Editor and see your changes in the People View.<br />
<br />
{{man note| Column Editor |The Column Editor is available in all Views and works the same way in each.}}<br />
<br />
[[Image:Side-filt.png|right|thumb|150px|Fig. 2.4. Filter Controls Displayed ]]<br />
<br />
Filters<br />
<br />
Genealogical databases can contain information on many people, families, places, and objects. It's therefore possible for a View to contain a long list of data that's difficult to work with. GRAMPS gives you two different means for controlling this condition by allowing you to filter a list to a more manageable size. These methods are Search and Filtering. A search will search the text displayed in list, whereas filters display people whose data match the criteria of the filter.<br />
<br />
Search is a simple but fast method of searching the columns displayed on the screen. Typing the characters into the Search box and clicking the Find button will display only lines that match the text.<br />
<br />
Alternatively, you can enable the Filter sidebar, which will be displayed on the right hand side of the display. When the filter sidebar is displayed, the Search bar is not displayed. The Filter side bar allows you to interactively build a set of filter rules that can be applied to the display. The filter is applied based on the rules and the data, not on the screen display.<br />
<br />
{{man tip| Searching vs. Filtering |Searching only searches for exact text matches. If the date displayed is "Jan 1, 2000", a search of "1/1/2000" will fail, but a filter of "1/1/2000" will match.}}<br />
<br />
<br />
When GRAMPS opens a database, no filtering is in effect. In People View, for example, all people in the database are listed by default.<br />
<br />
== Relationships View ==<br />
<br />
The Relationships View displays all the relationships of the Active Person (the selected person). Specifically, it shows his or her parents, siblings, spouses, and children.<br />
<br />
The Relationships View is designed to allow for quick navigation. You can quickly change the Active Person simply by clicking the name of any person listed on the page. Each name is actually a hypertext link, similar to a web page.<br />
[[Image:Family.png|right|thumb|150px|Fig. 2.5. Relationships View]]<br />
<br />
The Relationships View displays the following sections:<br />
<br />
*Active Person: At the top of the screen, name, ID, birth, and death information of the Active Person is displayed. If a photo of the person is available, it is shown on the right hand side. Next to the person's name is a symbol indicating gender, and an Edit button. Clicking the '''Edit''' button will allow you to edit all of the person's individual information in an '''Edit Person''' dialog.<br />
<br />
*Parents: The next section, the Parents section, displays the families in which the person is a child. Since it is possible for a person to have multiple sets of parents, it is possible to have several Parents sections.<br />
<br />
You can control how much information is displayed by using the View menu. The view menu allows you to show or hide details (the birth and death information) and to show or hide siblings. Next to each person listed is an {{man button|Edit}} button, which will allow you to edit all the details of that particular person.<br />
<br />
You may add a new set of parents by either selecting the '''Add Parents''' or the '''Share Parents''' . The {{man button|Add Parents}} button will create a new family with the Active Person listed as a child. The {{man button|Share Parents}} button will allow you to choose from a list of existing families, and then add the person as a child to that family.<br />
<br />
You may edit an existing parents by selecting the {{man button|Edit}} button next to the parents. If you select the '''Delete''' next to a set of parents, then the Active Person will be removed as a child from the parents. This button does not delete the parents' relationship.<br />
<br />
{{man warn| Warning |If you are not careful, it is possible to create multiple families with the same parents. This is rarely what the user wants to do. If you attempt to add a new family that has the same parents as an existing family, GRAMPS will issue a warning dialog. If you get this dialog, you should probably Cancel the edit, and then use the '''Select''' button to select the existing family.}}<br />
<br />
<br />
*Family: Similar to the Parents section is the Family section, which displays families where the Active Person is a parent. Because it is possible to have multiple families, it is possible to have multiple Family sections. Each family section displays the spouse and any children.<br />
<br />
{{man note | Spouse |We use the term spouse for sake of simplicity. However, please note that spouse may in fact be a domestic partner, a partner in a civil union, or various other similar relationships between two people. Spouse relationships are not required to be only between a male and female.}}<br />
[[Image:Reorder.png|right|thumb|150px| Fig.2.x Relation reordering]]<br />
You may add a family by selecting the '''Add Spouse''' in the toolbar. This will create a new family with the Active Person listed as a father or mother.<br />
<br />
Selecting the Edit button next to the spouse will allow you to edit the displayed family. Clicking the Delete button will remove the person from the displayed family.<br />
<br />
{{man warn| Remove a person |Removing a person from a family does not delete the family. The person is removed as the father or mother, and any other relationships in the family continue to exist.}}<br />
<br />
{{man note | Note |We use the terms father and mother for the sake of simplicity. Even if there are no children in a family, the father and mother terminology is still used. In the case of male/male or female/female relationships, the father and mother labels should be considered to be convenience labels.}}<br />
<br />
You can reorder the parents and spouses by selecting the '''Reorder''' . This option will only be enabled if more than one set of parents or more than one set of spouses exists for the Active Person. Selecting this button will display a dialog that will allow you to reorder the families.<br />
<br />
== Family View ==<br />
[[Image:Family_List.png|right|thumb|150px|Fig. 2.x. Family List View ]]<br />
<br />
The Family List View displays a list of all families in the database. From this view, you may add, edit, or delete families. The default display lists the ID, Father, Mother, and Relationship. Children cannot be displayed on the screen in this view.<br />
<br />
{{man warn| Remove button |Unlike the Relationships View, clicking the Remove button in this view will remove the family from the database. All people will remain, but all relationships between the people in the family will be removed.}}<br />
<br />
== Pedigree View ==<br />
[[Image:pedigree.png|right|thumb|150px|Pedrigree view]]<br />
The Pedigree View displays a family tree of the Active Person's ancestors. The Pedigree View shows up to five generations, depending on the size of the window. Each person is indicated by a box labeled with his or her name, birth and death information, and optionally an image if available. Two lines branch from each box. The top one shows the person's father and the bottom one the mother. Solid lines represent birth relations, while dashed lines represent non-birth relations such as adoption, step-parenthood, guardianship, etc.<br />
<br />
<br />
To the left of the Active Person is a left arrow button. If the Active Person has children, clicking this button expands a list of the Active Person's children. Selecting one of the children makes that child the Active Person.<br />
[[Image:pedigree-child-cut.png|right|thumb|150px|children menu]]<br />
<br />
The appearance of the children's names in the menu differentiates the dead ends of the tree from the continuing branches.<br />
<br />
Children who have children themselves appear in the menu in the boldface and italic type, while children without children (dead ends) appear in a regular font. If the Active Person has only one child, no menu will be displayed (since there is only one choice) and the child will become the Active Person when the arrow button is clicked.<br />
<br />
<br />
<br />
The right-hand side of the window shows two right arrow buttons. When the top button is clicked, the Father of the Active Person becomes the Active Person. When the bottom button is clicked, the Mother of the Active Person becomes the Active Person.<br />
<br />
[[Image:pedigree-siblings-cut.png|right|thumb|150px|Personal context]]<br />
<br />
Right-clicking on any person's box in the Pedigree View will bring up the "context menu".<br />
<br />
Among other useful items, the context menu has sub-menus listing '''Spouses''' , '''Siblings''' , '''Children''' , and '''Parents''' of that person.<br />
<br />
"Greyed-out" sub-menus indicate the absence of the data in the appropriate category. Similar to the children menu above, Childrens' and Parents' menus distinguish continuing lines from dead ends.<br />
<br />
<br />
New in version 2.2 is the inclusion of an Events View.<br />
<br />
Events can be shared between multiple people and multiple families. The Events View lists the all the events recorded in the database.<br />
<br />
== Events view ==<br />
<br />
The default view displays the '''Description''' , '''ID''' , '''Type''' , '''Date''' , '''Place''' and '''Cause''' of the event.<br />
[[Image:events.png|right|thumb|150px|Fig. 2.x Events view]]<br />
<br />
{{man warn| Meaningful event description |Because events can be shared, you should take the extra time to give each event a unique and meaningful description. This will help you find the correct event if you decide to share events.}}<br />
<br />
The list of Events can be sorted in the usual manner, by clicking on the column heading. Clicking once sorts in ascending order, clicking again sorts in descending order. The {{man label|Column Editor}} dialog can be used to add, remove and rearrange the displayed columns.<br />
<br />
== Sources View ==<br />
[[Image:sources.png|right|thumb|150px|Fig.2.x Sources view]]<br />
Sources View lists the sources of certain information stored in the database.<br />
<br />
These can include various documents (birth, death, and marriage certificates, etc.), books, films, journals, private diaries, - nearly anything that can provide genealogical evidence. GRAMPS gives you the option to provide a source for each event you record (births, deaths, marriages, etc.). The Sources View lists the '''Title''' , '''ID''' , and '''Author''' of the source, as well as any '''Publication''' information that may be associated with it.<br />
<br />
The list of Sources can be sorted by clicking on a column heading.<br />
<br />
Clicking once sorts in ascending order, clicking again sorts in descending order. The {{man label|Column Editor}} dialog can be used to add, remove and rearrange the displayed columns.<br />
<br />
== Places View ==<br />
[[Image:places.png|thumb|150px|Fig. 2.x.Places view]]<br />
<br />
The Places View lists the geographical places in which the events of the database took place. These could be places of birth, death, and marriages of people, as well as their home, employment, education addresses, or any other conceivable reference to the geographical location. The Places View lists the places' '''Name''' , '''ID''' , '''Church Parish''' , '''City''' , '''County''' , '''State''' , and '''Country''' . All of these columns can be used for sorting by clicking on a column heading.<br />
<br />
Clicking once sorts in ascending order, clicking again sorts in descending order. The {{man label|Column Editor}} dialog may be used to add, remove and rearrange the displayed columns.<br />
<br />
If a place has been highlighted, you may select the {{man button|Google Maps}} button to attempt to display the place in a web browser.<br />
<br />
Your default web browser should open, attempting to use either the longitude and latitude coordinates or the place name to display the location using the Google Maps web site.<br />
<br />
This feature is limited, and may not always produce the results you desire.<br />
<br />
== Media View ==<br />
[[Image:media.png|right|thumb|150px|Fig.2.x.Media view]]<br />
<br />
<br />
The Media View is a list of Media Objects used in the database.<br />
<br />
Media Objects are any files that relate somehow to the stored genealogical data.<br />
<br />
Technically, any file can be stored as a Media Object. <br />
<br />
Most frequently, these are images, audio files, animation files, etc. The list box on the bottom lists the '''Name''' , '''ID''' , '''Type''' , and '''Path''' of the Media Object.<br />
<br />
The {{man label|Column Editor}} dialog may be used to rearrange the displayed columns, which obey usual sorting rules. The top part of the GRAMPS window shows a preview (if available) and information about the Media Object.<br />
<br />
== Repositories View ==<br />
[[Image:repository.png|thumb|150px|Fig.2.x.Repositories view]]<br />
<br />
Version 2.2 adds support for Repositories.<br />
<br />
A repository can be thought of as a collection of sources.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Each source in the database can reference a repository (such as a library) in which it belongs. The functionality of the Repositories View is similar to the other views.<br />
<br />
== Notes View ==<br />
[[Image:Notesview.png|right|thumb|200px|Fig.1.y Notes view]]<br />
Version 3.0 added support for Notes. A Note is pure text, as stored in the other objects.<br />
<br />
<br />
<br />
The functionality of the notes View is similar to the other views. The view lists all {{man label|Notes}} stored in the {{man label|Family Tree}}. With the '''Edit ->Column Editor''' you can change the displayed columns. The possibilities are {{man label|Preview}}, {{man label|ID}}, {{man label| Type}} and {{man label|Marker}}.<br />
<br />
<br />
<br />
The {{man label|Type}} can be (amongst others): ''Event Note'', ''Adress Note'',''Source text'', ''Place Note''<br />
<br />
Double-clicking on a Note in the list will bring up a window where you can edit the Note. You can change fonts, font color and backgroundcolor. A spellchecker is available for ''English'' and your local language.<br />
<br />
<br />
{{man index|Gramps 3.0 Wiki Manual - Getting Started|Gramps 3.0 Wiki Manual - Manage Family Trees}}<br />
<br />
<br />
[[Category:Documentation]]<br />
<br />
<br />
{{languages}}</div>Nomeatahttps://blog.gramps-project.org/wiki/index.php?title=Addon:Place_completion_tool&diff=3494Addon:Place completion tool2007-08-11T12:07:21Z<p>Nomeata: </p>
<hr />
<div>[[Category:Proposed_Tool_Specifications]]<br />
A tool to bring the places in your GRAMPS database in accordance with the GRAMPS requirements: batch add country, county; look-up latitude-longitude; set description (title); ...<br />
<br />
This tool '''only''' works with version 2.2.5+ of GRAMPS! [[Place_completion_tool#Download|Download beta]].<br />
<br />
[[Category:Plugins]]<br />
<br />
== Place Completion tool ==<br />
This tool helps you fill in the place attributes like county, country, ..., by allowing you to select the places you work on, and do changes on all these places with one button click.<br />
<br />
The general aims are:<br />
*Place/Location is a newer concept in GRAMPS. Many older databases only have a Place title field which is a descriptive text containing city, state, country. This should be parsed to insert the values in the correct attribute fields.<br />
*Latitude and longitude are important to show data on a map. However, doing a look-up of this data on the internet is slow and time consuming. The tool allows to search in the free resources on the net.<br />
*Setting of an attribute of a set of places in one go. Eg you give a <br />
*Conversion of latitude and longitude to a fixed data format. On import one might obtain latitude and longitude in several different formats. A conversion tool to store them all in the same format is usefull.<br />
*Construction of a uniform title/description field, from the data in the place object<br />
<br />
== Design Specification ==<br />
See [[Place completion tool specification]]<br />
<br />
== Manual ==<br />
The place completion tool gives a lot of functionality. This manual should help you to understand how it works.<br />
<br />
=== Download resources ===<br />
The place completion tool can look up for you latitude/longitude, add county information (USA), ... . For some of this functionality, you must download datafiles of the countries you are interested in. Right now you have three options:<br />
<br />
#Download geonames country files. You can do this [http://download.geonames.org/export/dump/ here freely]. Geonames parses fastest, so is the advised format to use<br />
#Download geonames USA state files. You can do this [http://geonames.usgs.gov/domestic/download_data.htm here freely]. This is advised for USA searches, as the data in the USA country file contains many doubles, which can be avoided by searching state per state. State info also contains county information.<br />
#download GNS Geonet country files (not available for usa). You can do this [ftp://ftp.nga.mil/pub/gns_data here freely with ftp]. <br />
<br />
Watch out, some of these downloads are '''VERY''' large, especially USA data. Only download what you need!<br />
<br />
<small>'''Note''': The geonames data of popular places is in English, so eg municipalities in Italy will be found, but Roma not, as this is Rome in English. To find data with these you need to search in the localised variants of the name (see below)</small><br />
<br />
'''DO NOT BETA TEST WITH YOUR RESEARCH DATA. EXPORT DATA FIRST TO HAVE A BACKUP'''<br />
<br />
=== Starting the tool ===<br />
The placecheck tool is in the '''tools menu''', option '''tools''', under '''Interactive place completion'''<br />
<br />
=== The dialog explained ===<br />
[[Image:place_completion_tool_empty.png|500px|The Place Completion Tool]]<br />
<br />
The Dialog consists of 4 parts:<br />
====Part 1: selection of places====<br />
First you need to choose with which places you want to work. You can use several methods to define your places:<br />
# Use a place filter. You can use two preset filters: ''All places'', which returns all places, and ''No Latitude/Longitude given'', which returns all places of which the latitude or the longitude is not set. You can also created a custom place filter in the place view, test it with the filter sidebar, and then use it in this tool. All custom filters you made will be available<br />
# To prevent the need to make a filter for every city, ... in your data, you can set country,state,county,city or parish of the places you want to search on. This works just like in the filter sideview in the places view.<br />
# Use a latitude, longitude rectangle. Eg, suppose you have the latitude and longitude of all places in the UK, and now want to add in the state attribute ''Wales'', for all places in Wales. You can look on a map, note down the centre of Wales in latitude and longitude, as well as roughly the width and height of this rectangle. This will allow you to obtain all places in Wales (and some in England), allowing to much faster set the state information.<br />
<br />
====Part 2. Completion of Places ====<br />
#The first posibility is to look up in a datafile the latitude and longitude of your places. For this you must have downloaded the necessary resourses, see section above. You can select with a file dialog the file you want to search, and set how this data must be parsed. The following parsing options are available:<br />
##''GeoNames country file, city search'': use the city attribute to look for lat/lon in a GeoNames country file. This is the fastest search.<br />
##''GeoNames country file, city localized variants search'': use the city attribute to look for lat/lon in a GeoNames country file using the localised (non-English) known names in the GeoNames file. Eg, Roma will be found with this option (as Roma is the Italian local variant of the English name Rome)<br />
##''GeoNames country file, title begin, general search'': Use the start of the title field to search in a GeoNames file. With start it is meant everything before a comma:''',''' . This allows to find landmarks, squares, ... . Eg, if the title of your place is: ''Piazza Navona, Rome'', using this search will find you the latitude and longitude of this famous square in Rome. <br />
##''GeoNames USA state file, city search'': Looking for places in the USA file is almost worthless: it takes a long time and every name exists several times. Hence, it is worthwile to use state by state. If a USA state file is selected for doing a search, you '''must''' select this option. The city attribute is used for the search.<br />
##''GNS Geonet country file, city search'': use the city attribute to search in a GNS file (slower than GeoNames search!).<br />
##''GNS Geonet country file, title begin search'': use the start of the title of a place to search in a GNS file. With start everything appearing before the first comma is meant.<br />
#A second option is to parse some existing data in your places.<br />
##You can parse the title attribute to extract information from it. Eg a title like ''Albany, NY'' can be used to set the city attribute to ''Albany'' and the state attribute to ''NY''.<br />
##You can set the title of all the selected places to a uniform way. This is interesting if due to imports you have different styles for the title field, which can be annoying in reports. At the moment there are two options:<br />
###Set title field to ''City[, State]'': This means the title of your places will contain the city, and if the state field is present, the state will be appended with a comma.<br />
###Set title field to ''Titlestart[, City][, State]'': This means the present start of your title will be kept. If this start is not the city, then the city will be appended. If state is present, also state will be appended. An example: suppose your title is ''Piazza Navona, Italy'', the city is ''Rome'' and the State is ''Lazio''. Using this option to set the title would change the title attribute into ''Piazza Navona, Rome, Lazio''.<br />
##Convert latitude and longitude to a uniform way. Again due to import, copy/paste, you might have latitude and longitude entered in different formats. This is annoying on reports. This options allows you to set for all selected places the lat/lon to one form. The options are:<br />
###All in degree notation: use the classical degree notation with degree, minutes and seconds.<br />
###All in decimal notation: use the decimal system to denote lat/lon.<br />
###Correct -50° in 50°S: a much seen error is to use - for the classical degree notation, which is wrong, and which GRAMPS will not be able to interpret. With this option this error is looked for and corrected.<br />
# A third option is to set attributes of all selected places. You can set the country, state, county, parish, zip/postal code and city attributes of all places in one sweep.<br />
<br />
====Part 3. Overview of the results ==== <br />
After having entered all data in Part 1 and 2, you click find for GRAMPS to search all changes that will occur. This part of the dialog shows all changes that will occur. <br />
<br />
[[Image:place_completion_tool_results.png]]<br />
<br />
All selected places are shown. If changes will be done all changes are listed as subentries of the place. Every change will be a subentry. <br />
<br />
If the change wil '''overwrite''' an existing entry, the subentry is '''shown in orange'''. <br />
<br />
<br />
'''TO AVOID PROBLEMS, GO OVER ALL CHANGES QUICKLY, AND CHECK ALL ENTRIES IN ORANGE!'''<br />
<br />
<br />
The following actions are possible in the result screen:<br />
# press delete to delete the entry, making sure that this change will not occur. You can delete the entry to delete all changes, or select one subentry, to only delete that specific chagne<br />
# double-click on an entry to open the place dialog. If you double-click on the entry, '''all changes will be preentered'''. If you double-click on a subentry, only this specific change will be preentered in the place dialog.<br />
# press tab to open in a browser window google maps. Pressing tab on a subentry showing a '''new''' lat/lon entry will open google maps on this new lat/lon position. Pressing tab on the top place entry will give open google maps with the old lat/lon position, or if that is not known the title/city field is used for the search.<br />
<br />
====Part 4. Actions ==== <br />
After you have checked the changes in Part 3, you can now apply them all with one button click, by clicking the ''Apply'' button. <br />
<br />
<br />
Clicking ''Help'' will bring you to this page, clicking ''Close'' will close the window and clicking ''Google Maps'' when an entry is selected in the results field has the same effect as pressing tab on an entry (see above).<br />
<br />
== Example == <br />
<br />
Open the example file from the examples where latitude and longitude are empty: [http://gramps.svn.sourceforge.net/viewvc/*checkout*/gramps/trunk/gramps2/example/gramps/example.gramps?revision=7186 example.gramps]. <br />
<br />
We will now show how the places in this file can be completed. The best thing to do is open a new family tree (.grdb), give it a name, and import the example.gramps file. This file has 852 places, which would mean a lot of manual edits if you do not use this tool!<br />
<br />
Now, open the place view. You will see all places are of the form:<br />
:Aberdeen, WA<br />
This value is the <code>Place Name</code> attribute (the title or description of the place). <br />
<br />
=== Step 1: City and State data ===<br />
Our first step will be to split this field into a <code>City</code> value (here Aberdeen), and a <code>State</code> value (here WA).<br />
<br />
We open the ''Place completion tool'':<br />
[[Image:place_completion_tool_example1.png|500px|Parse the Place Name Field]]<br />
Here we have selected ''All Places'', and we parse the title as ''City [,|.] State''. Click on ''Find'', quickly scan the data if all looks ok, and then click on ''Apply''. You are notified that 851 places are updated. This is one less that the number of places. Indeed, one place does have a different type of title: ''Puerto Rico'' has no state information.<br />
<br />
=== Step 2: Look-up latitude and longitude ===<br />
We have downloaded the GeoNames datafiles for the USA states, and will now use that to complete the latitude and longitude of the data. At the same time, this will fill up the county field.<br />
<br />
[[Image:place_completion_tool_example2.png|500px|Look up lat/lon for Alaska]]<br />
<br />
In the above screenshot, you see we have selected All Places with State=AK. In the second part of the window we give that we want to search in the AK_DECI.txt file downloaded from GeoNames, using the parsing method: ''GeoNames USA state file, city search''.<br />
<br />
Note that if you want to change AK into Alaska, this would be possble. Just set state=Alaska in the set attributes section of the window.<br />
<br />
<br />
Do this now for all the states. Always check for doubles. Eg, for state ''AL'', going over the changes, we encounter:<br />
<br />
<br />
[[Image:place_completion_tool_example3.png|Double in lat/lon, city Enterprise exists in two counties]]<br />
<br />
<br />
We see that the first time 'Enterprise' if found, it is in county ''Coffee'' in lat/lon:31.31/-85.85. The second hit is for county ''Chilton'' with lat/lon:32.73/-86.62. <br />
<br />
You can now use the Google Maps button (or press TAB key) while the lat/lon subentry is selected to see where this city is in both cases. From this it will be clear for example that one is a hamlet, not really a city, while the first is a real city. So now, select the second lat/lon entry, and delete it by pressing the DEL key. Do the same for the second county entry. <br />
<br />
In case google maps did not allow you to determine which is the correct city, you can double click on the city to open the Place Dialog ('''Warning: this will preenter the data of the Place Completion tool. So hit cancel here if you want to exit without these changes done'''). In this dialog the references tab allows you to navigate to all events coupled to this place. This will give you extra information you might use to decide which of the two found places is the correct place.<br />
<br />
=== Step 3: Problem entries===<br />
While updating all places in step 2, you will have noticed some errors in the state information: Some places have a dubious state: eg OH-AL<br />
<br />
You can obtain these states by choosing ''All Places'' en setting the state search box to '''-'''. Clicking Find will give you all these problem places. You can use google maps or the place dialog to sort them out. You can also use the USA country GeoNames file to search these places in the entire USA. You will need sufficient memory for this, or you will obtain a MemoryError (see below)!<br />
<br />
=== Step 4: Lat/Lon not found ===<br />
<br />
After the above, still some 45 places have no latitude/longitude found. You can now select these places by setting the Place filter to 'No Latitude/Longitude', which will find you all places with no coordinates. <br />
<br />
It will be clear that many of those can be quickly corrected: abbreviations, eg the city field contains ''St.George'', which should be ''Saint George''; double names, eg Waterloo-Cedar Falls, IA means Waterloo near Cedar Falls, changing the city to Waterloo and redoing the search using Google Maps will allow to quickly find which coordinates for Waterloo are needed.<br />
<br />
== Advanced Usage ==<br />
This is for advanced users only knowing regular expressions. <br />
<br />
The parsing fields have entry fields allowing you to give your own parsing. Parsing uses regular expressions. You can use this to parse your title, and to parse a lat/lon file in your own way. For reference, here an overview of the parsing codes used for the predefined parses:<br />
=== Parse title details ===<br />
The following regex expressions are used, where for brevity we use some variables defined lower.<br />
<br />
#<nowiki>"City [,|.] State" is parsed by : r'\s*(?P<'+city_translated +r'>.+?)\s*[.,]\s*(?P<'+state_translated +r'>.+?)\s*$'</nowiki><br />
#<nowiki>"City [,|.] Country" is parsed by : r'\s*(?P<'+city_translated +r'>.+?)\s*[.,]\s*(?P<'+country_translated +r'>.+?)\s*$'</nowiki><br />
#<nowiki>"City (Country)" is parsed by : r'\s*(?P<'+city_translated +r'>.*?)\s*\(\s*(?P<'+country_translated +r'>[^\)]+)\s*\)\s*$'</nowiki><br />
#<nowiki>"City" is parsed by : r'\s*(?P<'+city_translated +r'>.*?)\s*$'</nowiki><br />
<br />
Here the variables used are: <br />
lat_translated = _('lat')<br />
lon_translated = _('lon')<br />
city_translated = _('city')<br />
county_translated = _('county')<br />
state_translated = _('state')<br />
country_translated = _('country')<br />
<br />
You can use one of these variables as a group, and the tool will recognise them, and use as values for the corresponding place attributes. <br />
<br />
=== Lat/Lon lookup parsing ===<br />
For the regex of lat/lon lookup, you need to indicate which data must be replaced with existing place attributes for the search, as well as indicate which regex groups must be extracted. <br />
<br />
#<nowiki>"GeoNames country file, city search" is parsed with: r'\t'+CITY_transl +r'\t[^\t]*\t[^\t]*\t' +latgr + r'[\d+-][^\t]*)\t' + longr + r'[\d+-][^\t]*)\tP'</nowiki><br />
#<nowiki>"GeoNames country file, city localized variants search" is parsed with: r'[\t,]'+CITY_transl+r'[,\t][^\t\d]*\t?' +latgr + r'[\d+-][^\t]*)\t' + longr + r'[\d+-][^\t]*)\tP'</nowiki><br />
#<nowiki>"GeoNames country file, title begin, general search" is parsed with: r'\t'+TITLEBEGIN_transl +r'\t[^\t]*\t[^\t]*\t' +latgr + r'[\d+-][^\t]*)\t' + longr + r'[\d+-][^\t]*)\t[PSTV]'</nowiki><br />
#<nowiki>"GeoNames USA state file, city search" is parsed with: r'\t'+CITY_transl+r'\tPopulated Place\t[^\t]*\t[^\t]*\t' + countygr + r'[^\t]*)' + r'\t[^\t]*\t[^\t]*\t[^\t]*\t' +latgr + r'[\d+-][^\t]*)\t' + longr + r'[\d+-][^\t]*)'</nowiki><br />
#<nowiki>"GNS Geonet country file, city search" is parsed with: r'\t'+latgr+r'[\d+-][^\t]*)\t'+longr+r'[\d+-][^\t]*)' + r'\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*\tP\t[^\t]*\t[^\t]*' + r'\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*' r'\t[^\t]*\t[^\t]*\t[^\t]*' + r'\t'+CITY_transl+r'\t[^\t]*\t[^\t\n]+$'</nowiki><br />
#<nowiki>"GNS Geonet country file, title begin search" is parsed with: r'\t'+latgr+r'[\d+-][^\t]*)\t'+longr+r'[\d+-][^\t]*)'+ r'\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*\t[PLSTV]\t[^\t]*\t[^\t]*'+ r'\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*\t[^\t]*' + r'\t[^\t]*\t[^\t]*\t[^\t]*' + r'\t'+TITLEBEGIN_transl+r'\t[^\t]*\t[^\t\n]+$'</nowiki><br />
<br />
For extraction of data you can use the same groupnames as in title parsing, so eg latgr in above should read: <nowiki>r'(?P<'+lat_translated +r'>'</nowiki> .<br />
<br />
The syntax for the values that need to be used for searching in the file, eg CITY_transl, is given by : _('CITY'). You can use as substitution values:<br />
_('CITY'), _('TITLE'), _('TITLEBEGIN'), _('STATE'), _('PARISH'). <br />
<br />
The tool will read in the given regex, replace the substitution strings by the values in the place object, do the search, and extract the regex groups given from the result.<br />
<br />
Resource: [http://de.wikipedia.org/wiki/Wikipedia:GEOnet_Names_Server GEOnet]<br />
<br />
== Troubleshooting ==<br />
=== Non UTF-8 latitude/longitude file ===<br />
The place completion tool expects the input files for location lookup to be in unicode (utf-8). In the occation this is not the case, you will get the error:<br />
<br />
<code><nowiki>File "/home/benny/programms/gramps/gramps2/src/plugins/PlaceCompletion.py", line 851, in load_latlon_file<br />
self.latlonfile_datastr = infile.read()<br />
File "/usr/lib/python2.4/codecs.py", line 481, in read<br />
return self.reader.read(size)<br />
File "/usr/lib/python2.4/codecs.py", line 293, in read<br />
newchars, decodedbytes = self.decode(data, self.errors)<br />
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 1610092-1610094: invalid data</nowiki></code> <br />
<br />
Note that the Place Completion tool catches this errors and shows you an information box. After this, the tool will attempt to read the file with utf-8 (unicode), ignoring errors. This might give good results, but will off course fail to produce results on non-unicode encoded files <br />
<br />
In the above example it is clear the problem is in two bytes, so you can correct this manually: open the file with eg <code>KHexEdit Binary Editor</code>, go to the specified position (offset 1610092), and change the two bytes with a space. <br />
<br />
In the case the file is completely non-unicode, you will have to convert it to unicode with a tool, before using it in the placecompletion tool. <br />
<br />
=== Memory Error ===<br />
The tool might fail with the error:<br />
<br />
<nowiki>self.latlonfile_datastr = infile.read()<br />
File "/usr/lib/python2.4/codecs.py", line 481, in read<br />
return self.reader.read(size)<br />
File "/usr/lib/python2.4/codecs.py", line 293, in read<br />
newchars, decodedbytes = self.decode(data, self.errors)<br />
MemoryError</nowiki><br />
<br />
The tool has to load the datafile for latitude/longitude searching into memory. For large files like USA.txt, this might be impossible if you have limited memory. You can try to close as many programs running at together with GRAMPS, and try the tool again.<br />
<br />
<br />
== Download ==<br />
You can download the beta version. You find it at [http://cage.ugent.be/~bm/varia/placecompletion_1_0.tar.gz placecompletion_1_0.tar.gz]. Put the .glade and .py file both in the plugins directory of GRAMPS 2.2.6+:<br />
* local install: place in <code>~/.gramps/plugins</code><br />
* global install: <code>place_to_gramps_install/src/plugins</code><br />
<br />
'''DO NOT BETA TEST WITH YOUR RESEARCH DATA. EXPORT DATA FIRST TO HAVE A BACKUP''<br />
<br />
==User Contributions==<br />
<br />
* I have patched the version to read the files on [http://tools.wikimedia.de/~kolossos/wp-world/pub_CSV_test3.csv.gz] (for more information, see http://meta.wikimedia.org/wiki/WikiProjects_Geographical_coordinates) You can find my changes on [http://svn.nomeata.de/wsvn/isaak-buch?op=comp&compare%5B%5D=%2Fgramps-plugins/PlaceCompletion.py@98&compare%5B%5D=%2Fgramps-plugins/PlaceCompletion.py@HEAD] --[[User:Nomeata|Nomeata]]</div>Nomeatahttps://blog.gramps-project.org/wiki/index.php?title=Specification:Geographic_Report&diff=3493Specification:Geographic Report2007-08-11T12:01:32Z<p>Nomeata: </p>
<hr />
<div>Proposed report of displaying data on a map<br />
[[Category:Proposed Report Specifications]]<br />
[[Category:Plugins]]<br />
<br />
{| {{Prettytable}} style="width:235px; line-height:2.25em; font-size:90%;" align=right<br />
|-<br />
|bgcolor="#8DA7D6"|'''Task'''<br />
|bgcolor="#8DA7D6"|'''Status''' <br />
|-<br />
|Specification draft <br />
|style="color:red;" |alpha<br />
|-<br />
|Approval <br />
|style="color:red;"|pending <br />
|-<br />
|Implementation <br />
|style="color:red;"|v0.1<br />
|}<br />
<br />
<br />
==Introduction==<br />
This report generates output that can be displayed on a map. For now, the [http://earth.google.com/ Google Earth] application is chosen to display this information, and hence the report is available as a code generator for KML files, the datafiles understood by Google Earth. <br />
<br />
The first aim is to display events given in GRAMPS on the map, using the latitude and longitude of the places in GRAMPS. <br />
The second aim is to function as a testbed on how to optimally display genealogy data on map, which should be useful if GRAMPS is ever extended with a map view.<br />
<br />
<small>'''Note''': It has come to my attention via the Eastman blog that a specific genealogy application exists that does this type of datarepresentation: Family Atlas. I do not have this application, but looking at the screenshots, it appears that much of its functionality can be done in Google Earth also.</small><br />
<br />
==Example/Screenshot==<br />
none yet<br />
<br />
==Download developer version==<br />
version 0.1 can be found at: [http://cage.ugent.be/~bm/varia/MapReport0_1.tar.gz MapReport0_1.tar.gz]. Read the INSTALL file for how to make it available in the SVN version of GRAMPS.<br />
<br />
<br />
=Specification of the code generator=<br />
==Code Sections==<br />
The report is saved to file. The sections contained should be the Document title and the Placemarks. Here, every placemark is a marker on the map.<br />
===Document Title===<br />
The document will be titled depending on the filter option:<br />
*If map data of a person is generated, the title will be "Events of the person<NAME>", where <NAME> is determined by the display settings of the program, using the unsorted display algorithm. This is typically "Firstname Lastname", but can be overriden by the Preferences settings.<br />
* If map data of the families of a person is generated, the title will be "Events of the family of <NAME>", where name is as before<br />
* If map data of a filter is generated, the title will be "Events in filter <filtername>"<br />
<br />
===Placemark Sections===<br />
TODO<br />
<br />
===Report Options===<br />
TODO<br />
<br />
==Future versions==<br />
:v0.1 : basic functionality, events with the active person and with the family of the active person<br />
:v0.2 : adding filters, and display all that is in a filter. ???''What type of filters to allow?''<br />
:v0.3 : Using the date of the events: movie of the life of person ( (?? ''is this usefull? Will there be enough events to make this worthwile''), plot out emigration paths of a family (Y-line / M-line)<br />
:v?.? : Map overlay. Google Earth allows to add polygons to the map, so in theory one could store a polygon map of a county, parish, as it used to be in eg 1741, and overlay it with the data seen in Google Earth. ( ?? Better place containers would be needed than available now, so that places can be grouped, eg town hall Ghent, church Ghent can be grouped in place Ghent). The goal would be to have a polygon attached to places outlining it's borders during several time periods. These could then be layers in Google Earth, like the boundary layers now. ( ?? I think I'm dreaming now...)<br />
<br />
==User Contributions==<br />
<br />
* I have patched v0.1 to let me select any filter, not just two. It works for me this way, YMMV. It’s using some classes from Calender.py, included in 2.2.8 at least. See [http://svn.nomeata.de/wsvn/isaak-buch?op=comp&compare%5B%5D=%2Fgramps-plugins/WriteGeographicData.py@98&compare%5B%5D=%2Fgramps-plugins/WriteGeographicData.py@HEAD] for the changes I did. --[[User:Nomeata|Nomeata]]<br />
<br />
==Links to other genealogy with google earth==<br />
*[http://gecensus.stanford.edu/gcensus/index.html gcensus]: with perl source code: [http://search.cpan.org/~ihaque/KML-PolyMap-1.32/lib/Geo/KML/PolyMap.pm CPAN].</div>Nomeatahttps://blog.gramps-project.org/wiki/index.php?title=Specification:Geographic_Report&diff=3353Specification:Geographic Report2007-07-25T19:29:45Z<p>Nomeata: Patched version of WriteGeographicData.py</p>
<hr />
<div>Proposed report of displaying data on a map<br />
[[Category:Proposed Report Specifications]]<br />
[[Category:Plugins]]<br />
<br />
{| {{Prettytable}} style="width:235px; line-height:2.25em; font-size:90%;" align=right<br />
|-<br />
|bgcolor="#8DA7D6"|'''Task'''<br />
|bgcolor="#8DA7D6"|'''Status''' <br />
|-<br />
|Specification draft <br />
|style="color:red;" |alpha<br />
|-<br />
|Approval <br />
|style="color:red;"|pending <br />
|-<br />
|Implementation <br />
|style="color:red;"|v0.1<br />
|}<br />
<br />
<br />
==Introduction==<br />
This report generates output that can be displayed on a map. For now, the [http://earth.google.com/ Google Earth] application is chosen to display this information, and hence the report is available as a code generator for KML files, the datafiles understood by Google Earth. <br />
<br />
The first aim is to display events given in GRAMPS on the map, using the latitude and longitude of the places in GRAMPS. <br />
The second aim is to function as a testbed on how to optimally display genealogy data on map, which should be useful if GRAMPS is ever extended with a map view.<br />
<br />
<small>'''Note''': It has come to my attention via the Eastman blog that a specific genealogy application exists that does this type of datarepresentation: Family Atlas. I do not have this application, but looking at the screenshots, it appears that much of its functionality can be done in Google Earth also.</small><br />
<br />
==Example/Screenshot==<br />
none yet<br />
<br />
==Download developer version==<br />
version 0.1 can be found at: [http://cage.ugent.be/~bm/varia/MapReport0_1.tar.gz MapReport0_1.tar.gz]. Read the INSTALL file for how to make it available in the SVN version of GRAMPS.<br />
<br />
<br />
=Specification of the code generator=<br />
==Code Sections==<br />
The report is saved to file. The sections contained should be the Document title and the Placemarks. Here, every placemark is a marker on the map.<br />
===Document Title===<br />
The document will be titled depending on the filter option:<br />
*If map data of a person is generated, the title will be "Events of the person<NAME>", where <NAME> is determined by the display settings of the program, using the unsorted display algorithm. This is typically "Firstname Lastname", but can be overriden by the Preferences settings.<br />
* If map data of the families of a person is generated, the title will be "Events of the family of <NAME>", where name is as before<br />
* If map data of a filter is generated, the title will be "Events in filter <filtername>"<br />
<br />
===Placemark Sections===<br />
TODO<br />
<br />
===Report Options===<br />
TODO<br />
<br />
==Future versions==<br />
:v0.1 : basic functionality, events with the active person and with the family of the active person<br />
:v0.2 : adding filters, and display all that is in a filter. ???''What type of filters to allow?''<br />
:v0.3 : Using the date of the events: movie of the life of person ( (?? ''is this usefull? Will there be enough events to make this worthwile''), plot out emigration paths of a family (Y-line / M-line)<br />
:v?.? : Map overlay. Google Earth allows to add polygons to the map, so in theory one could store a polygon map of a county, parish, as it used to be in eg 1741, and overlay it with the data seen in Google Earth. ( ?? Better place containers would be needed than available now, so that places can be grouped, eg town hall Ghent, church Ghent can be grouped in place Ghent). The goal would be to have a polygon attached to places outlining it's borders during several time periods. These could then be layers in Google Earth, like the boundary layers now. ( ?? I think I'm dreaming now...)<br />
<br />
==User Contributions==<br />
<br />
* I have patched v0.1 to let me select any filter, not just two. It works for me this way, YMMV. It’s using some classes from Calender.py, included in 2.2.8 at least. See [http://www.joachim-breitner.de/various/WriteGeographicData.py]. --[[User:Nomeata|Nomeata]]<br />
<br />
==Links to other genealogy with google earth==<br />
*[http://gecensus.stanford.edu/gcensus/index.html gcensus]: with perl source code: [http://search.cpan.org/~ihaque/KML-PolyMap-1.32/lib/Geo/KML/PolyMap.pm CPAN].</div>Nomeata