as you pointed out, it will only work for point data. But that's what those addresses in Crab are. And indeed it was meant as a suggestion for Kurt. So he can choose from a number of possible workflows.
m On Wed, Oct 23, 2013 at 1:43 PM, Glenn Plas <gl...@byte-consult.be> wrote: > On 2013-10-23 12:43, Marc Gemis wrote: > > > > > On Wed, Oct 23, 2013 at 12:16 PM, Glenn Plas <gl...@byte-consult.be>wrote: > >> On 2013-10-23 10:28, Marc Gemis wrote: >> >> You could also make a csv file with the diffs and open that with the >> OpenData plugin in JOSM. (see my presentation at ESI on import VMM >> monitoring stations ) >> But of course that requires people to install this plugin. >> >> >> The great thing about having to go dig deep in the data itself is that >> it will be fairly easy to structure this the way JOSM does it. Since you >> already have to deal with different formats, why spend time on an extra one >> ? All you need to do is save 'the result' set locally and start looking >> at the format. It would be a huge feature. I'm not against csv's but their >> use is limited, xml's (not my favorite!) however gives a structure to the >> data and makes the data also more human readable. Next to being an >> established standard. >> >> >> > You know that after importing the csv file, you have an osm layer that > you can save and work with. So if you happen to have a tool that exports > the new/update records in csv format (any decent DB-tool can generate files > in that format), you do not have to write a tool that generates OSM-xml. > So when you can determine the new/updated records in the Crab DB (I do not > know in which format the updates from Crab are provided) with a simple SQL > query, you export the result in csv, import with the OpenData plugin and > you don't need to write any other program. That's all that I wanted to say. > > > Yeah, I understand the reasoning but I'm thinking at some point you want > to inject something halfway , so in this case, you need to update the csv's > (record, line based). Then it gets complicated -perhaps-. I was just > thinking idealistically out loud. I'm thinking, how would a complex > building be represented in a csv format, I think I would get frustrated > using it as my local app working storage (that's what I consider it to be > in this case) Your shortcut to results seems worth considering, I aggree. > Thanks for bringing this feature to my attention too. > > It doesn't hurt bringing idea's on the table I hope. > > Glenn > > _______________________________________________ > Talk-be mailing list > Talk-be@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-be > >
_______________________________________________ Talk-be mailing list Talk-be@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-be
