Boundary Mapping

Validates fire perimeter geometry and generates sector-level boundary reports with acreage checks.

Updated Dec 20, 2025

Search Tags:#boundary #GIS #perimeter #polygon #fire-perimeter #boundary-report

Ready to run

npx skills add https://github.com/jvalenzano/ranger-twin --skill boundary-mapping

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Boundary Mapping
Source: https://github.com/jvalenzano/ranger-twin/tree/main/agents/burn_analyst/skills/boundary-mapping
Command: npx skills add https://github.com/jvalenzano/ranger-twin --skill boundary-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps fire managers and analysts quickly validate fire perimeter geometry, ensuring accurate acreage calculations and reliable sector boundaries for decision-making.

Core Features & Use Cases

Polygon validation: checks for proper closure, valid coordinates, and sufficient points.
Perimeter and area calculations: computes boundary length and area in acres for multi-sector fires.
Discrepancy checking: compares calculated acreage to reported totals and flags significant differences.
Sector-level reporting: returns per-sector boundaries with validity flags and geometric issues.

Quick Start

Start by running the Boundary Mapping skill with a fire_id (e.g., cedar-creek-2022) and optionally provide pre-loaded sector data to obtain a structured boundary report including perimeter stats, acreage, and quality checks.

Frequently Asked Questions about Boundary Mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate a fire perimeter polygon for proper geometry closure?▼

Fire perimeter validation involves checking polygon closure, verifying coordinate ranges, and confirming sufficient boundary points to ensure geometric integrity for accurate acreage reporting and incident mapping.

How do I calculate fire perimeter length and acreage from polygon boundaries?▼

Calculating fire perimeter length and acreage requires running boundary scripts that compute polygon boundary length and total area in acres, returning structured statistics for each sector in the fire incident.

Can I check for discrepancies between calculated fire acreage and reported acres?▼

Yes, discrepancy checking compares calculated polygon acreage against reported totals and flags significant differences, ensuring reported fire acreage aligns with validated geometric calculations for accurate incident reporting.

What is a fire perimeter boundary report and when do I need one?▼

A fire perimeter boundary report provides perimeter statistics, acreage calculations, and geometry quality checks for a fire incident. You need one when requiring perimeter integrity validation for fire management decision-making and sector-level reporting.

Does boundary mapping work with multi-sector fire data?▼

Yes, boundary mapping supports multi-sector fire data by generating sector-level reports that return per-sector boundaries with individual validity flags and geometric issue alerts alongside overall perimeter and acreage statistics for the entire incident.

What are the limitations of using scripts for fire perimeter geometry validation?▼

Boundary mapping scripts focus on polygon closure, coordinate range checks, and acreage discrepancy assessment but do not handle external GIS data integration or satellite imagery processing, limiting use to pre-loaded perimeter geometry and sector data validation.