executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
georeferencing-and-crsRoute BlenderGIS CRS, geoscene origin, coordinate transform, and reprojection-engine tasks.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task depends on BlenderGIS scene georeferencing: CRS/SRID state, scene origin coordinates, WGS84/Web Mercator/UTM transforms, projection engine selection, predefined CRS preferences, or recovery from broken partial georef state.
GeoScene state stored on bpy.context.scene custom properties.geoscene.* operators or GeoScene.crs.longitude, latitude) and projected origin (crs x, crs y).AUTO, GDAL, PYPROJ, BUILTIN, and EPSGIO / MapTiler Coordinates reprojection engines.raster-dem-and-basemaps.vector-data-and-osm.geocameras-and-rendering.GeoScene, SRS, Reproj, custom keys, operators, preferences, and engine behavior.GeoScene(scene).isGeoref is true and GeoScene(scene).isBroken is false.SRID, crs x, and crs y; longitude and latitude are synchronized convenience keys when reprojection succeeds.python sub-skills/georeferencing-and-crs/scripts/transform_point.py --src-crs EPSG:4326 --dst-crs EPSG:3857 --x 2 --y 48 --json