FHRS/OSM comparison

Wychavon

District statistics

The colours in this table act as a key for the maps below

*A match is considered successful when the OSM node/way's fhrs:id matches an FHRS one and the OSM addr:postcode or not:addr:postcode matches the FHRS one.

**OSM nodes/ways with an addr:postcode or not:addr:postcode that matches the FHRS postcode, or with an addr:postcode but no fhrs:id tag.

District progress graphs

Click on a graph below to enlarge it. There are also graphs showing progress across the whole of Great Britain

Overview

Dotted lines in the map below show the difference between the OSM and FHRS locations for establishments that have been matched when those locations are more than 500 metres apart. Please see the table below for a list of these distant matches.

Suggested matches

Download suggested matches GPX

Postcodes missing/mismatched

Below is a list of OSM entities which have a valid fhrs:id tag but a missing/mismatched addr:postcode. N.B. This does not necessarily indicate an error with the OSM data. If a not:addr:postcode tag matching the FHRS postcode is found, the OSM entity is removed from the table and is instead considered a successful match.

Mismatched fhrs:id tags

Below is a list of OSM entities which have an fhrs:id tag for which there is no matching FHRS establishment. This may indicate an establishment which has closed, but please check before making any changes to the OSM data. Parsing multiple FHRS IDs separated by semicolons is currently unsupported so these may also appear below.

Duplicate fhrs:id tags

Below is a list of all the OSM entities which have an fhrs:id tag that is shared with at least one of the OSM entities in this district. N.B. This does not necessarily indicate an error with the OSM data.

Distant matches

Below is a list of all the OSM entities which have been matched to an FHRS establishment where the OSM and FHRS locations are more than 500 metres apart. N.B. This does not necessarily indicate an error with the OSM data as OSM locations tend to be more accurate than those in the FHRS database.

Generated using python-fhrs-osm on Mon 22 Apr 2019 at 07:41.

Report bug or suggest feature

Contains Ordnance Survey data © Crown copyright and database right