Peter Miller <peter.mil...@...> writes:
>Thinking about it, one could get OSM to produce a list of things to check for
>any particular trip - First one would produce a GPX for the trip and then a
>'job-creator' would identify streets without names, villages without letter
>boxes, ways with 'FIXME' tags and also of course unchecked bus stops and
>produce an itinerary and map to things to do on the way.
Yes, it would be good for this to integrate somehow with Openstreetbugs
and Walking Papers.
Adding a new Openstreetbugs entry for every naptan:verified=no bus stop would
be excessive, so there needs to be some way for independent sites to produce a
list of errors to check.
Perhaps some simple 'OSM-bugs format' could be defined:
<bugs>
<bug lat="51.53603" lon="-0.0087" type="keepright:mixed-layer">
<msg>This node is a junction of ways on different layers.</msg>
<node id="262545510" />
<way id="24249588" />
<way id="35148998" />
</bug>
<bug lat="51.61759" lon="-0.00207" type="osb">
<msg>Need to map the paths through the wood.</msg>
<reporter>Ed Avis</reporter>
</bug>
<bug lat="51.56052" lon="-0.00966" type="naptan:unverified">
<msg>This bus stop needs verifying.</msg>
<node id="469766073" />
</bug>
</bugs>
Then anyone who wants to provide data checks for OSM need only set up a web
page that takes a bbox in the URL and returns an OSM-bugs XML file. Existing
checkers such as keepright and Openstreetbugs could, I hope, be easily modified
to generate this format.
A mapper would configure the app with a list of bug sources to read.
--
Ed Avis <[email protected]>
_______________________________________________
Talk-GB mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/talk-gb
