[OSM-dev] Data source for robot

Ian Dees ian.dees at gmail.com
Tue Oct 12 16:22:36 BST 2010


On Tue, Oct 12, 2010 at 9:56 AM, Peter Budny <peterb at gatech.edu> wrote:

> Ian Dees <ian.dees at gmail.com> writes:
>
> > Regardless, how do you plan on handling the situation where a human
> > has to fill in the blanks?
>
> I thought there were already tools for this.  There's the wiki, where
> people leave comments like "Complete from Cobb to Bartow county".
> There's OpenStreetBugs, where we can mark things like overlapping nodes
> that don't connect.  Putting data into these where the robot can't make
> a good decision isn't difficult.
>

These are good tools but I guess I'd like to see how you plan on displaying
the information. Can you get it to the point where there's a big long TODO
list that gets checked every so often so we can see progress towards the
goal? Something like http://funmap.co.uk/cityrouting/dupenodes2.html?


>
> If people aren't already using those tools (or others) to know what to
> work on in OSM, then how are they doing it?  Blind luck... just pick a
> spot on the map and check everything to see if it's right?


Most of the prolific mappers have a specific physical area or recreation
they are particularly interested in and perceive that as their project. If
they notice something is wrong in their area of interest they fix it. For
example, I care about my current city and my hometown. I also care about the
Great Lakes borders. Stuff that happens outside of these areas of interest
(e.g. fixing Oregon's state highway route relations) isn't very important to
me. Not everyone has overlapping sets of interests, so when you create a new
set of bugs or problem area it's difficult to drum up support to fix it.

I don't use any of the tools you mentioned to find bugs in my area, I
already find enough to do with aerial imagery and GPS traces. However, if
there was a TIGER-fixup-style checklist that auto updated to show progress
(especially if it showed problems in my areas of interest) I might work on
fixing those.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20101012/fb19fa14/attachment.html>


More information about the dev mailing list