Re: [OSM-talk] Quality of OSM Notes

On Tue, Mar 10, 2015 at 10:42 AM, Alex Barth wrote: > > On Mon, Mar 9, 2015 at 10:38 PM, Bryce Nesbitt > wrote: > >> While we can build better tools to process large numbers of notes, the >> one thing we can't >> do under the current system is ask the person who wrote the note for more >> inform

Re: [OSM-talk] Quality of OSM Notes

On Mon, Mar 9, 2015 at 10:38 PM, Bryce Nesbitt wrote: > While we can build better tools to process large numbers of notes, the one > thing we can't > do under the current system is ask the person who wrote the note for more > information. There's (usually) > just one chance to collect that infor

Re: [OSM-talk] Quality of OSM Notes

Bryce - that is a good point. When a note gets resolved, we have the ideal opportunity to engage the casual contributor who is kind enough to leave a note that is good enough for someone to act on. Unfortunately we cannot (easily?) do that the way notes are set up right now. At Telenav we go around

Re: [OSM-talk] Quality of OSM Notes

Hi all. I think, we could ask people to provide us with some contact info after note being added. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Quality of OSM Notes

On Mon, Mar 9, 2015 at 5:47 PM, Alex Barth wrote: > Less notes should not be an objective, smarter ways to look at them and >> process them should. >> I agree, simplicity rules. >> > Some ideas to manage the overkill. > While we can build better tools to process large numbers of notes, the one t

Re: [OSM-talk] Quality of OSM Notes

Bryce - this is an interesting review, thanks for sharing. On Fri, Feb 20, 2015 at 12:42 PM, Martijn van Exel wrote: > As for Scout, I talked about this in my diary entry > some time ago - > not all of these are going to be useful and there

Re: [OSM-talk] Quality of OSM Notes

On 22/02/2015, Paul Johnson wrote: > On Sat, Feb 21, 2015 at 9:39 PM, Russ Nelson wrote: >> I agree with Greg. If the not submitter didn't put a lot of effort >> into it, then you as a mapper shouldn't put a lot of effort into it >> either. Unless you feel like solving a puzzle! > > I'd still at

Re: [OSM-talk] Quality of OSM Notes

Bryce Nesbitt writes: > It would be easy enough to run an experiment where the notes > interface steps the user through writing a good report, and see > what the impact on volume of notes is. Sounds like a job for A/B testing. -- --my blog is athttp://blog.russnelson.com Crynwr supports o

Re: [OSM-talk] Quality of OSM Notes

On Sat, Feb 21, 2015 at 7:39 PM, Russ Nelson wrote: > Greg Troxel writes: > > That said, there is a lot of junk. But I just close them if I can't > > figure them out and if I'm fairly sure I wouldn't be able to if I showed > > up. > > I agree with Greg. If the not submitter didn't put a lot o

Re: [OSM-talk] Quality of OSM Notes

On Sat, Feb 21, 2015 at 10:19 PM, Eduardo wrote: > Maybe I could do research into an app which would allow for no-frills >> GPS trace collection and upload to some service (actually this can be >> done in HTML5 - you can ask specifically for GPS in geolocation API). >> This way when someone compl

Re: [OSM-talk] Quality of OSM Notes

On Sat, Feb 21, 2015 at 9:39 PM, Russ Nelson wrote: > Greg Troxel writes: > > That said, there is a lot of junk. But I just close them if I can't > > figure them out and if I'm fairly sure I wouldn't be able to if I showed > > up. > > I agree with Greg. If the not submitter didn't put a lot o

Re: [OSM-talk] Quality of OSM Notes

El 20/02/2015 10:42 pm, Michał Brzozowski escribió: On Fri, Feb 20, 2015 at 10:11 PM, Bryce Nesbitt wrote: Perhaps the most frustrating type of note is one where the writer clearly meant to help, but there's just not enough information available to act on it. I can also relate to this. Any h

Re: [OSM-talk] Quality of OSM Notes

Greg Troxel writes: > That said, there is a lot of junk. But I just close them if I can't > figure them out and if I'm fairly sure I wouldn't be able to if I showed > up. I agree with Greg. If the not submitter didn't put a lot of effort into it, then you as a mapper shouldn't put a lot of eff

Re: [OSM-talk] Quality of OSM Notes

On Feb 21, 2015 3:03 PM, "Bryce Nesbitt" wrote: > > On Sat, Feb 21, 2015 at 12:27 PM, Paul Johnson wrote: Do we have a graph of how many notes are open? It wouldn't be surprising to see a downward trend in the last few weeks from this change. > > > http://resultmaps.neis-one.org/osm-no

Re: [OSM-talk] Quality of OSM Notes

On Sat, Feb 21, 2015 at 12:27 PM, Paul Johnson wrote: > Do we have a graph of how many notes are open? It wouldn't be surprising >> to see a downward trend in the last few weeks from this change. >> >> http://resultmaps.neis-one.org/osm-notes ___ talk

Re: [OSM-talk] Quality of OSM Notes

