Search for content in message boards

FTM 2012 finds places on map but still unresolved

FTM 2012 finds places on map but still unresolved

Posted: 26 Oct 2012 8:31AM GMT
Classification: Query
I am trying to sort out my places and FTM 2012 will find most of the unresolved places on the map just fine, however when you try to find the name of the city in the list to resolve it the place does not appear.
I can move the city up to the Place Detail field but that seems a bit silly for places that are current and have not been replaced with a new name.
As an example - Campsie, New South Wales, Australia appears on the map but when I try to resolve the place name it is not listed.
Am I just being dumb??

Re: FTM 2012 finds places on map but still unresolved

Posted: 26 Oct 2012 9:06AM GMT
Classification: Query
There are names of places that are not in the FTM Place Name Authority Index of Places

One workaround is to in this example

Place: New South Wales, Australia

Description: Campsie

This will be resolved by FTM

Alternatively,

Put Campsie, New South Wales in the Place field and then tell FTM to ignore it.

It will show as you want it and Bing Maps will locate it

John D

Re: FTM 2012 finds places on map but still unresolved

Posted: 26 Oct 2012 9:27AM GMT
Classification: Query
Thanks for the reply.

The problem with using the description field is that it won't work in the Hierarchy view will it? At least when I move Campsie to the Place Detail field the heirarchy still works, but I have to manually place the pin on the map so it shows the correct location.
It also means that I can't for example, have 12 Smith Street in the Place Detail field so that it appears under Campsie in the Heirarchy. I can only have 12 Smith Street, Campsie which then appears under New South Wales which is not really how it should work.
Likewise if I ignore it the hierarchy doesn't work right.
Any other options?

Re: FTM 2012 finds places on map but still unresolved

Posted: 26 Oct 2012 10:05AM GMT
Classification: Query
I have a lot of correct addresses that are unresolved. At the moment I have just ignored it, and once I am doing a tidy up I will probably look at the issue again.

I might be tempted to just click ignore for once I am sure are OK.

Re: FTM 2012 finds places on map but still unresolved

Posted: 26 Oct 2012 3:45PM GMT
Classification: Query
Johndd189 comment

“There are names of places that are not in the FTM Place Name Authority Index of Places

One workaround is to in this example

Place: New South Wales, Australia

Description: Campsie

This will be resolved by FTM”



The above does not resolve “Camsie”

What it does is move “Camsie” to the description field

Then it resolves “New South Wales, Australia”

The reason it resolves “New South Wales, Australia” is that “New South Wales, Australia” is in the FTM 2012 Place data base

Camsie, New South Wales, Australia is not in the FTM 2012 data base therefore the system cannot resolve it [as stated in the comment by Johndd189]

In many cases even though the system cannot resolve a place it still has the capability to find the place on the map and point to it

Another type of workaround is to

1- Put Camsie, New South Wales, Australia in the place field
2- Go to some other place where you can find the coordinates of Camsie, New South Wales, Australia, e.g., Wikipedia
4- Enter the coordinates in the coordinate field
5-Let the system find the place on the map
6- If when you hover over the pin and it does not say “Camsie, New South Wales, Australia”, then resolve the place [but don’t remove the coordinates] and after you are done resolving the place go back and type “Camsie, New South Wales, Australia” in the place field

Note: This will NOT resolve “Camsie, New South Wales, Australia”, but your map will point to the correct place and your place name will be Camsie, New South Wales, Australia and when you hover over the pin it will say “Camsie, New South Wales, Australia”

I am not advocating this workaround. The correct thing that needs to be done is users need to point out the issues with place names and send these issues to the development group for resolution

Re: FTM 2012 finds places on map but still unresolved

Posted: 26 Oct 2012 5:10PM GMT
Classification: Query
Edited: 26 Oct 2012 5:24PM GMT
For FTM2012 (only, not in previous versions)

1) Right click resolve

2) Note a little "up" arrow next to the name to be resolved. Click on that. Note that the text field to the left of the left-most comman will move to the top text field - called "Place Detail".

3) Note the bottom shows it will resolve to "New South Wales, Australia"

