OK, I'll give that a try. Except I am now in a mess with the JOSM plugins. I made the mistake of clicking on "Update" because the waydownloader plugin wasn't installing.
validator requires JOSM 1725 waydownloader requires JOSM 1722 wmsplugin requires JOSM 1722 They won't run on the latest version 1743. They won't run on version 1720. Unfortuanately JOSM 1722 - 1727 have a critical bug and are blocked from editing data. So I am stuck again, but now with JOSM and it's plugins. Andy Tyler wrote: > Hey Andy, > > I just checked out the area on your user history page and it looks like > it's mostly you and elyk editing there (mostly you, it's possible a > county/state boundary was turned into a relation). This following would > be my solution as XAPI doesn't seem to be using recent data. > > In JOSM make sure you have the waydownloader plugin. Download a small > area containing only one of your boundaries of interest. If it is part > of a relation go to the relation manager and select download all > members. otherwise just go to the end of that way and do a "download > way" in the tools menu. Continue doing this with until you have all of > your ways/nodes of interest. change and upload. > > You don't want to upload over previous data as you'll be duplicating > nodes and ways which is a real mess. You can also download your > changeset xml (from your edit history) and modify those files to do what > you want (say delete or modify nodes). > > Once XAPI is consistently up and running it would be the appropriate way > to do this sort of thing. > > > On Wed, Jul 8, 2009 at 12:34 PM, Andrew Ayre <a...@britishideas.com > <mailto:a...@britishideas.com>> wrote: > > Update: > > When I go to the live slippy map and look at the piece that was deleted > I see someone added a boundary relation. So the piece is still there, > but JOSM wants to remove it. Totally confused...... > > Andy > > Andrew Ayre wrote: > > Perhaps I am going about this the wrong way, but I am about ready to > > give up. > > > > <rant> > > I started uploading the forest boundaries for Arizona using JOSM. > > Working well so far. However I saw that I made a mistake with one > of the > > tags. So now I started re-uploading all my data using my original OSM > > files to correct the tag mistake. > > > > I used my original OSM files because I cannot see a way of > downloading > > just my data, even though I have a unique UUID tag for it all. > The data > > covers 1000's of square miles and JOSM will only let you tediously > > download it in small pieces, along with vast amounts of other > data that > > is not interesting to me. > > > > When I go to upload I am getting conflicts saying someone else has > > modified a primitive. I have a choice to keep mine or use theirs. > There > > is no indication in JOSM of which node this is and seemingly no > way of > > working out what the change is. So I blindly choose to use theirs > - err > > on the side of caution. > > > > I go through this cycle about 20 times and start to see a pattern - > > someone has deleted an entire section of the national forest, even > > though I got this data from the US Forest Service. What?? Am I > wasting > > my time with this? > > > > OK, so now I want to see all the changes that have been made and > I try > > to update the current data set. Oops. JOSM won't let you do that > because > > I haven't downloaded anything. Strange, because it will let me update > > single nodes and selections. However the selections have to be 50 > nodes > > or less, which is totally useless. My dataset has maybe 1,000 nodes. > > > > OK, perhaps I can just delete that changed section from my file and > > upload the rest, fixing the tags for that - nope - JOSM wants to > delete > > from the server the data I delete. That's not what I want because I'm > > not sure what effect that would have. > > > > So now I'm thinking that maybe I will just leave that incorrect > tag in > > there for someone else to worry about, as this is now too much of > a hassle. > > </rant> > > > > If I am going about this the wrong way please let me know. > > > > Andy > > > > -- > Andy > PGP Key ID: 0xDC1B5864 > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org <mailto:Talk-us@openstreetmap.org> > http://lists.openstreetmap.org/listinfo/talk-us > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-us -- Andy PGP Key ID: 0xDC1B5864 _______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
