When are WikiTree members going to start addressing/correcting Counties that didn't exist before a certain date?

+15 votes
835 views

I am finding too many profiles where the county didn't exist for the date entered?  Who is going to take responsibility to correct all these profiles? What's even worse is that the status button is selected as certain on some the profiles.

  • Berks County, Pennsylvania over 2700 profiles

https://plus.wikitree.com/default.htm?report=srch1&Query=Berks+Pennsylvania+sql%3D%22(%5BDefault%5D.%5BBirth+Date%5D.AsNumber+%3C+17520311)+and+(%5BDefault%5D.%5BBirth+Location%5D.AsString+like+%27*Berks*%27)%22&MaxProfiles=500&Format=

  • Berkeley County, South Carolina over 1600 profiles

https://plus.wikitree.com/default.htm?report=srch1&Query=%09Berkeley+South+Carolina+sql%3D%22(%5BDefault%5D.%5BBirth+Date%5D.AsNumber+%3C+18820000)+and+(%5BDefault%5D.%5BBirth+Location%5D.AsString+like+%27*Berkeley*%27)%22&MaxProfiles=500&Format=

in Policy and Style by Tommy Buch G2G Astronaut (1.9m points)
edited by Tommy Buch
I see this issue several times per week and these types of errors, as you know, make categories less useful than they might be. When I try to open your links above in FireFox, I get a blank screen result so I can't quite see what this allows us to view.

One problem I see is the drop down menu choices. I know this comes from an external source but it does not account for the many hundreds if not thousands of county border changes, defunct counties, etc. I suspect it often leads people entering correct information to suspect it is in error because it's not one of the choices seen in the drop down. They then pick what they think might be the best choice even though it is in error.

I'm not sure there is a way to deal with moving borders but could the database be programmed with county start (and end) dates so if there is a conflict between date and location a flag goes up? I realize that might involve a tremendous amount of research and programming.
T - You are correct, it is a tremendous amount of work. The Atlas of Historical County Boundaries took well over 30 years to create. It is a great resource, though. https://digital.newberry.org/ahcb/
Hi Kay. That link reminded me of all the boundary animations Newberry has. That tells me that the info we could use has already been data-entered -- but is it in a form that could help this issue...it might be.
I can't see your list so I don't know what date you are using for Berkeley County, South Carolina.  Berkeley County was one of the original counties in the Province of South Carolina.  It is not the same as the present day Berkeley County.  Many of the profiles created for the colonial period in South Carolina just use South Carolina, which is what comes up on the dropdown list, or some variation of British Colony. But the US Southern Colonies Project guidelines says to use Province of South Carolina.  I am trying to change them as I find them.
If I remember correctly, the entire database can be downloaded. I do not know what formats it may now be in (used to be in an exchange format I helped develop) nor what mechanisms there are to search the data (e.g., by name vs location and by date). That said, it seems to me that it would still be a large undertaking.

But first perhaps we need country, then state (or equivalent), etc.
The date used for Berkeley County, South Carolina was Birthdate < “18820000”.
If you click on the link above and then click the “Get Profiles” button on the left side of the webpage that comes up, it should show you the list of profiles.
Yes, I see the list now.  Using the 1882 date brings up the colonial profiles, as well as the profiles for the modern Berkeley County, so some are correct and some probably aren't.
It is a continuing problem, the drop down list as other's have mentioned is from Family Search.

FS has thousands of errors ranging from just incorrect locations as in the place did not exist for many years in some cases 50 or more years before the location as used existed. Or just inaccurate transcriptions of place names.

A large number of WT members through no fault of their own use the location that pops up.

It's wishful thinking that PMs who discover family connections in other countries will have any knowledge about accurate place names in the other countries.

