On Thu, Aug 25, 2011 at 7:31 PM, Bryce Nesbitt <bry...@obviously.com> wrote:
> On 08/25/2011 03:27 PM, Frederik Ramm wrote: > >> Another problem which you don't seem to solve is the relationship of >> imported and already existing data; it seems that in your particular case >> you evaluated the situation by hand before importing. This is often one of >> the more complicated things to do with imports, and it is important to >> stress that even if you have your code right you still have to do this >> analysis. We must not give people the impression that importing was easy if >> only you have the right tool. >> > If the target data has a consistent key, the tool can prepare a preliminary > diff. > For example I used initial search: > node[radar_transponder=NEXRAD] > node[operator=City CarShare] > > Which brought in all the existing nodes to merge and compare. I was easily > able to see what existing data needed preservation. > > At the initial import time the conflation key can be changed: > node[source=osmfetch:noaa:**nexrad] > node[source=osmfetch:ccs] > > Unfortunately xapi is pretty weak at search, as you can only specify one > key. But one can override the osmfetch class to have a programmatic filter. > Some day maybe xapi will support rich search: > > *[radar_transponder=NEXRAD][**operator=NOAA][country=us] | > [man_made=beacon][type=NEXRAD] > > And one can target a melange of hand mapped keys more readily. JXAPI allows one or more predicates of any sort (tag or bounding box/polygon). If I remember my code correctly they are all AND'd together (if you want OR use the | to do multiple values/keys per tag).
_______________________________________________ Imports mailing list Imports@openstreetmap.org http://lists.openstreetmap.org/listinfo/imports
