In tracking down why a PointStacker transform isn't working, I found that the StreamingRenderer adapts the original query then reapplies it to the transformed feature collection. StreamingRenderer:2236 on 8.x is the start of the relevant block of code.
The issue in my case is that the original query[1] contains an attribute that the PointStacker doesn't preserve and hence the second query on the transformed collection yields nothing. Certainly one improvement would be to allow PointStacker to preserve one of the aggregated feature's attributes to represent the new stacked output feature, but my question is: Why is the query being run a second time? I could see that preserving the BBOX would be useful for transformations that create new features that lie outside the initial BBOX but it seems like the other work is redundant as the features have already been filtered via the first query. I admit I might be short-sighted here. Regards, -Ian [1] [[ Date = Tue Jan 15 17:00:00 MST 1980 ] AND FastBBOX [property=location, envelope=ReferencedEnvelope[-216.56249996985542 : 216.56249996985542, -75.1441685694744 : 86.89368497984668]]] ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
