Not a real Problem ...
see the document for FEFLOW ASCII file description ...
maybe create first a dummy-fem-file and save as ASCII
So you see the required format ... its something like this
.. the lines starting with 'x' mean, here's a comment from me ..
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
PROBLEM: A new feflow problem
CLASS (v.5.012)
2 1 1 3 10 1 8 8
DIMENS
xxxxx number of elements, number of nodes ... the other see documentation
61303 108800 6 1 2000 0 4 0 0 1
0 0 145 0 0 0
SCALE
1.782178e-002,3.000000e+002,1.000000e+000,1.000000e+000,0.000000e+000,0.000000e+\
000
xxxxxx here starts the element definition
xxxxxx elemt N1 has nodes 2,3,5146 in upper slice, 5575 ... in lower
slice - one line per element - for each element in 3D- Mesh !
NODE
2 3 5146 5575 5576 10719
2 5146 265 5575 10719 5838
3 5003 5146 5576 10576 10719
3 4 5003 5576 5577 10576
.......
xxxxx next the node coordinate definition for your mesh (only 2D
geometry! and relative Mesh coordinates)
COOR ... x-coordinates for node 1 .. n
1.50000000000000e+002,1.00000000000000e+002,1.00000000000000e+002,1.000000000000\
00e+002,1.00000000000000e+002,1.00000000000000e+002,1.00000000000000e+002,1.0000\
0000000000e+002,1.00000000000000e+002,1.00000000000000e+002,1.00000000000000e+00\
2,1.00000000000000e+002,
1.00000000000000e+002 ..... <CR>
next without a comment ...
... all y-coordinates for node 1 .. n
1.50000000000000e+002,1.00000000000000e+002,1.00000000000000e+002,1.000000000000\
00e+002,1.00000000000000e+002,1.00000000000000e+002,1.00000000000000e+002,1.0000\
0000000000e+002,1.00000000000000e+002,1.00000000000000e+002,1.00000000000000e+00\
2,1.00000000000000e+002,
1.00000000000000e+002 ..... <CR>

... next comes boundary conditions ... etc ...

now look for the GK_COOR - flag
here's the offset of your mesh to real world

GK_COOR
4545455.000000, 5800000.000000 -... or something like this

... if you have 3D Mesh search next for ELEV_I - flag ...

ELEV_I
1.00000000000000e+002 1-5573 (constant elevation for first slice)
2 (second slice ...
9.50000000000000e+001 1-100
9.50000000000000e+001 100-5570 (nonequal elevations
9.50000000000000e+001 5571 (nonequal elevations
9.50000000000000e+001 5572 (nonequal elevations
9.50000000000000e+001 5573 (nonequal elevations
(you may define one elevation per node, even if equal elevations,
FEFLOW doc sayes,the elevation values have to be sorted -
i checked it without sorting - FEFLOW will do the sorting work for you)
3 (third slice ...
8.00000000000000e+001 1-5573
4
7.00000000000000e+001 1-5573
.......

Hope this helps,
Thomas

--- In feflow@..., Giovanni <g.firmani@...> wrote:
>
> Dear all,
>
> Is there anybody who can help me to import a mesh in FEFLOW?
> I had previously generated a mesh with another program and now I would
> like to import it with FEFLOW.
>
> Thank you for your help
>
> Giovanni
>