If mappers tick the checkbox, should they be able to ask specific questions what they want to be reviewed?

In my opinion, they should put this as part of their changeset comment - I don’t see the need to add additional tags or layers when comment is supported as a free text field for exactly questions like this :) - hope that works.

Hi Athalis - I’m one of the developers working on OSMCha, thank you for your comment -

I think I could replace that workflow with OSMCha if the bbox matching would be better.

Yes. So the problem currently is we just the BBOX from OSM which indicates the overall bounding box that the changeset covers. The bounding box query on OSMCha currently queries for all changesets with bounding boxes that intersect in any way with your query bbox.

I see a few options here:

• add an option to only find changesets fully contained within the bbox you are searching for.
• display the overall area covered by a changeset in the list view to be able to quickly eye-ball changesets that are very large.
• … would be appreciative of any other ideas ..

I think adding the option to only find changesets fully contained within the bbox you are searching for would be easy to add, but then you could also miss some changesets relevant to the area you are searching. Am not sure of a good solution here, but would be very appreciative of hearing what you think.

It would be great if users could save their custom filters and see in an overview how many “new” changesets there are per filter (both suspicious & all, being not verified).

Being able to subscribe to a custom RSS feed based on your filters is very high up on my list of priorities. Hope to have this working soon - really good to know that there is desire for such a feature.

Thanks again for your feedback and inputs!

This is also related to: https://github.com/mapbox/osm-comments-api/issues/44 - unfortunately, a limitation right now is that we will only show changesets that have been created by the user/s that are being searched for.

This is primarily because the immediate use case for us was finding changesets that we had created that had conversations / comments.

I can see that one expects to find all changesets where one has participated in conversation when searching for users: though, and the documentation could use some clarification, and ideally, this feature implemented soon.

Hi,

Thanks for the bug report. Indeed, “from” searches for the date of the changeset and not the comment. Tracking that here: https://github.com/mapbox/osm-comments-api/issues/45

For now, will clarify the documentation to reflect the same.

Thanks again for the report - it is entirely possible that there are other problems with the current SQL code, which is in dire need of a refactor. Will look into the issue - happy to know there are more people than us trying to use this :)

Would be very happy if you filed issues on our public issue tracker: https://github.com/mapbox/osm-comments/issues . Of course, feel free to email me at sanjay at thecompanyiworkfor.com (mapbox)

Thanks, Sanjay