Corrupted FamilySearch Places KML file: Utah?

genthusiast

https://www.familysearch.org/research/places/?reqParents=342&reqParentsLabel=State&reqParentsType=362&includeIsParent=true&primaryText=Utah%2C%20United%20States&searchTypeaheadInputText=Search%20Within%3AUtah%2C%20United%20States

There are at least 4 outliers that need relocation? whoops ... none of those are in Utah - someone accepted them in error or the KML got corrupted somehow.

Gordon Collett

What are the four places you are referring to? When I look at your link, I do see some dots over in Nevada but for all of them I have checked so far, they all have end dates of 1861. That is when Nevada territory was created from the western half of Utah territory. (see: https://en.wikipedia.org/wiki/Utah_Territory ) Since Nevada territory did not exist until 1861, any place in current Nevada is correctly described as being in Utah for 1861 or earlier.

One example is Antelope in Humbolt county. It has two entries in the database: https://www.familysearch.org/research/places/?searchTypeaheadInputText=Antelope,%20humbolt&text=Antelope%2C%20humbolt One for when it was in Utah and one for when it was in Nevada. The Nevada copy is missing all dates

If I was in charge, I think I would have made this more clear in the database by having two entries for Antelope in the same "folder" that is as two time periods under the same place rather than as two separate places. But as we've discussed before, this database is a gargantuan task with lofty goals and perfecting it is a long term effort.

genthusiast

Also, why are there no County boundaries displaying in Utah? I zoom in and don't see them. I guess contact INEGI

genthusiast

Thanks Gordon, I guess I didn't look at Utah Territory timeframe - just saw those 4 out there and was confused.