# CGNS domain file: split domain surfaces

**URL:** https://discourse.paraview.org/t/cgns-domain-file-split-domain-surfaces/13813
**Category:** ParaView Support
**Created:** [January 28, 2024, 4:06pm UTC](https://discourse.paraview.org/t/cgns-domain-file-split-domain-surfaces/13813 "2024-01-28T16:06:25Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![GabriB](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/g/34f0e0/32.png) [@GabriB](https://discourse.paraview.org/u/GabriB)
#### Post date: [January 28, 2024, 4:06pm UTC](https://discourse.paraview.org/t/cgns-domain-file-split-domain-surfaces/13813/1 "2024-01-28T16:06:25Z")

</div>

Dear all,

I imported my CGNS domain file. When I load the domain everything is defined as “one-block” (please refer to the attached Figure).

I would like to split my domain patches, like the domain boundaries and my geometry boundaries.

Do you know how can I achieve that?

Many thanks in advance.

Regards,

Gabriele

 ![CGNS_domain](https://discourse.paraview.org/uploads/default/original/2X/8/86f7b87c1ce4a69cee9202614c12162eca94ba81.png)

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 29, 2024, 9:44am UTC](https://discourse.paraview.org/t/cgns-domain-file-split-domain-surfaces/13813/2 "2024-01-29T09:44:33Z")

</div>

please share your data

---

<div class="post-metadata">

### Author: ![GabriB](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/g/34f0e0/32.png) [@GabriB](https://discourse.paraview.org/u/GabriB)
#### Post date: [January 29, 2024, 12:14pm UTC](https://discourse.paraview.org/t/cgns-domain-file-split-domain-surfaces/13813/3 "2024-01-29T12:14:01Z")

</div>

Dear Mathieu,

Many thanks in advance for your support.

Please find below the link of the CGNS file:

> **[run.zip](https://cloud.oossanen.nl/s/YcdTbrfzcZFJpHd)**
>
> Cloud - Oossanen - a safe home for all your data

FYI: I am using Paraview 5.12.0-RC2

Regards,

Gabriele

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 29, 2024, 1:20pm UTC](https://discourse.paraview.org/t/cgns-domain-file-split-domain-surfaces/13813/4 "2024-01-29T13:20:23Z")

</div>

So looking at your file, it indeed does not contain the boundaries.

I can see these warnings though:

```auto
( 27.668s) [paraview] vtkCGNSReader.cxx:4268 WARN| vtkCGNSReader (0x76e684006a20): Skipping BC_t node: BC_t type 'BCFarfield' not supported yet.
( 27.670s) [paraview] vtkCGNSReader.cxx:4268 WARN| vtkCGNSReader (0x76e684006a20): Skipping BC_t node: BC_t type 'BCFarfield' not supported yet.
( 27.671s) [paraview] vtkCGNSReader.cxx:4268 WARN| vtkCGNSReader (0x76e684006a20): Skipping BC_t node: BC_t type 'BCFarfield' not supported yet.
( 27.671s) [paraview] vtkCGNSReader.cxx:4268 WARN| vtkCGNSReader (0x76e684006a20): Skipping BC_t node: BC_t type 'BCSymmetryPlane' not supported yet.
( 27.671s) [paraview] vtkCGNSReader.cxx:4268 WARN| vtkCGNSReader (0x76e684006a20): Skipping BC_t node: BC_t type 'UserDefined' not supported yet.
( 27.671s) [paraview] vtkCGNSReader.cxx:4268 WARN| vtkCGNSReader (0x76e684006a20): Skipping BC_t node: BC_t type 'UserDefined' not supported yet.

```

So maybe it does contain some information that ParaView is unable to use yet.

In any case, you want to check how you generated that data.

---

<div class="post-metadata">

### Author: ![MicK7](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mick7/32/1374_2.png) [@MicK7](https://discourse.paraview.org/u/MicK7)
#### Post date: [January 31, 2024, 9:38am UTC](https://discourse.paraview.org/t/cgns-domain-file-split-domain-surfaces/13813/5 "2024-01-31T09:38:03Z")

</div>

To be available in Paraview, the CGNS BCNode\_t need to be defined through “FamilySpecified” and the Family associated will also contains the type of boundary. This is something all good meshers do (Cadence Pointwise, Ansa from Beta CAE, Cadence Automesh, …).  
As suggested by Matthieu, you want to check how the data was generated.