As someone who researches early Canadian immigrants I frequently or perhaps almost always find errors in the FS location database.
Since WikiTree strives to be accurate, at least with pre-1700 profiles, perhaps this is an area where WT can take a leadership position in the field and find a better way to address the problem. As others have noted it may be wishful thinking to hope those working family connections in other countries will have knowledge of accurate historical place names and as other issues which arise in WT have shown getting all members to take personal responsibility for this on their managed profiles (sadly) isn't going to work.

13 Answers

+20 votes

Addressing issues like these and providing guidance on the correct historical usage is a collective responsibility.

While it can be overwhelming given the volume of profiles needing corrections, many community members are already actively engaged in correcting these types of errors. Several projects even have dedicated teams that monitor and work to resolve such issues as their time permits.

Additionally, there are general suggestions available for addressing these types of errors, which can be found under the DBE 6xx series Suggestions.

If you are encountering numerous issues, consider reaching out to the relevant projects to discuss these concerns. They may be able to alert their members and include these corrections in their to-do lists or goals. Collaborating with these groups can help ensure that the necessary updates are made efficiently and effectively.

by Steven Harris G2G6 Pilot (752k points)
Yes, there is a "correct" format. The "correct" format is one that is consistent. You are right when you say there is "no 'correct' format", but you need to continue your sentence and add "on WikiTree and its projects".  Find a Grave uses a consistent format.
People on WikiTree legitimately have different opinions about which of those location formats to use. Who is to decide which is "correct"? It's likely that the two projects decided to allow a variety because there is no prospect of consensus on a single choice.
@Tommy - and FGs "consistent format" renders Australian locations into something most of us do not recognise.
Who is to decide which is "correct"? Well, usually a database comes with a user's manual and what values are acceptable. In order to run an efficient and consistent database, the owner(s) of the database decide what is going to be a "correct" or "consistent" value.
@Melanie - I don't know if you mean that Find a Grave doesn't have the locations that you need, but my point is that they have predefined locations in a database which allows them to maintain an efficient and consistent database.
@Jim the England Project allows for either "London, England, United Kingdom" or just "London, England". Is partly true. Most People don't use Great Britain but it was used from 1707 until 1800 and United Kingdom wasn't used until after 1801. The England Project is fine with people not adding United Kingdom after 1801.

Here is what is on the page you linked to -

Great Britain did not become an entity until 1707, and from 1801, it was superseded by the United Kingdom. Do not use Great Britain in an English location before 1707 or after 1801. Spell out Great Britain (and only "Great Britain", do not use any variants) in full. Great Britain is in addition to England and does not replace it:

Village or town, county, England, Great Britain

The United Kingdom did not become an entity until 1801. Do not use United Kingdom in an English location before this date. Spell out United Kingdom (and only "United Kingdom", do not use any variants) in full. United Kingdom is in addition to England and does not replace it:

Village or town, county, England, United Kingdom

It is not a requirement to add Great Britain or United Kingdom after England in their respective time periods.
Kathy, what you are saying is that the England Project (the closest thing to the "owner(s) of the database" in this case) allows "London, England" or "London, England, Great Britain" between 1707 and 1801, and "London, England" or "London, England, United Kingdom" since 1801. In both cases, to avoid argument, it permits variants. The point I was making is not challenged.

In each time period, enforcing either variant would leave one group of people dissatisfied. The project's decision to avoid that, rather than imposing an arbitrary and oppressive "consistency", is very sensible.

These are all correct at some time period:

  • Liverpool, Lancashire, England
  • Liverpool, Lancashire, England, Great Britain
  • Liverpool, Lancashire, England, United Kingdom
  • Liverpool, Merseyside, England
  • Liverpool, Merseyside, England, United Kingdom
Each week we get suggestions regarding United Kingdom at the wrong time period, and every week members do wikitree+ queries for profile using Lancashire/Merseyside incorrectly (I think we get a lot of the current county coming from Find a Grave on profiles for people who died before the county shift). While it would be nice for people to get these correct, they are easy for people who know the area to fix.
In my mind the much bigger problem is profiles that do not match the standard format and so are not in our reports and wikitree+ searches for region and country. These problems include
  • Liverpool
  • Lancashire Liverpool
  • Liverpool Lanc
  • Liverpool Lancashire UK
  • Liverpool, Lancashire, England. UK
  • Liverpool, Lancashire, Angleterre, Royaume-Uni
  • Liverpool Lancashire, England
