Ken:
Here is a discrete example of a problem in the Geodatabase, v5, Nov 16
When I try to test the following for validity:
Alliance, Box Butte Co, NE
The following entry's are filled for the Core+ & Core fields:
Core+ Alliance, Box Butte Co, Ne, , , Italy
Core Ne, , , Italy
I get basically the same thing for the following:
Adams, Gage Co, NE
Core+ Adams, Gage Co, Ne, , , Italy
Core Ne, , , Italy
It would appear that the NE for Nebraska is not being recognized as a state.
Leon Chapman
[EMAIL PROTECTED]
----- Original Message -----
From: "Ken McGinnis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, November 16, 2003 7:58 PM
Subject: Re: [LegacyUG] V5 Geodatabase - Functionality
> Problem 1. (Attachment sent directly to Christer) See attached zzz.jpg
> file. Can you give a few specific examples for me to try.
>
> Problem 2. (Attachment sent directly to Christer) See attached zzz2.jpg
> file. I cannot duplicate your problem of the Core+ and Core fields not
> filling in the City name.
>
> Problem 3. again, I'd love exact locations you are using which would let
me
> see right away what you are seeing. Now, let me try to explain a few
things
> about the Core+ and Core text boxes.
>
> When we get a location like "Cedar Cemetery, Duvall, King, Washington,
USA".
> We split it apart into separate pieces. We then start with the right
piece
> and see if it's a country. If it is then we look on piece to the left
> "Washington" and see if we can find a match in the State table. If we do
> then we take the next piece to the left "King" and look in the County
table
> for a match. If we find a match we then look to the next piece to the
left
> "Duvall" and see if we can find a match in the City table. At this point
if
> there are any extra pieces that we haven't used we put them together into
an
> "extra pieces" variable and this gets added to the left of the Core+
field.
> The + refers to the extra pieces that we couldn't find matches for and
don't
> know what they are. By adding them to the Core+ field it's easy for a
user
> to cut/paste or edit the location in the Core+ field to fix it to be how
> they want it to be when they click Select. Clicking Select next to the
> Core+ field will return the user edited, fixed up location.
>
> In the above if the "USA" piece was not found in the country table or in
the
> GeoCountryCodes.txt list we then use that data and move to the State table
> to see if we find it. If not we continue looking left then go to the next
> piece and see if we can find a country. With exact examples I can better
> answer questions as I can then explain in detail why we are doing
something.
> I appreciate the help and hope you are not frustrated with my answer and
> that you will get back to me with specific examples. We want the Geo
search
> to work great and I'm sure there will be additional refinements.
>
> Thanks
>
> Ken McGinnis
> Millennia Corporation
> [EMAIL PROTECTED]
> http://www.LegacyFamilyTree.com
> We are changing the world of genealogy!
>
> ----- Original Message -----
> From: "Christer Siverud" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, November 16, 2003 10:16 AM
> Subject: [LegacyUG] V5 Geodatabase - Functionality
>
>
> Hi Ken
>
> You asked for specific data for developing Geo database - here you have
> some.
>
> Did some serious testing of Geo database after I had updated it with all
> Swedish counties to get a grip on how it is supposed to work sometimes in
> the future. I did the test with Scandinavian places as I have a lot of
> different data there and could have use of Geo database in that research.
> And yes - I have used unique UID and PlaceID for my places.
>
> Found 3 strange things:
> --------------------------------------------------------------------------
--
> -------------
> First strange thing:
>
> In master locations I have the following:
> , Countyname, Statename,
> So there is a blank for Cityname and for Countryname but a something for
> County and State.
>
> In Geo database I have put in:
> No city but County, State and Country
> You have put in:
> County in city field, no county, State and Country.
>
> This is what I do:
> Open master location, select the location (above) and click on Show Geo
> location list (button bottom right).
> IF I have written it exactly the same in Master location as it is in Geo
> database it takes me to the correct line in Geo database - good.
> BUT if I have not written the correct county it puts the countyname from
> Master location list into the city field for searching in Geo database and
> then shows me the wrong place. - not good.
>
> I expected the countyname in master location list to be placed in county
> field and the search to be done among counties using that name.
>
> Is this something you have hardcoded for all non-US countries as you have
> not put any county information there or is this just an error ?
> If you have hardcoded it - could you please give us an option of what
field
> you put county in when opening Geo search screen. If not, please fix the
> error.
> --------------------------------------------------------------------------
--
> -------------------------------
> Second strange thing:
>
> In master locations I have the following:
> Cityname, Countyname, Statename,
> So there is a blank for Countryname but a something for City, County and
> State.
>
> In Geo database I have put in:
> No city but County, State and Country
> You have put in:
> County in city field, no county, State and Country. The city I am
searching
> for is not anywhere in Cityfield.
>
> This is what I do:
> Open master location, select the location (above) and click on Show Geo
> location list (button bottom right).
> Get no hit in Geo database - thats ok. Search fields are filled in
correctly
> but both Core fields are empty.
>
> So I set search on Cityfield to "Skip this field" and press Search.
> Now I get a hit on my County, State and Country - thats ok.
> BUT the Core fields only contains County, State and Country. City is not
> included.
>
> Is this by design and why ? I expected the Core fields to take what was
> found in Geobase and add that to the City, not take Cityname away.
> --------------------------------------------------------------------------
--
> -----------------------------------
> Third strange thing:
>
> In master locations I have the following:
> Cityname, Countyname, Statename,
> So there is a blank for Countryname but a something for City, County and
> State.
>
> In Geo database I have put in:
> No city but County, State and Country
> You have put in:
> County in city field, no county, State and Country. The County I am
> searching for is in Cityfield but the City is not there.
>
> This is what I do:
> Open master location, select the location (above) and click on Show Geo
> location list (button bottom right).
> The County is put in City field (same as first situaton) and get a hit on
> the county you have out in City field. Well, found something but not the
> correct one.
> So I move the Countyname from City to County search filed and Search
again.
> Get a hit in Geo database in my County - thats ok.
> BUT Core + now contains Cityname, , Countyname, Statename, Countryname and
> Core contains , Countyname, Statename, Countryname. So Cityname have
"moved"
> one position to the left in the hieracy as Core+ have added a comma and a
> blank between Cityname and Countyname.
> Same thing in Merge Location screen. Only choice I have is take Master
> location or the wrong Geobase name.
>
> That extra comma and blank should not be there.
> --------------------------------------------------------------------------
--
> ----------
>
> Enough for now.
>
> Christer
>
> Legacy User Group Etiquette guidelines can be found at:
> http://www.LegacyFamilyTree.com/Etiquette.asp
>
> To find past messages, please go to our searchable archives at:
> http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
>
> To unsubscribe please visit:
> http://www.legacyfamilytree.com/LegacyLists.asp
>
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
