<?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>02452nmc a2200241   4500</leader>
  <controlfield tag="005">20260524145545.0</controlfield>
  <controlfield tag="008">260224s2014                             </controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">BAAB</subfield>
  </datafield>
  <datafield tag="082" ind1=" " ind2=" ">
    <subfield code="a">CD I116 64 0015466</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Chammaa, Leandro</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Carmona, Daniel</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Ribera, Nora</subfield>
  </datafield>
  <datafield tag="111" ind1="2" ind2=" ">
    <subfield code="a">Congreso de Exploraci&#xF3;n y Desarrollo de Hidrocarburos (9no. : 2014 nov. 3-7 : Mendoza)</subfield>
  </datafield>
  <datafield tag="111" ind1="2" ind2=" ">
    <subfield code="a">Jornadas de Geotecnolog&#xED;a (5tas. : 2014 nov. 3-7 : Mendoza)</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Estrategia e implementaci&#xF3;n de soluciones SIG en yacimientos del sur</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Buenos Aires</subfield>
    <subfield code="b">Instituto Argentino del Petr&#xF3;leo y del Gas, IAPG</subfield>
    <subfield code="c">2014</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">15/05/2020 ; 14/02/2017</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">20 p.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">GIS can be used in any industry where information has a geospatial component, but it is especially useful in the petroleum industry, which is map driven. As part of the geoscience workflow, GIS is an valuable tool for quickly and dynamically solving complex spatial problems. Initially, the use of GIS was by a small group of trained "geotechonologists" who knew the details of making maps and how to manage spatial data. Sharing GIS resources within this small group was fairly easy. However, as more and more people began using GIS, these departmental workflows proved too limiting to scale across the entire organization. Problems with finding data, data inconsistency, and difficulty in sharing maps forced us to develop ways to more effectively deliver GIS resources. Our solution is an enterprise GIS that stores geographic data in a central repository and provides seamless access using desktop and web-based tools. In this presentation, we cover our technical approach to disseminating GIS resources to all of our operations using an enterprise GIS architecture. This architecture includes a centralized repository of spatial data, deployment of desktop GIS using Citrix, and an intranet website for accessing resources called the YSur GeoPortal(2). We also highlight how this architecture has been deployed in our country to allow users to find and open pre-built maps, publish their own content to share with others, and run various workflows for land/lease, permitting, and exploration using an easy-to-use web-based map viewer.</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://biblioteca.iapg.org.ar/ArchivosAdjuntos/CONEXPLOR2014/JornadasDeGeotecnolog&#xED;a/94Estrategiaeimplementacion.pdf</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CONGTP</subfield>
  </datafield>
  <datafield tag="945" ind1=" " ind2=" ">
    <subfield code="a">Dominguez, Silvia</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">190040</subfield>
    <subfield code="d">190040</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">CD I116 64 0015466</subfield>
    <subfield code="p">200062287</subfield>
    <subfield code="r">2026-03-06 00:20:10</subfield>
    <subfield code="y">ARCHIVO</subfield>
  </datafield>
</record>
