[OpendTect_Users] Mapping horizons across thrust faults 'MANUALLY'

[Dirk Nieuwland]

Dear All, 

This problem exists as long as mapping in fold and thrust belts exists (decades).
In handdrawn maps one could use a hatching for the overthrusted zone, in interpretation software this is not possible and would not look nice.
Until now the best practical solution is to name the upthrown and downthrown elements slightly different, for example by adding 'U' and 'D' to respectively the Upthrown and Downthrown unit (e.g. unit-U and unit-D). The underthrown unit is now normally not visible in the overthrusted section.
In situations where it is desirable to see the underthrusted unit it can be chosen to do so.

Regards, Dirk

Dirk Nieuwland
Geo-mechanics and seismicity advisor, TAQA Energy B.V.



-----Original Message-----
From: users-bounces at opendtect.org on behalf of Colin Hawke
Sent: Wed 5/22/2013 4:11 PM
To: Gery .; Muslim Aminu; OPENDTECT USERS
Subject: Re: [OpendTect_Users] Mapping horizons across thrust faults 'MANUALLY'
 
Interpretation of horizons across thrust faults are multi-Z valued. So for any one position at the fault you have two or more values for the interpreted surface. Typically software that does this treats surfaces as meshes (tessellated surfaces) which can be multi-Z valued - I believe opendtect doesn't support this (yet).


From: gamejihou at hotmail.com
To: muslimaminu at ymail.com; users at opendtect.org
Date: Wed, 22 May 2013 10:45:05 +0000
Subject: Re: [OpendTect_Users] Mapping horizons across thrust faults 'MANUALLY'




Hello,

If I understand correctly, you need to draw manually the thrust fault and then extract the Z (time I think) of that fault?


__________________________________________________________________________________________
Piensa en el medio ambiente - mantenlo en la pantalla. NO lo imprimas si NO es necesario.
Think green - keep it on the screen. Do NOT print if it is NOT necessary.
Denken Sie an die Umwelt - bewahren Sie es auf dem Bildschirm. Drucken Sie es NICHT, wenn es NICHT notwendig ist.


Date: Wed, 22 May 2013 01:02:40 -0700
From: muslimaminu at yahoo.com
To: users at opendtect.org
Subject: [OpendTect_Users] Mapping horizons across thrust faults 'MANUALLY'


Hello all,
I need help on mapping horizons across thrust faults. It is expected the horizon will have a Z shape across the fault but i can't get opendtect to do that. I've searched the help files perhaps i'm missing something. The software just re-interprets earlier picks say on the upthrown block as though it can only recognize normal faults.  
_______________________________________________
Users mailing list
Users at opendtect.org
http://lists.opendtect.org/mailman/listinfo/users

You receive this mail because you are listed on users at opendtect.org To unsubscribe please go to http://lists.opendtect.org/mailman/options/users or click here : http://lists.opendtect.org/mailman/options/users/gamejihou%40hotmail.com . If you encounter any problems, please contact support at opendtect.org . 		 	   		  

_______________________________________________
Users mailing list
Users at opendtect.org
http://lists.opendtect.org/mailman/listinfo/users

You receive this mail because you are listed on users at opendtect.org To unsubscribe please go to http://lists.opendtect.org/mailman/options/users or click here : http://lists.opendtect.org/mailman/options/users/colinhawke%40predictgeo.com . If you encounter any problems, please contact support at opendtect.org . 		 	   		  




The information contained in this communication is confidential, may be
attorney-client privileged, and is intended only for the use of the addressee. 
It is the property of Abu Dhabi National Energy Company PJSC (TAQA) or one
of its affiliates. Unauthorized use, disclosure or copying of this 
communication or any part thereof is strictly prohibited and may be unlawful. If
you have received this communication in error, please notify me immediately by
return email and destroy this communication and all copies thereof, including
attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendtect.org/pipermail/users/attachments/20130522/0dc8c3a0/attachment.html>