Changeset 70728
- Timestamp:
- Mar 4, 2017, 11:53:59 PM (7 years ago)
- Location:
- grass/trunk/temporal/t.register
- Files:
-
- 2 edited
-
t.register.html (modified) (12 diffs)
-
t.register.py (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
-
grass/trunk/temporal/t.register/t.register.html
r68510 r70728 3 3 The module <em>t.register</em> is designed to register raster, 3D 4 4 raster and vector maps in the temporal database and in specific space 5 time datasets . This module must be used to assign timestamps to5 time datasets (stds). This module must be used to assign timestamps to 6 6 raster, 3D raster and vector maps. The existing timestamp modules 7 7 <a href="r.timestamp.html">r.timestamp</a>, … … 13 13 database. 14 14 <p> 15 If the <em>input</em> option is not used (i.e.: no stds is provided), maps 16 will be only registered in the temporal database with assigned 17 timestamps. If, however, the <em>input</em> option 18 is used and a stds is provided, maps will be first registered in the temporal 19 database (if not registered before) and then, in the stds specified. If the 20 user wants to register maps that are already registered in the temporal 21 database in a different stds, there is no need to pass information regarding 22 start and end time, <em>t.register</em> will read timestamps from the temporal 23 database. 24 <p> 15 25 This module supports absolute and relative time. The absolute temporal type 16 26 refers to a fixed date while the relative temporal type refers to data 17 without fixed time stamps (e.g., sequential maps used to calculate27 without fixed timestamps (e.g., sequential maps used to calculate 18 28 multi-decadal averages). 19 20 <p> 21 Maps can be registered by command line argument (a list of comma separated map 29 <p> 30 Maps can be registered by command line argument (i.e.: a list of comma separated map 22 31 names) or using an input file. The start time, the end time and a temporal 23 32 increment 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 a33 increment are mutually exclusive. The user can register single maps or a 25 34 list of maps at once. Maps can be registered in several space time 26 35 datasets using the same timestamp. … … 28 37 The <em>increment</em> option and the <b>-i</b> flag (to create time intervals) 29 38 work only in conjunction with the <b>start</b> option. 30 If an input file with time stamps is used, then the <em>increment</em> option31 and the <b>-i</b> flag are not supported.39 If an input file with timestamps (either start time or start time and end time) 40 is used, then the <em>increment</em> option and the <b>-i</b> flag are not supported. 32 41 <p> 33 42 Start 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 specify35 only the date <b>yyyy-mm-dd</b>. In case of relative time the temporal43 format <b>yyyy-mm-dd HH:MM:SS +HHMM</b>. It is also supported to specify 44 only the date <b>yyyy-mm-dd</b>. In case of relative time, the temporal 36 45 unit (years, months, days, hours, minutes or seconds) must be provided. 37 The relative start time, end time and theincrement are integers.46 In this case, the relative start time, end time and increment are integers. 38 47 39 48 <h2>NOTES</h2> … … 49 58 <h2>INPUT FILE FORMAT</h2> 50 59 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: 60 There are several options to register maps by means of a file. The input file 61 consists of a list of map names, optionally along with timestamps. Each map 62 name (and timestaps if provided) should be stored in a new line in this file. 63 <p> 64 When only map names are provided, the <em>increment</em> option and the <b>-i</b> 65 flag are supported. However, when along with map names any kind of timestamp is 66 provided, as well, the <em>increment</em> option and the <b>-i</b> are no longer 67 supported. 68 <p> 69 Specification of map names only (<em>increment</em> option and <b>-i</b> flag 70 supported): 58 71 <div class="code"><pre> 59 72 terra_lst_day20020113 … … 65 78 66 79 <p> 67 Specification of map names and theabsolute start time (date) of the time68 instances , not support for <em>increment</em> option and the <b>-i</b> flag:80 Specification of map names and absolute start time (date) of the time 81 instances (no support for <em>increment</em> option nor <b>-i</b> flag): 69 82 <div class="code"><pre> 70 83 terra_lst_day20020113|2002-01-13 … … 76 89 77 90 <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:91 Specification of map names and absolute start time (datetime) of the time 92 instances (no support for <em>increment</em> option nor <b>-i</b> flag): 80 93 <div class="code"><pre> 81 94 terra_lst_day20020113|2002-01-13 10:30 … … 87 100 88 101 <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: 102 Specification 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): 92 104 <div class="code"><pre> 93 105 prec_1|2001-01-01|2001-04-01 … … 104 116 105 117 <h4>Using a text file</h4> 106 Register maps in a absolute space time dataset, creating a time interval118 Register maps in an absolute space time dataset, creating a time interval 107 119 108 120 <div class="code"><pre> … … 117 129 <h4>Using <em>g.list</em> to generate the input</h4> 118 130 119 Register maps in a absolute space time dataset, creating a time interval131 Register maps in an absolute space time dataset, creating a time interval 120 132 121 133 <div class="code"><pre> … … 129 141 In this example we create 6 raster maps that will be registered in a 130 142 single space time raster dataset named precip_abs using a monthly 131 temporal granularity. The <b>-i</b> flag generates interval time. The132 generated timestamps will be inspected using <em>r.timestamp</em> and133 <em>t.rast.list</em>. We will register an additional map with a timestamp 134 that was set with <em>r.timestamp</em>.143 temporal granularity. The <b>-i</b> flag generates time intervals of the 144 provided <em>increment</em>. The generated timestamps will be inspected 145 using <em>r.timestamp</em> and <em>t.rast.list</em>. We will register an 146 additional map with a timestamp that was set with <em>r.timestamp</em>. 135 147 136 148 <div class="code"><pre> … … 190 202 Europe based on ECA&D information. 191 203 192 Download and decompress mean temperature data from: 204 Download and decompress mean temperature data from: 193 205 <a href="http://eca.knmi.nl/download/ensembles/data/Grid_0.25deg_reg/">here</a> 194 206 by accepting their … … 214 226 # create text file with all temperature_mean rasters, one per line, 215 227 # a) using a shell script 216 for i in `seq 1 23922` ; do 228 for i in `seq 1 23922` ; do 217 229 echo temperature_mean.$i >> map_list.txt 218 230 done -
grass/trunk/temporal/t.register/t.register.py
r70357 r70728 6 6 # AUTHOR(S): Soeren Gebbert 7 7 # 8 # PURPOSE: Register raster, vector and raster3d maps in a space time datasets8 # PURPOSE: Registers raster, vector and raster3d maps in a space time dataset 9 9 # COPYRIGHT: (C) 2011-2014, Soeren Gebbert and the GRASS Development Team 10 10 # … … 16 16 17 17 #%module 18 #% description: Registers raster, vector and raster3d maps in a space time dataset s.18 #% description: Registers raster, vector and raster3d maps in a space time dataset. 19 19 #% keyword: temporal 20 20 #% keyword: map management … … 51 51 #% type: string 52 52 #% 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. 54 54 #% required: no 55 55 #% multiple: no … … 61 61 #% type: string 62 62 #% 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. 64 64 #% required: no 65 65 #% multiple: no … … 71 71 #% type: string 72 72 #% label: Time stamp unit 73 #% description: Unit must be set in case of relative time stamps73 #% description: Unit must be set in case of relative timestamps 74 74 #% required: no 75 75 #% multiple: no … … 82 82 #% type: string 83 83 #% 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 isinteger: 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) 85 85 #% required: no 86 86 #% multiple: no
Note:
See TracChangeset
for help on using the changeset viewer.
