<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2012-11-21 14:47, Sander Deryckere
wrote :<br>
</div>
<blockquote
cite="mid:CABUOUO-PRt-U=tzY80zJfYvYgCze2EZUN17Lh3UHH+aJ44U+Yg@mail.gmail.com"
type="cite">Always take some time, you knew that uploading 1000
POI wasn't going to be appreciated.<br>
<br>
Uploading bugs to OpenStreetBugs is very easy. A few lines of bash
or perl code would do <a moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/OpenStreetBugs/API_0.6#addPOIexec">http://wiki.openstreetmap.org/wiki/OpenStreetBugs/API_0.6#addPOIexec</a><br>
</blockquote>
I'm sorry not to always make every answer personal.<br>
<br>
I have just been round correcting a 20+ bugs of OSB over a rather
large area (low density).<br>
Most of what I did was erasing the requests because they had already
been corrected outside OSB, even 1 or 2 years ago. Other bugs were
saying things like "priority is the other way" without thinking that
if it was corrected outside OSB too, doing what is said would set
the priority wrong again.<br>
On the other hand, we have just heard of Teddy: kudos, Teddy:
<blockquote type="cite">I have worked with <a
href="http://tools.geofabrik.de/osmi/">http://tools.geofabrik.de/osmi/</a>
hto fix error of
routing. 2 months of work and hundreds of roads have been
corrected in
Wallonia and in the surrounding area. Pffff, it is well
advanced...
</blockquote>
<a
href="http://tools.geofabrik.de/osmi/?view=routing&lon=5.23069&lat=50.14893&zoom=8&overlays=unconnected_major1,unconnected_major2,unconnected_major5,unconnected_minor1,unconnected_minor2,unconnected_minor5">New
crater on Earth.</a><br>
This is why I believe more in OSMI/OSMOSE than in OSB.<br>
<blockquote
cite="mid:CABUOUO-PRt-U=tzY80zJfYvYgCze2EZUN17Lh3UHH+aJ44U+Yg@mail.gmail.com"
type="cite">But the problem isn't in uploading to OSB or OSM, it's
checking if there isn't already a speed limit present. The OSM
database shouldn't be filled with duplicate data if the data is
already okay. For OSB, this might be less of a problem, but it's
still not wanted.<br>
</blockquote>
As I have just explained, someone finding an already corrected
problem is just half surprised, the less if he is warned why, and he
feels like working terribly fast ;)<br>
I betcha some would rush <br>
<blockquote
cite="mid:CABUOUO-PRt-U=tzY80zJfYvYgCze2EZUN17Lh3UHH+aJ44U+Yg@mail.gmail.com"
type="cite">Does anyone see a way on how to achieve this?<br>
</blockquote>
Да. Jo the Polyglot, <a class="moz-txt-link-abbreviated" href="mailto:WinFixIT@gmail.com">WinFixIT@gmail.com</a> as he wrote this afternoon<br>
<br>
<div class="moz-cite-prefix">On 2012-11-21 16:53, Jo wrote :<br>
</div>
<blockquote
cite="mid:CAJ6DwMD8AFR7VbPigTfio80rMwAFmBNpKoRx8C2pBfHoHrje4Q@mail.gmail.com"
type="cite">I may have a way to upload them to OSB. The API is
indeed quite accessible. In order to take out the ones that are
already in the OSM data, I can download all the maxspeed=30 with
Overpass API and remove the ones which have end nodes near to
them.
<div>
<br>
</div>
<div>I'll see what I can do with some help from PostGIS.</div>
<div><br>
</div>
<div>Polyglot</div>
</blockquote>
<br>
I'm standing by, finger on the trigger. When you want.<br>
<br>
Cheers, <br>
<br>
<table>
<tbody>
<tr>
<td valign="top">André.</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>