<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">445365056</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180317142927.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170323e20110301xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/s11001-011-9137-x</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/s11001-011-9137-x</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Dyer</subfield>
   <subfield code="D">Julie</subfield>
   <subfield code="u">Acergy, Tarland Road, AB32 6JZ, Westhill, Aberdeen, UK</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">Geohazard identification: the gap between the possible and reality in geophysical surveys for the engineering industry</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Julie Dyer]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">Offshore Contractors engaged in the business of installing pipelines and subsea structures routinely rely on third party survey data to identify and assess the risk of surface and buried geohazards. In many cases, route or site survey data are supplied to a marine Contractor with the latter having little or no input to the manner in which the geophysical and geotechnical data are acquired, processed and reported. Often, the completed survey reports indicate that neither data acquisition nor the subsequent data processing were carried out with the ultimate goal of the survey or the end user in mind. This lack of focus at the survey stage can contribute to incorrect or over-optimistic assessments of geohazard risk, with serious impact on offshore installation operations as a consequence. Two case studies from the North Sea are discussed where inappropriate data processing and reporting of geophysical data had a negative impact on offshore installation operations; these are used as a basis for a more general discussion of the underlying reasons for the production of engineering survey reports which are &quot;not-fit-for-purpose”.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer Science+Business Media B.V., 2011</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Geohazards</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Geophysical route surveys</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Offshore engineering</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Data quality</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Marine Geophysical Research</subfield>
   <subfield code="d">Springer Netherlands</subfield>
   <subfield code="g">32/1-2(2011-03-01), 37-47</subfield>
   <subfield code="x">0025-3235</subfield>
   <subfield code="q">32:1-2&lt;37</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">32</subfield>
   <subfield code="o">11001</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/s11001-011-9137-x</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/s11001-011-9137-x</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">100</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Dyer</subfield>
   <subfield code="D">Julie</subfield>
   <subfield code="u">Acergy, Tarland Road, AB32 6JZ, Westhill, Aberdeen, UK</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Marine Geophysical Research</subfield>
   <subfield code="d">Springer Netherlands</subfield>
   <subfield code="g">32/1-2(2011-03-01), 37-47</subfield>
   <subfield code="x">0025-3235</subfield>
   <subfield code="q">32:1-2&lt;37</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">32</subfield>
   <subfield code="o">11001</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
