Marc, you can still run it by clicking "show query editor" and clicking the blue play button. If you see a yellow bar and no data, it means that that specific query has no results - try a different query. The "query editor" mode allows you to make changes to OSM data (you are in a developer mode), but the direct "show results" does not - until I make some changes to the service that were suggested earlier.
There are several differences with Osmose, but it does share some concepts with it (and some bits of code) * Any user can write a query and share it via OSM wiki, without the need to update the backend. * If query needs to be adjusted, anyone can fix the query and update it on the wiki. * Queries can offer specific changes (e.g. change tag X to a new calculated value), let user decide if they are appropriate, and save them to OSM. This is similar to JOSM's auto fix validations. * The service will allow much easier rollback path - multiple change types are not compounded together - the whole changeset is for just one type of change, and can be easily tracked. * Depending on the query, some changes can be saved right away, and some can be voted on. Those votes are stored in the same database as everything else, and the queries can access it just like any other data. * Once a specific query has been used globally for a while, and there are no issues, some bot service can automatically continue running it without additional work. This ensures that the fully-automatic bot actually uses exactly the same code as was used during the test period. * The database contains OSM tags, a copy of Wikidata DB, Wikipedia page popularity, and could be syndicated with any other RDF data source (once specific syndication is added in server configuration, any query can join results from external data sources) So in a way, this is a 3-in-one tool: * A power-user search and replace tool, where each change has to be confirmed. * A "bot testing platform" - for the community to write bots, share them on a wiki, let the whole community trial run it with human oversight, and once established that there are no issues, let automation take over. The automation step is not done by the platform, but could be fairly easily implemented by the bot operators. * A change voting system, where users can vote if certain proposed changes should be made (either yes/no, or pick from multiple choices) On Fri, Oct 27, 2017 at 7:08 AM, marc marc <marc_marc_...@hotmail.com> wrote: > Le 14. 10. 17 à 11:56, Andy Townsend a écrit : > > On 13/10/2017 22:25, Yuri Astrakhan wrote: > >> I would like to introduce a new quick-fix editing service. > >> I have started a Quick fixes wiki page, where we can share and discuss > >> quick fix ideas. > >> * Quick fixes <https://wiki.openstreetmap.org/wiki/Quick_fixes> > > What are the differences and advantages over Osmose? > I try to test I only get an error > > Regards, > Marc > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
