Hi Andrew, Thanks for the patch! I've applied it to the current trunk. I haven't tested it, or even looked at the code much but I'll assume it works :-) It complements the existing --node-key, --node-key-value and --way-key-value well.
The only change I made was to add a --way-key-0.6 name to TaskRegistrar because all tasks have a version based entry as well. Can you please update the wiki detailed usage page to reflect the new task? http://wiki.openstreetmap.org/wiki/Osmosis/DetailedUsage On this note, if anybody is keen Osmosis could really do with somebody to take on creating a consistent set of filtering tasks for all entity types (at a minimum it appears that relations are missing from the existing set of tasks). I'm not sure what the requirements would be and I don't do any filtering myself so don't have much experience with it. I think all existing tasks have a bug at the moment where they don't handle ',' characters in the key names which probably should also be fixed. Brett On Thu, Nov 19, 2009 at 8:47 AM, Andrew Byrd <[email protected]> wrote: > Hello Osmosis, > > I saw that there is some desire to filter ways based on the presence > of a key. This is useful for extracting all highways, whatever the > type, for instance. I basically just made a hybrid of the > WayKeyValueFilter and NodeKeyFilter, and it seems to do exactly that. > The patch is at the following address: > > http://global_void.mailc.net/ > > Usage example: > osmosis --read-xml file="input.osm" --way-key keyList="boundary" -- > used-node --write-xml file="output.osm" > > Happy data filtering, > Andrew > > _______________________________________________ > osmosis-dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/osmosis-dev >
_______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
