Update to GovBot Energy Infrastructure

{
  "description": "Summarize held EIA pipeline and, when requested, DOE NETL/HIFLD transmission-line records intersecting a public research area, preserving source vintages, mapped geometry limits and counts without inferring exact routes, operating conditions or excavation safety.",
  "included_files": [],
  "name": "pipeline-corridor-records",
  "skill_md_contents": "---\nname: pipeline-corridor-records\ndescription: Summarize held EIA pipeline and, when requested, DOE NETL/HIFLD transmission-line records intersecting a public research area, preserving source vintages, mapped geometry limits and counts without inferring exact routes, operating conditions or excavation safety.\n---\n\nUse this workflow for public research about EIA-mapped pipeline corridors. Start with `describe_energy_layers` to identify available pipeline types, source vintages, source URLs and geometry coverage. These held map layers are not current operator field drawings and do not inherit the August 2026 generator-workbook period. Electric transmission has its own DOE NETL/HIFLD source and operation; substations and utility service territories remain unsupported.\n\nAccept a public research point and radius or an explicit bounding box. Use `find_pipelines_in_area` with exactly one of the supported geometry forms and any requested supported pipeline-type filter. Validate coordinate ranges, west/east and south/north ordering and size bounds against the actual schema. The service does not support an antimeridian-crossing box; do not silently reinterpret one. Ask for a smaller valid public area when a query is outside bounds. No home-address solicitation, device geolocation or property geocoding.\n\nReport the held layers searched and the requested area before results. Separate `pipeline_groups_matching` from `returned` displayed groups and their limit. The service groups matching records by type and source attributes; per-group `matching_mapped_records` and layer counts count matched records, not unique physical systems. Do not label a group count as a segment or physical-pipeline count. A line record is not necessarily a unique named pipeline system, segment in operation or number of physical pipes. Preserve source identifiers and names; missing ownership/status/diameter/throughput/depth fields remain unknown and should not be inferred from the name, commodity or proximity. Do not join different layers into a single physical asset without source identity evidence.\n\nDescribe geometry as generalized EIA mapping. An area intersection or approximate mapped distance does not locate a pipe precisely on the ground, determine which side of a parcel it lies on, establish a connection, show a safe setback, or supply an excavation/tapping location. Keep any output distance units and approximation qualifiers together. Point searches use a local equirectangular closest-point approximation on mapped straight segments, with approximate radius-edge inclusion; a bounding-box query has no point-distance measure. Current held pipeline layers are January 2020 and omit local distribution and most gathering lines. Do not present a derived line length as an engineering length, authoritative route or guaranteed closest physical pipe. Preserve returned order when rounded distances tie.\n\nProvide a short table only for requested fields that exist, then explain each layer's source vintage/coverage, original download date and held-read time. Source periods can differ across pipeline types and facilities. A fresh query/read timestamp is not evidence the corridor is current. Cite EIA's published source link for the specific layer when returned. Do not claim every constituent dataset shares a single public-domain license; retain source-specific attribution and terms.\n\nNo matches means no mapped records in the queried held scope, not absence of pipelines or permission to dig. Source/asset/schema errors are unavailable evidence, not empty results. Decline exact field route, depth, pressure, capacity availability, connection feasibility, operating condition, digging/tapping, safety, legal/insurance or financial determinations. Refer authoritative location and operational questions to the relevant operator or qualified authority; do not promise a result. Offer the supported historical corridor inventory with clearly bounded conclusions.\n\nFor an explicit pipeline/transmission comparison, call `find_transmission_lines_in_area` separately with the same valid public area and requested limit. Keep EIA pipeline groups and NETL-hosted HIFLD transmission records in separate result sections; their counts, source periods and identifiers are not interchangeable. Transmission credits are HIFLD2022, retrieved by NETL2023. Retain each returned owner/status/voltage/inferred flag and record source/date; unknown stays unknown. Voltage kV is not power MW, spare capacity or connectivity. Explain the returned query generalization settings and approximate distances; no engineering route precision. Cite NETL and supplied constituent credits. Historical/live outages and restoration estimates are excluded. No proximity-based plant/line identity or physical connection inference.\n"
}