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
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
|
<!DOCTYPE html>
<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Categorical Variables — HARP 1.5 documentation</title>
<link rel="stylesheet" href="../_static/css/theme.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<link rel="stylesheet" href="../_static/custom.css" type="text/css" />
<link rel="index" title="Index" href="../genindex.html" />
<link rel="next" title="Datetime values" href="datetime.html" />
<link rel="prev" title="Variable names" href="variable_names.html" />
<script src="../_static/js/modernizr.min.js"></script>
</head>
<body class="wy-body-for-nav">
<div class="wy-grid-for-nav">
<nav data-toggle="wy-nav-shift" class="wy-nav-side">
<div class="wy-side-scroll">
<div class="wy-side-nav-search">
<a href="../index.html" class="icon icon-home"> HARP
</a>
<div class="version">
1.5
</div>
</div>
<div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="../install.html">Installation</a></li>
<li class="toctree-l1 current"><a class="reference internal" href="index.html">Conventions</a><ul class="current">
<li class="toctree-l2"><a class="reference internal" href="datatypes.html">Data types</a></li>
<li class="toctree-l2"><a class="reference internal" href="dimensions.html">Dimensions</a></li>
<li class="toctree-l2"><a class="reference internal" href="global_attributes.html">Global attributes</a></li>
<li class="toctree-l2"><a class="reference internal" href="variable_attributes.html">Variable attributes</a></li>
<li class="toctree-l2"><a class="reference internal" href="variables.html">Variables</a></li>
<li class="toctree-l2"><a class="reference internal" href="variable_names.html">Variable names</a></li>
<li class="toctree-l2 current"><a class="current reference internal" href="#">Categorical Variables</a></li>
<li class="toctree-l2"><a class="reference internal" href="datetime.html">Datetime values</a></li>
<li class="toctree-l2"><a class="reference internal" href="filenames.html">File naming</a></li>
<li class="toctree-l2"><a class="reference internal" href="netcdf3.html">netCDF-3</a></li>
<li class="toctree-l2"><a class="reference internal" href="hdf4.html">HDF4</a></li>
<li class="toctree-l2"><a class="reference internal" href="hdf5.html">HDF5/netCDF-4</a></li>
<li class="toctree-l2"><a class="reference internal" href="compatibility.html">Compatibility with other standards</a></li>
<li class="toctree-l2"><a class="reference internal" href="collocation_result.html">Collocation result file</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../algorithms/index.html">Algorithms</a></li>
<li class="toctree-l1"><a class="reference internal" href="../operations.html">Operations</a></li>
<li class="toctree-l1"><a class="reference internal" href="../ingestions/index.html">Ingestion definitions</a></li>
<li class="toctree-l1"><a class="reference internal" href="../libharp.html">C library</a></li>
<li class="toctree-l1"><a class="reference internal" href="../idl.html">IDL interface</a></li>
<li class="toctree-l1"><a class="reference internal" href="../matlab.html">MATLAB interface</a></li>
<li class="toctree-l1"><a class="reference internal" href="../python.html">Python interface</a></li>
<li class="toctree-l1"><a class="reference internal" href="../tools.html">Command line tools</a></li>
</ul>
</div>
</div>
</nav>
<section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
<nav class="wy-nav-top" aria-label="top navigation">
<i data-toggle="wy-nav-top" class="fa fa-bars"></i>
<a href="../index.html">HARP</a>
</nav>
<div class="wy-nav-content">
<div class="rst-content">
<div role="navigation" aria-label="breadcrumbs navigation">
<ul class="wy-breadcrumbs">
<li><a href="../index.html">Docs</a> »</li>
<li><a href="index.html">Conventions</a> »</li>
<li>Categorical Variables</li>
<li class="wy-breadcrumbs-aside">
</li>
</ul>
<hr/>
</div>
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div itemprop="articleBody">
<div class="section" id="categorical-variables">
<h1>Categorical Variables</h1>
<p>HARP has special support for categorical variables, which are variables that can be represented by an enumeration type.</p>
<p>Categorical variables are represented in HARP using integer data types that provide an index into a fixed list of
enumeration labels. These enumeration labels are stored as metadata together with a variable. For <code class="docutils literal notranslate"><span class="pre">int8</span></code> data the
labels are stored as a <code class="docutils literal notranslate"><span class="pre">flag_meanings</span></code> attribute (together with a <code class="docutils literal notranslate"><span class="pre">flag_values</span></code> attribute) in netCDF3, HDF4, and
HDF5 files.</p>
<p>HARP does not impose a rule on which integer value maps to a specific enumeration label. The integer values are
just plain indices into the enumeration label list, and the list can be sorted in any way.</p>
<p>Any integer value in a categorical variable that is outside the range of the available enumeration labels
(<code class="docutils literal notranslate"><span class="pre">value</span> <span class="pre"><</span> <span class="pre">0</span></code> or <code class="docutils literal notranslate"><span class="pre">value</span> <span class="pre">>=</span> <span class="pre">N</span></code>) will be treated as an invalid value (<code class="docutils literal notranslate"><span class="pre">valid_min</span></code> and <code class="docutils literal notranslate"><span class="pre">valid_max</span></code> should therefore
always be set to <code class="docutils literal notranslate"><span class="pre">0</span></code> and <code class="docutils literal notranslate"><span class="pre">N-1</span></code> respectively for these variables). Invalid values are represented by an empty string
as label.</p>
<p>Operations in HARP on categorical variables will need to primarily use the enumeration label <cite>names</cite>
(and not the <cite>integer values</cite>). Any standardization (such as for the variable names) on the categories for
categorical variables in HARP will thus only be on enumeration names and not on their numbers.</p>
<p>In HARP we distinguish category types and category values. The name of the category type <code class="docutils literal notranslate"><span class="pre"><cattype></span></code> is used in the
variable name and the names of the category values <code class="docutils literal notranslate"><span class="pre"><catval></span></code> are the enumeration labels. Variables for category
types should generally be called <code class="docutils literal notranslate"><span class="pre"><cattype>_type</span></code>. For instance, if we want to classify clouds we would have
<code class="docutils literal notranslate"><span class="pre"><cattype>=cloud</span></code> and a variable name <code class="docutils literal notranslate"><span class="pre">cloud_type</span></code>, and for land use classification we would have <code class="docutils literal notranslate"><span class="pre">land_type</span></code>.</p>
<p>The enumeration labels for a variable should ideally be fully distinct categories. This means that if you have land
types <code class="docutils literal notranslate"><span class="pre">A</span></code>, <code class="docutils literal notranslate"><span class="pre">B</span></code>, and <code class="docutils literal notranslate"><span class="pre">C</span></code>, you should try to avoid also having land types for <code class="docutils literal notranslate"><span class="pre">A_and_B</span></code>, <code class="docutils literal notranslate"><span class="pre">B_and_C</span></code>,
<code class="docutils literal notranslate"><span class="pre">A_and_B_and_C</span></code>, etc.
A <code class="docutils literal notranslate"><span class="pre"><cattype>_type</span></code> variable should ideally indicate just a single dominant applicable category.
To deal with mixed presence of multiple categories one can use variables such as <code class="docutils literal notranslate"><span class="pre"><catval>_flag</span></code> and
<code class="docutils literal notranslate"><span class="pre"><catval>_fraction</span></code>.</p>
<p>For instance, for a <code class="docutils literal notranslate"><span class="pre">land_type</span></code> variable we could have <code class="docutils literal notranslate"><span class="pre">forest</span></code> as enumeration label, but then also have variables
<code class="docutils literal notranslate"><span class="pre">forest_flag</span></code> and <code class="docutils literal notranslate"><span class="pre">forest_fraction</span></code>.</p>
<p>A <code class="docutils literal notranslate"><span class="pre"><catval>_flag</span></code> variable in HARP should always be a binary/dichotomous variable (it should contain true/false, 1/0
values). A flag variable denotes whether something is present/applicable/true or not. A flag variable will therefore
generally always have an <code class="docutils literal notranslate"><span class="pre">int8</span></code> data type and is not treated as categorical variable (i.e. it will not have
enumeration labels). Important to note is that <code class="docutils literal notranslate"><span class="pre"><*>_flag</span></code> variables in HARP should not be used as bitfield variables
(unlike the <code class="docutils literal notranslate"><span class="pre"><*>_validity</span></code> variables).</p>
<p>A <code class="docutils literal notranslate"><span class="pre"><catval>_fraction</span></code> variable can be used to define the fraction of the area that has the given <code class="docutils literal notranslate"><span class="pre"><catval></span></code>
classification. This fraction is a floating point value between 0 and 1.</p>
<p>Note that many other data product formats use bitfields to indicate applicability of multiple classification categories
in order to save storage space. However, the aim of HARP is not to provide a compact data format, but to have data
variables that can be readily used by algorithms. For this reason, combining multiple information elements in a single
variable is discouraged within the HARP conventions.</p>
</div>
</div>
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
<a href="datetime.html" class="btn btn-neutral float-right" title="Datetime values" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right"></span></a>
<a href="variable_names.html" class="btn btn-neutral" title="Variable names" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left"></span> Previous</a>
</div>
<hr/>
<div role="contentinfo">
<p>
© Copyright 2015-2018 S&T, The Netherlands
</p>
</div>
</footer>
</div>
</div>
</section>
</div>
<script type="text/javascript" id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<script async="async" type="text/javascript" src="/usr/share/javascript/mathjax/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
<script type="text/javascript" src="../_static/js/theme.js"></script>
<script type="text/javascript">
jQuery(function () {
SphinxRtdTheme.Navigation.enable(true);
});
</script>
</body>
</html>
|