Lancashire folks also do searches for these but this does not seem to be the norm for most geographic projects/teams.
If you do a search for unknowncountry you will find many many locations that are not formatted in a way that work with the database. (The other problem is places that are not yet in or corrected in the locations table Aleš maintains and which allow variants to be found in wikitree+ and included in reports - the gaps here are because location experts have not let him know what needs to be included).
There are currently 519,958 profiles with an unknown country in the birth location
Some place (United States, Canada, Nederland, England, Australia, South Africa etc.) have the states/provinces/counties included as regions as well. You can find these with birthregion=unknownregion but this will also retrieve a country with no region (that is, England on its own) so I do not know how many are locations that need to be fixed. At least in these cases they come up in the country searches so the people that know the area may find them to correct them.
I would really like us all to collectively work on these unknown country problems. These really need to be in order before all the subtleties of a name of a place in specific time period can be addressed on all of wikitree.
When I was at school it was England, Sorry but I am new at this game.I will stick to Western Australia.
As long as you include England you are perfect
+19 votes
Ideally, each person who manages a profile should be the person to make the correction. But perhaps we could have a "challenge" occasionally for those interested to tackle these kinds of errors.

It's not easy, though. I just made a correction to one profile. It helped that a "town" name was provided for that profile. But Berks was created from portions of three other counties. If only Berks County is supplied in the data field and no town--as is often the case--and if no sources are provided--as happens too often--there is not really any way to figure out which of those counties an individual was actually born in, was married in, or died in without some deep research.
by Nelda Spires G2G6 Pilot (567k points)
+11 votes

Often, source records (such as delayed birth records, death records, newspaper articles, etc.) list the current name for the location of birth, and users simply transfer this information. I've been told that we don't have control over the list that appears in the dropdown when selecting locations. However, it would be beneficial if the dates for counties and townships appeared alongside their names, similar to how it's done for countries. This could help resolve many of the issues.

I haven't checked all the profiles you mentioned, but the categorization isn't incorrect in all cases. The individuals did live in the county after its creation. The main issue lies with the birth location.

Given that mistakes in source records are easy to make, adding dates at the end of each location could help reduce these errors.

by Jimmy Honey G2G6 Pilot (160k points)
Birth Locations are not always correct on birth certificates. My eldest Brother according to Mother was Born at home, Waterloo the Birth certificate has Bunbury. Western Australia, the same applies to some of the cousins. I thought I would just add this fact.
When researching, many times I question the Place listed in the document, so in a separate window I keep open https://familysearch.org/research/places which will give you much more information based on time periods. One problem is you need to spell the name correctly which is a common problem in many records. It does contain an error or two, but a very good resource. If you find an error, you need to advise them.
Some local towns here in Western Australia come up with red line under them are correct. Because they are Native Australian names which do not ad up  with the English language and even worse the American English Language.
+12 votes
While it would be nice for these to be corrected, they at least appear in results when you search for Pennsylvania (or South Carolina). I am much more concerned about locations that lack a state (and a country), use abbreviations, are not ordered from smallest to largest division (city, county, state, country), or are not punctuated correctly for the locations to be properly parsed. For example, https://plus.wikitree.com/function/WTWebProfileSearch/Profiles.htm?Query=birthlocation%3DPennsylvania+not+birthregion%3DPennsylvania&MaxProfiles=50000&Format=&SortOrder=BiLoc&PageSize=1000
I work on my only little section because as Steven said, it is a collective responsibility,
by W Robertson G2G6 Pilot (121k points)
I was just going to say something similar.  Glance through your results.  How often do you see any version of United States in them?  You have questioned previously about getting United States to be consistent, but there are more records that don't have United States, of any variation, so expecting the country on all records is a much larger situation.   Once it is on the records, then you have to worry about the punctuation (required commas in front of state and country), as well as abbreviations for state or country.  

