[josm-dev] OSC format for offering proposed changes
Hey JOSM-dev, I am curious what JOSMs capabilities are with regard to reading OSC files. I tried a few OSC files and they seem to read in correctly, but I am not sure how useful they are for a use case where you would want to offer a small file with proposed changes to OSM. Say I have a set of changes that consist of a mix of new tags to existing objects, changed ways / nodes, added ways / nodes, removed ways / nodes. I want to give this file to someone to load in JOSM and review + upload if they think the data is good. Would JOSM XML be a better choice for this? Thanks for your help, -- Martijn van Exel skype: mvexel ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] OSC format for offering proposed changes
The first two downsides you mention, invisible deletes and ignored changeset tags, are not specific to the TODO plugin, or are they? I mean, making deletes visible (through a toggle switch perhaps) and supporting changeset tags in the JOSM XML format is something that could be added to JOSM core? I think this may be useful. Martijn On Wed, Feb 25, 2015 at 6:32 PM, Bryce Nesbitt bry...@obviously.com wrote: I use JOSM XML for this all the time. I'm able build a file representing add/update/delete operations. It works well with the TODO plugin. It's all pretty smooth. Downsides: * The delete operation is a bit invisible: deleted notes only show up at upload time. * Changeset tags in the file are ignored, so I can't pre-set the tags used for any eventual upload. * If the file has ways, the TODO plugin is hard to use. It ends up stepping you through each node of the way, which gets tedious. The workaround is to search for any tag, then step through only things that have tags. On Wed, Feb 25, 2015 at 1:48 PM, Martijn van Exel m...@rtijn.org wrote: Hey JOSM-dev, I am curious what JOSMs capabilities are with regard to reading OSC files. I tried a few OSC files and they seem to read in correctly, but I am not sure how useful they are for a use case where you would want to offer a small file with proposed changes to OSM. Say I have a set of changes that consist of a mix of new tags to existing objects, changed ways / nodes, added ways / nodes, removed ways / nodes. I want to give this file to someone to load in JOSM and review + upload if they think the data is good. Would JOSM XML be a better choice for this? Thanks for your help, -- Martijn van Exel skype: mvexel ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev -- Martijn van Exel skype: mvexel ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] OSC format for offering proposed changes
I use JOSM XML for this all the time. I'm able build a file representing add/update/delete operations. It works well with the TODO plugin. It's all pretty smooth. Downsides: * The delete operation is a bit invisible: deleted notes only show up at upload time. * Changeset tags in the file are ignored, so I can't pre-set the tags used for any eventual upload. * If the file has ways, the TODO plugin is hard to use. It ends up stepping you through each node of the way, which gets tedious. The workaround is to search for any tag, then step through only things that have tags. On Wed, Feb 25, 2015 at 1:48 PM, Martijn van Exel m...@rtijn.org wrote: Hey JOSM-dev, I am curious what JOSMs capabilities are with regard to reading OSC files. I tried a few OSC files and they seem to read in correctly, but I am not sure how useful they are for a use case where you would want to offer a small file with proposed changes to OSM. Say I have a set of changes that consist of a mix of new tags to existing objects, changed ways / nodes, added ways / nodes, removed ways / nodes. I want to give this file to someone to load in JOSM and review + upload if they think the data is good. Would JOSM XML be a better choice for this? Thanks for your help, -- Martijn van Exel skype: mvexel ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] OSC format for offering proposed changes
n Wed, Feb 25, 2015 at 5:50 PM, Martijn van Exel m...@rtijn.org wrote: The first two downsides you mention, invisible deletes and ignored changeset tags, are not specific to the TODO plugin, or are they? I mean, making deletes visible (through a toggle switch perhaps) and supporting changeset tags in the JOSM XML format is something that could be added to JOSM core? I think this may be useful. Because a deleted node is deleted, it can't be selected, so can't be added to the TODO plugin list. -- The changeset tag is already supported in the OSM XML format... it's just not processed by the JOSM core. -- Don't discount the third downside. If you have a mixture of nodes ways and areas, the third issue really bites. You select all and the TODO plugin walks you through every darn node. It gets a little better if you review only objects with a tag, but that's hard to explain. The dream TODO plugin for me would walk through in proximity order: a) New objects b) Modified objects c) Deleted objects d) Unmodified objects With the plugin jumping to the next nearest object at each step ( a proximity search ). ___ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
