<div>The data is available in OSM format (or as a set of z12 tiles, obvs) if anyone wants to do this.</div><div> </div><div>Stretching a set of mid-zoom tiles to be a background in Potlatch could be a fairly re-usable approach. But I've no idea how practical that is.</div>
<div> </div><div>Richard<br><br></div><div class="gmail_quote">On Tue, Oct 2, 2012 at 2:01 PM, Andy Allan <span dir="ltr"><<a href="mailto:gravitystorm@gmail.com" target="_blank">gravitystorm@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div class="im">On 2 October 2012 09:55, Richard Mann <<a href="mailto:richard.mann.westoxford@gmail.com">richard.mann.westoxford@gmail.com</a>> wrote:<br>
<br>
</div><div class="im">> 1) put the output back in the database, by using existing keys (eg<br>
> maxspeed=30 mph + maxspeed:source=inferred from presence of residential side<br>
> streets)<br>
> 2) put the output back in the database, using new keys (eg<br>
> maxspeed:inferred=30 mph + maxspeed:inferred:source = presence of<br>
> residential side streets)<br>
<br>
</div>Please don't put auto-generated data back into the database, in either form.<br>
<br>
It would be best to hook the output from your algorithm into an<br>
existing QA system, such as the ITO maps, or keepright, or if none<br>
fit, then into a new QA system.<br>
<br>
Cheers,<br>
Andy<br>
</blockquote></div><br>