On Fri, Feb 20, 2015 at 12:33 AM, Bryce Nesbitt wrote: > Many open notes were not actionable: > > 1) Pure junk (empty, scribbles) > > This is probably a UI situation. I know the old Skobbler app was *notorious* for this, and probably a huge reason behind the massive flop that was Mapdust

Re: [OSM-talk] Quality of OSM Notes

On Fri, Feb 20, 2015 at 8:42 PM, Michał Brzozowski wrote: > On Fri, Feb 20, 2015 at 10:11 PM, Bryce Nesbitt > wrote: > > Perhaps the most frustrating type of note is one where the writer clearly > > meant to help, but there's just not > > enough information available to act on it. > > I can also

Re: [OSM-talk] Quality of OSM Notes

On Fri, Feb 20, 2015 at 10:11 PM, Bryce Nesbitt wrote: > Perhaps the most frustrating type of note is one where the writer clearly > meant to help, but there's just not > enough information available to act on it. I can also relate to this. Any help on getting this is appreciated: https://github.

Re: [OSM-talk] Quality of OSM Notes

On Feb 20, 2015 1:42 PM, "Martijn van Exel" wrote: > > As for Scout, I talked about this in my diary entry some time ago - not all of these are going to be useful and there is going to be noise. We're looking at improving the quality of the notes that make it through - which is already a tiny, tin

Re: [OSM-talk] Quality of OSM Notes

On Feb 20, 2015 6:00 PM, "Greg Troxel" wrote: > > > Bryce Nesbitt writes: > > > 6) Lazy Requests to do cleanup that the note writer did not want to do > > themselves. > > That's unnecessarily perjorative. I've seen a number of notes around me > that could be characterized that way, and I've ente

Re: [OSM-talk] Quality of OSM Notes

Bryce Nesbitt writes: > 6) Lazy Requests to do cleanup that the note writer did not want to do > themselves. That's unnecessarily perjorative. I've seen a number of notes around me that could be characterized that way, and I've entered a number myself. I view it as a public shared todo list.

Re: [OSM-talk] Quality of OSM Notes

*A challenge*: clear 50 notes, and come back to this discussion with your ideas ;-). ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Quality of OSM Notes

On Fri, Feb 20, 2015 at 12:42 PM, Martijn van Exel wrote: > > In general I think it should be easier, not harder, to create notes and > Ian's onosm is a good example of how to accomplish that. Adding artificial > friction makes no sense to me. Less notes should not be an objective, > smarter ways

Re: [OSM-talk] Quality of OSM Notes

As for Scout, I talked about this in my diary entry some time ago - not all of these are going to be useful and there is going to be noise. We're looking at improving the quality of the notes that make it through - which is already a tiny, tiny

Re: [OSM-talk] Quality of OSM Notes

On Fri, Feb 20, 2015 at 12:39 PM, Bryce Nesbitt wrote: > > In general feel that more "friction" should be added to the notes process, > so it's harder to make a note, so there are less notes. > That process should continue until the production and processing of notes > gets into balance. > Addin

Re: [OSM-talk] Quality of OSM Notes

Hi Bryce, I don't think people read the text above OSM's notes submission form anyway. I fall in to the camp of "less is better". Mapbox blogged about how they do it recently. I really like the big "describe what's wrong" header as it achieves so much in so few words (and I'm sure if it made sense

Re: [OSM-talk] Quality of OSM Notes

On Fri, Feb 20, 2015 at 12:29 AM, Toby Murray wrote: > I believe it was Ian Dees who came up with http://onosm.org/ to address > this. It collects detailed information and then creates an actionable note > with that information. > What would it take to get "onosm" or something like that linked to

Re: [OSM-talk] Quality of OSM Notes

On Feb 20, 2015 1:37 AM, "Bryce Nesbitt" wrote: > > A fair number of the notes in my areas were people (usually correctly) identifying the business at a given location. > Perhaps an "easy" form could prompt them to enter complete data. This would unburden the note system. I believe it was Ian De

Re: [OSM-talk] Quality of OSM Notes

On Thu, Feb 19, 2015 at 11:20 PM, Mateusz Konieczny wrote: > "OSM is easy to edit" - I think that it is better to avoid false > information. OSM is not easy to edit for beginners (iD is a bit better for > start, but it is also quite hard) > A fair number of the notes in my areas were people (usu

Re: [OSM-talk] Quality of OSM Notes

I been meaning to write up an email about this subject last week but never got to it. The problem with osm notes i have is scout. The last week I've been trying to close a lot of scout notes and have found that at least 75 of them are app errors. Of which i can doing nothing but close. Just a huge

Re: [OSM-talk] Quality of OSM Notes

"OSM is easy to edit" - I think that it is better to avoid false information. OSM is not easy to edit for beginners (iD is a bit better for start, but it is also quite hard) 2015-02-20 7:33 GMT+01:00 Bryce Nesbitt : > In preparation for a project, I made a concerted effort to clear "notes" > in a

[OSM-talk] Quality of OSM Notes

In preparation for a project, I made a concerted effort to clear "notes" in areas I know well. There were a few gems in there, but mostly it was pretty rough going. Many open notes were not actionable: 1) Pure junk (empty, scribbles) 2) Unsolvable wishes 3) Incomplete information (with no way to