<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02401nab a2200217   4500</leader>
  <controlfield tag="005">20260520000314.0</controlfield>
  <controlfield tag="008">260224s2011    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">From outcrop to flow simulation: Constructing discrete fracture models from a LIDAR survey</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">nov. 2011</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">16/04/2012 ; 16/04/2012</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">23 p. ; 1883 - 1905</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Resumen del autor: Terrestrial light detection and ranging (LIDAR) surveys offer potential enrichment of outcrop-based research efforts to characterize fracture networks and assess their impact on subsurface fluid flow. Here, we explore two methods to extract the three-dimensional (3-D) positions of natural fractures from a LIDAR survey collected at a roadcut through the Cretaceous Austin Chalk: (1) a manual method using the University of California, Davis, Keck Center for Active Visualization in the Earth Sciences and (2) a semiautomated method based on mean normal and Gaussian curvature surface classification. Each extraction method captures the characteristic frequencies and orientations of the primary fracture sets that we identified in the field, yet they extract secondary fracture sets with varying ability. After making assumptions regarding fracture lengths and apertures, the extracted fractures served as a basis to construct a discrete fracture network (DFN) that agrees with field observations and a priori knowledge of fracture network systems. Using this DFN, we performed flow simulations for two hypothetical scenarios: with and without secondary fracture sets. The results of these two scenarios indicate that for this particular fracture network, secondary fracture sets marginally impact (~10% change) the breakthrough time of water injected into an oil-filled reservoir. Our work provides a prototype workflow that links outcrop fracture observations to 3-D DFN model flow simulations using LIDAR data, an approach that offers some improvement over traditional field-based DFN constructions. In addition, the techniques we used to extract fractures may prove applicable to other outcrop studies with different research goals</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">11</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">AAPG Bulletin</subfield>
    <subfield code="g">95</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Wilson, Christopher E.</subfield>
    <subfield code="9">51415</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Aydin, Atilla</subfield>
    <subfield code="9">13994</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Karimi-Fard, M.</subfield>
    <subfield code="9">20067</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Durlofsky, Louis J.</subfield>
    <subfield code="9">21214</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">187061</subfield>
    <subfield code="d">187061</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">254880</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200059166</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200059166</subfield>
    <subfield code="r">2026-03-06 00:16:40</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