It isn't just the United States. I am sure most countries have plenty of records with only a county or region and not the country because people don't include their country when they are familiar with their area.

W, I didn't quite follow this "they at least appear in results when you search for Pennsylvania (or South Carolina)."  Could you clarify that? Doing some research two weeks ago in two counties of colonial Pennsylvania if found that none of the historically accurate locations appear in the drop down selection menu imported from FamilySearch. 

I am referring to using WikiTree+ to search and the reports for suggestions, unconnected, unsourced. If you use Pennsylvania somewhere in a location field (it may lack correct punctuation or be first, followed by the town, include "British American Colonies" etc) it will appear in a search for birthlocation=Pennsylvania but it will not appear in birthregion=Pennsylvania. If you structure a location correctly and use PA, United States, it will not come up in a search for birthlocation but it will be in a search for birthregion=Pennsylvania. If you use Penn or Penna it will not come up in either search.  In my mind, getting places to a correct country and then to a correct region is a more pressing problem overall. Once there, people who know the region well can make corrections as needed.

For example, this search  https://plus.wikitree.com/default.htm?report=srch1&Query=open+birthlocation%3DLancaster+birthcountry%3Dunknowncountry+or+open+birthlocation%3DLancaster+birthregion%3Dunknownregion&MaxProfiles=5000&Format=&SortOrder=BiLoc&PageSize=1000 has locations that the system cannot identify either what country they are in (probably all US and Canada) or what region (a lot in  Pennsylvania and South Carolina and Ontario, but also other places). I think this makes profiles much harder to find including for people who work on that area can help improve them.
W,

I feel you. I've been chipping away at these improperly encoded PA locations as my attention allows.

Thanks again for the queries you wrote me previously. They've been a big help.
You might want to see how many profiles for Pennsylvania have been created each year, and at the end of 2024 check again. The past years will increase due to making corrections and I am enjoying being able to see these numbers for our efforts. I wish I had numbers from November 2022 when we began a lot of location cleanup for Lancashire. Lancashire totals over 3 months https://www.wikitree.com/wiki/Space:Lancashire_Team#Profiles_Created_by_Year
+15 votes
There are over 1 million profiles where the country is called either "Germany" or "Deutschland". Because this naming should be only used from 1949, one can say that the biggest part of it is wrongly named. Well, who is gonna change those? Someone who knows what naming is correct at a certain point of time... Roughly 4,300 profiles for those two counties sounds somehow doable compared to the 1m+ German profiles.
by Jelena Eckstädt G2G Astronaut (1.5m points)
So Germany was "Deutschland" before1949, If that is correct then I have some profiles to correct.
Before 1806 it was "Heiliges Römisches Reich" (Holy Roman Empire). There were about 750 different territories in the about 800 years of its existence. To know the correct naming of the territory, you have to know the location and the date, because many locations were part of different territories in different times.

Some parts of Germany were from 1806 through 1813 part of the "Rheinbund" (Confederation of the Rhine). Again, you have to know the location to know if "your" territory was part of the Confederation of the Rhine.

In 1815 was founded the "Deutscher Bund" (German Confederation). All of today's Germany was part of it.

In 1866 was founded the "Norddeutscher Bund" (North-German Confederation). Some parts of today's southern Germany were not part of it

In 1871 the "Deutsches Reich" (German Empire) was founded. Through 1945 the country is always "Deutsches Reich".

From May 1945 through May 1949 it is "... Besatzungszone" (... occupation zone) Depending on the location it is American, British, French or Soviet occupation zone.

