neqsim-pipe-route-profile

Computes subsea pipeline route lengths, KP profiles, and seabed elevation statistics from waypoints.

4|2|Updated May 31, 2026
One-click install
npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-pipe-route-profile-equinor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neqsim-pipe-route-profile
Source: https://github.com/equinor/neqsim-community-skills/tree/main/skills/subsea/pipe-route-profile
Command: npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-pipe-route-profile-equinor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers planning subsea flowlines and risers need a quick screening of route length and seabed elevation before committing to detailed hydraulic design, but often only have an ordered list of waypoints with water depths. This Skill converts those waypoints into segment lengths, a cumulative KP profile, total route length, and elevation statistics without requiring proprietary survey data. ## Core Features & Use Cases - Route Geometry Calculation: Computes per-segment horizontal and 3D lengths, depth changes, and slopes using planar Euclidean or great-circle haversine distance for cartesian and geographic coordinates. - Elevation Profile Screening: Produces cumulative KP profiles, net elevation change, total rise and descent, maximum slope, and a slope warning flag against a configurable public guideline. - Open Data Guidance: Documents how to source waypoints from Norwegian Offshore Directorate FactPages and seabed depths from the EMODnet Bathymetry REST API for real-field screening. - Use Case: An engineer has tree and riser-base coordinates with seabed depths and needs the total route length and steepest slope to feed a NeqSim pressure-drop and hydrate screening workflow. ## Quick Start Ask the agent to compute the total route length, KP profile, and slope warning for an ordered list of waypoints with names, coordinates, and seabed depths.

Frequently Asked Questions about neqsim-pipe-route-profile

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

FAQPage Schema
How do I calculate subsea pipeline route length from waypoints in Python?▼

Create a PipeRouteModel and call evaluate with an ordered list of waypoints containing name, x, y, and depth_m. The result includes per-segment lengths, total horizontal and 3D route length in kilometres, and a cumulative KP profile.

How to get seabed depth data for a pipeline route profile?▼

Query the EMODnet Bathymetry REST API depth_sample endpoint with each route point and negate the returned elevation to get depth. End-point coordinates and water depths can come from Norwegian Offshore Directorate FactPages CSV exports.

Does the route profile calculation support latitude and longitude coordinates?▼

Yes, set coordinate_system to geographic and supply x as longitude and y as latitude in degrees. Horizontal distances are then computed with the great-circle haversine formula instead of planar Euclidean distance.

Can this replace hydraulic or flow assurance analysis for pipeline design?▼

No, it is a screening-level geometry tool only and performs no pressure drop, thermal, hydrate, span, or stability analysis. Design-grade work must use validated NeqSim workflows such as PipeBeggsAndBrills and qualified engineering review.

Why is my computed route length much shorter than expected?▼

The route follows only the supplied waypoints, so too few points over a curved corridor underestimates length. Add intermediate waypoints, for example by interpolating along the great circle and sampling the bathymetry DTM at fixed spacing.