Suggestions for FTAnalyzer

Alexander the colour does work.

 

A good idea, however a test GEDCOM would probably need sample instructions to go with it and as you have noted I'm not that good at instructions It might also take some time to prepare to make sure it demonstrated particular features.

Which genealogy program do you use? Which tags is it that aren't appearing?

 

All the custom tags will appear in a GEDCOM as EVEN, I just put the t at the end to make the text readable!! Same with Lost Cousins tag. I should have given examples sorry about that. It also looks like I had a typo and missed the space again apologies.

My Lost Cousins tag appears in my GEDCOM as

1 EVEN
2 TYPE Lost Cousins
2 DATE 1841

If yours looks different let me know and I could perhaps amend the code to suit. Or if you prefer if you change your's to match what mine looks like that should work too.

The date bit is important as obviously an ancestor could easily appear in more than one Lost Cousins Census thus have more than one Lost Cousins facts.

 

One of the most tricky things to deal with in the entire program is dates. I am aware of varying date formats in use many of which bear no resemblance to the GEDCOM standard but I've attempted to cater for them none the less. Could you give me a few test examples of date strings you use, so I can add them to the FactDate test case.

Ideally the string the expected start and end date values. eg: the string "BET JAN 1910 AND NOV 1918", should become start 01/01/1910, end 30/11/1918. If you can possibly express your example date strings in that format that would be ideal. I can then ensure that the date reader string copes with those test cases.

 

Ah I think I see what you meant now if answer 25 gives you what you wanted. An example GED of a single individual with CENS and custom Lost Cousins tags is

Code:

0 @I4232@ INDI
1 NAME Ann /Bisset/
2 SOUR @S284@
2 SOUR @S5@
2 SOUR @S7@
1 SEX F
1 REFN 4232
1 EVEN
2 TYPE Lost Cousins
2 DATE 1881
1 BIRT
2 DATE 14 SEP 1872
2 PLAC Alford, Aberdeenshire, Scotland
2 SOUR @S284@
2 SOUR @S5@
2 SOUR @S7@
1 CENS
2 DATE 1881
2 PLAC Bridgend, Lintrathen, Angus, Scotland
2 SOUR @S5@
1 DEAT
2 DATE BET 1901 AND 1982
1 CENS
2 DATE 1901
2 PLAC Jubilee Cottage, Monifieth, Angus, Scotland
2 SOUR @S7@
1 CENS
2 DATE 1891
2 PLAC Church Street, Broughty Ferry, Dundee, Scotland
2 SOUR @S6@
1 FAMC @F1256@

Note it has CENS entries for 1881, 1891, 1901 but only a Lost Cousins entry for 1881 as the others aren't LC census years. Incidentally this should mean that the LC report for this person should show grey for 1841-1871 cenus (she wasn't born till 1872) and green for 1881-1901 (all are either entered to LC or is not a LC year), and finally red for 1911 as I've not looked her up on the 1911 cenus and so obviously not entered a 1911 LC record for her.

 

Code:

0 @I4232@ INDI
1 NAME Ann /Bisset/
2 SOUR @S284@
2 SOUR @S5@
2 SOUR @S7@
1 SEX F
1 REFN 4232
1 EVEN
2 TYPE Lost Cousins
2 DATE 1881
1 BIRT
2 DATE 14 SEP 1872
2 PLAC Alford, Aberdeenshire, Scotland
2 SOUR @S284@
2 SOUR @S5@
2 SOUR @S7@
1 CENS
2 DATE 1881
2 PLAC Bridgend, Lintrathen, Angus, Scotland
2 SOUR @S5@
1 DEAT
2 DATE BET 1901 AND 1982
1 CENS
2 DATE 1901
2 PLAC Jubilee Cottage, Monifieth, Angus, Scotland
2 SOUR @S7@
1 CENS
2 DATE 1911
2 PLAC Church Street, Broughty Ferry, Dundee, Scotland
2 SOUR @S6@
1 FAMC @F1256@

I've marginally edited the example so now the 1891 census is missing and 1911 census is done.

This means the she has a census for 1881, 1901, 1911, and a Lost Cousins entry for 1881 but not 1911. The report will therefore show grey 1841, 1851, 1861, 1871 (she wasn't alive), green for 1881 (census AND Lost cousins tags entered), red for 1891 (no census record), green for 1901 (census record but not a LC year), yellow for 1911 (census record found but no Lost Cousins tag entered for 1911).

This then covers all the bases for the Lost Cousins report.

 

For occupation it picks whatever is marked in your GEDCOM as the "preferred" fact. For Best Location it chooses whatever is the longest location name, ie: in theory the most precise. So for example it would select "Farm cottage, some parish, some county, England" over "some parish, some county, England". So unfortunately its somewhat of a random "best" location.

One of the things on my to do list is to pick locations closer to event dates. I plan to write a routine that checks the location facts and dates and to try to always display a location that is closest to the date in question. My gut feeling is that whatever location is closest in year to the year you are interested in ought to be the year displayed. As I say it's on the to do list.

Windows 8 not always identifying the version of .Net is a known bug in Windows 8, I thought I read there was a windows update that fixed that, perhaps not.

 

Version 1.5.5.0 now released uses locations as close to the relevant date as possible!!

Windows 8 should come with .Net 4.5. The program runs with .Net 4.0 as this is supported on Windows 7. Windows 8 can easily run with .Net 2.0 (I think) and above and indeed it is common to have various versions eg: 2.0, 3.0, 3.5, 4.0 and 4.5 all installed. This is for backwards compatibility so that Windows 8 doesn't suddenly fail when running programs targeted to older platforms.

The census location issue was the same as the best location issue it was using the longest location it could find irrespective of date. The new code uses location facts as close to the date of the event (eg: census) as possible.

 

I've tweaked a bit more v1.5.5.1 now available. In this version all the searching features for census are now available on the main census form.

This means that you can look at a census report to see who is missing, select your preferred search site at the top of the form and double click a person to search the site for that person.

 

Amazing, something to try later then

 

As an example for the use of being able to get data out of the gedcom and into excel.

I have created a new custom fact called Children Status. This contains the information that's given on the 1911 census; that shows how many children born alive, how many still living and how many had died. I use this to establish and verify that I have captured all the children for that couple. So now, I need to know who has this fact added and who hasn't (who was alive in 1911 census), so that I know who to add this fact to and then check the number of children.

 

Hi Alexander,

Was just thinking about your Families tab report. I don't know about other people, but I quite often use the search sites by just putting in the parents names and seeing what names of children come up in the search results, to find children born to the couple but then don't appear on the next census/s.

Would it be feasible from the family tab to double click on a line, and have the parent names and date range added to the website search criteria and then the search performed?

I do this type of search on IGI and Ancestry at the moment, I'll have to look to see if it can be done at FMP.