Re: [OSM-talk] Crazy ways after editing - A real argument for changeset data
Andy Robinson \(blackadder\) wrote: > I can't comment on the flash-zoom functionality I can. :) As of last night the 'Zoom in' and 'Zoom out' options on the Flash right-click menu are disabled in Potlatch. Better to use an OS-level magnifier, as John McK suggested... and there'll be other zoom options in future Potlatchs. cheers Richard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Crazy ways after editing - A real argument for changeset data
David Muir Sharnoff wrote: >Sent: 06 February 2008 10:28 PM >To: Andy Robinson (blackadder) >Cc: OSM-Talk Openstreetmap >Subject: Re: [OSM-talk] Crazy ways after editing - A real argument for >changeset data > >I've now fixed the trouble. I used JOSM to do it. Here's what I did: > >1. Figure out how to install JOSM, install/enable YWMS, download data. >2. Figure out how to use JOSM a bit. The key things for me where the > select mode, the edit mode, zooming and panning with the keyboard. >3. Using potlatch, place a reference dot where the end of one of my > broken ways should be. >4. Select all the broken stuff. For me that was both whole ways and > selected points from partially-broken ways. >5. Tag them with "notes3: Oakland Potlach Fubar" >6. Using the scrolling keys, drag the whole lot of them half a screen > at time back to where they should be. > >Since it's a problem that's created by Potlatch but needs JOSM to >repair, it's going to be hard for anyone else who gets hit. > >That all said, I wish flash-zoom worked. I like Potlatch. In the >hills of Oakland, it's really hard to see where the streets are even >with flash-zoom. Often impossible without. Sometimes I have to >compare to Google imagery which is MUCH better. > >-Dave > Great that you found a workable and relatively quick solution. Once the volunteer programming bunch find sufficient time to sort the changeset data out then these sort of issues should hopefully be easier to deal with. I can't comment on the flash-zoom functionality but wanted to point out that comparison with Google's data or anyone else's imagery is not advisable. It risks tainting the OSM data with derived information so please watch out for that. Cheers Andy ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Crazy ways after editing - A real argument for changeset data
I've now fixed the trouble. I used JOSM to do it. Here's what I did: 1. Figure out how to install JOSM, install/enable YWMS, download data. 2. Figure out how to use JOSM a bit. The key things for me where the select mode, the edit mode, zooming and panning with the keyboard. 3. Using potlatch, place a reference dot where the end of one of my broken ways should be. 4. Select all the broken stuff. For me that was both whole ways and selected points from partially-broken ways. 5. Tag them with "notes3: Oakland Potlach Fubar" 6. Using the scrolling keys, drag the whole lot of them half a screen at time back to where they should be. Since it's a problem that's created by Potlatch but needs JOSM to repair, it's going to be hard for anyone else who gets hit. That all said, I wish flash-zoom worked. I like Potlatch. In the hills of Oakland, it's really hard to see where the streets are even with flash-zoom. Often impossible without. Sometimes I have to compare to Google imagery which is MUCH better. -Dave On Feb 6, 2008 4:46 AM, Andy Robinson (blackadder) <[EMAIL PROTECTED]> wrote: > David, > > I took a look at this area a little more closely with JOSM and I can see its > not straight forwards to correct because it's not just one way that got > moved but blocks of connected ways from what I can tell. Unfortunately they > now lie over the top of other exiting ways so its difficult to select the > ones effected so that they can be simply slid back. I think the only way to > sort it will be to evaluate the history data for the nodes in the whole > area. From this you can see which nodes (and hence ways) were moved at > around the same time instance. > > For instance if I look at two connected ways that are displaced (6331826 and > 6397132) and look at the node history for some of their nodes I can see > that their position was last moved at a timestamp around > "2008-02-04T04:32:24+00:00" they vary by some minutes in some cases so > perhaps it took a while for all the changes to update to the database. > Anyway, if a bit more checking was done it should be possible to automate a > rollback for all the affected data. Would need someone perhaps to help with > scripting that so perhaps David Hansen can assist with ideas. > > Another option might be to use last week's planet dump and do a compare and > revert between the state last week and the state now. This will though mean > you loose data from the time of planet last week to Feb 04 if a delete and > re-insert is done. > > Lets hope the folks that are looking at change set info via the API can find > us a long term solution to this problem as I'm sure its going to happen > again soon. > > Hope this helps move things along for you. > > Cheers > > Andy > > >-Original Message- > >From: [EMAIL PROTECTED] [mailto:talk- > >[EMAIL PROTECTED] On Behalf Of SteveC > >Sent: 06 February 2008 11:11 AM > >To: David Muir Sharnoff > >Cc: OSM-Talk Openstreetmap > >Subject: Re: [OSM-talk] Crazy ways after editing > > > >David, > > > >There is also a talk-us list which may be of help in future. > > > >On 5 Feb 2008, at 18:46, David Muir Sharnoff wrote: > > > >> The area of Oakland, California I've been editing > >> (with Potlatch) suddenly changed in a very bad way. > >> > >> There are a whole bunch of ways (at least 50, > >> perhaps a lot more) that have had one or more > >> of their points move several miles south-east. > >> > >> A major street, Park Ave, seems to have > >> disappeared entirely. Or, at least, I can't find > >> it any more. > >> > >> Edit at this location to see: > >> http://www.openstreetmap.org/?lat=37.81886&lon=- > >122.21229&zoom=16&layers=B0FT > >> > >> Some example ways that are messed up: > >> 6403309, Saint James Dr. > >> 6380125, Somerset Rd > >> 6365079, Pershing Dr > >> 6391271, Indian Rd > >> 6381464, Hampton Rd > >> 6374990, Excelsior Ave > >> 6359191, E 33rd St > >> 6390297, Everett Ave > >> > >> Does anyone have any idea what happened > >> or how to fix it? > >> > >> Thanks, > >> -Dave > >> > >> ___ > >> talk mailing list > >> talk@openstreetmap.org > >> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk > >> > > > >have fun, > > > >SteveC | [EMAIL PROTECTED] | http://www.asklater.com/steve/ > > > > > > > >___ > >talk mailing list > >talk@openstreetmap.org > >http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk > > ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Crazy ways after editing - A real argument for changeset data
David, I took a look at this area a little more closely with JOSM and I can see its not straight forwards to correct because it's not just one way that got moved but blocks of connected ways from what I can tell. Unfortunately they now lie over the top of other exiting ways so its difficult to select the ones effected so that they can be simply slid back. I think the only way to sort it will be to evaluate the history data for the nodes in the whole area. From this you can see which nodes (and hence ways) were moved at around the same time instance. For instance if I look at two connected ways that are displaced (6331826 and 6397132) and look at the node history for some of their nodes I can see that their position was last moved at a timestamp around "2008-02-04T04:32:24+00:00" they vary by some minutes in some cases so perhaps it took a while for all the changes to update to the database. Anyway, if a bit more checking was done it should be possible to automate a rollback for all the affected data. Would need someone perhaps to help with scripting that so perhaps David Hansen can assist with ideas. Another option might be to use last week's planet dump and do a compare and revert between the state last week and the state now. This will though mean you loose data from the time of planet last week to Feb 04 if a delete and re-insert is done. Lets hope the folks that are looking at change set info via the API can find us a long term solution to this problem as I'm sure its going to happen again soon. Hope this helps move things along for you. Cheers Andy >-Original Message- >From: [EMAIL PROTECTED] [mailto:talk- >[EMAIL PROTECTED] On Behalf Of SteveC >Sent: 06 February 2008 11:11 AM >To: David Muir Sharnoff >Cc: OSM-Talk Openstreetmap >Subject: Re: [OSM-talk] Crazy ways after editing > >David, > >There is also a talk-us list which may be of help in future. > >On 5 Feb 2008, at 18:46, David Muir Sharnoff wrote: > >> The area of Oakland, California I've been editing >> (with Potlatch) suddenly changed in a very bad way. >> >> There are a whole bunch of ways (at least 50, >> perhaps a lot more) that have had one or more >> of their points move several miles south-east. >> >> A major street, Park Ave, seems to have >> disappeared entirely. Or, at least, I can't find >> it any more. >> >> Edit at this location to see: >> http://www.openstreetmap.org/?lat=37.81886&lon=- >122.21229&zoom=16&layers=B0FT >> >> Some example ways that are messed up: >> 6403309, Saint James Dr. >> 6380125, Somerset Rd >> 6365079, Pershing Dr >> 6391271, Indian Rd >> 6381464, Hampton Rd >> 6374990, Excelsior Ave >> 6359191, E 33rd St >> 6390297, Everett Ave >> >> Does anyone have any idea what happened >> or how to fix it? >> >> Thanks, >> -Dave >> >> ___ >> talk mailing list >> talk@openstreetmap.org >> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk >> > >have fun, > >SteveC | [EMAIL PROTECTED] | http://www.asklater.com/steve/ > > > >___ >talk mailing list >talk@openstreetmap.org >http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
