Changeset 70728


Ignore:
Timestamp:
Mar 4, 2017, 11:53:59 PM (7 years ago)
Author:
huhabla
Message:

temporal modules t.register: Applied patch from Veronica Andreo for better documentation and spelling

Location:
grass/trunk/temporal/t.register
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • grass/trunk/temporal/t.register/t.register.html

    r68510 r70728  
    33The module <em>t.register</em> is designed to register raster, 3D
    44raster and vector maps in the temporal database and in specific space
    5 time datasets. This module must be used to assign time stamps to
     5time datasets (stds). This module must be used to assign timestamps to
    66raster, 3D raster and vector maps. The existing timestamp modules
    77<a href="r.timestamp.html">r.timestamp</a>,
     
    1313database.
    1414<p>
     15If the <em>input</em> option is not used (i.e.: no stds is provided), maps
     16will be only registered in the temporal database with assigned
     17timestamps. If, however, the <em>input</em> option
     18is used and a stds is provided, maps will be first registered in the temporal
     19database (if not registered before) and then, in the stds specified. If the
     20user wants to register maps that are already registered in the temporal
     21database in a different stds, there is no need to pass information regarding
     22start and end time, <em>t.register</em> will read timestamps from the temporal
     23database.
     24<p>
    1525This module supports absolute and relative time. The absolute temporal type
    1626refers to a fixed date while the relative temporal type refers to data
    17 without fixed time stamps (e.g., sequential maps used to calculate
     27without fixed timestamps (e.g., sequential maps used to calculate
    1828multi-decadal averages).
    19 
    20 <p>
    21 Maps can be registered by command line argument (a list of comma separated map
     29<p>
     30Maps can be registered by command line argument (i.e.: a list of comma separated map
    2231names) or using an input file. The start time, the end time and a temporal
    2332increment can be provided by command line or in the input file. End time and
    24 increment are mutual exclusive. The user can register single maps or a
     33increment are mutually exclusive. The user can register single maps or a
    2534list of maps at once. Maps can be registered in several space time
    2635datasets using the same timestamp.
     
    2837The <em>increment</em> option and the <b>-i</b> flag (to create time intervals)
    2938work only in conjunction with the <b>start</b> option.
    30 If an input file with time stamps is used, then the <em>increment</em> option
    31 and the <b>-i</b> flag are not supported.
     39If an input file with timestamps (either start time or start time and end time)
     40is used, then the <em>increment</em> option and the <b>-i</b> flag are not supported.
    3241<p>
    3342Start time and end time with absolute time must be provided using the
    34 format <b>yyyy-mm-dd HH:MM:SS +HHMM</b>. It is supported to specify
    35 only the date <b>yyyy-mm-dd</b>. In case of relative time the temporal
     43format <b>yyyy-mm-dd HH:MM:SS +HHMM</b>. It is also supported to specify
     44only the date <b>yyyy-mm-dd</b>. In case of relative time, the temporal
    3645unit (years, months, days, hours, minutes or seconds) must be provided.
    37 The relative start time, end time and the increment are integers.
     46In this case, the relative start time, end time and increment are integers.
    3847
    3948<h2>NOTES</h2>
     
    4958<h2>INPUT FILE FORMAT</h2>
    5059
    51 The input file consists of a list of map names, optionally along with time stamps.
    52 Each map name is to be stored in a row in this file.
    53 <p>
    54 There are several options to register maps, <em>increment</em> option and
    55 the <b>-i</b> flag are supported:
    56 <p>
    57 Specification of map names:
     60There are several options to register maps by means of a file. The input file
     61consists of a list of map names, optionally along with timestamps. Each map
     62name (and timestaps if provided) should be stored in a new line in this file.
     63<p>
     64When only map names are provided, the <em>increment</em> option and the <b>-i</b>
     65flag are supported. However, when along with map names any kind of timestamp is
     66provided, as well, the <em>increment</em> option and the <b>-i</b> are no longer
     67supported.
     68<p>
     69Specification of map names only (<em>increment</em> option and <b>-i</b> flag
     70supported):
    5871<div class="code"><pre>
    5972terra_lst_day20020113
     
    6578
    6679<p>
    67 Specification of map names and the absolute start time (date) of the time
    68 instances, not support for <em>increment</em> option and the <b>-i</b> flag:
     80Specification of map names and absolute start time (date) of the time
     81instances (no support for <em>increment</em> option nor <b>-i</b> flag):
    6982<div class="code"><pre>
    7083terra_lst_day20020113|2002-01-13
     
    7689
    7790<p>
    78 Specification of map names and the absolute time stamp (datetime),
    79 not support for <em>increment</em> option and the <b>-i</b> flag:
     91Specification of map names and absolute start time (datetime) of the time
     92instances (no support for <em>increment</em> option nor <b>-i</b> flag):
    8093<div class="code"><pre>
    8194terra_lst_day20020113|2002-01-13 10:30
     
    87100
    88101<p>
    89 Specification of the map name and the absolute time interval with start,
    90 not support for <em>increment</em> option and the <b>-i</b> flag:
    91 and end time:
     102Specification of map names and absolute time interval with start and end time
     103(no support for <em>increment</em> option nor <b>-i</b> flag):
    92104<div class="code"><pre>
    93105prec_1|2001-01-01|2001-04-01
     
    104116
    105117<h4>Using a text file</h4>
    106 Register maps in a absolute space time dataset, creating a time interval
     118Register maps in an absolute space time dataset, creating a time interval
    107119
    108120<div class="code"><pre>
     
    117129<h4>Using <em>g.list</em> to generate the input</h4>
    118130
    119 Register maps in a absolute space time dataset, creating a time interval
     131Register maps in an absolute space time dataset, creating a time interval
    120132
    121133<div class="code"><pre>
     
    129141In this example we create 6 raster maps that will be registered in a
    130142single space time raster dataset named precip_abs using a monthly
    131 temporal granularity. The <b>-i</b> flag generates interval time. The
    132 generated timestamps will be inspected using <em>r.timestamp</em> and
    133 <em>t.rast.list</em>. We will register an additional map with a timestamp
    134 that was set with <em>r.timestamp</em>.
     143temporal granularity. The <b>-i</b> flag generates time intervals of the
     144provided <em>increment</em>. The generated timestamps will be inspected
     145using <em>r.timestamp</em> and <em>t.rast.list</em>. We will register an
     146additional map with a timestamp that was set with <em>r.timestamp</em>.
    135147
    136148<div class="code"><pre>
     
    190202Europe based on ECA&amp;D information.
    191203
    192 Download and decompress mean temperature data from: 
     204Download and decompress mean temperature data from:
    193205<a href="http://eca.knmi.nl/download/ensembles/data/Grid_0.25deg_reg/">here</a>
    194206by accepting their
     
    214226# create text file with all temperature_mean rasters, one per line,
    215227# a) using a shell script
    216 for i in `seq 1 23922` ; do 
     228for i in `seq 1 23922` ; do
    217229    echo temperature_mean.$i &gt;&gt; map_list.txt
    218230done
  • grass/trunk/temporal/t.register/t.register.py

    r70357 r70728  
    66# AUTHOR(S):    Soeren Gebbert
    77#
    8 # PURPOSE:      Register raster, vector and raster3d maps in a space time datasets
     8# PURPOSE:      Registers raster, vector and raster3d maps in a space time dataset
    99# COPYRIGHT:    (C) 2011-2014, Soeren Gebbert and the GRASS Development Team
    1010#
     
    1616
    1717#%module
    18 #% description: Registers raster, vector and raster3d maps in a space time datasets.
     18#% description: Registers raster, vector and raster3d maps in a space time dataset.
    1919#% keyword: temporal
    2020#% keyword: map management
     
    5151#% type: string
    5252#% label: Valid start date and time of the first map
    53 #% description: Format absolute time: "yyyy-mm-dd HH:MM:SS +HHMM", relative time is of type integer).
     53#% description: Format for absolute time: "yyyy-mm-dd HH:MM:SS +HHMM", relative time is of type integer.
    5454#% required: no
    5555#% multiple: no
     
    6161#% type: string
    6262#% label: Valid end date and time of all map
    63 #% description: Format absolute time: "yyyy-mm-dd HH:MM:SS +HHMM", relative time is of type integer).
     63#% description: Format for absolute time: "yyyy-mm-dd HH:MM:SS +HHMM", relative time is of type integer.
    6464#% required: no
    6565#% multiple: no
     
    7171#% type: string
    7272#% label: Time stamp unit
    73 #% description: Unit must be set in case of relative time stamps
     73#% description: Unit must be set in case of relative timestamps
    7474#% required: no
    7575#% multiple: no
     
    8282#% type: string
    8383#% label: Time increment, works only in conjunction with start option
    84 #% description: Time increment between maps for valid time interval creation (format absolute: NNN seconds, minutes, hours, days, weeks, months, years; format relative is integer: 5)
     84#% description: Time increment between maps for creation of valid time intervals (format for absolute time: NNN seconds, minutes, hours, days, weeks, months, years; format for relative time is of type integer: 5)
    8585#% required: no
    8686#% multiple: no
Note: See TracChangeset for help on using the changeset viewer.