GIS Comprehensive Knowledge Base
Paste the following prompt into your AI chat to install this skill:
Please install @user_15292d5a/yjkj-giser according to https://skillhub.cn/install/skillhub.md.
About this skill
Problem
GIS engineers often switch between coordinate offsets, standards QA, software workflows, scripting, and point-cloud processing. This skill organizes scattered knowledge such as SKILL.md, coordinate systems, national surveying standards, ArcGIS Pro, QGIS, FME, LiDAR360, Python/R, and WebGIS into searchable modules with pre-execution checks.
How It Works
It follows a 7-stage workflow: requirements lock, data inspection, solution design, environment prep, core execution, quality self-check, and output archiving. When a step is uncertain, it asks for a diagnostic report instead of directly modifying data or running scripts.
Core capabilities include:
- Foundations & standards: WGS84, EPSG, CGCS2000, GB/T standards, QA, and delivery archiving.
- Software workflows: ArcGIS Pro, QGIS/PyQGIS, CASS, FME, GlobalMapper, LiDAR360.
- Development & analysis: GeoPandas, Rasterio, PostGIS, WebGIS, GEE, spatial statistics, and multi-source fusion.
- Pitfalls & format choices: error triage, format decision trees, and modern GIS stacks such as GeoParquet, COG, PMTiles, and DuckDB.
Boundaries
It is best used for locating GIS knowledge, decomposing tasks, and checking execution steps; it is not a full data-production environment. For version-sensitive tools, confirm ArcGIS Pro, QGIS, SuperMap, or other versions first. Some standard clauses are limited by source material and should be verified against official standard text before formal delivery.
Use Cases
- Before an ArcGIS Pro 3.7 task, verify the 3.6 manual and 3.7 difference file to avoid misusing new features.
- When coordinates fly, topology fails, or Chinese text garbles, check the pitfall library to locate EPSG, projection, and encoding issues.
- Before delivering DLG/DEM/DOM outputs, use the standards files to check secondary QA, acceptance, naming, and metadata.
- Before writing PyQGIS or FME workflows, break work into requirements lock, data inspection, solution design, and self-check.
Best For
- GIS engineers who need to confirm workflow differences and version-specific features across ArcGIS Pro 3.6/3.7, QGIS, and FME.
- Surveying data engineers who must complete DLG/DEM/DOM QA, acceptance, and delivery archiving against GB/T standards.
- Python/R spatial developers who want to process vector/raster data and run spatial statistics with `GeoPandas`, `Rasterio`, and `PostGIS`.
- Project technical leads who need to decompose requirements, data risks, execution plans, and output self-checks before production.
Related Skills
Automatically compiles Feishu documents with quality checks, deduplication, Wiki updates, and multidimensional table index writes.
Open-ended visual QA for images, combining CV and LLM for scene description, chart interpretation, reasoning, and cloud history lookup.
Fast CLI for summarizing URLs, local files, and YouTube links with multi-provider models and JSON output.
Extracts an eight-layer reasoning fingerprint from scholar texts and applies a nine-module constraint to run peer review, supervision, lecturing, or panel discussion with quantitative scores and qualitative comments.