raidriar7170/hermes-skilleval/geospatial-routing-data
Claude Code and agent skill by raidriar7170/hermes-skilleval
- community
Checking that the SKILL.md file is still in the repository.
Geospatial routing data handling for depot and station coordinates, route node IDs, internal index mappings, great-circle distance matrices, and route-distance reconstruction. Use when optimization or reporting tasks involve latitude/longitude, station IDs, depots, distance metrics, vehicle routes, or validating travel distance from reported paths.
Install
npx vskill@latest install raidriar7170/hermes-skilleval/geospatial-routing-dataSKILL.md
The same SKILL.md was published earlier as benchflow-ai/skillsbench/geospatial-routing-data.
Geospatial Routing Data
Use this skill before building a routing model or validating a routing report that contains coordinates, depots, station IDs, and route sequences.
The main risk is mixing user-facing IDs with internal array indices or using a different distance metric from the task.
Parse Data Safely
Load structured data with a parser and build explicit mappings:
Use internal indices in optimization variables. Use original station IDs in final reports.
Coordinate Validation
Check coordinates before building distances:
Latitude and longitude are degrees. Convert to radians only inside the distance function.
Great-Circle Distance
Match the task's declared distance metric. If the task specifies an Earth radius, use that exact value.
For great-circle miles with Earth radius 3960.0, use:
Clamp cos_arc into [-1, 1] to avoid floating-point domain errors.
Do not mix:
- Euclidean distance on degrees;
- haversine with a different Earth radius;
- miles and meters;
- rounded distances inside the optimization objective.
Build Routing Nodes
Use separate depot labels when the route output must show a start and end depot:
Build distances over the same arc set used by the optimization model:
If direct depot-to-depot travel is allowed, keep the (START, END) arc.
Convert Routes Between IDs and Indices
Optimization route using internal indices:
Report route using original station IDs:
Parse a reported route back to internal indices:
Never assume station IDs are 0..n-1.
Reconstruct Route Distance
Recompute reported travel distance from route sequences:
For multiple vehicles:
Compare with tolerance, not exact string equality:
Route Data Checks
Before trusting a route:
- first node is the start depot label;
- last node is the end depot label;
- every non-depot node is a known station ID;
- route has at least one station if vehicles cannot stay at the depot;
- station sequence length equals the stop list length;
- no repeated station within a route when per-vehicle no-repeat is required;
- distance is recomputed from coordinates, not copied from model output.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/raidriar7170/hermes-skilleval/geospatial-routing-data)