From May 1949 to Oct 1990 the western part of Germany was "Bundesrepublik Deutschland" (Federal Republic of Germany). From Oct 1949 to Oct 1990 the Eastern part was "Deutsche Demokratische Republik" (German Democratic Republic). On 3 Oct 1990 the area of the GDR joined the area of the FRG to create the new Bundesrepublik Deutschland. The German ID-cards have "Bundesrepublik Deutschland" on it.
Perhaps I would better just sticking to Western Australia, where I know what is what.Craigie 321
+13 votes
This question appears to relate to the USA or it's predecessor status as colonies without actually saying so, a common problem faced by those of us in other parts of the world when dealing with American profiles, no few of which only have state codes (eg Ca) rather than names.
 I routinely find this same issue in New Zealand, our counties, towns and cities have been thru' serial reorganisation but sources such as Findagrave use current counties/districts instead of the historicaly correct name.
 Even finding the historic boundaries and dates can be an issue.
by Gary Burgess G2G6 Mach 7 (78.2k points)
+11 votes
It has occurred to me that some of the location problems may arise when FindAGrave is used as a source.  The cemetery is listed there in its current location, but at the time a person was buried, it may have been in a different county.  And if the birth date is taken from FindAGrave, it might also have the wrong county.
by Mary Morgan G2G6 (6.2k points)
I find FinAGrave frustrating in putting "Brisbane CIty" when my home city has NEVER been called Brisbane CIty just Brisbane.
Once a place has over 10,000 people it is a city Here in Western Australia, trust this helps. We do not say Perth City it is just Perth.
I agree that Findagrave is the cause of many errors. I find profiles of people born in England in the 1600s buried in the wrong county because of changes two centuries later. In addition, the adresses for graveyards and cemeteries  includes the names for subdivisions of counties not created  until the late 20th century . They're not even correct for today because there have been further changes since 2019. (e.g. Trent Somerset, 1600; Trent, Dorset, 1894; Trent, West Dorset, 1974; Trent, Dorset 2019. (Find a grave uses Trent, West Dorset but includes burials from the late 16th Century)
+11 votes
Though this does not directly address Tommy's issue.  This is a way, we can begin to help stop more errors from happening.

You do have some control over the location list that appears in the WikiTree drop-down menu.  The dropdown list is based on FamilySearch Places. So you must be logged into your FamilySearch account to do this.

 You go to this website:

https://www.familysearch.org/research/places/

Find the place that is questionable.  Click on the one in the results that you would like corrected.  Then click on "Improve This Place".

A window opens and you select from the drop-down menu "What is incorrect or incomplete?".  Then you describe the issue, provide any sources to back up your request, and provide your email.

The FamilySearch teams research your request and will either approve it or tell you they need more information.  

The key thing is to provide the years that apply to that location as that will help WikiTree users from selecting the right one.  Also the creation of Free Space Profiles for locations outlining the history of that particular place would be helpful to find out which historic category to select.

I personally have changed approximately 35 places on FamilySearch since I joined WikiTree in January.  I have also requested multiple duplicated locations be merged together.  FamilySearch always sends you an email to let you know once it has been done.

At least this is one easy way all of us can start to fix the location issues.
by M Gillies G2G6 Mach 4 (48.0k points)
edited by M Gillies

"You do have control over the location list that appears in the WikiTree drop-down menu.  The dropdown list is based on FamilySearch Places. So you must be logged into your FamilySearch account to do this."

I will have to try that.

My problem is with Stamford Baron in England.  It was in Northhamptonshire  from the time of the conquest til the late 1800s.  For a while in the late 1800s and early 1900s it was in Lincolneshire. Since 1974 it has been in Cambridgeshire. (For part of the 20th century it was in Huntngdonshire, but I do not have the precise dates.)

The "puldown" options are

Northamptonshire, England (- 1801)

Northhamptonshire, England, United Kingdom (1801-)

Lincolnshire, England  (-1801) (THIS WAS NEVER RIGHT)

Lincolnshire, England, United Kingdom (1801-)

There are no options for Cambridgeshire or Huntingdonshire.

I think that much of the Soke of Peterborough suffers from the same problem.

