<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">136104</controlfield>
  <controlfield tag="005">20260218073539.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1080/13658816.2024.2361274</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">138970</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2024-138970</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="0">(orcid)0000-0003-0287-9488</subfield>
    <subfield code="a">Martín-Segura, S.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">An empirical study of the limitations of minimum bounding boxes for defining the extent of geospatial resources: the use of DGGS and other alternatives for improving the performance of spatial searches</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2024</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">A Minimum Bounding Box (MBB) is a rectangle which bounds a geographic feature or dataset. It is commonly used in spatial information systems as a simplified way of describing the spatial extent of a resource. MBBs are typically indexed for searching and discovering resources relevant to a given geographic area of interest. However, this simplification leads to a loss of precision in the description of the extent and can affect the overall precision of the search results. We propose an alternative technique for describing the spatial extent based on the use of DGGS tiles. To measure the precision improvements offered by our method, we designed and implemented an empirical method for evaluating the average precision, and applied it to three different systems: one based on MBB, another on Convex Hull, and ours based on DGGS. The three methods were evaluated with the same test collection obtained from some of the main European geospatial data catalogues compliant with the INSPIRE directive. The results showed that our method outperformed the other two. Where the catalogue average precision of the MBB search scenarios is between 73% and 97%, the DGGS is between 96% and 99%. Additionally, we propose a realistic method of transitioning from the current technologies to the technology we are proposing, considering the current state of the spatial data infrastructures.</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/grantAgreement/ES/AEI/PID2020-113353RB-I00</subfield>
    <subfield code="9">info:eu-repo/grantAgreement/ES/DGA/T59-23R</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
    <subfield code="a">by-nc</subfield>
    <subfield code="u">https://creativecommons.org/licenses/by-nc/4.0/deed.es</subfield>
  </datafield>
  <datafield tag="590" ind1=" " ind2=" ">
    <subfield code="a">5.1</subfield>
    <subfield code="b">2024</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">COMPUTER SCIENCE, INFORMATION SYSTEMS</subfield>
    <subfield code="b">48 / 258 = 0.186</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">GEOGRAPHY, PHYSICAL</subfield>
    <subfield code="b">9 / 67 = 0.134</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">INFORMATION SCIENCE &amp; LIBRARY SCIENCE</subfield>
    <subfield code="b">21 / 166 = 0.127</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">GEOGRAPHY</subfield>
    <subfield code="b">12 / 174 = 0.069</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="592" ind1=" " ind2=" ">
    <subfield code="a">1.502</subfield>
    <subfield code="b">2024</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Geography, Planning and Development</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Library and Information Sciences</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Information Systems</subfield>
    <subfield code="c">2024</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="594" ind1=" " ind2=" ">
    <subfield code="a">11.2</subfield>
    <subfield code="b">2024</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="4">
    <subfield code="a">info:eu-repo/semantics/article</subfield>
    <subfield code="v">info:eu-repo/semantics/acceptedVersion</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="0">(orcid)0000-0001-6491-7430</subfield>
    <subfield code="a">López-Pellicer, F. J.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="0">(orcid)0000-0001-7866-3793</subfield>
    <subfield code="a">Béjar, R.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="0">(orcid)0000-0002-1279-0367</subfield>
    <subfield code="a">Nogueras-Iso, J.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="0">(orcid)0000-0002-6557-2494</subfield>
    <subfield code="a">Zarazaga-Soria, F. J</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">38, 10 (2024), 2019-2038</subfield>
    <subfield code="p">Int. j. geogr. inf. sci.</subfield>
    <subfield code="t">INTERNATIONAL JOURNAL OF GEOGRAPHICAL INFORMATION SCIENCE</subfield>
    <subfield code="x">1365-8816</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">3232099</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/136104/files/texto_completo.pdf</subfield>
    <subfield code="y">Postprint</subfield>
    <subfield code="z">info:eu-repo/date/embargoEnd/2025-06-05</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">1796369</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/136104/files/texto_completo.jpg?subformat=icon</subfield>
    <subfield code="x">icon</subfield>
    <subfield code="y">Postprint</subfield>
    <subfield code="z">info:eu-repo/date/embargoEnd/2025-06-05</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="o">oai:zaguan.unizar.es:136104</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2026-02-17-20:39:48</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>