Not sure what the issue is? If you expect a grid for each polygon, you should use Group By and select the unique Id of the polygon layer. If you have no Unique Id attribute you can generate this using a UUIDGenerator or a Counter.

@gcarmich​ It depends on what you want form the grid, but search FME HUB for grid and you'll see quite a few tools for generating grids optimized for different scenarios. But 2DGridAccumulator should work if you use group by as suggested by @nielsgerrits​ 

The .kmz polygon is about the size of a US County. My expectation is that the 2DGridAccumulator would create a grid of 3meterx3meter square polygons across the entire .kmz polygon so that I could bin point data for analysis. I'm away from my PC but will try the GroupBy and FME Hub resources when I get back. Thank you

For polygons you can use the Tiler. To test use better a greater grid. ​

I changed the .kmz boundary to 3 smaller .shp boundaries because the workflow was indicating "no geometry" with the .kmz.

I ran the grid routing using Tiler. It produces grids when I specify "Number of Tiles" but not "Dimensions in Ground Units"

I want to create 3meter x 3 meter grids overlaying each polygon. I think I have ground units specified correctly so I'm not sure why the 3mx3m grid won't generate.

I've attached the files that I am using in a .zip to see if anyone has thoughts on the issue.

you have a very small expansion:

min -74.0336702568992, 40.73238691114595

max -74.02460372691843, 40.73675877954369

Your tiler params are 3 ground units. It's more than the expansion.

Maybe I don't understand Ground Units. I though my workflow changed the Ground Units to "meters" which would be significantly less than the expansion - which I measure as 905m diagonal.

Measure in the DataInspector. Use as tiler param 0.001 and you sea a result.