* Finding incorrectly placed locations in map

[AdrianBruce]

... It should already be identifying places for Lancashire, England that are plotted outside the UK ...

Oh it did. I only wrote that because I'd said filter on "Lancashire" (only) - and then mentally I thought about filtering "just" on "Essex" and realised that I had Essex in both Ontario and New Jersey, as well as the UK, so selecting Essex (UK) for display on the map was more than just a filtering on a single word.

[Gowermick]

Adrian,
Not being one enamoured of plugins, (I prefer to control what happens to my data), so tried your method of mapping a county at a time, and found some right bloomers!

I religiously use Town, County, Country for my placenames in UK, yet despite this I have just found more than a dozen places in Kent, that were geocoded to Kent, Washington, USA

Sorry, but there is really no excuse for this poor geocoding by Openstreetmap, but what can we do?
PS is Openstreetmap a US product by any chance?

[mjashby]

It's very far from being a 'US' sponsored product: https://hardware.openstreetmap.org/thanks/

It's also a World-wide OpenSource project so anyone with sufficient interest and commitment can register and contribute to its continuous development/improving accuracy.

Mervyn

[tatewise]

Mike, the Place Exceptions plugin (along with several others such as Show Project Statistics) does not change your data in any way. It would have probably reported those outlier plots but it is up to you to correct them.
Why not try the Plugin and it might find other exceptions you were unaware of
The earlier users in this thread found plenty.
BTW: The Place Exceptions plugin is now in the Plugin Store and has a Help & Advice page.

Also, the FH place geocoding is not performed by https://www.openstreetmap.org/about but by https://www.algolia.com/ as explained via Help > About Family Historian in https://www.family-historian.co.uk/geocoding.