/
g.gui.metadata.html
133 lines (100 loc) · 5.37 KB
/
g.gui.metadata.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
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
<h2>DESCRIPTION</h2>
<em>g.gui.metadata</em> supports advanced tools for metadata management according
to <a href="http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020">ISO 19115</a>.
<p>
The metadata editor includes a graphical interface for converting metadata
from r.info and v.info into ISO based metadata, editing metadata files and
creating metadata templates. In addition, the graphical module allows validating
INSPIRE and GRASS Basic profile.
<h2>NOTES</h2>
For dependencies and installation instructions see the dedicated
<a href="http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support">wiki page</a>.
<h3>Naming of metadata files and storage</h3>
Default location for exported metadata files is the <i>metadata</i> directory
in the map's mapset. For raster maps, the prefix derived from the current
nomenclature is <em>raster</em>, and for vector maps <em>vector</em>. The files
end with <em>.xml</em> extension.
<p>
For example, default metadata file name for the vector map "roads"
is <em>vector_roads.xml</em>.
<h3>Metadata profile</h3>
The <i>basic</i> profile is substituted from intersection between
items stored in GRASS native metadata format and INSPIRE profile. The
intersect (subset) includes all available GRASS metadata. Metadata
which cannot be assigned to ISO based attributes are stored in
metadata attribute <em>abstract</em>. The <i>inspire</i> profile
fulfills the criteria of INSPIRE profile. Values that cannot be read from
native GRASS metadata are filled by the text string <tt>'$NULL'</tt>.
This rule applies for both profiles.
<h4>Profile for temporal dataset</h4>
This function is based on t.info.iso which allows to create ISO based metadata
for temporal maps. Product of this function cannot be compiled by INSPIRE profile
because an additional attribute from ISO 19115 package have been added.
<!-- have or have not? -->
<h3>Creation of metadata</h3>
The editor offers two editing modes. The first one allows to create metadata
from selected GRASS maps from an active location. The second one allows editing
of an external metadata file.
<h4>Metadata editor for spatial and temporal maps</h4>
The basis of this editor is similar to r|v.info.iso. After the selection of the
map, the editor converts native metadata of map to ISO based metadata.
By exported xml file is metadata editor initialized.
<!-- This last sentence is not clear-->
There are three options to select:
<b>basic</b>, <b>inspire</b> or <b>load custom</b>. The last one allows to load
a metadata profile from a file, for example in the case of using a predefined
template. The intersection of GRASS Basic profile (all the available metadata
for the selected map) and loaded custom profile will proceed with this selection.
<!-- This last sentence is not clear-->
<h4> External metadata editor</h4>
This editor mode allows to load user own templates and xml files for editing.
This option does not support any connection with GRASS maps metadata.
<h3>Defining templates</h3>
<p>
This function allows to create pattern of metadata profile. In other words it
supports defining fixed values to template. When using created template, the
editor does not initialize texts inputs of defined values. These attributes are
only visible in the Tree Browser in the editor. Direct link on this function is
multiple editing mode (see below).
<p>
If the check-box of metadata attribute is checked, the OWSLib object in the
template will be replaced by value. Unchecked attributes will not change this
'part' of the template.
<p>
The yellow background of the text fields indicates metadata attributes that
cannot be read from GRASS map information.
<h3>Editing metadata of multiple map selection</h3>
This option can be used by selecting multiple maps in the data catalog. It is
possible to use predifined templates with this editing mode.
<!--To use pre-defined template for this editing mode is suitable-->
<h3>Validation of metadata profile </h3>
On the right side of editor there is a validator of metadata. Currently,
validator is able to validate two build-in profiles.
<!--For selection of profile “Load custom” is set by default the inspire profile.-->
<h3>Updating GRASS native metadata </h3>
The g.gui.metadata module allows to update native GRASS metadata with the
modules r.support and v.support. The intersection between ISO based metadata
and r|v.support is limited by the available parameters for these modules.
<h3>Creating reports for GRASS maps in PDF format</h3>
This function allows to automatically generate metadata reports as PDF documents.
Missing values are replaced by "Unknown" string.
<h2>SEE ALSO</h2>
<em>
<a href="https://grass.osgeo.org/grass-stable/manuals/r.info.html">r.info</a>,
<a href="v.info.iso.html">v.info.iso</a>,
<a href="g.gui.metadata.html">g.gui.metadata</a>
<a href="db.csw.harvest">db.csw.harvest</a>
<a href="db.csw.admin">db.csw.admin</a>
<a href="db.csw.run">db.csw.run</a>
</em>
<p>
See also related <a href="http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support">wiki page</a>.
<h2>AUTHOR</h2>
Matej Krejci, <a href="http://geo.fsv.cvut.cz/gwiki/osgeorel">OSGeoREL</a>
at the Czech Technical University in Prague, developed
during <a href="http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS">Google
Summer of Code 2014</a> (mentors: Margherita Di Leo, Martin Landa)
<!--
<p>
<i>Last changed: $Date$</i>
-->