Well as a start is I put a section into the QA tools page http://wiki.openstreetmap.org/wiki/Quality_assurance#Remap-a-Tron Several projects there that ideas/code/SQL might be borrowed from.
Well your obviously familiar with this :) did the issues found by this query all get resolved? http://oegeo.wordpress.com/2012/04/07/detecting-highway-trouble-in-openstreetmap/ Also some SQL from a bot http://wiki.openstreetmap.org/wiki/OSM_Fixer that might be of use in building other queries. Dale On Mon, Oct 1, 2012 at 4:04 PM, Martijn van Exel <m...@rtijn.org> wrote: > The setup involves designing the SQL queries and the initial database, > and tweaking the front end for different types of problems. Up until > now, we have been able to get away with just displaying the > non-remapped way as a vector element on the leaflet map, but for > example forfolding ways that may not be enough, as the folds may be > really tiny and not visible without also displaying the offending > piece of the way in a kind of magnifying glass (or in the popup > balloon). That would mean significant front-end tweaking as well as > partial re-engineering of the webservices that transmit the geojson. > (these are really really simple things[1] so that should not be hard > to do for someone with a little python / json experience). For the > connectivity errors, which are as high on my list as anything to fix, > we'd need to transmit both ways involved and find a way to display the > issue effectively. Maybe just the two ways in different colors. Nice > extra would be if the popup would say 'hey, there are x more > connectivity errors within a mile, do you just want to go ahead and > edit all of them?' > > A wiki page is an excellent idea, who has time to set that up? > > [1] https://github.com/mvexel/remapatron/blob/master/service/get.py > > On Mon, Oct 1, 2012 at 1:59 AM, Dale Puch <dale.p...@gmail.com> wrote: > > For setting up the runs, is it all SQL queries or are there other items > > involved? Perhaps start a wiki page for useful queries to identify > problems > > (for this or other projects), or even just collaboration on plain text > > criteria ideas for future runs and build what is needed from there. > > > > Dale > > > > > > On Mon, Oct 1, 2012 at 1:52 AM, Martijn van Exel <m...@rtijn.org> wrote: > >> > >> Also a good one. I will make a list of all the suggestions some time > >> this week. There's some low hanging fruit here, and some more complex > >> ideas. I don't know when I will have time to implement the next level, > >> I hope to have something up before Portland. Any help is appreciated! > >> > >> Martijn > >> > >> On Sun, Sep 30, 2012 at 11:46 PM, Alexander Jones <happy5...@gmail.com> > >> wrote: > >> > Alan Millar wrote: > >> > > >> >> Another suggestion: motorways and trunks without lanes=number tags > >> >> > >> >> - Alan > >> > > >> > I'd help out with that. > >> > > >> > Alexander > >> > > >> > > >> > _______________________________________________ > >> > Talk-us mailing list > >> > Talk-us@openstreetmap.org > >> > http://lists.openstreetmap.org/listinfo/talk-us > >> > >> > >> > >> -- > >> martijn van exel > >> http://oegeo.wordpress.com > >> > >> _______________________________________________ > >> Talk-us mailing list > >> Talk-us@openstreetmap.org > >> http://lists.openstreetmap.org/listinfo/talk-us > > > > > > > > > > -- > > Dale Puch > > > > -- > martijn van exel > http://oegeo.wordpress.com > -- Dale Puch
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us