If I have a coverage envelope assuming OGC PIXEL-IS-CENTER, the actual area covered by the raster is not only the envelope but the envelope plus the area covered by the pixels: the envelope plus a buffer the size of a pixel divided by two (assuming square pixels).
In my code I crop a large coverage to a ROI polygon using the CoverageCrop operation. The envelope of the resulting coverage does not always fully contain the envelope of my cropping polygon (but the pixel area does cover the entire polygon). My problem is that if I then use VectorToRasterProcess to rasterize my original ROI cropping polygon with the output bounds set to my cropped coverage bounds, it decides in the setBounds() method that the features to rasterize lie outside the given output raster bounds. VectorToRasterProcess then curiously decides to change the output bounds to the intersection of the bounds of the features to rasterize and the output bounds (why not crop the features to the output bounds instead???). If I want to prevent this I guess I have to buffer my ROI polygon so that the cropped coverage envelope always always fully contains the features I want to rasterize or crop these features to the coverage envelope. Is my line of reasoning correct and is this intended behaviour? Matthijs ------------------------------------------------------------------------------ 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-GT2-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
