StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POComputation of fault interpretation and polyline intersections
primarykey
Id
8323320
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-30T08:59:08.477
FavoriteCount
0
LastActivityDate
2011-12-22T19:52:20.423
LastEditDate
LastEditorUserId
0
OwnerUserId
1039632
ParentId
0
PostTypeId
1
Score
0
ViewCount
99
LastEditorDisplayName
text
Body
<p>I am planning to make functionality that can test if a borehole is crossing a fault. My first idea was to make a workstep component that takes a Borehole and a Fault Interpretation as input and returns the number of intersections. I have already made a workstep that checks if a fault interpretation is intersecting a surface. The core of this function is the following:</p> <pre><code>ICoordinateReferenceSystem inputCRS = PetrelProject.PrimaryProject.CoordinateReferenceSystem; SpatialUnitsPolicy unitsPolicy = SpatialUnitsPolicy.AllDataInSI; SpatialContext spatialCtx = new SpatialContext(inputCRS, unitsPolicy); ISurfaceIntersectionService sis = CoreSystem.GetService<ISurfaceIntersectionService>(arguments.Surface); foreach (FaultInterpretationPolyline p in arguments.Fault.GetPolylines()) { IEnumerable<PolylineSurfaceIntersection> intersections = sis.GetSurfacePolyLineIntersection(arguments.Surface, p.Polyline); foreach (PolylineSurfaceIntersection intersection in intersections) { arguments.NumberOfIntersections++; } } </code></pre> <p>The above works fine and I was thinking I could make something along the same lines to compute the intersection between a polyline (well trajectory) and a surface generated from the collection of polylines representing the fault interpretation. The key question is, is there a way to get/generate a surface from a collection of polylines? The fault interpretation can be displayed as a surface (triangulated), is this surface accessible from the api? The surface returned from the api must be such that it can be used as an argument to ISurfaceIntersectionService. If this is not possible through the Ocean api, is there a way that the user could prepare the fault interpretation up front making surfaces from the fault interpretations? Or maybe there is a complete different approach to solve the above in an efficient way?</p>
Tags
<ocean>
Title
Computation of fault interpretation and polyline intersections
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRDM
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.