[GRASS-SVN] r61661 - in grass-addons/grass7/gui/wxpython/wx.metadata: g.gui.metadata r.info.iso v.info.iso
svn_grass at osgeo.org
svn_grass at osgeo.org
Fri Aug 15 23:32:28 PDT 2014
Author: krejcmat
Date: 2014-08-15 23:32:28 -0700 (Fri, 15 Aug 2014)
New Revision: 61661
Modified:
grass-addons/grass7/gui/wxpython/wx.metadata/g.gui.metadata/g.gui.metadata.html
grass-addons/grass7/gui/wxpython/wx.metadata/r.info.iso/r.info.iso.html
grass-addons/grass7/gui/wxpython/wx.metadata/v.info.iso/v.info.iso.html
Log:
further manual cosmetics
Modified: grass-addons/grass7/gui/wxpython/wx.metadata/g.gui.metadata/g.gui.metadata.html
===================================================================
--- grass-addons/grass7/gui/wxpython/wx.metadata/g.gui.metadata/g.gui.metadata.html 2014-08-15 21:27:43 UTC (rev 61660)
+++ grass-addons/grass7/gui/wxpython/wx.metadata/g.gui.metadata/g.gui.metadata.html 2014-08-16 06:32:28 UTC (rev 61661)
@@ -1,119 +1,87 @@
<h2>DESCRIPTION</h2>
-Metadata editor according to according
-to <a href="http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020">ISO
+<em>g.gui.metadata</em> support advanced tools for metadata management according to <a href="http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020">ISO
19115</a>.
+
<p>
Metadata editor includes graphical interface for conversion metadata from r.info and v.info to ISO based metadata, editing metadata files and creating metadata templates. In addition, the graphical module allows validating of INSPIRE and Basic profile.
<h2>NOTES</h2>
-For dependencies and installation instructions see
-<a href="http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support">wiki page</a>.
+For dependencies and installation instructions see <a href="http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support">wiki page</a>.
-<p>
-<em><b>Dependencies</b></em>
-<p>
-Current development of metadata management requires external libraries:
-<p>
-<ul>
-<li>OWSLib development version
+<h3>Naming of metadata files and storage</h3>
-<p>
-<em>git clone git://github.com/geopython/OWSLib.git</em>
-<br>
-<em>cd OWSLib && sudo python setup.py install</em>
-<br>
+Default location for exported metadata files is
+<i>metadata</i> directory in the map's mapset. For raster maps, the prefix
+derived from the current nomenclature is <em>cell</em>, for vector
+maps <em>vector</em>. File ends with <em>.xml</em> extension.
-<li>Jinja templates
<p>
-<em>git clone git://github.com/mitsuhiko/jinja2.git
-<br>
-<em>cd jinja2 && sudo python setup.py install</em>
-</ul>
+For example default metadata file name for vector map
+"roads" is <em>vector_roads.xml</em>.
-<h3>Naming of metadata files and storage</h3>
-The metadata product fully supports XML Default location of exported metadata uses folder “metadata”
- in GRASS Location. In case the metadata file name is not changed, the name is build from prefix
-according to characteristic of maps. For raster maps prefix is derived from current nomenclature -
-'cell' and for vector map – 'vector' by the same way. File name is derived from the the name of the
-map. Postfix-extension is '.xml'.
-<p>
-example: vector map - roads vector_roads.xml
+<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 which are not able to
+get from native GRASS metadata are filled by text
+string <tt>'$NULL'</tt>. This rule applies for both profiles.
-<p>
-<em><b>Metadata profile</b></em>
-<p>
+<h3>Creation of metadata</h3>
-The Basic profile is substituted from intersection between GRASS native metadata 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 - abstract. The Inspire profile fulfills the criteria
- of INSPIRE profile. Values which are not able to get from native GRASS metadata are filled by text string
- '$NULL'. This rule applies for both profiles.
-
-<p>
-<em><b>Creation of metadata</b></em>
-<p>
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 external metadata file.
-<ul>
-<li>Metadata map editor
+<h4>Metadata map editor </h4>
-Combo box for selection of ISO profile:
-<ul>
+The product of this editor mode is similar to product of r|v.info.iso. After selection of map, the editor convert native metadata of map to ISO based. By exported xml file is metadata editor initialized.
<li> basic
<li> inspire
-<li> load custom - this option allows to load metadata profile from file. For example in case of use of predefined template. With this selection the editor make intersection of GRASS Basic profile(all available metadata for selected map) and loaded custom profile.
-</ul>
+<li> load custom - this option allows to load metadata profile from file. For example in case of using predefined template. The intersection of GRASS Basic profile(all available metadata for selected map) and loaded custom profile will proced with this selection.
-<li> External metadata editor
-[[Image:Wxmetadata-externalEdit.png|center|150]]
-In this case to load metadata profile file and metadata file is necessary for editing. This option does not support any connection with GRASS maps metadata. Of course, it is possible to load exported metadata from the past.
-</ul>
+<h4> External metadata editor</h4>
+This editor mode allows to load own template and xml file for editing. This option does not support any connection with GRASS maps metadata.
-<em><b>Defining templates</em></b>
-<p>
-This function allows to create pattern of metadata profile. In other words it support defining fixed values to template. With using created templates, the editor does not initialize texts inputs of defined values. These attributes is able to see only in Tree Browser. Direct link on this function is multiple editing mode (see below).
+<h3>Defining templates</h3>
<p>
-
-<em><b>Usage </em></b>
+This function allows to create pattern of metadata profile. In other words it support defining fixed values to template. With using created template, the editor does not initialize texts inputs of defined values. These attributes is able to see only in Tree Browser in editor. Direct link on this function is multiple editing mode (see below).
<p>
+If check-box of metadata attribute is checked, the OWSLib object in template will be replaced by value. Unchecked attributes will not change this 'part' of the template.
+<p>
+The yellow background of text fields indicates metadata attributes, which are not possible get from GRASS map information.
-<li> If check-box of metadata attribute is checked, the OWSLib object in template will be replaced by value. Unchecked attributes will not change this 'part' of the template.
-<li> The yellow background of text fields indicates metadata attributes, which are not possible parsed from GRASS map information.
+<h3>Editing metadata of multiple map selection</h3>
-<p>
-<em><b>Editing metadata of multiple map selection</em></b>
+This option can be used by selection of multiple maps in data catalog. To use pre-defined templete for this editing mode is suitable
-<p>
-Advantages of this editing mode is in work using of defined template. This option can be used by selection of multiple maps in data catalog.
-<p>
-<em><b>Validation of metadata profile </em></b>
+<h3>Validation of metadata profile </h3>
-<p>
-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 in the inspire profile.
-<p>
+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.
-<em><b>Updating GRASS native metadata </em></b>
-<p>
-The g.gui.metadata module allows to update native GRASS metadata with using modules r.support and v.support. The intersection between ISO based metadata and r|v.support is limited by available parameters for these modules.
+<h3>Updating GRASS native metadata </h3>
+
+The g.gui.metadata module allows updating native GRASS metadata with using modules r.support and v.support. The intersection between ISO based metadata and r|v.support is limited by available parameters for these modules.
+
<h2>SEE ALSO</h2>
<em>
- <a href="v.info.iso.html">v.info.iso</a>,
- <a href="r.info.iso.html">r.info.iso</a>,
+ <a href="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>
</em>
@@ -123,7 +91,8 @@
<h2>AUTHOR</h2>
-Matej Krejci, <a href="http://geo.fsv.cvut.cz/gwiki/osgeorel">OSGeoREL</a>
+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)
Modified: grass-addons/grass7/gui/wxpython/wx.metadata/r.info.iso/r.info.iso.html
===================================================================
--- grass-addons/grass7/gui/wxpython/wx.metadata/r.info.iso/r.info.iso.html 2014-08-15 21:27:43 UTC (rev 61660)
+++ grass-addons/grass7/gui/wxpython/wx.metadata/r.info.iso/r.info.iso.html 2014-08-16 06:32:28 UTC (rev 61661)
@@ -1,6 +1,6 @@
<h2>DESCRIPTION</h2>
-<em>r.info.iso</em> creates metadata of raster maps according
+<em>r.info.iso</em> creates metadata of raster maps according
to <a href="http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020">ISO
19115</a>.
@@ -15,10 +15,6 @@
<h3>Naming of metadata files and storage</h3>
-<!--
-what does it mean?
-The metadata product fully supports XML
--->
Default location for exported metadata files is
<i>metadata</i> directory in the map's mapset. If the name for output
@@ -29,7 +25,7 @@
<p>
For example default metadata file name for raster map
-"elevation" is <em>raster_elevation.xml</em>.
+"elevation" is <em>cell_elevation.xml</em>.
<h3>Metadata profile</h3>
Modified: grass-addons/grass7/gui/wxpython/wx.metadata/v.info.iso/v.info.iso.html
===================================================================
--- grass-addons/grass7/gui/wxpython/wx.metadata/v.info.iso/v.info.iso.html 2014-08-15 21:27:43 UTC (rev 61660)
+++ grass-addons/grass7/gui/wxpython/wx.metadata/v.info.iso/v.info.iso.html 2014-08-16 06:32:28 UTC (rev 61661)
@@ -13,39 +13,20 @@
For dependencies and installation instructions see
<a href="http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support">wiki page</a>.
-<p>
-<em><b>Dependencies</b></em>
-<p>
-Current development of metadata management requires external libraries:
-<p>
-<ul>
-<li>OWSLib development version
+<h3>Naming of metadata files and storage</h3>
-<p>
-<em>git clone git://github.com/geopython/OWSLib.git</em>
-<br>
-<em>cd OWSLib && sudo python setup.py install</em>
-<br>
+Default location for exported metadata files is
+<i>metadata</i> directory in the map's mapset. If the name for output
+metadata file is not specified by <b>output</b> option than the name
+is built from map's type and its name. For raster maps, the prefix
+derived from the current nomenclature is <em>cell</em>, for vector
+maps <em>vector</em>. File ends with <em>.xml</em> extension.
-<li>Jinja templates
<p>
-<em>git clone git://github.com/mitsuhiko/jinja2.git
-<br>
-<em>cd jinja2 && sudo python setup.py install</em>
-</ul>
+For example default metadata file name for raster map
+"basins" is <em>vector_basins.xml</em>.
-<h3>Naming of metadata files and storage</h3>
-
-The metadata product fully supports XML Default location of exported metadata uses folder “metadata”
- in GRASS Location. In case the metadata file name is not changed, the name is build from prefix
-according to characteristic of maps. For raster maps prefix is derived from current nomenclature -
-'cell' and for vector map – 'vector' by the same way. File name is derived from the the name of the
-map. Postfix-extension is '.xml'.
-<p>
-example: vector map - roads vector_roads.xml
-
-
<h3>Metadata profile</h3>
The <i>basic</i> profile is substituted from intersection between
More information about the grass-commit
mailing list