<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>On 2020-08-13 12:25, Robert Whittaker (OSM lists) wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">On Wed, 12 Aug 2020 at 16:56, SK53 <<a href="mailto:sk53.osm@gmail.com">sk53.osm@gmail.com</a>> wrote:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">OpenRoads from the Ordnance Survey contains a field containing the toid for the street name. I wonder if we should include these alongside usrn & uprn. They may be more useful than either for gathering complex roads which share a name.</blockquote>
<br /> I'd tend to see the TOIDs are just an internal ID used in OS MasterMap<br /> and not something that there's much value in adding to OSM.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">That is apparently not how OS are positioning TOIDs, according to Wikipedia</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><a href="https://en.wikipedia.org/wiki/TOID">https://en.wikipedia.org/wiki/TOID</a></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">TOIDs are intended to be persistent, and aimed at integration between databases. OSM would be one such database, wouldn't it?</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<p><br /></p>
</body></html>