Changeset 459 for trunk/docs
- Timestamp:
- Apr 1, 2014, 11:32:29 PM (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/docs/services/zcfg-reference.txt
r349 r459 131 131 A ``<LiteralData>`` node contains: 132 132 133 - one (optional) ``AllowedValues`` key containing all value allowed for this input 134 - one (optional) ``rangeMin`` (``rangeMin``) properties containing the minimum (maximum) value of this range 135 - one (optional) ``rangeSpacing`` properties containing the regular distance or spacing between value in this range 136 - one (optional) ``rangeClosure`` properties containing the closure type (``c``,``o``,``oc``,``co``) 133 137 - one ``<Default>`` node, 134 138 - zero or more ``<Supported>`` nodes depending on the existence or the number of supported Units Of Measure (UOM), and … … 159 163 </LiteralData> 160 164 165 166 A typical ``<LiteralData>`` node, defining a ``float`` data type which 167 should take values contained in ``[0.0,100.0]``, looks like the following: 168 .. code-block:: guess 169 :linenos: 170 171 <LiteralData> 172 dataType = float 173 rangeMin = 0.0 174 rangeMax = 100.0 175 rangeClosure = c 176 <Default /> 177 </LiteralData> 178 179 A typical ``<LiteralData>`` node, defining a ``string`` data type which 180 support values ``hillshade``, ``slope``, ``aspect``, ``TRI``, ``TPI`` 181 and ``roughness``, looks like the following: 182 .. code-block:: guess 183 :linenos: 184 185 <LiteralData> 186 dataType = float 187 AllowedValues = hillshade,slope,aspect,TRI,TPI,roughness 188 <Default /> 189 </LiteralData> 190 191 Properties``AllowedValues`` and ``range*`` can be conbined with both ``<Default>`` and 192 ``<Supported>`` nodes in the same ``<LiteralData>`` node. 193 161 194 .. _BoundingBoxData: 162 195
Note: See TracChangeset
for help on using the changeset viewer.