Well, Janet.  The two duplicates with the United Kingdom will be very easy for them to fix and will not need any source.  You will just have to submit the two requests separately.

As other people say, it is tough to actually find out the histories of some locations as we are only as good as the sources we are using.  However, I just look on the positive side and every location we fix is one less that is wrong smiley

+6 votes
I have an issue with this in that

Historicaly accurate  does not translate to

Easy to understand unless you know beforehand.

So many colonies such as "Victoria" all over the world.

Canada, South Africa, Australia and possible more.

My Answer to the problem is easily programmable and doable, as I have personally created a code to do so in the past. (when I could code - now not so good at coding).

Put in the "THEN" and the program picks up the "NOW" and both are displayed.

Maybe a thought for the next Hacktober!
by NG Hill G2G6 Mach 8 (85.4k points)
+7 votes
Some parts of the world have more changes than others.   The Germany project created a spreadsheet to help members. A large part of Europe was part of the Holy Roman Empire even into 1800s.  Countries like Germany did not exist until 1871.  There was German cultural identity long before there was a political country.    Portugal wasn’t a country until 1700s.   Parts of France were ruled by Switzerland and Alsace and Lorraine went back and forth with what is now Germany several times.   During Napoleon’s reign a lot of Germany and points even farther Eat were absorbed into France.    I suggest the concept of a birth location is better handled by modern names as most members I think have a better idea of where their ancestors came from in modern map terms.  Expecting people who are not into being geohistorians to get locations correct is unrealistic.   Even many existing databases are riddled with errors.     our info is only as good as the sources we use
by Laura Bozzay G2G6 Pilot (835k points)

"Portugal wasn’t a country until 1700s."

Huh? Portugal became an independant kingdom in the 12th century

The History of Portugal - Portugal.com  in the wee hours of the morning my tired eyes read 1179 as1779 so my mistake.

+5 votes
I change them all of the time here and on other sites but I'm fallible and use the drop down menu often for places as I trily thought this was something created and uodated through WikiTree; so now I'm also realizing when I make a suggestion for a place name it is for Category only and doesn't have anything to do with the actual locations, correct? No idea the "drop down menu" was externally sourced?

 Thanks for this as I will make sure to check these past any suggestion / error notifications for each of the profiles I work on from here out!
by Becky Simmons G2G6 Mach 2 (27.3k points)
I don't think it's possible for any of us to get everything correct. I went through London (England) profiles adding locations where there weren't any, but being born there and still thinking of my 'patch' as Middlesex, it didn't occur to me that after 1889 they should all be London and not Surrey, Kent, Middlesex etc. (so had to go back and change quite a few!)

Even in 2000 I still thought of it as Middlesex! While some of us can begin to tidy them up, it's just too much for the average person to cope with. I avoid profiles from other countries because I just can't know (or have the time to look up) where somewhere should be.
+4 votes
Could there be a programming solution to this issue? I realize it may take a bit of time to complete but it should be doable. I believe currently the drop down list is only based on the location field.  Couldn’t the location drop down list be programmed to look at the year and provide a location list based on this? The currently used list can still be used as a default for everything else until other specific lists are developed.

Of course, a specific location may need many different lists based on time, but as I’ve read here in the answers and comments, many individuals and groups have such lists developed already for personal use.

Also, it may be necessary to have separate year and location (country) input fields for a lookup.

Maybe I’m crazy or overly optimistic or this has been discussed before but I think this could be accomplished in a relatively short timeframe. Maybe some programmers can add some perspective regarding how realistic this would be.
by Dennis Heltemes G2G5 (5.1k points)

There is already an option quite similar to this in the WikiTree Browser Extension - see https://www.wikitree.com/wiki/Space:WikiTree_Browser_Extension#Locations_Helper. It looks at the relevant date and moves any location suggestions that are not valid for that date to the bottom of the list. So if the list contains the correct name for that time period it makes it easier to find it, but it doesn't help if the correct name isn't in the list at all.

There is a programming solution, but it's just not a priority.

