The colours in this table act as a key for the maps below
|OSM nodes/ways with valid fhrs:id and matching addr:postcode or not:addr:postcode||5|
|Relevant OSM nodes/ways with postcode but no valid fhrs:id||37||GPX|
|Relevant OSM nodes/ways without postcode or fhrs:id||237||GPX|
|OSM nodes/ways with valid fhrs:id but mismatched/missing postcode||1|
|OSM nodes/ways with invalid fhrs:id||0||GPX|
|FHRS establishments with no matching OSM node/way||715||GPX|
|Total number of relevant OSM nodes/ways||280|
|Total number of FHRS establishments||721|
|Percentage of FHRS establishments successfully matched*||0.7%|
|Percentage of relevant OSM nodes/ways with a postcode**||15.0%|
*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.
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.
Download suggested matches GPX
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.
|Name||OSM addr:postcode||FHRS postcode|
|Popadom's||TS24 0YB||TS24 0YD||Edit in JOSM|
There are no fhrs:id mismatches to show for this district.
There are no fhrs:id duplicates to show for this district.
There are no distant matches to show for this district.
Generated using python-fhrs-osm on Tue 22 Aug 2017 at 07:28.
Report bug or suggest feature
Contains Ordnance Survey data © Crown copyright and database right