Trevor, I don't think that's his problem.
For the Raster Filter, the attribution is irrelevant.
The potential problems (ignoring standard raster issues because he gets it working with other methods):
M/Z Attribution
some applications have decided to start exporting PolygonZ shapefiles rather than Polygon shapefiles by default.
Since Z and M are unused by my application and M is pretty much unused by every GIS application in the universe, I don't bother to process these. There's a number of other issues with the geometry like being twice as large in computer memory, twice as large on your computer (which is a problem with a limited size format like SHP), twice as long to read, and substantially longer to use any GIS functions on.
There's 3 options and I went with the easiest:
- Reject any Z/M geometries (what it does now)
- Strip all Z/M geometries and turn them into regular geometries
- Rewrite all my Geometric Functions to handle 3D geometries and measures.
This should warn you and not apply a filter. In general, this happens on any geometry that isn't a Polygon.
Projection Issues
Self Explanatory for most of it but the filter polygon does need to be in the same projection that the raster inputs are.
This will legitimately produce no output unless your raster tiles are around 0 N,0 E
No Polygons Actually Exported
If the shapefile has the proper attribution but no entries in the file, it will produce no output with no warning because that's what the shapefile is telling it to do.