neqsim-field-layout-import

Normalizes parsed GeoJSON or tabular rows into validated subsea field-layout node lists.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw subsea layout data from GeoJSON maps or spreadsheets often contains missing water depths, inconsistent node type labels, and duplicate names that break downstream geometry and routing analysis. This Skill converts already-parsed GeoJSON FeatureCollections or CSV-like rows into a clean, validated node list of wells, manifolds, hosts, and riser bases, flagging every data-quality issue instead of failing silently. ## Core Features & Use Cases - GeoJSON and Tabular Import: Accepts an already-parsed GeoJSON FeatureCollection of Point features or a list of dict rows with x/y or longitude/latitude coordinates. - Validation with Issue Reporting: Defaults missing water depths to 0.0, normalizes unknown kinds to 'well', and records duplicates and skipped records in an issues list rather than raising errors. - Offline and Public-Safe: Performs no file reading, URL fetching, or coordinate transformation, so it works fully offline with no credentials or proprietary data. - Use Case: An engineer has a parsed GeoJSON map of a subsea tieback with a host, two wells, and a drilling centre. The importer returns three normalized nodes with coordinates and depths, plus issues noting the drilling-centre kind was coerced to 'well', ready to feed the subsea-layout-geometry skill. ## Quick Start Ask the agent to normalize your parsed GeoJSON FeatureCollection of subsea wells, manifolds, and hosts into a validated node list and report any data-quality issues before routing screening.

Frequently Asked Questions about neqsim-field-layout-import

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

FAQPage Schema
How do I convert GeoJSON to a subsea field layout node list in Python?▼

Parse the GeoJSON file yourself, then pass the resulting dict to FieldLayoutImporter.from_geojson. It returns a LayoutImportResult with normalized nodes containing name, x, y, water_depth_m, and kind, plus an issues list flagging data-quality problems.

How do I import subsea well coordinates from CSV rows?▼

Load your table into a list of dicts with name, x/y or longitude/latitude, and optional water_depth_m and kind, then call FieldLayoutImporter.from_rows. Each row becomes a validated node, and unparseable rows are skipped with an issue recorded.

Does the field layout importer read files or fetch data from URLs?▼

No, the importer performs no file or network I/O by design. Callers must parse GeoJSON or load tabular data themselves and pass already-parsed Python objects, keeping the skill offline and free of credentials.

What happens when water depth or node kind is missing?▼

Missing or invalid water_depth_m values default to 0.0 with an issue recorded, and unknown kind labels are normalized to 'well' with an issue. Duplicate names and unparseable features are also flagged rather than raising errors.

What are the limitations of this layout import approach?▼

It supports only GeoJSON Point features, performs no coordinate projection or transformation, and does no geometry, routing, or hydraulic calculation. The output is a normalized node list that must feed validated tools like subsea-layout-geometry or NeqSim PipeBeggsAndBrills.