4) Click Replace - FTM will now add the two pieces together - the top text box and the bottom place name box. (In this same way, address, churches and cemeteries can be "kind of resolved" so that will appear in the new heirarchical view.)

The new, resolved place name "Campsie, New South Wales, Australia" will now appear in your places list and will appear in the "heirarchical" list under New South Wales. However the little icon to the left of the place name will not a check mark name. One could interpret this symbol to mean "Partially resolved".

OR... You could simply leave the name unresolved or ignored.

_______________________

Keep in mind that the PNA is just a tool to help with spelling and to be a bit of a primitive county finder. It is not a requirement that each and every name in your database conform to the PNA.

That said, it would help if FTM structured the Heirarchal view to simply view the names from right to left as you've entered them and not force one into this cunundrum of what to do with unresolved or even unresolvable place names. For that reason, I have given up on using the Heirarchical View - it is useless to me because of all of the purposefully unresolved or unresolvable names (many historical names or historical past spellings or historical boundary changes, etc) in my database.

Re: FTM 2012 finds places on map but still unresolved

Posted: 26 Oct 2012 8:21PM GMT
Classification: Query
Edited: 26 Oct 2012 8:26PM GMT
silverfox3280 comment

"The new, resolved place name "Campsie, New South Wales, Australia""

The place name "Campsie, New South Wales, Australia" is NOT RESOLVED

The place name "New South Wales, Australia" is resolved

but "Campsie, New South Wales, Australia" is NOT resolved. The reason it is not resolved is because FTM 2012 has no information about "Campsie, New South Wales, Australia" in its data base and therefore the system cannot resolve it

There is a diffrence between being correct and being resolved.

"Campsie, New South Wales, Australia" is probably a correct place but FTM 2012 has no information about it and can't resolve it so it leaves it unresolved

The way you can tell if a place has been resolved is to look at the [resolved/unresolved] symbol icon - if it has a checkmark it has been resolved. If it doesn't have a checkmark it has not been resolved by the system. And my interpretation is that there is no such resolution as "Partially resolved"

I have no idea what happens when the FTM 2012 data base is updated to show "Campsie, New South Wales, Australia" and hence users need to be cautious about developing workarounds. When they do update it what does the system do with the workaround that someone has used/developed






Re: FTM 2012 finds places on map but still unresolved

Posted: 26 Oct 2012 10:21PM GMT
Classification: Query
Edited: 26 Oct 2012 10:22PM GMT
You said: ""Campsie, New South Wales, Australia" is probably a correct place but FTM 2012 has no information about it and can't resolve it so it leaves it unresolved"...and:

You said: " And my interpretation is that there is no such resolution as "Partially resolved"

No, that is not true. The system's new structure leaves 3 "states" for resolved:

Checkmark - fully resolved
Question mark - unresolved - does not show in heirarchical view.
No mark inside the icon - partially resolved and recognized in the heirarchical view.

This change in FTM's structure was made commensurate with the new capability for the heirarchical view and was meant as a way for people using addresses, church names, cemtery names, etc in the place fields to be recognized as resolved for purposes of the heirarchical view.

It also allows one to correct misspellings, insert county names etc, for those with addresses, churches, cemeteries in the place field.

This change was actually quite a change forward for the FTM structure - but the heirarchical view would still be better served to simply read a person's places from right to left without any reference to whether they are resolved or not resolved or partially resolved.



Re: FTM 2012 finds places on map but still unresolved

Posted: 27 Oct 2012 12:39AM GMT
Classification: Query
Thanks all for the replies. It looks like what I am doing is the only way to get the hierarchy view to work properly, so I will just keep splitting the unrecognized part into the place details. It will be interesting though what will happen if these unrecognized places become part of the database.

Re: FTM 2012 finds places on map but still unresolved

Posted: 27 Oct 2012 11:33AM GMT
Classification: Query
silverfox3280 comment

"No, that is not true. The system's new structure leaves 3 "states" for resolved:

Checkmark - fully resolved
Question mark - unresolved - does not show in heirarchical view.
No mark inside the icon - partially resolved and recognized in the heirarchical view.

silverfox - Could you please "point" me to the FTM 2012 documentation where these resolution definitions are delineated. I have been unable to find them.

Thanks

per page

Find a board about a specific topic