OSM Schools Matching Queries

The tables below list possible errors in the matching between OSM objects and schools on the official list. Many will be due to mistakes in the OSM tagging. Some may be due to mistakes in the official data. Others will be fine as they are.

• OSM ref:* value not in official data, but school matched anyway
• OSM ref:* value not found in official data, and school unmatched
• OSM ref:* value not in official data, but school has a 'successor' institution
• OSM ref:*=* value could not be parsed, or value in ref=*
• Matched object a long way from postcode in official list

OSM ref:* value not in official data, but school matched anyway

OSM objects with a suitable ref:* key, whose value does not match an entry in the appropriate official list, but for which the school has been matched (rightly or wrongly) by proximity to a different entry on the list. A lot of these errors will be caused by schools changing status and being issued with a new reference number. Some may be typos in the OSM tagging, and others may be schools that have closed but the old site has been incorrectly matched to a different (possibly unmapped) school. The update links will work with the JOSM Remote Control functionality to update the reference number and name for the OSM object. Some matches will be wrong so not all such changes will be appropriate. You must therefore check each one individually before applying it.

Found 30 such OSM objects.

OSM ref:* value not found in official data, and school unmatched

OSM objects with a suitable ref:* key, whose value does not match an entry in the appropriate official list, and which has not been matched to any school on the list. Many will be errors or typos in the OSM tagging. Some may be caused by a correct number for a school that has now closed (and is thus no longer listed in the official data). Others will be institutions listed in Edubase as an "LA Nursery School". These have been excluded from my tool on the grounds that they would probably be better tagged as amenity=kindergarten.

Found 86 such OSM objects.

OSM ref:* value not in official data, but school has a 'successor' institution

OSM objects with a suitable ref:* key, whose value does not match an entry in the appropriate official list, but for which the school has a "Successor" insititution defined in the Edubase Links database (England and Wales only). The update links will work with the JOSM Remote Control functionality to update the reference number and name for the OSM object. Some matches will be wrong so not all such changes will be appropriate. You must therefore check each one individually before applying it.

Found 5 such OSM objects.

OSM ref:*=* value could not be parsed, or value in ref=*

OSM objects with a ref:* key, whose value is not in the right format for an official reference value. Also listed are objects with a ref key that do not have an appropriate ref:* key as well. Note that if an object correponds to two official refererence values, then the correct thing to do is to seperate them with a semi-colon. Unfortunately my tools do not currently deal appropriately with this situation, so such values will be listed below.

Found 17 such OSM objects.

Matched object a long way from postcode in official list

OSM objects with a suitable ref:* key, whose matching entry in the official list has a postcode location that is a long way away. These may be errors in the OSM ref:* tagging. However, they may also be caused by a single school having multiple sites and/or a PO box address.

Found 172 such OSM objects.

Schools matched with more than one OSM object

OSM objects with a a suitable ref:* key, where that key's value appears on more than one object.

Coming soon...

Data derived from OpenStreetMap data, © OpenStreetMap Contributors, licensed under Open Data Commons Open Database License (ODbL). XAPI courtesy of Overpass API.