Skip to content
Back to skills

Georeferencing And Crs

ASecurity

"Route BlenderGIS CRS, geoscene origin, coordinate transform, and

  • 247 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 8, 2026
toolspythongobashgitapi

Works with

  • api

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill georeferencing-and-crs --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Georeferencing And Crs?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Georeferencing And Crs
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-georeferencing-and-crs/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-georeferencing-and-crs)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: georeferencing-and-crs
description: "Route BlenderGIS CRS, geoscene origin, coordinate transform, and
  reprojection-engine tasks."
disable-model-invocation: true
metadata:
  disco-role: operating
license: GPL 3.0
---

# georeferencing-and-crs

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.

## Use this sub-skill for

- Inspecting or repairing `GeoScene` state stored on `bpy.context.scene` custom properties.
- Setting or switching the scene CRS through `geoscene.*` operators or `GeoScene.crs`.
- Linking geographic origin (`longitude`, `latitude`) and projected origin (`crs x`, `crs y`).
- Choosing among `AUTO`, `GDAL`, `PYPROJ`, `BUILTIN`, and `EPSGIO` / MapTiler Coordinates reprojection engines.
- Transforming one point safely outside Blender with [scripts/transform_point.py](scripts/transform_point.py).

## Route elsewhere

- Raster images, DEMs, world files, GeoTIFF details, basemap tiles, and raster reprojection outputs belong to `raster-dem-and-basemaps`.
- Shapefile, OSM XML, Overpass query, feature fields, and imported vector geometry workflows belong to `vector-data-and-osm`.
- Camera geophotos, georeferenced render cameras, and camera world-file output belong to `geocameras-and-rendering`.

## Read next

- [references/api-reference.md](references/api-reference.md) for `GeoScene`, `SRS`, `Reproj`, custom keys, operators, preferences, and engine behavior.
- [references/workflows.md](references/workflows.md) for CRS setup, origin linking, broken-state recovery, engine choice, and point-transform examples.
- [references/troubleshooting.md](references/troubleshooting.md) for invalid CRS, partial georef state, missing engines, MapTiler/EPSG.io network risk, optional dependency differences, and axis-order gotchas.

## Fast checks

1. A usable BlenderGIS scene is georeferenced when `GeoScene(scene).isGeoref` is true and `GeoScene(scene).isBroken` is false.
2. Required scene custom keys are exactly `SRID`, `crs x`, and `crs y`; `longitude` and `latitude` are synchronized convenience keys when reprojection succeeds.
3. For a quick WGS84-to-Web-Mercator smoke test, run:

```bash
python sub-skills/georeferencing-and-crs/scripts/transform_point.py --src-crs EPSG:4326 --dst-crs EPSG:3857 --x 2 --y 48 --json
```

Files in this skill

  • SKILL.md2.4 KB
  • references/api-reference.md13 KB
  • references/troubleshooting.md11.2 KB
  • references/workflows.md9.7 KB
  • scripts/transform_point.py13.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.