<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">79561</controlfield>
        <controlfield tag="005">20191212102140.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="2">doi</subfield>
            <subfield code="a">10.1007/s12518-018-0235-1</subfield>
        </datafield>
        <datafield tag="024" ind1="8" ind2=" ">
            <subfield code="2">sideral</subfield>
            <subfield code="a">108401</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">ART-2018-108401</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">eng</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="a">Prevital, Mattia</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">A brokered virtual hub approach for the generation of web applications based on historical maps</subfield>
        </datafield>
        <datafield tag="260" ind1=" " ind2=" ">
            <subfield code="c">2018</subfield>
        </datafield>
        <datafield tag="506" ind1="0" ind2=" ">
            <subfield code="a">Access copy available to the general public</subfield>
            <subfield code="f">Unrestricted</subfield>
        </datafield>
        <datafield tag="520" ind1="3" ind2=" ">
            <subfield code="a">Integration between historical maps and current cartography is nowadays recognized of primary importance in many applications (e.g. urban planning, landscape valorisation and preservation, land changes identification). However, due to large variety in Geographical Information (GI) standards and interfaces for data publishing, some technical issues arise for developers when integrating different data for the generation of new web-based applications. In addition, information overload makes difficult their discovery and management: without knowing the specific repository where the data are stored, it is difficult to find the information required. To partially cope with those problems, this paper describes a new brokering-based approach for the generation of web applications based on multi-temporal GI data gathered from different providers. In particular, this new approach is exemplified by a couple of new web applications built on top of the developed solution. Even if the two applications deal both with historical maps, they present significant differences in technical (e.g. libraries, development environment, data formats) and non-technical (e.g. user addressed, user requirements) aspects showing the flexibility of the solution.</subfield>
        </datafield>
        <datafield tag="540" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
            <subfield code="a">by-nc-nd</subfield>
            <subfield code="u">http://creativecommons.org/licenses/by-nc-nd/3.0/es/</subfield>
        </datafield>
        <datafield tag="592" ind1=" " ind2=" ">
            <subfield code="a">0.296</subfield>
            <subfield code="b">2018</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Earth and Planetary Sciences (miscellaneous)</subfield>
            <subfield code="c">2018</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Geography, Planning and Development</subfield>
            <subfield code="c">2018</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Environmental Science (miscellaneous)</subfield>
            <subfield code="c">2018</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Engineering (miscellaneous)</subfield>
            <subfield code="c">2018</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="655" ind1=" " ind2="4">
            <subfield code="a">info:eu-repo/semantics/article</subfield>
            <subfield code="v">info:eu-repo/semantics/publishedVersion</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0002-6682-8383</subfield>
            <subfield code="a">Latre, Miguel Ángel</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="710" ind1="2" ind2=" ">
            <subfield code="1">5007</subfield>
            <subfield code="2">570</subfield>
            <subfield code="a">Universidad de Zaragoza</subfield>
            <subfield code="b">Dpto. Informát.Ingenie.Sistms.</subfield>
            <subfield code="c">Área Lenguajes y Sistemas Inf.</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="g">10, 4 (2018), 453–472</subfield>
            <subfield code="p">Appl. geomat.</subfield>
            <subfield code="t">Applied geomatics</subfield>
            <subfield code="x">1866-9298</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">5751394</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/79561/files/texto_completo.pdf</subfield>
            <subfield code="y">Versión publicada</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">9886</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/79561/files/texto_completo.jpg?subformat=icon</subfield>
            <subfield code="x">icon</subfield>
            <subfield code="y">Versión publicada</subfield>
        </datafield>
        <datafield tag="909" ind1="C" ind2="O">
            <subfield code="o">oai:zaguan.unizar.es:79561</subfield>
            <subfield code="p">articulos</subfield>
            <subfield code="p">driver</subfield>
        </datafield>
        <datafield tag="951" ind1=" " ind2=" ">
            <subfield code="a">2019-12-12-10:11:48</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">ARTICLE</subfield>
        </datafield>
    </record>

    
</collection>