Even basic valid data checks are not a priority.
+5 votes
One of the causes of this is that it can be very difficult to know what is correct or not, even if you're trying to do it right and have the best intentions.

Constantly changing county boundaries can be hard to follow and we don't always know what we don't know. Records are often described as being of a certain place, because they are currently held in that place. I've had this experience in both the U.S. and Scotland.

Early U.S. records may end up as part of a county's records, but the county didn't exist at the time. Something will pop up in my research some way down the line and it's hard to remember all the places I need to go back and update to the correct place.

Scotland's parish records tend to be named with the post-1890 counties. But before that the counties weren't contiguous, so you have to look at old maps to know exactly where the person lived, where the parish was, etc. Functionally, the parish was part of that county's parishes, but it might have physically been in an exclave of a different county. So the citation might say one place, but it was really another. I'm pretty sure that virtually all the places that were in exclaves before the counties were made contiguous are wrong in the drop down. But if you have a parish record that says its from Ross-shire and a drop down that says that's where the place is, it takes some pretty advanced knowledge to know that it's not.

Anyway, I agree that the goal should be to make all the places correct and we should correct them as we find them, but I don't think it's just people being sloppy or lazy in their work.

It might help to start a mini-campaign to make it clear to users that the drop down menu is there to help, but they aren't obligated to choose something because it isn't always correct for the dates, places are know to be missing, etc.
by Regan Conley G2G6 Mach 4 (47.1k points)
Yes many parishes in Scotland cross county lines.

I have had a continuing conversation with someone regarding the birth location of a 2nd or 3rd Cousin several times removed in the 1780s.

The parish was located on the border between Berwickshire and Roxburghshire, the parents lived in the same place during the time their 5 children were born, the parish did not move, the baptism records however sometimes give Berwickshire as the location and other times Roxburghshire.

Quite why the details in the record were recorded differently I don't know, maybe it depended on who the person was who recorded the baptism.

Sometimes I think the records stated where the people lived, sometimes where the parish was. Those early Scotland parish records are a bit like the wild west.

There are some good maps on the National Library of Scotland website.

There is a nice colorized 1807 county map that does a good job of showing all the exclaves scattered around. Nairn and Cromarty in the Highlands have a lot of them, but they aren't the only ones.

The Boundary Map shows the parish and county outlines with the names of each—use the slider at the bottom of the left hand column to set it to 1840s. You can see that there are lots and lots of small bits outlined as counties. When you zoom in on a particular place it will tell you what it actually was at the time. Sometimes, you may see the place name in the box change as you move your cursor, but no obvious boundary if the parish is in multiple counties. Then you might need to go back to the 1807 map for that detail.

Related questions

+5 votes
1 answer
186 views asked Dec 14, 2018 in WikiTree Tech by Philip Smith G2G6 Pilot (342k points)
+7 votes
1 answer
328 views asked Jun 30, 2022 in WikiTree Tech by Stuart Awbrey G2G6 Mach 8 (86.0k points)
+7 votes
1 answer
275 views asked Jul 11, 2023 in The Tree House by Kathy Zipperer G2G6 Pilot (476k points)
+15 votes
3 answers
+12 votes
3 answers
233 views asked Dec 31, 2023 in WikiTree Tech by Kathy Zipperer G2G6 Pilot (476k points)
+6 votes
2 answers
223 views asked Jul 21, 2023 in Genealogy Help by JG Weston G2G6 Mach 2 (28.8k points)
+18 votes
4 answers
+4 votes
1 answer
598 views asked Apr 3, 2022 in WikiTree Tech by Cindy Cooper G2G6 Pilot (331k points)
+11 votes
1 answer
368 views asked Feb 10, 2022 in The Tree House by Kathy Zipperer G2G6 Pilot (476k points)
+6 votes
3 answers
331 views asked Oct 24, 2021 in WikiTree Help by Cindy Cooper G2G6 Pilot (331k points)

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright

...