Geometry Transformation Practice Sheets

How to use Geometry Transformation Practice Sheets

Turn your own integer-grid polygons into drawable rigid-transformation exercises. Each task keeps its source figure and explicit movement instruction on the student page; a separate teacher section can show the image and its exact coordinates.

1. Set a grid extent from 3 to 12 and author 1–12 distinct named polygons with 3–8 integer vertices in boundary order.
2. Choose one operation per task: translate with dx/dy; rotate 90, 180 or 270 degrees counterclockwise about center; or reflect across vertical/horizontal offset or diagonal/antidiagonal.
3. Choose include or omit for the separate teacher pages, then download and inspect the printable HTML. The complete on-page report always retains the answer geometry.

Good to know

• Coordinates, extent, offsets and angles must be plain integer JSON tokens. Polygon vertices must be distinct, simple, nonzero-area and free of consecutive collinear edges. Concave polygons and either boundary orientation are supported. Source and transformed vertices must fit the same declared grid. No arbitrary angle, dilation, skew, expression, inferred question or movement sequence is included.
• Reflection uses axis vertical with x=offset, horizontal with y=offset, diagonal with y=x, or antidiagonal with y=−x. Offset is required only for vertical/horizontal. Rotation center lies inside the grid; translation offsets are bounded by ±24. Adjacent source/image figures can naturally overlap.
• One student page is generated per task, followed by optional teacher pages. The student HTML has the source polygon, numbered grid, movement instruction and blank answer cells; it omits the image polygons and explicit answer coordinate tables. Answers remain derivable from the exercise and are present in the separate report. This is not exam secrecy or a learning/curriculum certification.
• The fixed A4-oriented layout has a 120 mm square plotting region inside a 160 mm SVG. Noninteger display positions are rounded to nine decimal SVG units; integer model results are exact. Font metrics, output scaling, page breaks, label collisions at very close vertices and physical print suitability require inspection. No automatic label collision solver is promised.
• Browser-local processing, with no upload, persistence, external resources or code execution. Model JSON is limited to 30,000 characters, 10,000 values and 18 levels. Generated HTML is capped at 750,000 characters, standalone SVG at 50,000 and the complete report at 1,000,000. The downloaded artifact must be inspected in the target browser and print setup.