{
  "context": "Evaluates how well the solution uses the h3 geometry containers and helpers to bridge between raw coordinate rings, native polygon/multipolygon objects, and GeoJSON. Checks emphasize relying on LatLngPoly/LatLngMultiPoly, GeoJSON conversion helpers, and proper __geo_interface__ usage rather than hand-rolled geometry handling.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Native polygon",
      "description": "Builds single polygons with the library's LatLngPoly class (outer plus holes) instead of manual dicts, producing shapes that expose __geo_interface__.",
      "max_score": 25
    },
    {
      "name": "Multi-shape merge",
      "description": "Combines multiple polygons via LatLngMultiPoly (or equivalent native multi-shape) so resulting objects report MultiPolygon geometry through __geo_interface__.",
      "max_score": 25
    },
    {
      "name": "GeoJSON export",
      "description": "Uses h3shape_to_geo or a shape's __geo_interface__ to emit GeoJSON with closed rings and [lng, lat] ordering instead of manually crafting coordinate arrays.",
      "max_score": 20
    },
    {
      "name": "GeoJSON import",
      "description": "Parses Polygon/MultiPolygon input through geo_to_h3shape (or equivalent) to produce native shapes, correctly mapping GeoJSON [lng, lat] coordinates into the library's (lat, lng) containers.",
      "max_score": 20
    },
    {
      "name": "Invalid geometry guard",
      "description": "Rejects unsupported geometry types by surfacing ValueError from geo_to_h3shape (or comparable library error) without constructing shapes.",
      "max_score": 10
    }
  ]
}