Historic & Modern OS Maps

I've released a new version of Family Tree Analyzer with a new mapping feature. This allows you to view your ancestors on a Historic OS Map as provided by the National Library of Scotland. This map which covers the WHOLE of the UK not just Scotland, is for maps from 1920-1947 so not perhaps as early as we'd like for most family history things but pre-dates the major post war clearances.

I understand they are releasing further OS Maps at a later date so I will update the program to incorporate them too at some point.

In addition to that I've added support for the Modern OS Maps as supplied by Bing. These give you far greater detail particularly in rural areas than a Google or Bing Street map gives. There is also a Bing Aerial view map so you can see what the area currently looks like too.

 

Come on guys, has anybody used this yet? What do you think of it? Did you find it useful?

 

In particular any stories of how you've been able to find ancestors locations using the program would be most interesting.

 

I've now released v3.1.1.0 that has several tweaks related to editing locations. A new text search feature and copy/paste commands make it far easier to edit your locations.

 

I like the zoom and being able to pick the pin from the bar.

 

Have you tried the text search?

 

Errr no, I've found copy and paste...

Where's that documentation when you need it ?

 

I'll need to sack the documentation team!!

 

Unfair dismissal! Tribunal! I demand a recount!!

 

I found it!!! Can I have my job back now please?
I'll do it for half what you were giving me before?

 

It sounds like it was the codeplex "click once" installer that froze. Note you cannot just reinstall in that case trying that will definitely fail. For Microsofts click once technology if it screws up like that you MUST uninstall first. Then click once will re-install.

Note XP is more prone to problems such as this. Make sure that all critical updates for XP have been installed from windows update as there were several critical windows hang bugs in explorer fixed to do with click once installs. So if you aren't patched up to date this may be the problem.

Also note that ALL support for XP from Microsoft will stop in April so make sure you have run windows update before then as it will simply stop providing updates in April. Actually most likely that windows update will take you to the buy the new windows 8.1 page once support stops. That's what they did with previous versions.

The other problem with support stopping from Microsoft is that companies will stop supporting their products on XP. It is over 12years old after all which in computing terms is ancient. Programmers like myself will find it increasingly difficult to assist if the problem is with XP/explorer crashes especially if the user didn't update their PC with windows updates.

On the Google geoocding. It depends which version you used there were early issues in v3.0 that we're addressed in v3.1. Mostly around the issue you mentioned of rogue points in different countries. These are better now but the quality of output varies with the input text. I'd be happy to look at the text it geo coded and see if I can improve the program further.

What was the EXACT text for the address in Glamorgan it was trying to find?

PS. Note if you wish to avoid the click once install you can use the .exe version.

 

I'll give you a raise to nada from nought!!

 

I'm getting a raise to nada and a benefits package? Things are looking up!

 

Hi Anne,

I don't think that's an error. Its just telling you you have a fact type that's non standard. I have them in mine, such as

Recorded unknown fact type Children Status

What does your says after type?

 

Anne, as I add more features extra things will be revealed. It struck me when I was adding support for age facts that I wasn't actually reporting anything about custom fact types I was ignoring. So I decided I'd report that during load and load the facts anyway. Thus it should pickup and display more facts.

So you don't actually need to do anything it's simply a warning that there are custom fact types it doesn't understand. eg: one of the testers discovered that he had a custom fact type of censuss 1871. This was getting ignored but he could clearly see that it was just a typo on his behalf so he was able to fix it.

BTW on the date errors I may be able to do something about that if you can give me an example. I take it they are all just 3 digit years?