Inputting CPT data without oriëntation

[MerelMoons]

Hello,
I would like to create a geological model using CPT data. This data is in a CSV file and consists of the following: formation, x, y and z.
I don't have orientations for the layers. Having looked at previous questions, I know it is possible to create a model without orientation, but I can't figure this out.

Can anyone help me with this?
Thank you!

[javoha]

Hello @MerelMoons,

thanks for your question. I am not sure which other questions you mean but it is not possible to create a gempy model without orientations. You can however set simple orientations (e.g facing upwards) for a model that is roughly planar.

Maybe take a look at the new video tutorial series for more information on how to format these files.

There are also ways to calculate orientations from your surface point data but that really depends on your specific setting and available data.

Cheers,
jan

[MerelMoons]

Thank you for the quick response!
I've watched all the tutorials currently available and also all the examples available but I can't figure out how to add these orientations (facing upwards). Could you give more information on this?

I am currently following this example:
https://docs.gempy.org/examples/real/mik.html#sphx-glr-download-examples-real-mik-py

In fact, this is exactly what I want to achieve. But there is an error every time I read my local csv file (Borealis.csv) in the first part:

collar_df: pd.DataFrame = read_collar(
GenericReaderFilesHelper(
file_or_buffer=raw_borehole_data_csv,
index_col="name",
usecols=['x', 'y', 'altitude', "name"],
columns_map={
"name": "id", # ? Index name is not mapped
"X": "x",
"Y": "y",
"altitude": "z"
}
)
).

The usecols I use are: ['CPT', 'X', 'Y', 'mTAW_top']

(note: mTAW is the height model of Belgium, measured opposite a fixed reference point near the coast).

Do you have any idea why this is so?

Thank you!

[javoha]

Ok so this is maybe a different problem. Let's split this.

A) In GemPy you define orientations using the formats explained in the videos. Here is an example of a file using azimuth, dip and polarity notation but you can alternatively also use pole vectors witht he columns G_x, G_y and G_z.

B) The example you linked is actually not a pure gempy example. The read_collar function that breaks for you is part of the subsurface package and I do not now this well enough to tell you where the issue is. It would probably make more sense to ask this question on their github: https://github.com/softwareunderground/subsurface

Cheers,
Jan