On Sat, Jan 16, 2010 at 04:25, Ulf Lamping <[email protected]> wrote: > Am 15.01.2010 09:05, schrieb Jiri Klement: >> I think it would be nice to use search patterns in mappaint. The style >> information is cached in OsmPrimitive so it shouldn't have impact on >> overall performance. And there are probably other usecases when >> key=value matching is not sufficient. >> >> Actually I was planning to do some prototype to see if performance >> really isn't a problem > > Might be a problem for initial reading of large datasets, but you cannot > say wether it's acceptable or not until you've really tried it. > > That's the conclusion I've got when doing the first round of mappaint > performance improvements a lot of time ago :-) > >> and then ask here if it is really a good idea >> to switch to search patterns. But when avar brought it up, we can >> start the discussion now. So are there any other usecases when search >> patterns would be usefull in mappaint or any objections agains search >> patterns? > > Avar was the first one I've seen to come up with "show me stuff from > user xy in a special way". I'm unsure if this is really a common use case.
FWIW potlatch does this every day by rendering things differently if user == the guy who uploaded tiger && tiger:reviewed == .... > Personally, I'd like to keep things simple here - so even none > developers have at least a chance to write their own rendering rules. > > Otherwise complexity grows and grows and ends up like the mapnik > rendering rules with embedded SQL statements - the learning curve is now > really high :-( Sure, but <condition user="foo" /> isn't that much harder than <condition k="" v=""/> :) _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
