<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">1811</controlfield>
  <controlfield tag="005">20160926141212.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="a">10.1029/2016EO044499</subfield>
    <subfield code="2">DOI</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">SCART-2016-0005</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Van Noten, Koen</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Visualizing Cross-Sectional Data in a Real-World Context</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2016</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">If you could fly around your research results in three dimensions, wouldn’t you like to do it? Visualizing research results properly during scientific presentations already does half the job of informing the public on the geographic framework of your research. Many scientists use Google Earth mapping service because it’s a great interactive mapping tool for assigning geographic coordinates to individual data points, localizing a research area, and draping maps of results over Earth’s surface for displaying the results in three dimensions. Yet scientists often do not fully explore the Google Earth™ platform. Visualizations of research results in vertical cross sections through these maps are often not shown at the same time as the maps. However, a few tutorials to display cross-sectional data in Google Earth do exist, and the workflow is rather simple. By importing cross-sectional data into in the open software SketchUp Make, any spatial model displaying research results can be exported to a vertical figure in Google Earth. Here I explain an easy workflow, give some tips, show a tutorial and discuss some of the endless applications of the method. This workflow will give your research results better spatial visibility and allows more dynamic scientific presentations during your next conference.</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="a">FNRS PDR T.0116.14/</subfield>
    <subfield code="c">FNRS PDR T.0116.14/</subfield>
    <subfield code="f">FNRS PDR T.0116.14</subfield>
  </datafield>
  <datafield tag="594" ind1=" " ind2=" ">
    <subfield code="a">NO</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">Science Visualization</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">Google Earth</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">Tutorial</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="p">EOS, Transactions AGU</subfield>
    <subfield code="v">97</subfield>
    <subfield code="y">2016</subfield>
    <subfield code="c">16-19</subfield>
  </datafield>
  <datafield tag="856" ind1="0" ind2=" ">
    <subfield code="f">koen.vannoten@observatoire.be</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="2">
    <subfield code="a">https://eos.org/project-updates/visualizing-cross-sectional-data-in-a-real-world-context</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">714626</subfield>
    <subfield code="u">http://publi2-as.oma.be/record/1811/files/VanNoten2016-EOS97.pdf</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">3155</subfield>
    <subfield code="u">http://publi2-as.oma.be/record/1811/files/VanNoten2016-EOS97.gif?subformat=icon</subfield>
    <subfield code="x">icon</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">4839</subfield>
    <subfield code="u">http://publi2-as.oma.be/record/1811/files/VanNoten2016-EOS97.jpg?subformat=icon-180</subfield>
    <subfield code="x">icon-180</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
    <subfield code="a">published in</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">REFERD</subfield>
  </datafield>
</record>
</collection>