When I enter a city and parish for Louisiana, it will always check and show a duplicate where the state is Missouri. I have queried Places for Missouri and these do not show up, but legitimate ones in Missouri do show up. There is, thus, a likelihood that I will eventually use the wrong state for family in my birthplace. Are you aware of a similar problem? Is there a way for me to correct this?
(I have checked that these city parish/county groups do not exist in Missouri.)
I am not fully understanding what you mean – can you provide screenshots so someone can provide you advise
Hi: Thank you for getting back with me. I have taken a picture of this occurring now but I cannot find how to upload it to this community site. I went into page by double clicking this person in my pedigree. I went to, I believe, the death information. In this case, I overwrote the death location that I had put in as New Orleans, Orleans, LA and wrote in Gretna, Jefferson, Louisiana. One choice was giving and I clicked on it and the data was written into the field.
When I clicked away from the field, this box came up: attached below.
You will see in this clip that I am presented a choice of the same city, parish and state: one correctly being in Louisiana and the other choice is Missouri. (Missouri does not have a Gretna, Jefferson.)
This has happened with several city/parish areas in that area near New Orleans. (fyi: Louisiana has parishes, instead of counties)
this might be similar to some places in NC and SC. (Gretna, Jefferson (county)..)
The tool is alerting you might have used wrong place because there is more than one similar place. If the first place is correct choice “keep orig” if not then change.
Keep in mind some town can be part of more than one county but usually have a default and might have changed over time periods.
Kevin
@DavidLumpkin To take a screen shot if you are on windows, hit the windows key, shift and S at same time–crop the area you want then just PASTE in here-- you should be able to use just Print Screen also …
I see what you are talking about and you are correct that there is no such place in MO now and I don’t think there ever was BUT I can’t be sure because I know very few places in MO when it was under French and Spanish rule and was considered part of the Louisiana Territory / Illinois Territory etc..
It appears that when you enter a place name, County check is doing just that checking counties rather than city and county..
You have several options here
also here in help Gazetteer
well based on date of event it might depend
In Missouri, Gretna is primarily known as a distinct neighborhood and historical district within the popular tourist destination of Branson (Taney County).
it appears to have been a recognized placed at one time.
“While it was once a standalone settlement, it has largely been absorbed into the city of Branson, though it still appears on topographical maps as a populated place.”
If I understand the question correctly, this issue has nothing to do with County Check or with Gazetteer or with whether the actual place exists in the real world or anything like that. There is not a built-in reference table of any sort that RM is using to pop-up the possible place suggestion.
Instead, if you are typing a place name into a new fact in RM, RM then tries to match what you are typing with places you have already entered into your RM database. That’s it, plain and simple. It doesn’t matter if the places you have typed in are correct or not. It doesn’t matter if County Check is turned on or not. The pop-up offering you places to use is offering you places from your own Place LIst. For example, if you have same named counties in different states, it’s likely first to offer you the county from the wrong state because it offers places is alphabetic order from what you have already typed. It becomes a more accurate guess by RM as you type in more letters.
@kevync1985 Thanks for the info on Gretna, Taney Co., Mo
edit-- I did a search for Gretna in Mo and came up with nothing-- next time, I’ll just check Find-a- grave…
That is true in most cases such as there was a cemetery that 1/2 was in Jefferson Co., IND and the other half in Switzerland Co., IND and of course Kansas City, Mo and KS-- both are good examples of why it would suggest another place BUT
what county check should have said was do you want
Gretna, Taney, Mo or
Gretna, Jefferson, Louisiana
and NOT suggested Jefferson CO for both MO and LA..
A Bug or is it due to the fact that Jefferson Co., LA was originally part of Orleans which was originally part of the Louisiana / Illinois etc territory and Jefferson Co., Mo was originally formed from part of St Genevieve Co., Mo which was originally part of the Louisiana / Illinois etc territory…
@DavidLumpkin – I’m still thinking that it is basically doing a county check BUT think that the 2 states both have to have the same county name ( and possibly the city)–some of the few others that I have had show up that were both same city/ different counties in LA and MO, I was able to get county check to stop showing up after adding United States BUT it doesn’t like Gretna-- no matter what county check shows up each time-- I will note that it only happens when you entering Louisiana 1st-- if you enter Taney Co., Mo, there is no problem
edit @thejerrybryan – Understand what you are saying and would agree with you in most cases BUT NOT THIS TIME!!!
I did NOT have Gretna, Jefferson , Louisiana in my database nor did I have Gretna, Taney Co., MO-- so I turned on County check and used the address Gretna, Jefferson , Louisiana and County check popped right up with the suggestion
Gretna, Jefferson, Missouri-- and now it does it every time, you use it—try it and you will probably see what we mean…
I understand what you are saying, but I cannot reproduce your results. For me, the behavior is identical with County Check turned on or turned off. I wonder if we are talking about exactly the same thing.
I’m talking about the pop-up as you are typing in the place name. My experience is that the name in the pop-up as you are typing in the place name is only using your existing place list. And your existing place list is the same whether County Check is turned on or turned off.
Even if County Check is turned on, it only comes into play when I actually try to save the place name. It doesn’t come into play as I am typing the place name. And if County Check does come into play, it matters not what is already in you database. If County Check comes into play, then it only looks at the County Check database, not at the places you may already have entered..
There is also a little icon for Gazetteer on the right side of the Place Name field where you type the place name. But for me, Gazetteer only comes into play if I click on its icon.
If we are really both talking about the pop-up suggestion that appears while you are typing in the place name, then I cannot explain the difference in the behavior between what I am seeing and what you are seeing
I remember that a few months ago someone posted messages about the same thing. It was different place names, but the same type of thing. It is possible it could be a corrupted personal database or county check database. You may need to send your database to support. You could also try downloading another copy of the places.db. Let us know if your RM is 32 or 64 bits.
CountyCheck doesn’t look at your place list or the city/town level. It will completely ignore Greta. CountyCheck looks at the county, state and country level. There is a Jefferson, Louisana and a Jefferson, Missouri. It’s probably spotting it as ambigious and that’s why it brings up both.
@thejerrybryan No Jerry I am NOT talking abt the pop up that shows when you start typing a name such as in the instance of Kansas City, Jackson Co., MO versus
Kansas City, Wyandotte, KS or St Louis City vs St Louis County
What we are talking abt is that after I type Gretna, Jefferson, Louisiana ( whether or NOT I have Gretna, Taney, Mo in the list and places or not) , this box shows up as soon as I
The problem is that EVERY TIME you enter Gretna, Jefferson, Louisiana, county check pops up-- there is no way to verify the address or change anything to make it stop-- a real pain if most of your ancestors lived there for many many years..
@cweese RM11 64 bit Win 11-- I tried downloading another copy of places.db BUT it didn’t change anything–it still happens–one corrupt database involving one person would make sense BUT since I was able to replicate @DavidLumpkin 's problem in RM 8, RM 9, RM 10 and RM 11-- I don’t think that would be the problem ..
@rzamor1 THANK YOU-- that is what I was thinking
Bottom line is that DavidLumpkin is right. The enabled CountyCheck facility erroneously displays a non-existent Place as an alternative SUGGESTION, despite NOT being in the Gazetteer, nor RM’s Place List. That’s just flat-out wrong.
While I don’t think I’ve entered bad data (after a career of database programming and maintenance), I am an old man. Okay, anything is possible.
So, saying that, and making the assumption that I might have actually previously entered New Orleans area data with a Missouri state, then you are intimating that is only in my data, maintained by the RM database program. If this is so, how do I access that data. I query locates for Missouri and only get back legitimate Missouri places. However, I am likely not querying a “place” table, but the place field found in my populated records.
The drop down list (so to speak) does fuzzy match to similar data and presents that to the user for a choice. Is that presented data in a “place” table. Most normalized databases save repetitive data in files and saves to your live record only a distinctive ID of the data that is actually, then and later, displayed. When the data is queried, it is made to return the full place data by using the ID lookup. I’m sorry, now I’m getting technical.
Basically, can I fix this?
David
Someone replied to your post.
| thejerrybryan
February 2 |
- | - |
If I understand the question correctly, this issue has nothing to do with County Check or with Gazetteer or with whether the actual place exists in the real world or anything like that. There is not a built-in reference table of any sort that RM is using to pop-up the possible place suggestion.
Instead, if you are typing a place name into a new fact in RM, RM then tries to match what you are typing with places you have already entered into your RM database. That’s it, plain and simple. It doesn’t matter if the places you have typed in are correct or not. It doesn’t matter if County Check is turned on or not. The pop-up offering you places to use is offering you places from your own Place LIst. For example, if you have same named counties in different states, it’s likely first to offer you the county from the wrong state because it offers places is alphabetic order from what you have already typed. It becomes a more accurate guess by RM as you type in more letters.
Ok. That’s was Nancy Kessler has been suggesting but she did not know for sure. And yes, there are Jefferson counties in both states. And there is a Gretna community in Missouri, but not in Jefferson County. This my have been an overlooked “gotcha” for the programmers. All the factors need to be compared as a whole against all entries when parsing out unique data. It does show, in this case, that there is a
Greta (city), Jefferson (county/parish), Louisiana (state)
AND a
Greta (city), Jefferson (county), Missouri (state)
The latter does not exist in Missouri, based on all three elements together.
Someone replied to your post.
| rzamor1
February 2 |
- | - |
CountyCheck doesn’t look at your place list or the city/town level. It will completely ignore Greta. CountyCheck looks at the county, state and country level. There is a Jefferson, Louisiana and a Jefferson, Missouri. It’s probably spotting it as ambigious and that’s why it brings up both.
Yeah that is what I was thinking but did not articulate well
Yes @DavidLumpkin , you are getting technical–so this may NOT be what you are asking but here goes-- as far as entering the info wrong, I don’t think you did..
As for the drop down menu offering a suggestion when you start to enter a place
( or checking to see if you accidentally entered info with a MO instead of LA location)–you can go to PLACE on the left hand side – it will show you every place you have used in the database — on the right side , it will show you how many times you have used this place..
If you need to, you can click on the arrow in the USED box and it will open another screen that shows you everyone this location was used on and you can edit it if needed-- if you have 2 of the same places such as my London, England and
London England above, you can merge the 2 places..
again I may NOT be understanding what you are saying BUT the programmers have nothing to do with the place.db ( which i assume controls the output of county check)-- as I understand it is from a 3rd party…
Basically overall as I said before I would just TURN off county check–I personally don’t use it as I don’t want United States listed but do want County included and that causes a county check pop up each time-- as I understand Gretna is a family location for you and every time you put in Gretna, Jefferson, La, county check will pop up-- once turned off, if you need to use county check for some reason, you can run it under tools on left side or the palette at top of page..
Aha! Much thanks for the clarification.
So I did go to Places on the Left and found Gretna, LA and Metairie, LA. ONLY Louisiana and no occurrences in that table with Missouri. So this must be coming from a Roots Magic database somewhere that has the mix up. And my copy of Roots Magic is data checking my entry with this outside (of my copy of the program) database. I am a retired database programmer and fully understand how database works with data. If “Places” is the only database inside of my copy of Roots Magic, then Missouri version of the Louisiana places cannot be show UNLESS there is a referenced internet database with this data mix-up. Just as a geographical fact, the places that are shown in Missouri, just do not exist.
I this point, I take it that I will just have to “live with it”. Sorry that I am so technically anal, just my professional habits still working.
