-
Notifications
You must be signed in to change notification settings - Fork 1
/
usecases_dev.html
117 lines (111 loc) · 4.82 KB
/
usecases_dev.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
// BIDDSAT - BIoDiversity DataSet Assessment Tool
// Copyright (C) 2012 Javier Otegui
// This file is part of BIDDSAT.
// BIDDSAT is free software: you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
// BIDDSAT is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU General Public License for more details.
// You should have received a copy of the GNU General Public License
// along with BIDDSAT. If not, see <http://www.gnu.org/licenses/>.
// Contact: javier.otegui@gmail.com
-->
<html>
<head>
<title>BIDDSAT: Biodiversity Datasets Assessment Tool</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<script src="./files/scripts.js" type="text/javascript"></script>
<!-- Imported from UNAV -->
<link rel="stylesheet" href="./files/style.css" type="text/css" />
<link rel="stylesheet" href="./files/interna_sin_anexo.css" type="text/css" />
<link rel="shortcut icon" href="http://www.unav.es/favicon.ico" />
<!-- End of import block -->
</head>
<body><div id="documento">
<div id="cabecera">
<!--<div id="foto-esquina"><div style="position:relative; z-index:1; width:100%;">
<img src="http://www.unav.es/evento/voluntarios-ambientales/files/slideshowmodule/interiores_ES/blanco_160_75.jpg" />
</div></div>-->
<div id="nombre-catedra">
<table>
<tr>
<td id="catedra-td">
<h1 id="catedra">
Biodiversity Datasets Assessment Tool
</h1>
<span id="fac">
<a href="http://www.unav.es/departamento/unzyec/" title="Dept. Zoology and Ecology">
DEPT. ZOOLOGY AND ECOLOGY
</a>
</span>
</td>
</tr>
</table>
</div>
<div id="logotipo"><a href="http://www.unav.es" title="Universidad de Navarra"><img src="http://www.unav.es/evento/voluntarios-ambientales/themes/unavcongresotheme/imagenes/marca-page.png" alt="Universidad de Navarra" /></a></div>
</div>
<p></p>
<h1>Use Cases</h1>
<p>We present some exemplar situations where these visualizations can help in detecting issues or biases in the key primary aspects of biodiversity data affecting part or entire collections.<p>
<ul>
<li>Geospatial issues</li>
<ul>
<li>Coordinate swap
</li>
<li>Coordinate imprecission
</li>
</ul>
</li>
<li>Temporal issues
<ul>
<li>Default values in mandatory fields
</li>
<li>Figure movement or dissappearing
</li>
</ul>
</li>
<li>Taxonomic issues
<ul>
<li>Unmappable kingdom values
</li>
<li>Wrong taxonomic hierarchy
</li>
</ul>
</li>
<li>Metadata issues
<ul>
<li>Potential of improvement
</li>
<li>Particular collections driving full publisher's data
</li>
</ul>
</li>
</ul>
<p><b><i>Page under construction</i></b>
<!--
<a href="#geoissues">asd</a>
-->
<a name="geoissues"><h2>Geospatial issues</h2></a>
<a name="coordswap"><h3>Coordinate swap</h3></a>
Coordinate swaps happen when latitude value is inserted in the longitude field and vice versa. This type of geospatial issue is fairly easy to detect when the original record has its longitude absolute value larger than 90 (since it is impossible for a record to be taken at latitudes higher than 90 N/S). But it becomes trickier when both values (latitude and longitude) are smaller than 90. In this case, a generic record-by-record check would not detect the problem, but when the full collection is represented with a density map, the wrong records stand out of the rest of the potentially clean records. Then, detecting the records in the owner's database is easy: it is enough with selecting those who fall inside a bounding box with negative latitude and positive longitude. See image below:<p>
<img src="./files/visualizations/CoordinateSwap.png" width="100%">
<a name="coordimprec"><h3>Coordinate imprecission</h3></a>
Sometimes<p>
<img src="./files/visualizations/LowPrecision.jpg" width="100%">
<a name="tempoissues"><h2>Temporal issues</h2></a>
<a name="defval"><h3>Default values in mandatory fields</h3></a>
<a name="figmov"><h3>Figure movement (197 instead of 1975)</h3></a>
<a name="taxoissues"><h2>Taxonomic issues</h2></a>
<a name="noking"><h3>Unmappable kingdom values</h3></a>
<a name="badtax"><h3>Wrong taxonomic hierarchy</h3></a>
<a name="metaissues"><h2>Metadata</h2></a>
<a name="improv"><h3>Potential of improvement</h3></a>
<a name="bigcols"><h3>Particular collections driving full publisher's data</h3></a>
<hr>
<input type="button" value="Back" onclick="window.location='index.html'"><p></p>
</body></html>