neqsim-field-layout-import

Field Layout Import

Use this skill to normalize a supplied subsea map into a clean node list for downstream geometry and routing screening. It accepts an already-parsed GeoJSON FeatureCollection of point features or a list of CSV-like rows, and produces a validated list of nodes (well, manifold, host, riser base) with coordinates, water depth, and kind. It is intentionally simple, performs no file or network I/O, and should feed validated NeqSim routing and hydraulic workflows.

When to Use

• When a user supplies a parsed GeoJSON layout or a table of node coordinates and wants a clean, validated node list.
• When an agent needs a normalized layout to feed subsea-layout-geometry or pipe-route-profile.
• When data quality issues (missing depth, duplicate names, unknown kind) should be flagged before screening.

Inputs

• from_geojson(obj): an already-parsed GeoJSON FeatureCollection dict with Point features. Each feature's geometry.coordinates is [x, y] (or [longitude, latitude]), and properties may include name, water_depth_m, and kind.
• from_rows(rows): a list of dicts with name, x/y (or longitude/latitude), optional water_depth_m, and optional kind.

Outputs

• nodes: the normalized node list, each with name, x, y, water_depth_m, and kind.
• node_count: the number of normalized nodes.
• issues: data-quality findings (missing depth defaulted, unknown kind normalized, duplicate name, skipped feature).
• neqsim_available: whether the optional NeqSim package is importable.
• assumptions: public assumptions and required follow-up.

Engineering Method

Each feature or row is mapped to a node with a non-empty name, finite x and y coordinates, a non-negative water_depth_m (defaulted to 0 with an issue when missing), and a kind normalized to a known set (well, manifold, host, riser_base, template, tie_in); unknown kinds are coerced to well with an issue. Duplicate names and features that cannot be parsed are recorded as issues rather than raising, so a partial map still yields a usable node list. This is a data-shaping step only and performs no geometry, routing, or hydraulic calculation.