<div dir="ltr"><div><div><div>No-one has solved conflation in OSM, so there is no mechanism for re-merging branches (I suspect that it's fundamentally very hard for geo data).<br><br></div>If there were usable common conflation techniques there would be many fewer problems with imports.<br><br></div>A more viable approach is a post-processed version of OSM data. A couple of the firms doing routing apps do various QA routines before pushing out new releases. The problem is that it's quite easy to do decent post-processing clean-up on data for specific domains (roads, boundaries, retail etc), but one gets back to the conflation problem it it's necessary to merge these together again. <br><br></div>Jerry<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 January 2017 at 12:40, Jez Nicholson <span dir="ltr"><<a href="mailto:jez.nicholson@gmail.com" target="_blank">jez.nicholson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">has there ever been discussion about code branching in OSM? In git terms, we are all making changes direct to master. I'm wondering whether small changes could be automatically approved and large changes would require peer review first.<div><br></div><div>I know that this is a huge change to the base infrastructure, so maybe a bot that auto-challenges large/sweeping changes?<br><div><br></div><div>....or is this like in QI when the siren goes off because someone proposes something that has is a commonly held fallacy? or been discussed ad nauseam</div></div><div><br></div><div>- Jez</div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, 9 Jan 2017 at 12:29 ael <<a href="mailto:law_ence.dev@ntlworld.com" target="_blank">law_ence.dev@ntlworld.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Jan 09, 2017 at 11:53:51AM +0000, SK53 wrote:<br class="m_9162558986095249653gmail_msg">
> Somehow I have been oblivious to the fact that large numbers of polygons<br class="m_9162558986095249653gmail_msg">
> tagged natural=heath have been added over the past few months to OSM.<br class="m_9162558986095249653gmail_msg">
<br class="m_9162558986095249653gmail_msg">
<br class="m_9162558986095249653gmail_msg">
I too have encountered at least one armchair mapper who (in my view)<br class="m_9162558986095249653gmail_msg">
incorrectly tagged large areas of Bodmin moor with this nonsense.<br class="m_9162558986095249653gmail_msg">
I changed this rubbish in the areas that I have directly surveyed, but<br class="m_9162558986095249653gmail_msg">
did not think that I should override another mapper who clearly had<br class="m_9162558986095249653gmail_msg">
spent a lot of effort in adjacent areas without consultation.<br class="m_9162558986095249653gmail_msg">
<br class="m_9162558986095249653gmail_msg">
I first noticed this problem several months ago: I cannot remember<br class="m_9162558986095249653gmail_msg">
whether I tried to contact the mapper to ask what was happening.<br class="m_9162558986095249653gmail_msg">
<br class="m_9162558986095249653gmail_msg">
I have had other instances of armchair mappers adding what I regard as<br class="m_9162558986095249653gmail_msg">
very dubious landuse tags to areas that I have extensively surveyed.<br class="m_9162558986095249653gmail_msg">
When I contacted one of the main offenders; I didn't get a very helpful<br class="m_9162558986095249653gmail_msg">
response.<br class="m_9162558986095249653gmail_msg">
<br class="m_9162558986095249653gmail_msg">
Anyway, I suspect that this is a problem over large areas.<br class="m_9162558986095249653gmail_msg">
<br class="m_9162558986095249653gmail_msg">
ael<br class="m_9162558986095249653gmail_msg">
<br class="m_9162558986095249653gmail_msg">
<br class="m_9162558986095249653gmail_msg">
______________________________<wbr>_________________<br class="m_9162558986095249653gmail_msg">
Talk-GB mailing list<br class="m_9162558986095249653gmail_msg">
<a href="mailto:Talk-GB@openstreetmap.org" class="m_9162558986095249653gmail_msg" target="_blank">Talk-GB@openstreetmap.org</a><br class="m_9162558986095249653gmail_msg">
<a href="https://lists.openstreetmap.org/listinfo/talk-gb" rel="noreferrer" class="m_9162558986095249653gmail_msg" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/talk-gb</a><br class="m_9162558986095249653gmail_msg">
</blockquote></div>
</blockquote></div><br></div>